Table Of Contents
Release Notes for Cisco MGX 8850 Software Version 2.1.10
New Hardware Support in Release 2.1.10
New Software Features in Release 2.1.10
Automatic Response to Nativity Check
Stage 1 Command Line Interface
Upgrading to a New Software Release
Changes to the Upgrade Procedure
General Limitations and Restrictions
RPM-PR and MPLS Limitations and Restrictions
Clearing the Configuration on Redundant PXM45s
RPM-PR auto_config File Management
Using tstdelay on Feeder Trunks
Manually Responding to Nativity Checks
Documentation Correction—PNNI Feeder Configuration Quickstart
Open Anomalies for Release 2.1.10
Problems Fixed in Release 2.1.10
Open Anomalies from Release 2.1.00
Problems Fixed in Release 2.1.00
Contacting TAC by Using the Cisco TAC Website
Release Notes for Cisco MGX 8850 Software Version 2.1.10
Contents
This document contains the following sections:
Introduction
These release notes describe the system requirements, new and changed procedures, upgrade procedures, and limitations that apply to Release 2.1.10. These notes also contain Cisco support information.
System Requirements
This section describes the hardware supported in this release and the software compatibility requirements.
Hardware Supported
Table 1 lists the hardware supported in Release 2.1.10.
Hardware Compatibility Matrix
Table 2 shows which back cards can be used with each front card in Release 2.1.10.
Software Compatibility
Table 3 lists the software that is compatible for use in a switch running Release 2.1.10 software.
Table 3 Software Compatibility Matrix
The following notes provide additional compatibility information for this release:
•
MGX 2.1.10 interoperates with SES PNNI 1.0.12 plus BPX Switch Software (SWSW) 9.3.11 plus BXM MFL.
•
•
•
•
Upgrade Path
This release supports the following graceful upgrades:
•
•
•
Additional Deliverables
The SNMP MIB release for 2.1.10 is mibs2012.
New and Changed Information
This section describes new and changed features and commands in Release 2.1.10.
New Hardware Support in Release 2.1.10
The following new cards are supported by the Release 2.1.10 software:
•
•
•
•
•
•
•
Note
The following sections provide additional information on this hardware.
AXSM/B Front Cards
The AXSM/B front cards are double-height ATM service modules that use serial line traces to access the crossbar switching fabric. The AXSM/B optical modules support 1:1 module redundancy and APS. The AXSM/B provides ATM switching and line functions.
The AXSM/B cards support the following features:
•
•
•
•
•
The following describe each of the new AXSM/B front cards.
Note
AXSM-4-622/B
The AXSM-4-622/B is a four-port, OC12c/STM4 front card. The optical back cards for the AXSM-4-622/B provide 2 ports per bay for a total of 4 ports per slot. This card supports the back cards listed in Table 2.
AXSM-16-155/B
The AXSM-16-155/B is an OC3c/STM1 front card that supports both optical and electrical interfaces. The optical back cards for the AXSM-16-155/B provide 8 ports per bay for a total of 16 ports per slot. The electrical interface back card provides 4 ports per bay for a total of 8 ports per slot. The AXSM-16-155/B card supports the back cards listed in Table 2.
AXSM-16-T3E3/B
The AXSM-16-T3E3/B is a 16-port front card that supports T3 and E3 interfaces. The back cards for the AXSM-16-T3E3/B provide 8 ports per bay for a total of 16 ports per slot. This card supports the back cards listed in Table 2.
MMF-8-155-MT/B
The MMF-8-155-MT/B is an 8-port back card for the AXSM-16-155/B front card. Each port on this card uses a Multimode Fiber (MMF) optical interface and an MT connector.
SMB-4-155
The SMB-4-155 is a new back card for the new AXSM-16-155/B front card. The SMB-4-155 provides four STM1 electrical ports per bay, for a total of eight STM1 electrical ports per front card. This card is an electrical version of the OC3 SONET interface and therefore supports intracard and intercard APS.
SMFIR-8-155-LC/B
The SMFIR-8-155-LC/B is an 8-port back card for the AXSM-16-155/B front card. Each port on this card uses a Single Mode Fiber (SMF) Intermediate Reach (IR) optical interface and an LC connector.
SMFLR-8-155-LC/B
The SMFLR-8-155-LC/B is an 8-port back card for the AXSM-16-155/B front card. Each port on this card uses a Single Mode Fiber (SMF) Long Reach (LR) optical interface and an LC connector.
New Software Features in Release 2.1.10
This release supports all the features provided in Release 2.0.x, such as PXM45, AXSM, AXSM redundancy, APS, and PXM1 to PXM45 feeder, and it supports all features provided in 2.1.00. The following sections describe new software features in Release 2.1.10.
Automatic Response to Nativity Check
The nativity check feature is used during PXM45 card insertion and card resets to determine if any PXM45 cards in the chassis have been changed. If a PXM45 has been configured in an MGX 8850 switch, the backplane serial number is stored on the PXM45 front card and on the PXM45 hard disk card. If a PXM45 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 PXM45 cards are native to the chassis. If the chassis serial numbers configured on all PXM45 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 PXM45 cards. Some configuration is stored on the PXM45 front card, and some information is stored on the PXM45 hard disk card. If one or more cards are replaced, the nativity check identifies which cards are new to the switch chassis. In previous releases, the nativity check feature identified configuration mismatches, but it could not automatically resolve them. The new automatic response feature uses the nativity check results to determine which cards hold the valid configuration so that the switch can properly configure the new cards. This feature can automatically respond to most configuration mismatches, but some mismatches still require a manual response.
The following sections describe how the automatic response feature works for standalone and redundant PXM45 installations, and how to respond when the system cannot automatically resolve conflicts.
Automatic Response for Standalone PXM45 Installations
For standalone installations, the nativity check feature detects and responds to PXM45 cards as shown in Table 4.
Table 4 Automatic Response to Nativity Checks in Standalone Installations
PXM45 front card and hard disk card have not changed.
Both PXM45 cards are configured with the correct chassis serial number.
No action is required.
PXM45 front card has been replaced with an unconfigured card.
PXM45 front card is not configured and the hard disk card is configured with correct chassis serial number.
The switch builds the PXM45 front card configuration from the configuration on the hard disk.
PXM45 front card has been replaced with a previously configured front card.
PXM45 front card is not configured with the correct chassis serial number. The hard disk card is configured with correct chassis serial number.
The switch rebuilds the PXM45 front card configuration from the configuration on the hard disk.
The hard disk card has been replaced with an unconfigured card.
PXM45 front card is configured with the correct chassis serial number, but the hard disk card is not configured.
The hard disk configuration cannot be completely built from the configuration on the front card. You must manually resolve the configuration conflict as described in "Manually Responding to Nativity Checks," which appears later in these Release Notes.
The hard disk card has been replaced with a previously configured hard disk card.
PXM45 front card is configured with the correct chassis serial number, but the hard disk card is not configured with correct chassis serial number.
The hard disk configuration cannot be completely rebuilt from the configuration on the front card. You must manually resolve the configuration conflict as described in "Manually Responding to Nativity Checks," which appears later in these Release Notes.
PXM45 front card and hard disk card are replaced with unconfigured cards.
No configuration exists on either card.
There is no existing configuration to use. You must configure the switch or restore a saved configuration.
PXM45 front card and hard disk card are replaced with a set that was configured in another switch.
PXM45 front card and hard disk card are configured with matching chassis serial numbers, but the configured serial number does not match the chassis serial number.
The switch uses the configuration on the matched set.
Both PXM45 front card and hard disk card are replaced with cards that were configured in different switches.
The PXM45 front and hard disk cards are configured with chassis serial numbers that do not match each other or the backplane serial number for the switch in which they are installed.
In this scenario, you can clear the configuration stored on the PXM45 cards, restore a configuration from a saved file, or you can use the configuration stored on the hard disk. You must manually resolve the configuration conflict as described in "Manually Responding to Nativity Checks," which appears later in these Release Notes.
Automatic Response for Redundant PXM45 Installations
For redundant PXM45 installations, the nativity check is performed only on the active PXM45 card set. If an active PXM45 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 4. Table 5 shows how the nativity check is used to assign mastership to a PXM45 card set.
Stage 1 Command Line Interface
This release provides a stage 1 Command Line Interface (CLI) feature that replaces the shellcon prompt (pxm45>) used in previous releases. In previous releases, the shellcon prompt appeared during switch startup, and if a PXM45 could not complete startup, it would stop at the shellcon prompt, where the available commands used a different structure from those used in the active state.
The new stage 1 CLI feature provides a limited set of commands that are identical to those used in the active state. This makes it easier to troubleshoot problems because there are fewer commands to learn.
The prompt for the stage 1 CLI is:
nodename.7.PXM45.i>The i character in the prompt indicates that the card is in the initialized state. In this state, the only valid username is user cisco, and the password is ciscoinc. The configured usernames and passwords are not supported until the switch reaches the active state, which is indicated with an a in the prompt.
If you log in during stage 1 and the card progresses to the active or standby state, the card will log out the stage 1 user and prompt you to log in again. At this point, you must log in as a configured user with the corresponding password. The stage 1 username and password are not supported on active and standby cards.
MPLS Interface Policy
The MPLS interface feature allows you to configure the following parameters for MPLS & PNNI partitions on RPM-PR on a per service category basis:
•
•
•
•
•
For example, you can configure the UBR service category on a PNNI partition to have a guaranteed bandwidth of 50% of the partition's maximum bandwidth.
Unknown.8.PXM.a > dsppnports
Summary of total connections
(p2p=point to point,p2mp=point to multipoint,SpvcD=DAX spvc,SpvcR=Routed spvc)
Type #Svcc: #Svpc: #SpvcD: #SpvpD: #SpvcR: #SpvpR: #Total:
p2p: 0 0 0 0 0 0 0
p2mp: 0 0 0 0 0 0 0
Total= 0/50000
Summary of total configured SPVC endpoints
Type #SpvcR #SpvpR #SpvcD #SpvpD Total
p2p: 0 0 0 0 0
p2mp: 0 0 0 0 0
Total=0
Summary of total active SVC/SPVC intermediate endpoints
Type #Svcc #Svpc #SpvcR #SpvpR Total
p2p: 0 0 0 0 0
p2mp: 0 0 0 0 0
Total=0
EndPoint Grand Total = 0/100000
Per-port status summary
Type <CR> to continue, Q<CR> to stop:
PortId LogicalId IF status Admin status ILMI state #Conns
1.1 17238785 up up Undefined 0
1.2 17238786 up up Undefined 0
2.1 17240833 up up Undefined 0
7.35 17251107 up up Undefined 0
7.36 17251108 up up Undefined 0
7.37 17251109 up up Undefined 0
7.38 17251110 up up Undefined 0
Unknown.8.PXM.a > dsppnportrsrc 1.2
cbr: rt-vbr: nrt-vbr: ubr: abr: sig:Maximum Tx Cell Rate (cells/sec): 176604 176604 176604 176604 176604 176604Maximum Rx Cell Rate (cells/sec): 176604 176604 176604 176604 176604 176604Min Guarant Tx Cell Rate (cells/sec): 0 0 0 0 0 0Min Guarant Rx Cell Rate (cells/sec): 0 0 0 0 0 0Minimum Cell Loss Ratio Tx : 8 8 8 8 8 8Minimum Cell Loss Ratio Rx : 8 8 8 8 8 8Available Tx Cell Rate (cells/sec): 176604 176604 176604 176604 176604 176604Available Rx Cell Rate (cells/sec): 176604 176604 176604 176604 176604 176604# of Available Tx Channels: 253 253 253 253 253 255# of Available Rx Channels: 253 253 253 253 253 255Unknown.8.PXM.a > cnfpnportcac
Err:Mandatory IP Type argument required.
Syntax:cnfpnportcac <portid> <service_catogory>
[-bookfactor <utilization-factor>]
[-maxbw <max-bw-percent>]
[-minbw <min-bw-percent>]
[-maxvc <max-vc-percent>]
[-minvc <min-vc-percent>]
[-maxvcbw <max-vc-bw>]
shelf.slot:subslot.port:subport -- [shelf.]slot[:subslot].port[:subport] (default=Mandatory Parameter); shelf -- valid value = 0
service_category -- service_category {cbr|rtvbr|nrtvbr|abr|ubr}
bookfactor -- bookfactor (default=100)
maxbw -- maxbw (default=100)
minbw -- minbw (default=0)
maxvc -- maxvc (default=100)
minvc -- minvc (default=0)
Type <CR> to continue, Q<CR> to stop:q
Unknown.8.PXM.a > cnfpnportcac 1.2 ubr -minbw 50
WARNING:New CAC parameters apply to existing connections also
Unknown.8.PXM.a > dsppnportrsrc 1.2
cbr: rt-vbr: nrt-vbr: ubr: abr: sig:
Maximum Tx Cell Rate (cells/sec): 158944 158944 158944 176604 158944 158944
Maximum Rx Cell Rate (cells/sec): 158944 158944 158944 176604 158944 158944
Min Guarant Tx Cell Rate (cells/sec): 0 0 0 17660 0 0
Min Guarant Rx Cell Rate (cells/sec): 0 0 0 17660 0 0
Minimum Cell Loss Ratio Tx : 8 8 8 8 8 8
Minimum Cell Loss Ratio Rx : 8 8 8 8 8 8
Available Tx Cell Rate (cells/sec): 158944 158944 158944 176604 158944 158944
Available Rx Cell Rate (cells/sec): 158944 158944 158944 176604 158944 158944
# of Available Tx Channels: 253 253 253 253 253 255
# of Available Rx Channels: 253 253 253 253 253 255
Unknown.8.PXM.a > dsppnportcac 1.2
cbr: rt-vbr: nrt-vbr: ubr: abr: sig:
bookFactor: 100% 100% 100% 100% 100% 100%
maxBw: 100.0000% 100.0000% 100.0000% 100.0000% 100.0000% 100.0000%
minBw: 0.0000% 0.0000% 0.0000% 50.0000% 0.0000% 0.0000%
maxVc: 100% 100% 100% 100% 100% 100%
minVc: 0% 0% 0% 0% 0% 1%
maxVcBw: 0 0 0 0 0 0
Changed Commands
The following sections describe AXSM CLI commands that have changed in this release.
dspalm
The dspalm command has been modified to display an additional row of alarm information. For example:
APS Alarm State: MajorThe Alarm State will be same as that shown for dsplns. For non-APS lines, the alarm state is "N/A" The rest of the Alarm values shown apply to the 'Active Line'.
dspalms
The display for the dspalms commands is similar dspalm.
dspapsbkplane
This command shows whether the APS connector, which is also called the mini backplane, is plugged in properly. It should be used only when the standby card is in Ready state and APS has been configured for the card pair. When the standby card is re-booting or failed, for example, intercard APS cannot work properly and hence this command will show 'NOT ENGAGED'.
The APS connector status is for the bay specified with the dspapsbkplane command and applies to all lines in that bay. This is because an APS connector is installed in a single bay and enables APS for all lines in that bay. To provide APS to all lines for a slot, APS connectors must be installed in the upper and lower bays.
dspapsln
The dspapsln command needs to be entered with both the working line ID and the protection line ID. The 'Alarm' shown is not an integrated alarm; it is for the LineId that was entered. The 'Alarm' can show the following alarm levels:
•
•
•
•
•
•
•
The Alarm states shown are independent of the APS line cross status.'
Note
dspapslns
The dspapslns command previously reported two alarm states: OK and ALM. This command now shows the same alarm levels as the updated dspapsln command. The alarms shown are independent of the APS line cross.
dspln
The dspln command displays an 'Alarm' column that shows the integrated alarm status for the APS line pair. It only shows line level alarms. The possible levels are:
•
•
•
•
dsplns
The dsplns command displays the same alarm status as dspln.
Removed Commands
There are no commands removed from version 2.1.10.
Upgrading to a New Software Release
This section contains installation and upgrade instructions. For complete details, refer to the MGX 8850 Routing Switch Software Configuration Guide that shipped with your system. Also see the "Related Documentation" section of these notes for a list of the new documentation that supports Release 2.1.10.
Changes to the Upgrade Procedure
Before upgrading PXM45, AXSM, or RPM-PR software, disable online diagnostics if they are running (CSCdu27378). After you upgrade the software as described in the MGX 8850 Routing Switch Software Configuration Guide and in the next section, you can turn on the diagnostics.
RPM-PR Upgrades
The section provides instructions on upgrading the following RPM-PR configurations:
•
•
The procedure for upgrading 1:N redundant configurations is not included in the Cisco MGX 8850 Routing Switch Configuration Guide, Release 2.1.00 and will be added to a future revision. The procedure for upgrading non-redundant RPM-PR cards is in the Cisco MGX 8850 Routing Switch Configuration Guide, Release 2.1.00, but Cisco Systems recommends that you modify this procedure. The following sections describe these recommended procedures.
Upgrading with 1:N Redundancy
The following procedure describes how to upgrade redundant RPM-PR cards.
Note
Step 1
Tips
Step 2
mgx8850a.7.PXM.a > softswitch <fromSlot> <toSlot>This step makes the secondary card active and resets the primary RPM-PR card. When the primary card resets, it loads the upgraded software defined in Step 1.
Step 3
This step makes the upgraded primary card active and resets the secondary card. When the reset is complete, the secondary card is ready to run the upgraded software.
Step 4
Upgrading Without Redundancy
The upgrade procedure in the Cisco MGX 8850 Routing Switch Configuration Guide, Release 2.1.00 is missing one step, which is the step that configures the RPM-PR card to save the configuration on the PXM45 hard drive as well as in bootflash and NVRAM. While this step is optional, Cisco Systems recommends that you use the following procedure when upgrading non-redundant RPM-PR cards.
Step 1
boot config e:auto_config_slot#Step 2
Tips
Limitations and Restrictions
The following sections describe the following issues for this release:
•
•
General Limitations and Restrictions
The following list describes limitations and restrictions that apply to this release:
•
•
•
•
•
•
•
•
•
RPM-PR and MPLS Limitations and Restrictions
The following list describes RPM-PR and MPLS limitations and restrictions that apply to this release:
•
•
•
•
•
•
•
•
•
•
–
–
APS Management Information
The following tips apply to the use of the dspapsbkplane command and the APS connector, which is sometimes called a backplane. The APS connector must be installed to enable intercard APS.
•
•
•
•
Caution
Note
Open APS Issues
Note
The following are some open APS issues in this release:
•
•
•
APS Events to Avoid
When using APS, try to avoid the following:
•
•
If it is impossible to avoid the above, check to see if there are erroneous alarms that will not clear. If there, do the following
1.
2.
Clearing the Configuration on Redundant PXM45s
When the nativity check discovers conflicts that cannot be automatically corrected, one option is to issue a clrallcnf command to establish the PXM45 card sets as new, unconfigured cards in the chassis. Unfortunately, there is a bug (CSCdt92422) that prevents this procedure from working on redundant PXM45s. The work around is to remove one set of PXM45 cards, clear the configuration on the installed set, and then install the redundant card set so that the cards are brought up in standby mode.
Recommendations
Cisco Systems provides the following information and recommendations for switch configuration:
•
•
Important Notes
This section provides general notes that apply to this release and covers some procedures that are not in the shipping versions of the manuals.
General Notes
The following list provides general notes on using the switch.
•
•
•
•
•
•
•
•
RPM-PR and MPLS Notes
The following list provides notes on using RPM-PR cards and MPLS in this release:
•
•
•
addcon
switch connection
rpmrscprtn
switch partition
atm pvc
pvc
RPM-PR auto_config File Management
The RPM-PR auto_config_slot# file stores the configuration for the RPM-PR card. The slot# portion of the name is automatically set to the slot number that corresponds to the RPM-PR card. This file can be stored in bootflash and in the E:RPM directory on the PXM45 hard disk. The configuration is also stored in NVRAM using the name startup-config.
When the RPM-PR card starts or reboots, it searches for the configuration file in the following sequence:
•
•
•
Note
To configure the RPM-PR card to store its configuration on the PXM45 hard disk, enter a command sequence similar to the following:
RPM-PR_LA_9>enablePassword:RPM-PR_LA_9#config terminalEnter configuration commands, one per line. End with CNTL/Z.RPM-PR_LA_9(config)#boot config e:auto_config_9RPM-PR_LA_9(config)#^ZRPM-PR_LA_9#copy run startDestination filename [startup-config]?Building configuration...[OK]RPM-PR_LA_9#Be sure to use the correct slot number for your RPM-PR card in the boot command, and remember to save the configuration change with the copy run start command.
Using tstdelay on Feeder Trunks
On feeder trunks, cnfoamsegep is required for tstdelay to work. The steps are as follows on PNNI:
Step 1
Step 2
Step 3
Step 4
Manually Responding to Nativity Checks
When the nativity check discovers conflicts that cannot be automatically corrected, you can resolve the conflict by doing one of the following:
•
Guest
