Revised October 17, 2005
February 11, 2004
THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.
PXM1E - all models
Several PXM1Es, PXM45/Bs and PXM45/Cs have shipped from the factory with incorrect bootChange data configured. The incorrect bootChange information may result in the PXM not booting up.
This problem is not a hardware issue and may be corrected easily in the field.
For the purposes of this field notice and ease of explanation, the term "PXM" refers only to the following products:
PXM1E - all models
PXM1 (all models) and PXM45 (first generation ) have not exhibited this problem in the field.
PXMs may boot up from runtime files on the PXM hard drive or may boot up from a server which downloads the runtime files to the PXM. When set to boot off a server, the PXM is said to be configured for netboot.
In order to netboot, the PXM must have the path to the netboot server defined in the bootChange entry. During the manufacturing process all PXMs are programmed to netboot. After the manufacturing process, the PXM configurations are cleared, however, the bootChange data is not cleared.
The result is that when the PXM reaches the field, it will attempt to netboot from the manufacturing server. Since the server is not reachable, will try to boot off the netboot server three times and then fail.
Depending on whether the PXM is active or standby, the symptoms will differ.
If the PXM is not redundant, the MGX switch will fail to come on-line and stay in boot mode.
If the PXM is a standby PXM and the other PXM is running on-line software normally, the standby PXM will continually reset.
Workaround and Solution:
Access affected PXM Console port. If the PXM is stuck in boot mode, you will see the backup boot prompt: pxm45bkup> for PXM45/B or PXM45/C or pxm1ebkup> for PXM1E models. If the PXM may be stuck in continuous boot cycles, issue the command sysPxmRemove at the prompt. The sysFWLoad() command can be used to download firmware from active PXM.
Verify what version of software is loaded in the C:FW directory. Use the command cd C:FW followed by the command ll to observe the contents of the directory. The display may look something like:
Listing Directory .: drwxrwxrwx 1 0 0 13312 Dec 17 2003 ./ drwxrwxrwx 1 0 0 13312 Nov 13 2003 ../ -rwxrwxAwx 1 0 0 880848 Sep 25 2002 pxm45_002.000.015.002_bt. -rwxrwxAwx 1 0 0 3777644 Sep 25 2002 pxm45_002.000.015.002_mgx -rwxrwxAwx 1 0 0 2503960 Sep 25 2002 axsm_002.000.015.002.fw -rwxrwxAwx 1 0 0 630992 Sep 25 2002 axsm_002.000.015.002_bt.f
In this example, the software is 2.0.15 on an MGX equipped with a PXM45.
Use the command sysVersionSet "002.000.015.002" (include quote marks) to set the version to 2.0(15.2) software.
Note: The software version used in the sysVersionSet command must be the numeric part typed exactly as it appears in the C:FW directory.
In this example, "pxm45_002.000.015.002_mgx" is shown. However, use only 002.000.015.002 for the sysVersionSet command. For more information on sysVersionSet, see the MGX 8850 and MGX 8950 Software Configuration Guide, Release 2.1.
Issue the command reboot.
The PXM should boot up normally on the run-time image specified in the sysVersionSet command.
Note: Replacing the PXM may solve the problem, but the recovery procedure as defined above can be implemented much faster provided the user has access to the MGX Console Port. Cisco recommends implementing the field recovery described in this Workaround and Solution section.
For More Information
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:
Receive Email Notification For New Field Notices
Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.