|
|
This chapter describes the configuration changes that need to be made after a switch has been initialized, started, and configured, and you want to do any of the following:
AXSM slots must be decommissioned when you want to change the type of AXSM card that runs in the slot.
After the initial installation and configuration of the MGX 8850 switch, you can add additional cards to empty slots in the chassis. When you add a card, rather than replacing a card, you must configure the switch to recognize the new card. The following sections describe how to configure the switch to recognize new PXM45 cards and AXSM cards.
During installation, single or redundant PXM45 cards can be installed in the switch. The procedure for initializing cards after installation is described in "Initializing the Switch" in "Configuring General Switch Features."
When you add a PXM45 card to the switch, you are adding a standby PXM45 card to a switch with a single active PXM45 card.
 |
Note If you are replacing a PXM45 card that previously operated as either an active or standby card in this switch, refer to "Replacing Cards," which appears later in this chapter. |
When adding a standby PXM45 card to your switch, you need to physically install the PXM45 card and the back cards in the following order:
1. PXM Hard Drive card (PXM-HD)
2. PXM45-UI-S3 card
3. PXM45 front card
After the new standby PXM45 front and back cards are installed, the active PXM45 card will initialize the standby card set. The initialization procedure takes some time. You can verify that initialization is complete by entering the dspcd command with the standby slot number, for example, dspcd 8. If the front card state is "Standby," initialization is complete.
When you add an AXSM card to a switch, you are adding new front and back cards to a slot that is not configured for an AXSM card. The following procedure describes how to add AXSM cards to unconfigured slots.
|
Note If the slot has been previously configured for an AXSM card, you can either replace that card with a card of the same type or you can decommission the slot. If you are replacing an AXSM card that previously operated in this switch, see "Replacing AXSM Cards," which appears later in this chapter. For instructions on decommissioning a slot, see "Decommissioning an AXSM Slot," which also appears later in this chapter. |
pop20one.7.PXM.a > dspcd 14
ERR: The slot specified, has no card configured in it.
ERR: Syntax: dspcd ["slot_number"]
slot number -- optional;
Step 2 Install the ASXM card and the appropriate back cards in an unconfigured slot as described in the Cisco MGX 8850 Hardware Installation Guide.
After the new AXSM front and back cards are installed, the Fail LED on the front card flashes and none of the LEDs on the back cards are lit. If you enter the dspcds command, the card state in the display appears as Failed.
Step 3 To initialize the slot for the AXSM card, enter the following command:
mgx8850a.7.PXM.a > setrev <slot> <revision>
Replace slot with the card slot number for the new AXSM card. Replace revision with the software version number for the runtime firmware the card will use. You can find the software version number in the Release Notes for the Cisco MGX 8850, Release 2.0. To determine the version number from the runtime firmware filename, see "Determining the Firmware Version Number from Filenames," which appears in "Switch Operating Procedures."
|
Note After installation, each card should be initialized with the setrev command only once. For instructions on upgrading the software on a card, refer to "Downloading and Installing Firmware Upgrades." |
Step 4 When prompted to confirm the command and reset the card, type y and press Return.
After you confirm the command, the slot initializes, the runtime firmware loads on the AXSM card, and the card resets. Be patient, the card reset takes a couple of minutes. While the card is resetting, you can use the dspcds command to display the status of the AXSM card. If you enter the command frequently, you will see the card state change from Empty to Boot/Empty to Empty to Init/Empty and finally to Active/Active.
Step 5 To verify that the new card is running the correct firmware, enter the dspcd command with the correct slot number. The following example shows that the AXSM card in slot 10 is running firmware version 2.0(10).
pop20one.7.PXM.a > dspcd 10
pop20one System Rev: 02.00 Aug. 30, 2000 21:24:09 GMT
MGX8850 Node Alarm: CRITICAL
Slot Number: 10 Redundant Slot:
Front Card Upper Card Lower Card
---------- ---------- ----------
Inserted Card: AXSM_4OC12 SMFIR_2_OC12 SMFIR_2_OC12
Reserved Card: AXSM_4OC12 SMFIR_2_OC12 SMFIR_2_OC12
State: Active Active Active
Serial Number: SAK0342003W SBK0406002N SAK0328000L
Prim SW Rev: 2.0(10) --- ---
Sec SW Rev: 2.0(10) --- ---
Cur SW Rev: 2.0(10) --- ---
Boot FW Rev: 2.0(10) --- ---
800-level Rev:
Orderable Part#: 800-05774-06 800-05383-01 800-05383-01
CLEI Code: BAA1BADAAA BAI9ADTAAA 0
Reset Reason: On Power up
Card Alarm: NONE
Failed Reason: None
Miscellaneous Information:
Type <CR> to continue, Q<CR> to stop:
pop20one System Rev: 02.00 Aug. 30, 2000 21:24:09 GMT
MGX8850 Node Alarm: CRITICAL
Crossbar Slot Status: Present
Alarm Causes
------------
NO ALARMS
After you confirm that the AXSM card has been added and is running the correct software, you can start bringing up lines as described in n "Preparing AXSM Cards and Lines for Communication."
The following sections describe how to replace standby PXM45 cards, standalone PXM45cards, and AXSM cards.
A standby PXM45 card is the non-active card in a pair of redundant PXM45 cards. If one card fails in a pair, the other card controls the switch and the failed card becomes the standby card.
When a standby card fails, replace it immediately. As long as the active card is operating correctly, you can simply remove the failed card and replace it with a good card. When the replacement card is inserted, the active PXM45 automatically configures and updates the new card.
To verify that the new card is configured and ready for operation, enter the dspcds command at the switch prompt for the active PXM45 card. When the new front card status in the dspcds command report is standby, the new card is ready to take control if the active PXM45 card fails.
|
Note The procedure in this section assumes that an active PXM45 card is installed and operating properly. If both cards have failed, you should replace one card using the procedure in the earlier section, "Replacing Standalone PXM45 Front Cards." When one PXM45 is operating, you can use the instructions in this section to upgrade the standby PXM45. |
A standalone PXM45 card is the only PXM45 card in a switch. When the only PXM45 card in the switch fails, there is no standby card to take over and configure the replacement card. So when you replace a standalone PXM45 card, you must complete a few extra steps (over replacing standby cards) to ensure the standalone card is properly configured. To replace a standalone PXM45 card, use the following procedure.
|
Note If two PXM45 cards have failed in a switch, use the following procedure to replace the first of the two cards. When one PXM45 card is operating correctly, use the procedure in the previous section, "Replacing Standby PXM45 Cards," to replace the other card. |
Step 2 Replace the failed card with a known good card.
The card starts up and displays the following message: "SHM ALERT ALERT."
Step 3 Enter the shmFailDisplay command to display more information.
The display that appears reports that BRAM is not native. This problem is that the serial number of the replacement PXM45 card does not match the serial number of the PXM45 card it replaced; the replacement card is not "native" to the switch.
Step 4 Enter the shmFailRecoveryHelp command.
The switch prompts you to enter the shmRecoverIgRbldDisk command to ignore the nativity issue and rebuild the configuration from disk.
Step 5 Enter the shmRecoverIgRbldDisk command.
The PXM45 should restart prompt you to log in.
Step 6 Log in to the switch and use the dspcd <slotNumber> command to view the status of the new PXM45 card. When the card is operating as the active PXM45 card, this procedure is complete.
The configuration for AXSM cards is stored on the PXM45. If an AXSM front or back card fails, remove the old card and insert a new card of the same type in the same slot. The switch will automatically configure the card and start it up. If the card is a standalone card, the card will start up as an active card. If the card is part of a redundant pair, the card will start up in standby mode.
When an AXSM card is installed and configured, the configuration is associated with a specific slot number and stored on the PXM45 card. If you replace the AXSM with another card of the same type, the new card will start operating with the established configuration. Any configuration previously used on that card will be discarded because the configuration is assigned to the slot, not the physical card.
If you want to use a previously configured AXSM slot for a different type of AXSM card, you must first decommission the slot to remove the existing configuration. Otherwise, the switch will attempt to run the old configuration on the new card, and the new card will not operate correctly.
To decommission a slot, you need to remove the existing connections, partitions, and ports as described below.
Step 2 Use the cc command to select the AXSM slot you want to decommission.
|
Note The AXSM card installed in the slot you are decommissioning must be the same type of card for which the slot was configured. You cannot decommission a slot with an AXSM card type that does not match the configured card type. |
Step 3 To display the connections you need to delete, enter the following command:
mgx8850a.10.AXSM.a > dspcons
The following is a sample dspcons display.
pop20one.7.PXM.a > dspcons Local Port Vpi.Vci Remote Port Vpi.Vci State Owner ----------------------------+-----------------------------+-------+------ 10:2.2:2 100 100 Routed 100 100 FAIL MASTER Local Addr: 47.00918100000000107b65f33c.0000010a1802.00 Remote Addr: 47.009181000000002a123f213f.000001011802.00\\
Step 4 Write down the interface, VPI, and VCI numbers for each connection. You need these numbers to complete the next step.
Step 5 Delete all connections by entering the following command for each connection:
mgx8850a.10.AXSM.a > delcon <ifNum> <VPI> <VCI>
Step 6 When all connections are deleted, bring down the interface by entering the following command:
mgx8850a.10.AXSM.a > dnport <ifNum>
Step 7 To display a list showing the partitions for this card, enter the dspparts command.
Step 8 Write down the interface number and partition number for each partition on the card. You need this information to complete the next step.
Step 9 Delete all resource partitions by entering the following command for each resource partition:
mgx8850a.10.AXSM.a > delpart <ifNum> <partId>
Replace ifnum with the interface number of the port, and replace partitionID with the partition number assigned to the port.
Step 10 To verify that the partitions have been deleted, enter the dspparts command.
Step 11 To display a list showing the ports configured for this card, enter the dspports command.
Step 12 Write down the interface number for each port on the card. You need this information to complete the next step.
Step 13 Delete all ports by entering the following command for each port:
mgx8850a.10.AXSM.a > delport <ifNum> <partId>
Replace ifnum with the interface number of the port.
Step 14 To verify that the ports have been deleted, enter the dspports command.
Step 15 To display a list showing the lines that are administratively up, enter the dsplns command.
Step 16 Write down the line number for each line that is up. You need this information to complete the next step.
Step 17 Bring down all lines by entering the following command for each line:
mgx8850a.10.AXSM.a > dnln <bay.line>
Step 18 To verify that the lines have been brought down, enter the dsplns command.
When all lines have been brought down, the slot is decommissioned and you can add an AXSM card of a different type in that slot as described in "Adding AXSM Cards," which appears earlier in this chapter.
Posted: Thu Sep 14 18:55:46 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.