Document ID: 10726
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
Upgrading Firmware on Y-Redundant Cards
Upgrading Firmware on Non-Redundant Cards
NetPro Discussion Forums - Featured Conversations
Related Information
Introduction
This document describes the recommended procedures on how to upgrade non-control card firmware. Two procedures are given, one for Y-redundant cards and one for non-redundant cards. These procedures apply to the IGX, the IPX, and the BPX. These procedures do not apply to AXIS.
Prerequisites
Requirements
Readers of this document should have knowledge of these topics:
-
IGX, IPX, and BPX configuration procedures
Components Used
This document is not restricted to specific software and hardware versions.
Conventions
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
Upgrading Firmware on Y-Redundant Cards
Complete these steps:
-
Use either TFTP or the getfwrev command to get the firmware image on the node.
-
Use the dspcds command to verify the standby card slot number(s) of the card types to be upgraded. Use the command dspyred to verify that the standby cards are part of a Y-redundant pair.
Caution: The next step may take several minutes to complete. Do not
interrupt the burn process until the burn completes and the card returns to
Standby state. -
Use the burnfwrev command on the standby card.
This example shows firmware image N.E.F being burned into slot 12:
burnfwrev N.E.F 12
Caution: Do not use the burnfwrev command on
the active card of any Y-redundant pair.
Caution: Use a separate burnfwrev command for
each y-redundant standby card.
Caution: It is important that the firmware is burned one slot at a
time.
Caution: Do not use a single command or a script to burn firmware into
multiple, Y-redundant, standby cards. -
Use the dspfwrev command to monitor progress. When the burn is complete the status displays "Complete." The card automatically resets when the firmware burn operation is complete.
-
Once the card has been reset, the configuration is transferred from the controller card to the standby that was just reset. Wait a minimum of 10 minutes for this operation to be completed.
-
Use the dspcds command to verify that this card has the new firmware and is in the standby state.
-
Use the resetcd slot_num h command on the active card to switch to the card just burned, and repeat the procedure (starting with Step 2 on the new standby card).
Upgrading Firmware on Non-Redundant Cards
Caution: Burning firmware on an active card takes the target card out of
service and interrupts traffic.
Complete these steps:
-
Use either TFTP or the getfwrev command to get the firmware image on the node.
-
Use the dspcds command to verify the card slot number(s) of the card types to be upgraded. Use the dspyred command to verify that the cards are not part of a Y-redundant pair.
Caution: The next step may take several minutes to complete. Do not
interrupt the burn process until the burn completes -
Use the burnfwrev command on the card.
This example shows the firmware image N.E.F being burned into slot 12:
burnfwrev N.E.F 12
-
Use the dspfwrev command to monitor progress. The status displays "Complete" when the burn is complete. The card automatically resets when the firmware burn operation is complete.
-
Use the dspcds command to verify that this card has the new firmware.
-
Once the card resets, the configuration is transferred from the controller card to the card that was just reset. It can take up to 10 minutes for this operation to complete.
NetPro Discussion Forums - Featured Conversations
| NetPro Discussion Forums - Featured Conversations for WAN Switching |
| Network Infrastructure: WAN Routing and Switching |
Related Information
- Cisco WAN Switching Solutions - Cisco Documentation
- Guide to New Names and Colors for WAN Switching Products
- Downloads - WAN Switching Software
- Technical Support - Cisco Systems
| Updated: Oct 04, 2005 | Document ID: 10726 |
