|
|
This chapter describes the configuration changes that are needed after a switch has been initialized, started, and configured, and you want to do any of the following tasks:
Service module and SRM slots must be decommissioned when you want to change the type of card that runs in the slot.
After the initial installation and configuration of a Cisco MGX 8850 or Cisco MGX 8830 switch, you can add additional cards to empty slots in the chassis. When you add a card, as opposed to 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 PXM cards, SRM cards, and the following narrowband service modules:
During installation, single or redundant PXM1E cards can be installed in the switch. The procedure for initializing cards after installation is described in the "Initializing the Switch" section in "Configuring General Switch Features."
When you add a PXM1E card to the switch, you are adding a standby PXM card to a switch with a single active PXM1E card.
 |
Note If you are replacing a PXM1E card that previously operated as either an active or standby card in this switch, refer to the "Replacing Cards with the Same Card Type" section later in this chapter. |
When adding a standby PXM1E card to your switch, you need to physically install the PXM1E card and the back cards in the following order:
1. PXM Hard Drive card (PXM-HD)
After the new standby PXM1E front and back cards are installed, the active PXM1E 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 any new service module to a switch, you are adding new front and back cards to a slot that is not pre-configured for any card. The following procedure describes how to add service modules to unconfigured slots.
|
Note If the slot has been previously configured for a service module, you can either replace that card with a card of the same type or you can decommission the slot. If you are replacing a service module that previously operated in this switch, see the "Replacing Cards with the Same Card Type" section later in this chapter. |
|
Note This procedure applies to any of the following service modules: VISM, FRSM, CESM, and AUSM. |
Step 2 Install the service module and the appropriate back cards in an unconfigured slot as described in the Cisco MGX 8850 Hardware Installation Guide (PXM45/B and PXM1E).
After the new service module 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 service module, enter the following command:
Replace <slot> with the card slot number for the new service module. 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 Cisco MGX 8850 and MGX 8830 Software Version 3 (PXM45/B and PXM1E). To determine the version number from the runtime firmware filename, see the "Determining the Software Version Number from Filenames" section 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, see "Downloading and Installing Software 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 service module card, and the card resets. Be patient. The card reset takes a couple of minutes. While the card is resetting, you can enter the dspcds command to display the status of the service module 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 CESM card in slot 6 is running firmware version 3.1(0).
After you confirm that the service module has been added and is running the correct software, you can start bringing up lines as described in the appropriate service module software configuration guide.
When you add an SRM card to a switch, you are adding new front and back cards to a slot that is not configured for an SRM card. The following procedure describes how to add SRM cards to unconfigured slots.
|
Note If the slot has been previously configured for an SRM card, you can either replace that card with a card of the same type or you can decommission the slot. |
Step 2 Install the SRM card and the appropriate back cards in an unconfigured slot as described in the Cisco MGX 8850 Hardware Installation Guide (PXM45/B and PXM1E).
Step 3 Configure SRM communications.
When you add an RPM card to a switch, you are adding new front and back cards to a slot that is not configured for an RPM card. The following procedure describes how to add RPM cards to unconfigured slots.
|
Note If the slot has been previously configured for an RPM 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 RPM card that previously operated in this switch, see the "Replacing RPM Cards" section later in this chapter. For instructions on decommissioning a slot, see the "Decommissioning an RPM Slot" section later in this chapter. |
Step 2 Install the RPM card and the appropriate back cards in an unconfigured slot as described in the Cisco MGX 8850 Hardware Installation Guide (PXM45/B and PXM1E).
Step 3 Initialize the RPM card as described in "Initializing RPM-PR Cards."
Step 4 Verify the RPM software version level as described in the "Verifying the Software Version in Use" section in "Preparing RPM-PR Cards for Operation."
Step 5 Establish card redundancy as described in the "Establishing Redundancy Between Two RPM-PR Cards" section in "Preparing RPM-PR Cards for Operation."
Step 6 Configure RPM communications as described in the Cisco MGX 8850 Route Processor Module Installation and Configuration Guide.
This section describes how to replace cards with another card of the same type. The following sections describe how to replace the following types of cards:
PXM1E front and back cards can be replaced when the switch is operating. If a PXM1E is operating in standalone mode, all calls are interrupted until the PXM1E is replaced and operating correctly. If the switch is using redundant PXM1E cards, enter the switchcc command to ensure that the card you want to replace is operating in standby mode.
Because the PXM1E front and hard disk cards store configuration information that controls switch operation, a nativity check is performed each time a PXM1E front card or hard disk card is added or replaced. If a PXM1E has been configured in a Cisco MGX 8850 or Cisco MGX 8830 switch, the backplane serial number is stored on the PXM1E front card and on the PXM hard disk card. If a PXM1E card is inserted into a chassis or the card is reset with a command such as resetsys, the nativity check is run to determine if the PXM1E cards are native to the chassis. If the chassis serial numbers configured on all PXM1E cards match the switch chassis serial number, the cards are all native and no special action is required.
The purpose of the nativity check is to resolve configuration differences between PXM cards. Some configuration is stored on the PXM1E front card, and some information is stored on the PXM1E hard disk card. This information includes the runtime software version to be used. The actual runtime software is stored on the PXM1E hard disk.
|
Note When you replace a PXM1E card, the replacement card uses the boot software stored on the replacement card and the runtime software configured for slots 7 and 8 in the Cisco MGX 8850, or slots 1 and 2 in the Cisco MGX 8830. If the boot software stored on the replacement card is not the correct version, you should upgrade it while the card is operating in standby mode. For instructions on upgrading boot software, see to "Downloading and Installing Software Upgrades." |
If one or more cards are replaced, the nativity check identifies which cards are new to the switch chassis and uses the nativity check results to determine which cards hold the valid configuration. This feature can automatically respond to most configuration mismatches, but some mismatches do require a manual response.
When a switch cannot automatically resolve a nativity check conflict, establish a console port session through the corresponding PXM-UI-S3 card and enter the shmRecoverIgRbldDisk command. This command ignores the nativity check and configures the entire switch according to the configuration on the hard disk.
The following sections describe how the automatic response feature works for standalone and redundant PXM installations, and how to respond when the system cannot automatically resolve conflicts.
For standalone installations, the nativity check feature detects and responds to PXM1E cards as shown in Table 10-1.
Table 10-1 Automatic Response to Nativity Checks in Standalone Installations
|
For redundant PXM1E installations, the nativity check is performed only on the active PXM1E card set. If an active PXM1E card set is operating correctly, you can replace any card in the standby or non-active card set, and the active card set will attempt to configure the replacement card and bring it up in standby mode.
When the entire switch is reset, the nativity check is used to determine which card set gains mastership. The card set that gains mastership will attempt to go active and will resolve nativity conflicts as described in Table 10-1. Table 10-2 shows how the nativity check is used to assign mastership to a PXM card set.
Table 10-2 Mastership Assignment to PXM Card Sets after Nativity Check
When the nativity check discovers conflicts that cannot be automatically corrected, you can resolve the conflict by doing one of the following tasks:
If the switch cannot resolve a nativity check conflict and all the cards are operating properly, the PXM1E cards enter stage 1 CLI mode, which offers a reduced set of commands that you can use to resolve the conflict.
When operating in stage 1 CLI mode, you can FTP files to the switch in preparation for a new configuration or a configuration restore. You can FTP files to the switch using the procedures described for copying files to the switch in "Downloading and Installing Software Upgrades."
To rebuild the configuration from a configured hard disk in the switch, do the following tasks:
The switch will build the PXM1E front card configuration from the configuration on the hard disk.
If a service module front or back card fails, remove the old card and insert a new card of the same type in the same slot. If the card is a standalone card, all communications are interrupted. If the card is part of a redundant card set, you can replace the standby card without disrupting traffic through the active card.
The configuration for service modules is stored on the PXM1E. The switch automatically configures the replacement service module and starts 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.
|
Note The switch automatically selects and loads the correct runtime software for a service module based on the configuration for that slot. The switch does not automatically burn the boot code for a service module. |
|
Note To replace one type of service module front card with another type, you must delete all connections, partitions, ports and down lines. If a service module fails, the same type of service module must be installed in that slot. |
If you have properly initialized an RPM card as described in the "Initializing RPM-PR Cards" section in "Preparing RPM-PR Cards for Operation." the configuration for the RPM card is stored on the PXM45 hard disk.
To replace a standalone RPM card, 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.
|
Note RPM-PR and RPM-B cards are not interchangeable. When replacing an RPM-PR card, you must replace it with another RPM-PR card. If you want to change types of cards, you must first decommission the slot as describe in the "Decommissioning an RPM Slot" section which appears later in this chapter. |
To replace an RPM card that is configured for redundancy, first switch control to the standby card, then replace the card while it is operating in standby mode. If the card you are replacing has failed, there is no reason to switch cards, as the failure should have triggered a switch to the standby card. If you need to switch cards, enter the softswitch command as described in the "Switching Between Redundant RPM-PR Cards" section in "Switch Operating Procedures."
|
Note After you replace a card that is configured for redundancy, it starts up in standby mode. If the active card is configured to operate as a standby card for multiple RPM cards, enter a softswitch command so that the active card returns to its normal standby state. |
To decommission an RPM slot, you must remove all configuration items you configured for that card. You can do this by entering each command in the startup-config file with the key word no in front of it. These configuration items are described in the Cisco MGX 8850 Hardware Installation Guide (PXM45/B and PXM1E).
Posted: Fri Jan 23 20:43:33 PST 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.