Specifications

4-2
Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide
Release 3, Part Number 78-14788-01 Rev. C0, January 2004
Chapter 4 Preparing FRSM12 Cards and Lines for Communication
Managing Firmware Version Levels for FRSM12 Cards
Managing Firmware Version Levels for FRSM12 Cards
The FRSM12 cards within the switch run two types of firmware: boot firmware and runtime firmware.
The boot firmware provides the startup information the card needs. The boot firmware is installed on the
board at the factory. The runtime firmware controls the operation of the card after startup. The runtime
firmware file is stored on the PXM45 hard disk.
After the FRSM12 cards are installed in the switch, you must specify the correct runtime firmware
version for each card before the switch can begin using the card. The following sections explain how to
• Locate the cards that need to have the firmware version level set
• Set the firmware version levels for cards in the switch
• Verify the firmware version levels being used by cards
Locating Cards that Need the Firmware Version Set
When an FRSM12 card is installed and the firmware version needs to be set, the System Status LED on
the front of the card blinks red. The dspcds command shows that the card status is Failed. Other events
can display these symptoms, but if the FRSM12 card is new, the problem is probably that the firmware
version number has not been set. To locate the cards that need to have the firmware version set, use the
following procedure.
Step 1 Establish a CLI management session at any access level.
Step 2 To display a list of all the cards in the switch, enter the dspcds command:
8850_NY.7.PXM.a > dspcds
Step 3
addred <options>
Related commands:
dspred
Define which FRSM12 cards are operating as redundant cards.
See “Establishing Redundancy Between Two FRSM12 Cards,”
which appears later in this chapter.
Step 4
cnfcdsct <sctid>
Related commands:
dspcd
Applies communications parameters from a preconfigured
Service Class Template (SCT) file to all communications
between the card you are configuring and the other FRSM12
cards in the switch.
For PNNI communications, use SCT ID 2 or 4 for policing
applications and use SCT ID 3 or 5 for non-policing applications.
If MPLS will be used on any card link, use SCT ID 4 for policing
applications and use SCT ID 5 for non-policing applications.
See “Selecting and Viewing Service Class Templates,” which
appears later in this chapter.
Command Purpose