Downloads |
 Feedback
|
Table Of Contents
Release Notes for Cisco MGX 8950 Software Version 2.1.79
Design Guides and Application Notes
Software/Firmware Compatibility Matrix
Additional Compatibility Information
New Features and Enhancements in Release 2.1.60 through 2.1.79
Hierarchical PNNI (Multiple Peer Group [MPG])
New Features in Release 2.1.70
New Features in Release 2.1.79
Multiprotocol Label Switching (MPLS) over ATM using VC Merge
Additional Software Information
Service Class Template File Information
New Hardware Supported in Release 2.1.76
AXSM-1-2488/B (No APS support)
New Commands for the MGX 8850 Switch Only
Previously Undocumented Commands
General Limitations, Restrictions, and Notes
Limitations for rteopt via parallel links
RPM-PR and MPLS Limitations, Restrictions, and Notes
Clearing the Configuration on Redundant PXM45 Cards
Installing and Upgrading to Release 2.1.79
Quickstart Procedures for Software Upgrades
Copying Software Files to the Switch
Upgrade Procedures for PXM45 and AXSM Cards
Upgrade Procedures for RPM-PR Cards
Using XModem to Download Flash to RPM Cards
Troubleshooting Upgrade Problems
Cisco WAN Manager Release 10.5 Documentation
Cisco MGX 8850 Release 2.1 Documentation
Cisco MGX 8950 Release 2.1 Documentation
SES PNNI Release 1.1 Documentation
Cisco WAN Switching Software, Release 9.3 Documentation
MGX 8850 Multiservice Switch, Release 1.1.40 Documentation
MGX 8250 Edge Concentrator, Release 1.1.40 Documentation
MGX 8230 Multiservice Gateway, Release 1.1.40 Documentation
Documentation on the World Wide Web
Contacting TAC by Using the Cisco TAC Website
Known Anomalies in Release 2.1.79
Anomalies Resolved in Release 2.1.79
Anomalies Known in Release 2.1.76
Release Notes for Cisco MGX 8950 Software Version 2.1.79
Contents
About Release 2.1.79
These release notes describe the system requirements, new features, and limitations that apply to Release 2.1.79 for the MGX 8950 multi-service switch. These notes also contain Cisco support information.
Use this document in conjunction with the documents listed in the "Related Documentation" section.
Type of Release
Release 2.1.79 is a maintenance release for the MGX 8850 switch and a hardware and software release for the new MGX 8950 switch.
For information about the MGX 8850, see the "Release Notes for Cisco MGX 8850 Software Version 2.1.79."
About the New MGX 8950 Switch
Description
The MGX 8950 Multiservice Switch was introduced with software release 2.1.76. For your convenience, information from that release is repeated here.
The MGX 8950 switch extends the MGX family to provide backbone switching solutions for major service provider networks.
In its first release, the MGX 8950 leverages the AXSM/B card set currently available on the MGX 8850 for the service modules and the PXM-45/B for the control processor. MGX Release 2.1.76 is the first MGX software to support the MGX 8950 platform.
The MGX 8950 differs from the MGX 8850 in two major areas:
•
The MGX 8950 switch has no future narrowband support capability planned.
•
The majority of features developed in earlier releases of the MGX 8850 switch also apply to the new MGX 8950 switch. Please call Product Management for confirmation of a particular feature.
The XM-60 Switch Fabric Card
In order to increase the switching capacity of the MGX 8950 product, a new switch fabric card was developed, called the XM-60. MGX 8950 can accommodate up to four XM-60 cards, each of which provides up to 60 Gbps of raw switching capacity. MGX 8950 does not use the 45 Gbps switch on the PXM like the MGX 8850, the PXM45/Bs are used as processors and management interfaces. This physically separates the user traffic from the control traffic, an architecture designed for the highest availability. In later releases, an MGX 8950 populated with 4 XM-60 switching fabrics and OC192c/STM64 cards will allow a full-duplex 10 Gbps line rate to each slot (even if one of the XM-60s were to fail). In the first release (2.1.76), the AXSM/B cards will use the XM-60s to achieve full line rate OC48c/STM-1, just as in the MGX 8850.
Software Information
The MGX 8950 uses the same software as the MGX 8850. The initial release of software that supports MGX 8950 is Release 2.1.76. This release also supports MPLS functionality. A later release will add higher speed line cards to fully use the capacity of the XM-60s and the serial lines on the backplane.
PNNI Information
The MGX 8950 uses the same PNNI code base as the MGX 8850, and runs it on the same processor--the PXM45/B. Complete interoperability is tested, and many if not all PNNI features that are supported on the MGX 8850 are supported on MGX 8950.
MPLS Information
MPLS functionality is supported in Release 2.1.76 by using a Route Processor Module (RPM-PR). Please note that since MGX 8950 is intended to be primarily a core platform with the current release, the RPM-PR acts only as the label switch controller for the platform. Even though the RPM-PR is the same one that is supported on the MGX 8850, edge functionality is not provided on the MGX 8950 with Release 2.1.76.
CWM Information
Basic connection provisioning on MGX 8950 is supported by CWM 10.5.10.
Benefits
Network applications that will benefit from the MGX 8950 include the following:
•
•
•
Platforms/Considerations
The MGX 8950 is the high-end platform in the MGX family.
Design Guides and Application Notes
None available. See the "Related Documentation" list for additional customer documentation.
References
None available.
Limitations
•
•
Marketing Contact
Contact Hugues Metayer or David Pool in the Multiservice Switching Business Unit of Cisco.
Locating Software Updates
Software updates are located at Cisco Connection Online (CCO) at http://www.cisco.com/kobayashi/sw-center/beta
Acronyms
Table 1 lists acronyms used in these release notes.
System Requirements
This section describes software compatible with this release, and lists the hardware supported in this release.
Software/Firmware Compatibility Matrix
Table 2 lists Cisco WAN or IOS products that are interoperable with MGX Release 2.1.79.
Table 3 lists the software that is compatible for use in a switch running Release 2.1.79 software. Note that the AXSM/B cards use the same software as AXSM cards.
Table 3 MGX and RPM Software Version Compatibility Matrix
Additional Compatibility Information
The following notes provide additional compatibility information for this release:
•
•
•
•
•
•
Hardware Supported
Table 4 lists the hardware supported in Release 2.1.79. Note that the MGX 8950 does not support the AXSM/A or the new AXSM-E cards. If these cards are present, they will show up as "Failed" when the dspcds command is issued.
Hardware Compatibility Matrix
Table 5 shows which back cards can be used with each front card in Release 2.1.79 .
New and Changed Information
This section contains a summary of recent features, hardware, or commands that have been implemented in MGX 8850.
New Features and Enhancements in Release 2.1.60 through 2.1.79
Release 2.1.60 contained these new features:
•
•
•
•
•
•
•
•
•
MGX/BPX APS Interoperability
This feature verifies that the Automatic Protection Switching (APS) feature operates as described in the Telcordia GR-253 standard on both the MGX and the BPX switches.
Benefits
Cisco's multiservice customers, whose networks started out with the BPX as a backbone switch, have APS operation unchanged as their networks evolve to include the MGX 8850 and 8950 switch.
Hierarchical PNNI (Multiple Peer Group [MPG])
Hierarchical PNNI (also referred to as Multiple Peer Group PNNI) allows the growth of PNNI networks to a very large size. As a simple example, a network with two levels of hierarchy and 50 nodes in each peer group and 50 groups would have 2500 nodes. Another way to describe this is as 50 peer groups, each containing 50 nodes. Expanding the same design to 3 levels of hierarchy yields 125,000 nodes. While network topology constraints will usually limit the size to smaller numbers, the growth potential is clear.
The practical size of PNNI networks is limited by several factors, all of which use either processor real time, or memory on the node:
•
•
•
•
•
•
For complete details, refer to the "Cisco MGX and SES PNNI Network Planning Guide" (see "Related Documentation" later in these notes).
The software can support up to 10 hierarchical levels. Testing of 2.1.79 is performed for four hierarchical levels.
To prepare for the future addition of hierarchy to a PNNI network, the addressing scheme should be planned prior to the provisioning of any connections on a PNNI network. If, at any time in the future, hierarchy must be added to a network in which the addressing was not planned properly, connections will have to be re-provisioned using the new addressing scheme.
Benefits
The introduction of hierarchical PNNI enables the building of very large ATM networks. It also enables the growth of flat PNNI networks with the addition of hierarchy. Enabling hierarchy on an existing PNNI network has no impact on existing ATM connections, assuming that the addressing scheme was planned in advance to accommodate hierarchy. Since connections can be managed end-to-end across a hierarchical network, the manageability of networks can be increased in situations that previously required splitting a large network into multiple routing domains.
192 Interfaces on PXM45/B
The PXM45/B module supports up to 192 interfaces. A physical port/trunk, virtual trunk or a logical port is counted as an interface. Among 192 interfaces, up to 100 interfaces can be signaling ports. The other 92 interfaces should be non-signaling ports, such as non self-supporting ports.
Benefits
Support for 192 interfaces allows the ability to completely fill the chassis (12 slots) with broadband service module ports, e.g., AXSM-16-155/B.
UNI 4.0
MGX 8850 switches currently provide UNI signaling compliant with ATM Forum UNI 3.1 (af-uni-0010.002). This feature adds the ability to utilize the UNI 4.0 protocol when connecting to ATM UNI devices that require signaling support. Also included in this feature is support for the ITU signaling specification Q.2931.
Benefits
The UNI 4.0 signaling capability is required to provide complete and standard interoperability with UNI devices in common use. Applications enabled by the full implementation of UNI 4.0 include voice transport, connection to certain class 5 voice switching equipment, and enhanced SVC UNI services including ABR.
AINI
The ATM Inter-Network Interface (AINI) is the new inter-networking standard for PNNI to PNNI, PNNI to B-ISUP, and B-ISUP to B-ISUP internetworking. AINI provides most of the advantages of PNNI networking and allows for a secure interface that does not allow the exchange of network topology and availability information.
AINI provides a resilient interface between networks since it takes advantage of many aspects of PNNI. Despite using static routes, AINI offers crankback, alternate routes, and load balancing across multiple parallel links. Crankback is defined as a mechanism for partially releasing a connection setup in progress, which has encountered a failure. This mechanism allows PNNI to perform alternate routing.
AINI support includes:
•
•
•
•
•
•
•
•
Note
Benefits
AINI allows two or more carriers to interconnect their PNNI-based networks without exchanging topology information. It provides end-to-end provisioning and resiliency of connections. This provides a significant manageability improvement over the traditional method of interconnecting such networks using standard NNI links.
The DSL Forum has defined AINI as the preferred protocol for interconnecting ATM switches with DSLAMs. This feature allows use of the MGX 8850 in applications such as DSL, wireless, and other aggregation applications.
LDP on RPM-PR
The MPLS label distribution protocol (LDP), as standardized by the Internet Engineering Task Force (IETF) and as enabled by Cisco IOS software, allows the construction of highly scalable and flexible IP Virtual Private Networks (VPNs) that support multiple levels of services.
LDP provides a standard methodology for hop-by-hop, or dynamic label, distribution in an MPLS network by assigning labels to routes that have been chosen by the underlying Interior Gateway Protocol (IGP) routing protocols. The resulting labeled paths, called label switch paths or LSPs, forward label traffic across an MPLS backbone to particular destinations. These capabilities enable service providers to implement Cisco's MPLS-based IP VPNs and IP+ATM services across multivendor MPLS networks.
From an historical and functional standpoint, LDP is a superset of Cisco's pre-standard Tag Distribution Protocol (TDP), which also supports MPLS forwarding along normally routed paths. For those features that LDP and TDP share in common, the pattern of protocol exchanges between network routing platforms is identical. The differences between LDP and TDP for those features supported by both protocols are largely embedded in their respective implementation details, such as the encoding of protocol messages, for example.
This software release of LDP provides the means for transitioning an existing network from a TDP operating environment to an LDP operating environment. Thus, you can run LDP and TDP simultaneously on any given router platform. The routing protocol that you select can be configured on a per-interface basis for directly connected neighbors and on a per-session basis for non directly connected (targeted) neighbors. In addition, a label switch path (LSP) across an MPLS network can be supported by LDP on some hops and by TDP on other hops.
Benefits
•
•
•
Multi-LVC on RPM
This feature enables support for initiation of Multiple label switched paths (LSPs) per destination on the RPM. Different label switched paths are established for different class of services. This feature enables interface level queueing rather than per-vc level on the RPM based on MPLS class of service policy.
Benefits
Customers can deploy IP VPN services with Class of Service SLAs.
RPM 1:N Redundancy
RPM 1:N redundancy is used to switch configuration and traffic from one RPM card to another. The main benefits are:
•
•
•
switchredcd Command on RPM-PR
The MGX RPM-PR now uses the switchredcd command to change active cards. This command replaces the softswitch command that was previously used and is now obsolete.
Enter the switchredcd command to manually change the active card to the standby card. You may want to do this if you need to remove the original active card from the MGX 8850 or MGX 8950 shelf.
Note
Using switchredcd to Change the Active Card
To change the active cards, follow the steps below, in which the primary or active card in slot 2 is switched to standby or secondary, and the standby card in slot 11 is switched to primary or active.
Step 1
Unknown.7.PXM.a > switchredcd 2 11switchredcd:Do you want to proceed (Yes/No)? ywhere 2 is the active or primary card and 11 is the standby or secondary card.
The card in slot 11 is now the active RPM-PR card, and the RPM-PR card in slot 2 is reset. It comes up in standby mode after a couple of minutes.
The new active card will not revert to standby mode automatically. Enter switchredcd to manually switch over the active card back to standby mode. This is the only way the active card will switch over to standby, unless the active card fails.
Step 2
Unknown.7.PXM.a > switchredcd 11 2switchredcd:Do you want to proceed (Yes/No)? ywhere 11 is now the active card and 2 is now the standby/secondary card.
New Features in Release 2.1.70
The following features were new in release 2.1.70:
•
Config Verify
This is an off-line utility that runs on a Solaris workstation to verify the integrity of configuration files transferred from the hard disk of the MGX 8850 to the Solaris workstation. This tool helps validate uploaded configuration files.
New Features in Release 2.1.79
Release 2.1.79 was a maintenance release.
Release 2.1.76 introduced Multiprotocol Label Switching (MPLS) over ATM using virtual circuit (VC) merge.
Multiprotocol Label Switching (MPLS) over ATM using VC Merge
The virtual circuit (VC) merge facility allows a switch to aggregate multiple incoming flows with the same destination address into a single outgoing flow. Wherever VC merge occurs, several incoming labels are mapped to one single outgoing label. Cells from different virtual channel identifiers (VCIs) going to the same destination are transmitted to the same outgoing VC using multipoint-to-point connections. This sharing of labels reduces the total number of VCs required for label switching.
Without VC merge, each path consumes one label VC on each interface along the path. VC merge reduces the label space shortage by sharing labels for different flows with the same destination. Therefore, VC-Merge connections are unidirectional, and furthermore, all merged connections must be of the same service type.
Note
VC Merge is enabled by default when the MPLS over ATM network is configured and is only used when the RPM is used as an LSC (Label Switch Controller). Because it is enabled by default, the only commands necessary are:
no tag-switching atm vc-merge to disable VC Merge
and
tag-switching atm vc-merge to enable VC Merge
For more information, see MPLS Label Switch Controller and Enhancements at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftlsc.htm#xtocid15
Enhancements
The product enhancement requests (PERs) in Table 6 were included in MGX 8850 and/or MGX 8950 Releases 2.1.70 through 2.1.76. Refer to the "MGX 8850 and MGX 8950 Command Reference for Release 2.1"at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850r21/index.htm for further details about the commands mentioned in these enhancements.
Additional Software Information
MIB
The SNMP MIB release for 2.1.76 is mgxmibs2176.tar.
Service Class Template File Information
The Service Class Template (SCT) bundle in release 2.1.79 includes updates:
•
•
•
The default SCTs provided with release 2.1.79 are as follows:
AXSM and AXSM/B
•
•
•
•
AXSM-E
•
•
•
Note
New Hardware Supported in Release 2.1.76
No new hardware was introduced in release 2.1.79, however the following new hardware was supported by Release 2.1.76 software:
•
•
AXSM-1-2488/B (No APS support)
The AXSM-1-2488/B/(OC-48/STM-16) is a double-height ATM service module that uses serial line traces to access the crossbar switching fabric. It supports 1:1 module redundancy and provides ATM switching and line functions. A future software release will activate the APS capability on the AXSM-1-2488/B.
One port is supported per single-height back card (SMFSR, SMFLR)
Benefits
This card is targeted for service providers using MGX 8950 and those who prefer to use a single OC-48/STM-16 card type for both MGX 8950 and the MGX 8850.
New and Changed Commands
Before the introduction of the MGX 8950 switch, releases 2.1.60 and 2.1.70 introduced many new commands. The commands that are common to both the MGX 8850 and MGX 8950 switches are listed in "New Commands". The commands that are unique to the MGX 8850 switch are listed under "New Commands for the MGX 8850 Switch Only." There are no commands that are unique to the MGX 8950 switch.
Please refer to the "MGX 8850 and MGX 8950 Command Reference, Release 2.1" (part DOC7812563=) for details about these commands (see the "Related Documentation" section later in these notes for additional documentation that supports this release).
New Commands
Caution
The command switchredcd is new to release 2.1.79, and makes softswitch obsolete. It is used to manually change the active card to the standby card.
These commands were new in Release 2.1.60:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
These commands were new to Release 2.1.70.
•
•
•
•
•
•
•
New Commands for the MGX 8850 Switch Only
The following new commands apply only to the MGX 8850 switch:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Changed CLI Commands
There are no changed commands in this maintenance release.
This command was changed in release 2.1.79:
•
Removed Commands
These commands were removed from release 2.1.70
•
•
•
Previously Undocumented Commands
The following commands are now documented in the "MGX 8850 and MGX 8950 Command Reference, Release 2.1":
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Limitations and Restrictions
This section describes the following issues for Releases 2.1.60 through 2.1.79:
•
•
•
•
General Limitations, Restrictions, and Notes
The following limitations and restrictions apply to this release.
Note
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Limitations for rteopt via parallel links
The following are limitations for rteopt via parallel link.
link 1 . . . . . .. . . .. . . . .link 2
Node A ------------- Node B -------------- Node C
fwd & bwd aw= 500 fwd & bwd aw= 1000
-------------
link 3 fwd & bwd aw = 2000
Configuration:
•
•
•
•
Scenario 1: Link 2 is down (e.g., via dnpnport), connections are re-routed right away but Node A hasn't had that info updated in the routing tables yet.
So SPVC on Node A will have routing cost = 2*500 + 2*1000 = 3000, but since link 2 is down, Node B will choose link 3. But the routing cost on Node A SPVC is still 3000 as it did the calculation during the route search.
Now if link 2 is up, if you do rteopt on Node A, it gets the new route, the new path selected has a cost of 3000.
Since spvc has 3000, it doesn't re-route through link 2.
Scenario 2: Instead of link 2 down, if there is a crankback on link 2, the same result stated above will happen.
Scenario 3 (for CBR and VBR): link selection is set as maxavcr or maxcr or random on node B (via cnfpnni-selection) If link 2 has less bandwidth than link 3, and the link selection criteria at Node B is set to maxavcr, Node A will still put the cost as 3000 with least aw calculation, but Node B will choose link 3 (even though it is costlier) because it has more bandwidth.
Scenario 4 (for ABR and UBR): link selection doesn't apply to ABR and UBR. (via cnfpnni-selection. This is exactly the same as Scenario 3 as ABR and UBR follow load balancing on parallel links instead of choosing the minaw link.
Workaround
If you dnpnport on link 2 (connections will be routed via link 3), after uppnport on link 2, then use cnfpnni-intf to change the existing admin weight on link 2 to lesser value, e.g., 800 (from 1000).
So when optrte is executed at Node A, routing cost will be = 2*500 + 800(fwd) + 1000 (bwd) = 2800 for the new route of link 2.
Since all SPVC connections have 3000 as the routing cost, connections will be rerouted on link 2.
Important Notes
This section provides general notes that apply to this release, and covers some procedures that are not yet in the manuals.
•
•
•
•
•
•
•
•
RPM-PR and MPLS Limitations, Restrictions, and Notes
The RPM-PR and MPLS limitations and restrictions that apply to this release are as follows:
•
•
•
•
•
•
•
•
•
•
•
•
–
–
•
•
•
–
–
RPM-PR and MPLS Notes
This section contains additional notes on using RPM-PR cards and MPLS in this release:
•
•
Table 7 lists RPM commands that are different in MGX Releases 1.x and 2.x.
Table 7 RPM Commands that are Different in Releases 1 and 2
addcon
switch connection
rpmrscprtn
switch partition
atm pvc
pvc
Configuring the Cellbus Clock (CBC) Rate
When two adjacent RPM-PR cards are on the same cell bus, that is, occupy adjacent slots, the cellbus clock (CBC) rate should be set to 42MHz. If, for any reason, one of the adjacent RPM-PRs goes to Failed or Empty state, the CBC must be reconfigured to 21MHz on the active, live RPM card for Traffic Shaping to work correctly.
If the PXM puts one of the RPMs into failed state, while the RPM is functioning, the RPM must stop sending idle cells to avoid impacting traffic shaping on the remaining functional RPM.
CBC is enabled by default when the RPM is configured. Because it is enabled by default, the only commands necessary are:
rpm-auto-cbclk-change to stop the RPM from sending idle cells in the event of a failure by implementing an automatic cellbus clock change.
and
no rpm-auto-cbclk-change to keep the RPM from initiating an automatic cellbus clock change, when traffic shaping is not required.
The following screen output displays an example of the rpm-auto-cbclk-change command.
RPM-11#config terminalEnter configuration commands, one per line. End with CNTL/Z.RPM-11(config)#int sw1RPM-11(config-if)#rpm-auto-cbclk-changeRPM-11(config-if)#endRPM-11#write memBuilding configuration...[OK]RPM-11#show run int sw1Building configuration...Current configuration :142 bytes!interface Switch1no ip addressno atm ilmi-keepaliverpm-auto-cbclk-changeswitch autoSynch offend! rpm_tag_id Apr 04 2002 02:49:04RPM-11#config terminalEnter configuration commands, one per line. End with CNTL/Z.RPM-11(config)#int sw1RPM-11(config-if)#no rpm-auto-cbclk-changeRPM-11(config-if)#endRPM-11#write memBuilding configuration...[OK]RPM-11#show run int sw1Building configuration...Current configuration :145 bytes!interface Switch1no ip addressno atm ilmi-keepaliveno rpm-auto-cbclk-changeswitch autoSynch offend! rpm_tag_id Apr 04 2002 02:49:57If traffic shaping is not required, enter the no rpm-cbclk-change command, either manually or during card configuration. The following screen output displays an example of the no rpm-auto-cbclk-change command.
RPM-11#config terminalEnter configuration commands, one per line. End with CNTL/Z.RPM-11(config)#int sw1RPM-11(config-if)#no rpm-auto-cbclk-changeRPM-11(config-if)#endRPM-11#write memBuilding configuration...[OK]RPM-11#show run int sw1Building configuration...Current configuration :124 bytes!interface Switch1no ip addressno atm ilmi-keepaliveswitch autoSynch offend! rpm_tag_id Apr 04 2002 02:52:54After a reload, it would look like this:RPM-11#show run int sw1Building configuration...Current configuration :142 bytes!interface Switch1no ip addressno atm ilmi-keepaliverpm-auto-cbclk-changeswitch autoSynch offend! rpm_tag_id Apr 04 2002 02:55:03
Note
New Bypass Feature for RPM
Note
The bypass feature was new in RPM release 2.2(4)T IOS. RPM cards have a maximum storage of 128 KB for the NVRAM. This size limitation creates a problem for customers with large configurations, who find it impossible to store the configurations in the NVRAM, even with compression enabled.
In order to support storage of large configuration files, a new bypass feature was introduced in the 12.2(4)T IOS Release. With the bypass feature enabled, the enhanced "write memory" is used to bypass the NVRAM and save the configuration on:
•
•
Where"##" represents the zero-padded slot number in which the RPM card is seated in the MGX chassis.
To enable the bypass feature, issue the command rpmnvbypass from the IOS run time image—not in the IOS boot image.
To disable the bypass feature, issue the command no rpmnvbypass.
To verify that the bypass feature is either enabled or disabled, issue the show running-configuration command. If the bypass feature is enabled, rpmnvbypass is seen on the display. If it is not seen, the feature is not enabled.
Example 1 through Example 5 illustrate how the feature is enabled and disabled, and how to validate each of these actions from the configuration display.
Note
Caution
Example 1 Running configuration without the bypass feature enabled
rpm_slot02#show running-configBuilding configuration...Current configuration : 470 bytes!version 12.2service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname rpm_slot02!boot system c:rpm-js-mz.122-3.6.T1enable password cisco!ip subnet-zero!!!!interface Switch1no ip addressno atm ilmi-keepaliveswitch autoSynch off!ip classlessno ip http serverip pim bidir-enable!!snmp-server community public ROsnmp-server community private RW!!line con 0line aux 0line vty 0 4no login!endExample 2 Enable the bypass feature (rpmnvbypass)
rpm_slot02#rpm_slot02#configure terminalEnter configuration commands, one per line. End with CNTL/Z.rpm_slot02(config)#rpmnvbypassThe "boot config" statement has been (re)added to yourruning configuration. Do not remove it else risk notusing the nvbypass featurerpm_slot02(config)#endrpm_slot02#Example 3 Running configuration with bypass feature enabled (note rpmnvbypass at end of output)
rpm_slot02#show running-configBuilding configuration...Current configuration : 515 bytes!version 12.2service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname rpm_slot02!boot system c:rpm-js-mz.122-3.6.T1boot config c:auto_config_slot02 <==== Line added as per output aboveenable password cisco!ip subnet-zero!!!!interface Switch1no ip addressno atm ilmi-keepaliveswitch autoSynch off!ip classlessno ip http serverip pim bidir-enable!!snmp-server community public ROsnmp-server community private RW!!line con 0line aux 0line vty 0 4no login!rpmnvbypassendExample 4 Disable the bypass feature (no rpmnvbypass)
rpm_slot02#configure terminalEnter configuration commands, one per line. End with CNTL/Z.rpm_slot02(config)#no rpmnvbypassrpm_slot02(config)#endrpm_slot02#Example 5 Running configuration after the bypass feature is disabled
rpm_slot02#show running-configBuilding configuration...Current configuration : 503 bytes!version 12.2service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname rpm_slot02!boot system c:rpm-js-mz.122-3.6.T1boot config c:auto_config_slot02enable password cisco!ip subnet-zero!!!!interface Switch1no ip addressno atm ilmi-keepaliveswitch autoSynch off!ip classlessno ip http serverip pim bidir-enable!!snmp-server community public ROsnmp-server community private RW!!line con 0line aux 0line vty 0 4no login!endrpm_slot02#Booting the RPM-PR
Refer to chapter 5 of the "Cisco MGX Route Processor Module Installation and Configuration Guide, Release 2.1" (part DOC-7812510=) for complete details on configuring the RPM-PR cards. (See the "Documentation" section for information on how to order a printed copy of this manual or locate the manual online.) A summary of the booting and upgrading procedures is presented here for your convenience.
When the RPM-PR is booted, the boot image must be the first file in the bootflash. If the bootflash does not have a valid boot image as a first file, the card may not be able to boot and can result in bootflash corruption. If the bootflash is corrupted, you will have to send the card back for an external burn with a valid boot image.
You can reboot the RPM-PR from the PXM by entering the command resetcd <card_number> from the switch CLI, where card_number is the slot number of the RPM-PR that is being rebooted.
Note
Also, you can reboot the RPM-PR from the RPM-PR using the RPM-PR console port and entering the reload command.
Each time you turn on power to the RPM-PR, by inserting the RPM-PR into the MGX 8850 or the MGX 8950, it goes through the following boot sequence:
1.
2.
The source of the Cisco IOS image is determined by the configuration register setting. To verify this setting, you can enter either the show version or show bootvar command. (See the "Viewing the Hardware Configuration" section of the "Cisco MGX Route Processor Module Installation and Configuration Guide, Release 2.1" (part DOC-7812510=).
•
•
3.
•
•
4.
5.
If you want to load from a specific configuration file, you should enter either the boot config bootflash:<config_file> command or the boot config e:<config_file> command.
6.
The first time you boot the RPM-PR, configure the RPM-PR interfaces and save the configuration to a file in NVRAM. Then follow the procedure described in "Initializing the RPM-PR Card." For information on the Cisco IOS instructions, see Appendix C, "IOS and Configuration Basics." (The section and appendix referred to are in the "Cisco MGX Route Processor Module Installation and Configuration Guide, Release 2.1" (part DOC-7812510=).
RPM-PR Bootflash Precautions
The RPM-PR bootflash is used to store boot image, configuration and "run time" files. The Flash stores and accesses data sequentially, and the RPM-PR boot image must be the first file stored to successfully boot the card. Erasing the boot image or moving it from the first position on the Flash will cause the card to not boot.
The RPM boot image, which comes loaded on the Flash, will work for all RPM IOS images. Therefore, there is no reason to ever delete or move the factory installed boot image.
Caution
In order to avoid this unnecessary failure, requiring card servicing, you should
•
•
•
As long as the boot file remains intact in the first position on the flash, the RPM will successfully boot.
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.
The APS commands dspapsln, dspapslns, switchapsln, and dspapsbkplane were modified in release 2.1.70.
The APS command dspadjlnalm was new to release 2.1.70. Refer to the "MGX 8850 Command Reference for Release 2.1" at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850r21/index.htm for further details about the commands mentioned in these release notes.
Note
The following are some open issues in this release:
•
•
–
Preparing for Intercard APS
The following components are required for intercard APS:
•
•
•
Use the dspapsbkplane command on both the standby and active card to verify that the APS connector is plugged in properly. The following example shows the results displayed by the dspapsbkplane command when the APS connector is in place:
M8850_NY.1.AXSM.a > dspapsbkplaneLine-ID Primary Card Signal Status Secondary Card Signal StatusSlot #1 Slot #21.1 PRESENT PRESENT1.2 PRESENT ABSENT2.1 PRESENT ABSENT2.2 PRESENT ABSENTRemote Front Card : PRESENTTop Back Card : ENGAGEDBottom Back Card : ENGAGEDThe following example shows the results displayed by the dspapsbkplane command when the APS connector is not place:
M8850_LA.1.AXSM.a > dspapsbkplaneLine-ID Primary Card Signal Status Secondary Card Signal StatusSlot #1 Slot #21.1 PRESENT ABSENT1.2 ABSENT ABSENT2.1 PRESENT ABSENT2.2 ABSENT ABSENTRemote Front Card : ABSENTTop Back Card : ENGAGEDBottom Back Card : NOT-ENGAGED
Note
If the dspapsbkplane command displays the message "APS Line Pair does not exist," suspect that the APS is not configured on a line.
If the dspapsbkplane command shows different values for each of the two cards, suspect that the APS connector is seated properly on one card but not on the other.
The APS connector status is the same for all lines in a single bay because the APS connector interconnects two back cards within the same bay. You need to enter the dspapsbkplane command only once to display the APS connector status for both upper and lower bays.
Enter the dspapslns command to verify APS configuration. If the working and protection lines show OK, both lines are receiving signals from the remote note.
Managing Intercard APS Lines
In AXSM and AXSM/B intercard APS, either front card can be active, and can be connected to either APS line through the APS connector joining the two back cards. The following process describes how intercard APS communication works:
1.
2.
3.
4.
5.
6.
Note
Figure 1 shows an example of how this process operates in a standard APS configuration, where the primary card monitors the working line and the secondary card monitors the protection line.
Figure 2 shows an example of how the APS communication process operates in a crossed APS configuration, where the secondary card monitors the working line that is attached to the primary card, and the primary card monitors the protection line that is connected to the secondary card.
Figure 1
Standard APS Configuration
Figure 2
Crossed APS Configuration
Line failures are always detected at the receive end of the line. This is where a switchover occurs when a failure is detected. Two different types of switchovers can occur, depending on whether the APS was configured as unidirectional or bidirectional in the cnfapsln command:
•
•
If the status of the standby line is good, a switchover from the failed active line to the standby is automatic.
Enter the cnfapsln command to enable an automatic switchover back to the working line after it recovers from a failure, as shown in the following example:
M8850_LA.1.AXSM.a > cnfapsln -w 1.1.1 -rv 2Table 8 describes the configurable parameters for the cnfapsln command.
If you want to manually switch from one line to another, enter the switchapsln <bay> <line> <switchOption> command, as shown in the following example:
M8850_LA.1.AXSM.a > switchapsln 1 1 6Manual line switch from protection to working succeeded on line 1.1.1Table 9 describes the configurable parameters for the switchapsln command.
Enter the dspapslns command to verify that the active line switched over from the protection line to the working line, as shown in the following example:
M8850_LA.1.AXSM.a > dspapslnsWorking Prot. Conf Oper Active WLine PLine WTR Revt Conf Oper LastUserIndex Index Arch Arch Line State State (min) Dir Dir SwitchReq------- ----- ---- ----- ------ ----- ----- ----- ---- ---- ---- ----------1.1.1 2.1.1 1+1 1+1 working OK OK 5 Yes bi bi ManualP->WTroubleshooting APS Lines
Port lights on AXSM and AXSM/B front cards indicate the receive status of APS lines. The active front card always displays the status of the active line. The standby card always displays the status of the inactive line. If only one APS line fails, the line failure LED is always displayed on the standby front card.
Caution
If the active line fails and the standby line is not available, the switch reports a critical alarm.
If the active line fails and the standby line takes over, the former standby line becomes the new active line, and the switch reports a major alarm.
If an AXSM front card fails, APS communication between the redundant front cards fails. This can result in one of the following situations:
•
•
Use the following procedure to troubleshoot APS lines.
Step 1
M8850_LA.1.AXSM.a > dsplnsMedium MediumSonet Line Line Line Frame Line Line Alarm APSLine State Type Lpbk Scramble Coding Type State Enabled----- ----- ------------ ------ -------- ------ ------- ----- --------1.1 Up sonetSts12c NoLoop Enable Other ShortSMF Clear Enable1.2 Up sonetSts12c NoLoop Enable Other ShortSMF Clear Disable2.1 Up sonetSts12c NoLoop Enable Other ShortSMF Clear Disable2.2 Up sonetSts12c NoLoop Enable Other ShortSMF Clear DisableIf the line in alarm is an APS line, and has always functioned properly as an APS line, proceed to Step 2.
If the line in alarm has never functioned properly as an APS line, verify that the following are true:
•
•
•
Step 2
Table 10 Troubleshooting APS Line Problems Using the dspaps Command
Working
OK
OK
Green
Green
Active card is receiving signal on working and protection lines. This does not guarantee that transmit lines are functioning properly. You must view the status on remote switch.
Protection
SF
OK
Green
Red
Active card is receiving signal on the protection line. No signal received on the working line.
Working
OK
SF
Green
Red
Active card is receiving signal on the working line. No signal received on the protection line.
Working
SF
SF
Red
Red
Active card is not receiving signal from either line. The working line was the last line to work.
Protection
SF
SF
Red
Red
Active card is not receiving signal from either line. The protection line was the last line to work.
Working
UNAVAIL
UNAVAIL
The card set is not complete. One or more cards have failed or been removed. See Table 11 to troubleshoot card errors.
If one or both lines appear to be bad, determine whether the working or protection line is in alarm. Troubleshoot and correct the standby line first. Replace the components along the signal path until the problem is resolved.
•
•
•
Clearing the Configuration on Redundant PXM45 Cards
Due to checks to prevent an inserted card from affecting the system, an additional step may be required when inserting two "non-native" PXM45 cards in a shelf. Insert the first PXM45, do a clrallcnf, and allow this to become active before inserting the second PXM45.
Recommendations
Cisco Systems provides the following information and recommendations for switch configuration:
•
•
Installing and Upgrading to Release 2.1.79
Note
You can gracefully upgrade to Release 2.1.79 from Release 2.1.76.
The procedures in this section are based on "Appendix A, Downloading and Installing Software Upgrades" in the "MGX 8850 and MGX 8950 Switch Software Configuration Guide, Release 2.1" (part DOC-7812551=). In this section, references to "chapters" refer to chapters in that manual.
You can download that manual from http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850r21/index.htm.
Caution
This section describes how to locate, download, and install software updates for the switch. Because software updates are stored in the switch file system, this section includes a subsection on browsing the file system. This section includes the following subsections:
•
•
•
•
•
•
•
•
Upgrade Process Overview
This section provides a series of quickstart procedures that describe how to perform graceful and non-graceful upgrades to the switch. To perform a graceful upgrade on a switch card, the card must be operating in redundant mode with another switch card of the same type. When performed properly, graceful upgrades have minimal impact on connections in progress and do not interrupt any established connections.
Note
When a card to be upgraded is not operating in redundant mode, you must do a non-graceful upgrade, which disrupts all traffic that passes through the card. For PXM45 cards, an ungraceful upgrade interrupts all traffic passing through the switch. For all other types of cards, an ungraceful upgrade affects only the traffic that passes through that card.
Each type of switch card runs boot and runtime software. The recommended sequence for upgrading the software (i.e., firmware) on switch cards is as follows:
1.
2.
3.
4.
5.
6.
Note
Typically, the boot software requires less frequent upgrades. However, in this release, both the boot and runtime software need to be upgraded.
When you upgrade the software on a switch card, proceed as follows:
•
•
•
The next subsection presents the quickstart procedures for switch card software upgrades.
Quickstart Procedures for Software Upgrades
The following subsections provide quickstart procedures for the following upgrades:
•
•
•
•
•
•
•
•
Caution
Preparing for Upgrades
Before you can upgrade the software on any card, you must copy the software to your switch and then log into the switch. The following table describes how to prepare for software upgrades on any card:
Graceful PXM45 Boot Upgrades
When performed properly, graceful upgrades have minimal impact on connections in progress and do not interrupt any established connections.
When a boot software upgrade is required, the procedure for upgrading redundant PXM45 cards updates the standby card and then makes that card active. This method ensures a smooth transition to the new software and preserves all established calls. Any calls that are not established are lost.
A graceful upgrade of the boot software does the following:
1.
2.
3.
Note
To upgrade the runtime software, use the following procedure.
Step 1
Copy the boot files you want to use to the switch and log into the active PXM45 card.
Step 2
sysPxmRemove
At the backup boot prompt, enter the sysPxmRemove command: This step prevents the active card from resetting the standby card while you are working with it.
Step 3
sysFlashBootBurn "Filename"
reboot
username
password
dspcds; dsprevs
Burn the boot software. Remember to enter quotation marks before and after the boot software filename. For example:
sysFlashBootBurn "C:FW/pxm45_002.001.075.015-A_bt.fw"Step 4
username
password
Establish a CLI session with the active PXM45 card (which is the non-upgraded card) using the CP port on the UI-S3 back card and a user name with CISCO_GP privileges.
Step 5
switchcc
y
Switch the roles of the active and standby cards so you can upgrade the non-upgraded card in standby mode.
Step 6
sh
sysBackupBoot
<Return> (2.0.11 and earlier)
Using the CP port connection, change to the PXM45 Backup Boot mode.
Note that the software versions 2.0.11 and earlier require you to press Return during the reboot sequence to enter backup boot mode.
See "Changing to PXM45 Backup Boot Mode" in Appendix B, "PXM45 Backup Boot Procedures.".
Step 7
sysPxmRemove
At the backup boot prompt, enter the sysPxmRemove command: This step prevents the active card from resetting the standby card while you are working with it.
Step 8
sysFlashBootBurn "Filename"
reboot
username
password
dspcds; dsprevs
Burn the boot software. Remember to enter quotation marks before and after the boot software filename. For example:
sysFlashBootBurn "C:FW/pxm45_002.001.075.015-A_bt.fw"See "Upgrading PXM45 Boot Software" section.
The boot software is now upgraded on both the active and standby cards. The card that was active before the upgrade is now operating in standby mode.
Non-Graceful PXM45 Boot Upgrades
Ungraceful upgrades disrupt all switch traffic and are usually used in lab installations where the use of standalone cards provides no opportunity for a graceful upgrade. The quickstart procedure is provided as an overview and as a quick reference.
Note
Graceful PXM45 and AXSM Runtime Software Upgrades
When performed properly, graceful upgrades have minimal impact on connections in progress and do not interrupt any established connections.
This quickstart procedure applies to both PXM45 and AXSM cards and does the following:
1.
2.
3.
Note
Note
Note
To upgrade the runtime software, use the following procedure.
Step 1
Copy the runtime files you want to use to the switch and log into the active PXM45 card.
Step 2
dspcds; dsprevs; dsprevs -s
commitrev <slot> <revision>
Verify that all previous upgrades have been committed.
If a previous upgrade has not been committed, commit to the new upgrade.
Step 3
loadrev <slot> <revision>
dspcds; dsprevs -s
Load the new runtime software on the standby card.
Step 4
runrev <slot> <revision>
dspcds; dsprevs -s
dspcd <slot>
Switch over to the standby card and load the new runtime software on the new standby (non-upgraded) card.
Step 5
commitrev <slot> <revision>
dspcds
dsprevs
dsprevs -s
This command prevents an accidental switch back to a previous software revision if someone enters the abortrev command. Enter the commitrev command after the former active card comes up in the standby-U state. Cisco Systems recommends that you avoid configuration changes until after you have run the commitrev or abortrev commands.
See "Aborting a Runtime Software Upgrade" section and "Committing to a Runtime Software Upgrade" section.
Non-Graceful PXM45 and AXSM Runtime Software Upgrades
Ungraceful upgrades disrupt all switch traffic and are usually used in lab installations where the use of standalone cards provides no opportunity for a graceful upgrade. The quickstart procedure is provided as an overview and as a quick reference.
Note
Note
Note
Step 1
Copy the runtime files you want to use to the switch and log into the active PXM45 card.
Step 2
dspcds; dsprevs -s
commitrev <slot> <revision>
Verify that all previous upgrades have been committed.
If a previous upgrade has not been committed, commit to the new upgrade.
Step 3
loadrev <slot> <revision>
dspcds; dsprevs -s
Define the new software version to be used.
Step 4
runrev <slot> <revision>
dspcds; dsprevs -s
Reset the card and run the new runtime software version.
Step 5
commitrev <slot> <revision>
dspcds
dsprevs -s
dsprevs
This command prevents an accidental switch back to a previous software revision if someone enters the abortrev command.
Cisco Systems recommends that you avoid configuration changes until after you have run the commitrev or abortrev commands.
See "Aborting a Runtime Software Upgrade" section and "Committing to a Runtime Software Upgrade" section.
Graceful AXSM Boot Upgrades
When performed properly, graceful upgrades have minimal impact on connections in progress and do not interrupt any established connections. The quickstart procedure is provided as an overview and as a quick reference.
Note
Note
Step 1
Copy the boot files you want to use to the switch and log into the active PXM45 card.
See "Upgrade Process Overview", which appears earlier in this section.
Step 2
burnboot <slot> <revision>
dspcd <slot>
dsprevs
Burn the boot software on the standby AXSM card by specifying the slot number of the standby card.
See "Upgrading Boot Software on an AXSM Card," which appears later in this section.
Step 3
switchredcd <fromSlot> <toSlot>
Activate the upgraded card and place the non-upgraded card in standby mode.
Step 4
burnboot <slot> <revision>
dspcd <slot>
dsprevs
Burn the boot software on the non-upgraded, standby AXSM card by specifying the slot number of the standby card.
See "Upgrading Boot Software on an AXSM Card," which appears later in this section.
Non-Graceful AXSM Boot Upgrades
Ungraceful upgrades disrupt all switch traffic and are usually used in lab installations where the use of standalone cards provides no opportunity for a graceful upgrade. The quickstart procedure is provided as an overview and as a quick reference.
Note
Note
Step 1
Copy the boot files you want to use to the switch and log into the active PXM45 card.
See "Upgrade Process Overview", which appears earlier in this section.
Step 2
burnboot <slot> <revision>
dspcd <slot>
dsprevs
Burn the boot software on the standby AXSM card by specifying the slot number of the standby card.
See "Upgrading Boot Software on an AXSM Card," which appears later in this section.
RPM-PR Software Upgrades for Cards with 1:N Redundancy
On the MGX 8950, the RPM cards can go into slots 1 through 6, or 11 through 14.
The RPM-PR card supports software upgrades when 1:N redundancy is established in the switch between RPM-PR cards. Boot software is generally upgraded less often than runtime software, so be sure to compare the recommended boot software version with the boot software running on your RPMs before starting an upgrade. The correct boot software might already be installed.
The following quickstart procedure describes how to upgrade redundant RPM-PR cards. For detailed instructions, see "Upgrade Procedures for RPM-PR Cards," which appears later in this section.
These procedures describe how to upgrade boot as well as runtime software together or runtime software only.
Note
Table 12
Step 1
Copy the files you want to use to the E:RPM directory of the switch and log in your switch.
See "Upgrade Process Overview"," which appears earlier in this section.
Step 2
username
password
Establish a CLI session with the active PXM45 card using a user name at any access level.
Step 3
copy
Copy and rename the runtime file to a generic name for easy updates.
See "Non-Graceful RPM-PR Runtime Software Upgrades," which appears later in this chapter.
Note
Step 4
cc <primarySlot>
Select the slot in which the primary RPM-PR card is installed.
Step 5
enable
password
Enter Enable mode for the router.
Step 6
dir e:
Verify router access to the PXM45 hard disk and the boot upgrade software.
Step 7
show flash:
Display current contents of bootflash.
Step 8
copy filename bootflash:
dir bootflash:
Copy the upgrade boot software to flash. For example:
copy e:rpm-boot-mz_002.001.060.000 bootflash:Step 9
del bootflash:
Delete older boot files from the bootflash. The switch always attempts to load the first bootable file in bootflash. If the upgraded file has a higher file number than another bootable file, it will not be used when the card is reset.
Note
Step 10
show flash:
Caution
Step 11
squeeze flash:
This step deletes all files that have been marked for deletion.
Step 12
copy
Optional: Copy and rename the runtime file to a generic name for easy updates.
See "Non-Graceful RPM-PR Runtime Software Upgrades," which appears later in this chapter.
Note
Step 13
show bootvar
Display the current runtime software filename.
Step 14
config terminal
Enter the router global configuration mode.
Step 15
no boot system
Remove the entire boot list. To remove a single file from the boot list, include a filename. For example:
Router(config)# no boot system c:rpm-js-mz_122-4.TStep 16
boot system c:filename
Add the new router runtime image to the boot list. For example:
Router(config)# boot system c:rpm-js-mz_122-4.TStep 17
boot config e:auto_config_RPM-PR_slot#
Configure the RPM-PR card to store its configuration on the PXM45 hard disk.
Note
Step 18
^Z
Exit global configuration mode.
Step 19
copy run start
Save the new configuration.
Note
Step 20
show bootvar
Verify the change in the runtime software filename.
Step 21
switchredcd <primarySlot> <secondarySlot>
This step makes the secondary card active and resets the primary RPM-PR card. When the primary card resets, it loads the upgraded boot software from bootflash.
Step 22
cc <secondarySlot>
Select the slot in which the secondary RPM-PR card is installed.
Step 23
enable
password
dir e:
show flash:
copy filename bootflash:
dir bootflash:
show flash:
squeeze flash:Repeat Step 5 through Step 11 to move the upgraded boot software into bootflash.
Step 24
show bootvar
config terminal
no boot system
boot system c:filename
^Z
copy run start
show bootvar
Repeat Step 13 through Step 16 andStep 18 through Step 20 to upgrade runtime software.
Step 25
switchredcd <secondarySlot> <primarySlot>
This step makes the upgraded primary card active and resets the secondary RPM-PR card. When the secondary card resets, it loads the upgraded boot software from bootflash. Both primary and secondary cards should now be using upgraded boot software.
Step 26
If there are other primary RPM-PR cards that need upgrading, repeat the part of this procedure that upgrades the primary card, then execute the switchredcd command once to reload the primary card. Finally, execute the switchredcd command a second time to make the upgraded primary card active.
RPM-PR Boot Software and Runtime Software Upgrades Together
RPM-PR Runtime Software Upgrade for Cards with 1:N Redundancy (no boot software upgrade)
The RPM-PR card supports upgrades when 1:N redundancy is established in the switch between RPM-PR cards.
The following quickstart procedure describes how to gracefully upgrade redundant RPM-PR cards.
Note
Table 13
Step 1
Copy the files you want to use to the E:RPM directory of the switch and log in your switch.
See "Upgrade Process Overview"," which appears earlier in this section.
Step 2
username
password
Establish a CLI session with the active PXM45 card using a user name at any access level.
Step 3
copy
Copy and rename the runtime file to a generic name for easy updates.
See "Non-Graceful RPM-PR Runtime Software Upgrades," which appears later in this chapter.
Note
Step 4
cc <primarySlot>
Select the slot in which the primary RPM-PR card is installed.
Step 5 .
enable
password
Enter Enable mode for the router.
Step 6
show bootvar
Display the current runtime software filename.
Step 7
config terminal
Enter the router global configuration mode.
Step 8
no boot system
Remove the entire boot list. To remove a single file from the boot list, include a filename. For example:
Router(config)# no boot system c:rpm-js-mz_122-4.TStep 9
boot system c:filename
Add the new router runtime image to the boot list. For example:
Router(config)# boot system c:rpm-js-mz_122-4.TStep 10
boot config e:auto_config_RPM-PR_slot#
Configure the RPM-PR card to store its configuration on the active PXM45 hard disk.
Note
Step 11
^Z
Exit global configuration mode.
Step 12
copy run start
Save the new configuration.
Note
Step 13
show bootvar
Verify the change in the runtime software filename.
Step 14
switchredcd <primarySlot> <secondarySlot>
This step makes the secondary card active and resets the primary RPM-PR card. When the primary card resets, it loads the upgraded boot software from bootflash.
Step 15
cc <secondarySlot>
Select the slot in which the secondary RPM-PR card is installed.
Step 16
enable
password
show bootvar
config terminal
no boot system
boot system c:filename
^Z
copy run start
show bootvar
Step 17
switchredcd <secondarySlot> <primarySlot>
This step makes the upgraded primary card active and resets the secondary RPM-PR card. When the secondary card resets, it loads the upgraded boot software from bootflash. Both primary and secondary cards should now be using upgraded runtime software.
Step 18
If there are other primary RPM-PR cards that need upgrading, repeat the part of this procedure that upgrades the primary card, then execute the switchredcd command once to reload the primary card. Finally, execute the switchredcd command a second time to make the upgraded primary card active.
RPM-PR Runtime Software Upgrade (no boot upgrade)
RPM-PR Software Upgrades for Non-Redundant Cards
Use the software upgrade procedure in this subsection when you need to upgrade RPM-PR boot software and the RPM-PR is operating in standalone mode.
Note
The following quickstart procedure is provided as an overview and as a quick reference for those who have already performed RPM-PR upgrades on the switch. For detailed instructions, see "Upgrade Procedures for RPM-PR Cards," which appears later in this section.
Table 14
Step 1
ftp
Copy the boot and runtime files you want to use to the switch (E:RPM).
See "Copying Software Files to the Switch," which appears later in this section.
Step 2
username
password
Establish a CLI session with the active PXM45 card using a user name at any access level.
Step 3
copy
Copy and rename the runtime file to a generic name for easy updates.
See "Non-Graceful RPM-PR Runtime Software Upgrades," which appears later in this chapter.
Note
Step 4
cc <RPM-PR_Slot>
Select the slot in which the RPM-PR card is installed.
Step 5
enable
password
Enter Enable mode for the router.
Step 6
dir e:
Verify router access to the active PXM45 hard disk and the boot upgrade software.
Step 7
show flash:
Display current contents of bootflash.
Step 8 S
copy filename bootflash:
dir bootflash:
Copy the upgrade boot software to flash. For example:
copy e:rpm-boot-mz_002.001.075.015-A bootflash:Step 9
del bootflash:
Optional. Delete older boot files from the bootflash. This step marks files to be deleted, but it does not delete them.
Step 10
show flash:
Caution
Step 11
squeeze flash:
This step deletes all files that have been marked for deletion.
Step 12
show bootvar
Display the current runtime software filename.
Step 13
config terminal
Enter the router global configuration mode.
Step 14
no boot system
Remove the entire boot list. To remove a single file from the boot list, include a filename. For example:
Router(config)# no boot system c:rpm-js-mz_122-4.TStep 15
boot system e:filename
Add the new router runtime image to the boot list. For example:
Router(config)# boot system e:rpm-js-mz.122-4.TStep 16
boot config e:auto_config_RPM-PR_slot#
Configure the RPM-PR card to store its configuration on the PXM45 hard disk.
Note
Step 17
^Z
copy run start
Exit global configuration mode and save the new configuration.
Step 18
show bootvar
Verify the change in the runtime software filename.
Step 19
cc <active_PXM45_slot>
resetcd <RPM-PR_Slot>
This command sequence restarts the RPM-PR card with the new boot image.
RPM-PR Boot and Runtime Software Upgrade (Together)
Non-Graceful RPM-PR Runtime Software Upgrades (no boot software upgrade)
Use the software upgrade procedure in this section when you need to upgrade RPM-PR runtime software and the RPM-PR is operating in standalone mode.
Note
The following quickstart procedure is provided as an overview and as a quick reference for those who have already performed RPM-PR upgrades on the switch. For detailed instructions, see "Upgrade Procedures for RPM-PR Cards," which appears later in this section.
Table 15
Step 1
ftp
Copy the boot and runtime files you want to use to the switch (E:RPM).
See "Copying Software Files to the Switch," which appears later in this section.
Step 2
copy
Copy and rename the runtime file to a generic name for easy updates.
See "Non-Graceful RPM-PR Runtime Software Upgrades," which appears later in this chapter.
Note
Step 3
username
password
Establish a CLI session with the active PXM45 card using a user name at any access level.
Step 4
cc <RPM-PR_Slot>
Select the slot in which the RPM-PR card is installed.
Step 5
enable
password
Enter Enable mode for the router.
Step 6
show bootvar
Display the current runtime software filename.
Step 7
config terminal
Enter the router global configuration mode.
Step 8
no boot system
Remove the entire boot list. To remove a single file from the boot list, include a filename. For example:
Router(config)# no boot system c:rpm-js-mz_122-4.TStep 9
boot system e:filename
Add the new router runtime image to the boot list. For example:
Router(config)# boot system e:rpm-js-mz.122-4.TStep 10
boot config e:auto_config_RPM-PR_slot#
Configure the RPM-PR card to store its configuration on the PXM45 hard disk.
Note
Step 11
^Z
copy run start
Exit global configuration mode and save the new configuration.
Step 12
show bootvar
Verify the change in the runtime software filename.
Step 13
cc <active_PXM45_slot>
resetcd <RPM-PR_Slot>
This command sequence selects the active PXM card and restarts the RPM card with the new runtime image.
Step 14
dspcds
dspcd <RPM-PR_Slot>
cc <RPM-PR_Slot>
Verify router reboot is complete.
RPM-PR Runtime Software Upgrades (no boot software upgrade)
Browsing the File System
The active PXM45 hard disk stores log files, configuration files, and boot and runtime software. The switch operating system supports a set of UNIX-like commands that you can use to locate log files or manage software updates. Table 16 lists commands that you can use to browse the file system.
Note
Copying Software Files to the Switch
This section describes how to copy software files to the MGX 8950 switch. The switch cards use boot software and runtime software. Each PXM45 and AXSM card uses the boot software to define communications between the card components and to enable cards to start up. The runtime software defines how the card operates after startup. RPM-PR cards function on the runtime software and use the boot software only when they cannot load the runtime software.
Note
The MGX 8950 switches provide a File Transfer Protocol (FTP) service to support file transfers to the switch. If you have FTP client software and network connectivity to both the switch and the server where the software files are stored, you can use FTP to transfer files directly from the server to the switch.
Note
Step 1
Step 2
The procedure you use for transferring the files depends on the FTP client software you are using. When initiating the FTP connection, remember the following:
•
•
•
Step 3
Step 4
Note
Step 5
For more information on browsing the switch file system, see "Browsing the File System," which appears earlier in this section.
Upgrade Procedures for PXM45 and AXSM Cards
The following sections describe procedures that support upgrades to PXM45 and AXSM cards. For complete upgrade procedures, see "Quickstart Procedures for Software Upgrades," which appears earlier in this section. The procedures in this section detail some of the tasks listed in the quickstart procedures.
Upgrading PXM45 Boot Software
This section describes how to upgrade the PXM45 boot software on a single PXM45 card. If you are performing a graceful upgrade, use the quickstart procedure described in "Graceful PXM45 Boot Upgrades," which appears earlier in this section. The following procedure provides detailed information on the upgrade task within the quickstart procedure.
Step 1
Step 2
Step 3
pxm45bkup> sysFlashBootBurn "filename"Replace filename with the complete path to the boot file on the PXM45 hard drive. For example:
pxm45bkup> sysFlashBootBurn "C:FW/pxm45_002.001.075.015-A_bt.fw"Step 4
When the boot software burning process is complete, the switch displays a message similar to the following:
Flash download completed ...value = 0 = 0x0Step 5
pxm45bkup> rebootBe patient and wait for Login prompt to appear.
Step 6
M8850_NY.8.PXM.a >Step 7
M8850_NY.8.PXM.a > dsprevsM8850_NY System Rev: 02.01 Feb. 11, 2002 17:01:54 PSTMGX8850 Node Alarm: CRITICALPhysical Logical Inserted Cur Sw Boot FWSlot Slot Card Revision Revision-------- ------- -------- -------- --------01 01 AXSM_4OC12 2.1(70.202) 2.1(70.202)02 01 AXSM_4OC12 2.1(70.202) 2.1(70.202)03 03 AXSM_4OC12 2.1(70.202) 2.1(70.202)04 04 --- --- ---05 05 --- --- 2.1(70.202)06 06 --- --- 2.1(70.202)07 07 PXM45 2.1(70.202) 2.1(70.202)08 07 PXM45 2.1(70.202) 2.1(70.202)09 09 RPM_PR --- ---10 10 --- --- ---11 11 --- --- ---12 12 --- --- ---13 13 --- --- ---14 14 --- --- ---Step 8
The Boot FW Rev row in the display should show the new revision as shown in the following example:
8850_NY.7.PXM.a > dspcd8850_NY System Rev: 02.01 Mar. 04, 2001 22:47:23 PSTMGX8850 Node Alarm: NONESlot Number 7 Redundant Slot: 8Front Card Upper Card Lower Card---------- ---------- ----------Inserted Card: PXM45 UI Stratum3 PXM HardDiskDriveReserved Card: PXM45 UI Stratum3 PXM HardDiskDriveState: Active Active ActiveSerial Number: SBK050302AF SBK045203PJ SBK044602HJPrim SW Rev: 2.1(70) --- ---Sec SW Rev: 2.1(70) --- ---Cur SW Rev: 2.1(70) --- ---Boot FW Rev: 2.1(75) --- ---800-level Rev: A0 A0 A0800-level Part#: 800-06147-08 800-05787-02 800-05052-04CLEI Code: BAA670YCAA BA7IBCLAAA BA7IADNAAAReset Reason: On Power upCard Alarm: NONEFailed Reason: NoneMiscellaneous Information:Type <CR> to continue, Q<CR> to stop:After you confirm the upgrade to the first PXM45 card, the boot software upgrade for that card is complete.
Loading the Runtime Upgrade Software
This section describes how to load the runtime upgrade software in preparation for running it. Production switches should have redundant cards installed, so that upgrades can occur without interrupting traffic. For graceful upgrades, the upgrade software is loaded on the standby card first, and then the control is switched to upgraded card so that the other card can be upgraded.
The best way to assess the boot software upgrade status of a card is to enter the dsprevs command (without any parameters), as in the following example:
M8850_NY.8.PXM.a > dsprevsM8850_NY System Rev: 02.01 Feb. 11, 2002 17:14:58 PSTMGX8850 Node Alarm: CRITICALPhysical Logical Inserted Cur Sw Boot FWSlot Slot Card Revision Revision-------- ------- -------- -------- --------01 01 AXSM_4OC12 2.1(70.202) 2.1(70.202)02 01 AXSM_4OC12 2.1(70.202) 2.1(70.202)03 03 AXSM_4OC12 2.1(70.202) 2.1(70.202)04 04 --- --- ---05 05 --- --- 2.1(70.202)06 06 --- --- 2.1(70.202)07 07 PXM45 2.1(70.202) 2.1(70.202)08 07 PXM45 2.1(70.202) 2.1(70.202)09 09 RPM_PR --- ---10 10 --- --- ---11 11 --- --- ---12 12 --- --- ---13 13 --- --- ---14 14 --- --- ---The current (Cur SW Revision) software revision label indicates the status of an upgrade for runtime software. The boot (Boot FW Revision) label indicates the status of an upgrade for the boot software.To assess the runtime software upgrade status of a card, enter the dsprevs -s command. For example:
M8850_NY.8.PXM.a > dsprevs -sM8850_NY System Rev: 02.01 Feb. 11, 2002 17:10:49 PSTMGX8850 Node Alarm: CRITICALPhy. Log. Cur Sw Prim Sw Sec Sw Rev ChgSlot Slot Revision Revision Revision Status---- ---- -------- -------- -------- -------01 01 2.1(70.202) 2.1(70.202) 2.1(70.202) ---02 01 2.1(70.202) 2.1(70.202) 2.1(70.202) ---03 03 2.1(70.202) 2.1(70.202) 2.1(70.202) ---04 04 --- --- --- ---05 05 --- 2.1(70.79)P1 2.1(70.79)P1 ---06 06 --- 2.1(70.79)P1 2.1(70.79)P1 ---07 07 2.1(70.202) 2.1(70.202) 2.1(70.202) ---08 07 2.1(70.202) 2.1(70.202) 2.1(70.202) ---09 09 --- --- --- ---10 10 --- --- --- ---11 11 --- --- --- ---12 12 --- --- --- ---13 13 --- --- --- ---14 14 --- --- --- ---The current (Cur SW Revision), primary (Prim SW Revision), and secondary (Sec SW Revision) runtime software revision labels indicate the status of an upgrade for runtime software. In this example, these numbers match because the software upgrade has not started.
The primary software revision indicates which revision a card will run if it becomes active, and the secondary revision indicates an alternate revision that the card will use if the abortrev command is entered. (For more information on aborting an upgrade, see "Aborting a Runtime Software Upgrade," which appears later in this section.) The current software revision represents the software the active card is using. During a runtime upgrade, the Rev Change Status column shows when the revision command is in progress and subsequently when it is done.
The normal sequence of commands for a runtime software upgrade is loadrev, runrev, and commitrev. Table 17 shows how the software revision levels change during a graceful runtime software upgrade. Software Versions Reported During Graceful Upgrades
For non-graceful upgrades, the load process defines the software version to which the switch is about to be upgraded. Table 18 shows how the revision levels change during a non-graceful upgrade.
If you are performing a graceful upgrade, use the quickstart procedure described in "Graceful PXM45 and AXSM Runtime Software Upgrades," which appears earlier in this section. The following procedure provides detailed information on the load task within the quickstart procedure.
Step 1
mgx8950a.7.PXM.a > loadrev <slot> <revision>Replace <slot> with the card slot number for the card to be upgraded, and replace <revision> with the software version number for the update. For graceful upgrades, you can specify either the active or the standby card. The switch software will automatically load the upgrade runtime software on the standby card when it is installed. The following example shows how to enter this command:
mgx8950a.7.PXM.a > loadrev 7 2.1(75)After you enter the loadrev command, the standby card comes up in the standby-U state.
You can find the software version number in Table 3. You can also determine the version number from the runtime software filename as described in "Determining the Software Version Number from Filenames," which appears in Chapter 7, "Switch Operating Procedures."
Step 2
Step 3
M8850_NY.8.PXM.a > dsprevs -sM8850_NY System Rev: 02.01 Feb. 11, 2002 01:16:26 PSTMGX8850 Node Alarm: CRITICALPhy. Log. Cur Sw Prim Sw Sec Sw Rev ChgSlot Slot Revision Revision Revision Status---- ---- -------- -------- -------- -------01 01 2.1(70.202) 2.1(70.202) 2.1(70.202) ---02 01 2.1(70.202) 2.1(70.202) 2.1(70.202) ---03 03 2.1(70.202) 2.1(70.202) 2.1(70.202) ---04 04 --- --- --- ---05 05 --- 2.1(70.79)P1 2.1(70.79)P1 ---06 06 --- 2.1(70.79)P1 2.1(70.79)P1 ---07 07 2.1(70.202) 2.1(70.202) 2.1(70.202) ---08 07 2.1(70.202) 2.1(70.202) 2.1(70.202) ---09 09 --- --- --- ---10 10 --- --- --- ---11 11 --- --- --- ---12 12 --- --- --- ---13 13 --- --- --- ---14 14 --- --- --- ---
Note
Activating the Upgraded Runtime Software
After you load the upgraded runtime software for a PXM45 or AXSM card, enter the runrev command to start using the software. The version levels for graceful and non-graceful upgrades change as shown earlier in Table 17 and Table 18. The following procedure describes how to activate the upgraded runtime software.
Step 1
mgx8950a.7.PXM.a > runrev <slot> <revision>Replace <slot> with the card slot number, and replace <revision> with the software version number specified with the loadrev command. For graceful upgrades, you can specify either the active or the standby card. The switch software will automatically run the upgrade runtime software on the standby card when it is installed. The following example shows how to enter this command:
mgx8950a.7.PXM.a > runrev 7 2.1(75)The active card is reset, and the former standby card comes up in the active-U state.
Step 2
Step 3
M8850_NY.8.PXM.a > dsprevs -sM8850_NY System Rev: 02.01 Feb. 11, 2002 01:16:26 PSTMGX8850 Node Alarm: CRITICALPhy. Log. Cur Sw Prim Sw Sec Sw Rev ChgSlot Slot Revision Revision Revision Status---- ---- -------- -------- -------- -------01 01 2.1(70.202) 2.1(70.202) 2.1(70.202) ---02 01 2.1(70.202) 2.1(70.202) 2.1(70.202) ---03 03 2.1(70.202) 2.1(70.202) 2.1(70.202) ---04 04 --- --- --- ---05 05 --- 2.1(70.79)P1 2.1(70.79)P1 ---06 06 --- 2.1(70.79)P1 2.1(70.79)P1 ---07 07 2.1(70.202) 2.1(70.202) 2.1(70.202) ---08 07 2.1(70.202) 2.1(70.202) 2.1(70.202) ---09 09 --- --- --- ---10 10 --- --- --- ---11 11 --- --- --- ---12 12 --- --- --- ---13 13 --- --- --- ---14 14 --- --- --- ---Step 4
After the runrev command is entered, the switch starts running the new runtime software revision. The secondary software revision shows that a previous revision is still available. Whenever the secondary runtime software revision is different from the primary and current runtime software revisions, you can revert back to the secondary software revision as described in "Aborting a Runtime Software Upgrade," which appears later in this section.
Upgrading Boot Software on an AXSM Card
Note
The upgrade procedure for the boot software on a single AXSM card is the same for graceful and non-graceful upgrades. The difference between the graceful and non-graceful boot software upgrades is the sequence of commands before and after the upgrade on a single card. For information on the proper sequence see "Graceful AXSM Boot Upgrades" or "Non-Graceful AXSM Boot Upgrades," both of which appear earlier in this section.
To upgrade the boot software, use the following procedure.
Step 1
Step 2
Step 3
mgx8950a.7.PXM.a > burnboot <slot> <revision>Replace <slot> with the slot number of a standalone AXSM card or an AXSM card operating in standby mode. Replace <revision> with the software revision number to which you are upgrading. For example:
mgx8950a.7.PXM.a > burnboot 1 2.1(75)Step 4
After you confirm the upgrade, the new boot software is burned into the AXSM card and the card is reset. Be patient, the card reset takes some time. You can use the dsprevs command to display the status of the AXSM card. At first, the status may show that the card slot is empty or the card is rebooting. Reenter the command periodically to see the current status of the card. When the card status returns to active or standby, you are ready to continue.
M8850_NY.8.PXM.a > dsprevsM8850_NY System Rev: 02.01 Feb. 11, 2002 17:14:58 PSTMGX8850 Node Alarm: CRITICALPhysical Logical Inserted Cur Sw Boot FWSlot Slot Card Revision Revision-------- ------- -------- -------- --------01 01 AXSM_4OC12 2.1(70.202) 2.1(70.202)02 01 AXSM_4OC12 2.1(70.202) 2.1(70.202)03 03 AXSM_4OC12 2.1(70.202) 2.1(70.202)04 04 --- --- ---05 05 --- --- 2.1(70.202)06 06 --- --- 2.1(70.202)07 07 PXM45 2.1(70.202) 2.1(70.202)08 07 PXM45 2.1(70.202) 2.1(70.202)09 09 RPM_PR --- ---10 10 --- --- ---11 11 --- --- ---12 12 --- --- ---13 13 --- --- ---14 14 --- --- ---M8850_NY.8.PXM.a >Step 5
After you confirm the boot software upgrade to the AXSM card, the boot software upgrade for that card is complete.
Aborting a Runtime Software Upgrade
After upgrading PXM45 or AXSM runtime software, you can revert to the previously used version of software at any time, as long as you have not committed to the new software version with the commitrev command (which is described in the next section).
Note
To revert to the previously used runtime software version, use the following procedure.
Step 1
Step 2
M8850_NY.8.PXM.a > dsprevs -sM8850_NY System Rev: 02.01 Feb. 11, 2002 01:16:26 PSTMGX8850 Node Alarm: CRITICALPhy. Log. Cur Sw Prim Sw Sec Sw Rev ChgSlot Slot Revision Revision Revision Status---- ---- -------- -------- -------- -------01 01 2.1(70.202) 2.1(70.202) 2.1(70.202) ---02 01 2.1(70.202) 2.1(70.202) 2.1(70.202) ---03 03 2.1(70.202) 2.1(70.202) 2.1(70.202) ---04 04 --- --- --- ---05 05 --- 2.1(70.79)P1 2.1(70.79)P1 ---06 06 --- 2.1(70.79)P1 2.1(70.79)P1 ---07 07 2.1(70.202) 2.1(70.202) 2.1(70.202) ---08 07 2.1(70.202) 2.1(70.202) 2.1(70.202) ---09 09 --- --- --- ---10 10 --- --- --- ---11 11 --- --- --- ---12 12 --- --- --- ---13 13 --- --- --- ---14 14 --- --- --- ---To complete the next step, you need to know the secondary software revision shown in the display.
Note
Step 3
mgx8950a.7.PXM.a > abortrev <slot> <revision>Replace <slot> with the card slot number for the active PXM45 or AXSM card, and replace <revision> with the software version number for the secondary software revision.
Step 4
M8850_NY.8.PXM.a > dsprevs -sM8850_NY System Rev: 02.01 Feb. 11, 2002 01:16:26 PSTMGX8850 Node Alarm: CRITICALPhy. Log. Cur Sw Prim Sw Sec Sw Rev ChgSlot Slot Revision Revision Revision Status---- ---- -------- -------- -------- -------01 01 2.1(70.202) 2.1(70.202) 2.1(70.202) ---02 01 2.1(70.202) 2.1(70.202) 2.1(70.202) ---03 03 2.1(70.202) 2.1(70.202) 2.1(70.202) ---04 04 --- --- --- ---05 05 --- 2.1(70.79)P1 2.1(70.79)P1 ---06 06 --- 2.1(70.79)P1 2.1(70.79)P1 ---07 07 2.1(70.202) 2.1(70.202) 2.1(70.202) ---08 07 2.1(70.202) 2.1(70.202) 2.1(70.202) ---09 09 --- --- --- ---10 10 --- --- --- ---11 11 --- --- --- ---12 12 --- --- --- ---13 13 --- --- --- ---14 14 --- --- --- ---
Committing to a Runtime Software Upgrade
Committing to an upgrade does the following:
•
•
Once you are sure that an upgrade is stable, you can use the commitrev command to commit that software version. This prevents other administrators from inadvertently reverting to the previous version. You must also commit the current software version before you can upgrade to another software version or other additional cards.
Note
To commit the currently running runtime software version, use the following procedure:
Step 1
Step 2
a.
b.
M8850_NY.8.PXM.a > dsprevs -sM8850_NY System Rev: 02.01 Feb. 11, 2002 01:16:26 PSTMGX8850 Node Alarm: CRITICALPhy. Log. Cur Sw Prim Sw Sec Sw Rev ChgSlot Slot Revision Revision Revision Status---- ---- -------- -------- -------- -------01 01 2.1(70.202) 2.1(70.202) 2.1(70.202) ---02 01 2.1(70.202) 2.1(70.202) 2.1(70.202) ---03 03 2.1(70.202) 2.1(70.202) 2.1(70.202) ---04 04 --- --- --- ---05 05 --- 2.1(70.79)P1 2.1(70.79)P1 ---06 06 --- 2.1(70.79)P1 2.1(70.79)P1 ---07 07 2.1(70.202) 2.1(70.202) 2.1(70.202) ---08 07 2.1(70.202) 2.1(70.202) 2.1(70.202) ---09 09 --- --- --- ---10 10 --- --- --- ---11 11 --- --- --- ---12 12 --- --- --- ---13 13 --- --- --- ---14 14 --- --- --- ---c.
If all version numbers are identical, the runtime software can be upgraded. There is no need to commit to the current software revision.
Step 3
mgx8950a.7.PXM.a > commitrev <slot> <revision>Replace <slot> with the card slot number for the active PXM45 or AXSM card, and replace <revision> with the software version number for the currently used software version. To display the software version numbers, use the dsprevs -s command to view the software version in use.
M8850_NY.8.PXM.a > dsprevs -sM8850_NY System Rev: 02.01 Feb. 11, 2002 01:16:26 PSTMGX8850 Node Alarm: CRITICALPhy. Log. Cur Sw Prim Sw Sec Sw Rev ChgSlot Slot Revision Revision Revision Status---- ---- -------- -------- -------- -------01 01 2.1(70.202) 2.1(70.202) 2.1(70.202) ---02 01 2.1(70.202) 2.1(70.202) 2.1(70.202) ---03 03 2.1(70.202) 2.1(70.202) 2.1(70.202) ---04 04 --- --- --- ---05 05 --- 2.1(70.79)P1 2.1(70.79)P1 ---06 06 --- 2.1(70.79)P1 2.1(70.79)P1 ---07 07 2.1(70.202) 2.1(70.202) 2.1(70.202) ---08 07 2.1(70.202) 2.1(70.202) 2.1(70.202) ---09 09 --- --- --- ---10 10 --- --- --- ---11 11 --- --- --- ---12 12 --- --- --- ---13 13 --- --- --- ---14 14 --- --- --- ---
Note
Upgrade Procedures for RPM-PR Cards
The following sections describe how to upgrade boot and runtime software on RPM-PR cards in detail.
Please read "RPM-PR and MPLS Limitations, Restrictions, and Notes" section.
Upgrading RPM Boot Software
At the factory, a boot file is installed in the bootflash on the RPM-PR card and is used to boot the card. The runtime software is updated more frequently than the boot software. However, the boot software is updated occasionally. When you are \updating runtime software, check Table 3 to see if a boot software upgrade is required.
The boot software is stored in bootflash memory on the RPM card. To manage the software in bootflash, you access it as if it were a hard disk. For example, in copy and delete file commands, files are identified as bootflash:filename (which is similar to e:filename).
The following example shows a directory of bootflash contents:
Router(boot)#show flash:-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name1 .D config D4F7352A 40330 18 686 Jan 30 2001 18:18:41 auto_config_slot092 .D config CBF007C1 40660 9 688 Feb 22 2001 15:33:11 slot9.cnf3 .. image F596869A 2973E8 27 2452744 Feb 28 2001 03:16:05 rpm-boot-mz_002.001.070.202
Note
In the example above, the numbers in the left column indicate the order in which the RPM-PR card will try to load software. The second column shows that the first two files are marked for deletion (D). The last column lists the names of the files stored in bootflash.
When managing the bootflash, you need to keep in mind the following:
•
•
Caution
Upgrading RPM Runtime Software
The runtime software on the RPM can be loaded from the following sources:
•
•
•
Cisco Systems recommends that you configure the RPM card to load from the E:RPM directory on the PXM45 hard disk. Note that images will load much faster from bootflash, but if you are using multiple RPM cards, it takes longer to complete an upgrade because the runtime software must be copied to each RPM card's bootflash instead of to a single location.
At startup, the RPM card attempts to load the software in the order listed in the startup-config file. The following example shows an excerpt from a startup-config file:
!boot system e:rpm-js-mz_122-4.Tboot system bootflash:rpm-js-mz_122-4.Tboot config c:auto_config_slot09logging rate-limit console 10 except errorsenable password cisco!In the startup-config file example, the RPM card attempts to load the runtime software from the PXM45 card (E:rpm-js-mz_122-4.T) first, and if that fails, it attempts to load the image copy stored in bootflash. This configuration takes longer to upgrade, but it assures the card can reboot if someone accidentally removes the file on the PXM45 hard disk.
Note
To configure the RPM to load upgraded runtime software from the PXM45 hard disk, you need to do the following:
•
•
•
RPM-PR cards can be configured for 1:N redundancy as well as for non-redundant configurations. The procedures for both types of configuration are in the sections that follow.
Tips
Upgrade Procedure for Boot Software and Runtime Software for Non-Redundant Cards
The following procedure describes how to upgrade boot software and runtime software.
Note
Step 1
Step 2
Step 3
pop20two.7.PXM.a > cc 9(session redirected)Router>The switch displays the IOS prompt for the router on the RPM-PR card. From this point on, all commands are Cisco IOS commands.
Note
Step 4
Router>enablePassword:Router#Step 5
Router#dir e:Directory of c:/65539 -rw- 815 Sep 13 2001 23:51:10 auto_config_slot0965540 -rw- 2588780 Mar 22 2001 19:06:54 rpm-boot-mz_002.001.070.20184611 -rw- 2452768 Apr 05 2001 05:34:44 rpm-boot-mz.122-4.T66805 -rw- 8529104 Mar 22 2001 19:09:00 rpm-js-mz_002.001.070.20185809 -rw- 7936012 Apr 05 2001 06:28:54 rpm-js-mz.122-4.T104857600 bytes total (83068928 bytes free)Step 6
Router#show flash:-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name1 .. image F596869A 296D88 27 2452744 Feb 28 2001 03:16:05 rpm-boot-mz_002.001.070.20130315128 bytes available (2452872 bytes used)Step 7
Router#copy c:rpm-boot-mz_122-4T bootflash:Destination filename [rpm-boot-mz_122-4T]?CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCC2334044 bytes copied in 35.768 secs (66686 bytes/sec)
Tips
Step 8
Step 9
Router#del bootflash:Delete filename []? rpm-js-mzDelete bootflash:rpm-js-mz? [confirm]Router#
Tips
Step 10
Router(boot)#squeeze flash:All deleted files will be removed. Continue? [confirm]ySqueeze operation may take a while. Continue? [confirm]Squeeze of bootflash completeStep 11
Caution
Tips
Tips
Once in rommon mode, you can enter the dir bootflash: command to display the images in bootflash. To boot one of the images, enter a boot command the following format: boot bootflash:filename.
See Using XModem to Download Flash to RPM Cards.This ends the boot software upgrade procedure. The following steps are for upgrading the runtime software. If you do not want to upgrade the runtime software, you need to restart the RPM card by entering the reload command.
Step 12
Step 13
Step 14
8950_LA.8.PXM.a > copy rpm-js-mz_122-4.T rpm-js-mzStep 15
Step 16
pop20two.7.PXM.a > cc 9(session redirected)Router>The switch displays the IOS prompt for the router on the RPM-PR card. From this point on, all commands are Cisco IOS commands.
Note
Step 17
Router>enablePassword:Router#Step 18
Router# boot config e:auto_config_slot#Step 19
Router#show bootvarBOOT variable = e:rpm-js-mz_122-4.T,12;CONFIG_FILE variable = c:auto_config_slot09BOOTLDR variable does not existConfiguration register is 0x2In the example above, the startup runtime software file is E:rpm-js-mz_122-4.T, and it has a version number attached to it. Another way to view the boot list is to enter the show startup-config command and look for the boot system commands.
Step 20
Router#config terminalEnter configuration commands, one per line. End with CNTL/Z.Step 21
Router(config)# no boot systemStep 22
Router(config)# boot system e:filenameReplace the filename variable with the name of the new runtime file that was previously transferred to the E:RPM directory on the switch. For example:
Router(config)# boot system e:rpm-js-mzIf you want to enter additional boot system commands, enter them in the order in which you want the RPM card to use them. The following example adds a statement to load from bootflash if the runtime file is not found on the PXM45 hard disk:
Router(config)# boot system bootflash:rpm-js-mz_122-4.T
Note
Step 23
Router(config)#^ZRouter#copy run startDestination filename [startup-config]?Building configuration...[OK]Step 24
Step 25
Router#cc 8(session redirected)8950_LA.8.PXM.a > resetcd 9The card in slot number 9, will be reset. Please confirm actionresetcd: Do you want to proceed (Yes/No)? yUpgrading RPM-PR Boot Software and Runtime Software for 1:N Redundancy
Redundancy must be established before you use the procedure in this section. If redundancy has not been established, upgrade each RPM-PR card using the procedure in the next section, "Upgrading Without Redundancy".
To upgrade the RPM-PR runtime software for 1:N redundancy, use the following procedure. (Note that the directory on the PXM45 card uses (E:) and the directory within the router card uses (e:).)
The following procedure describes how to upgrade boot software and runtime software.
Note
Step 1
Step 2
Step 3
pop20two.7.PXM.a > cc 9(session redirected)Router>The switch displays the IOS prompt for the router on the RPM-PR card. From this point on, all commands are Cisco IOS commands.
Note
Step 4
Router>enablePassword:Router#Step 5
Router#dir e:Directory of c:/65539 -rw- 815 Sep 13 2001 23:51:10 auto_config_slot0965540 -rw- 2588780 Mar 22 2001 19:06:54 rpm-boot-mz_002.001.070.20184611 -rw- 2452768 Apr 05 2001 05:34:44 rpm-boot-mz.122-4.T66805 -rw- 8529104 Mar 22 2001 19:09:00 rpm-js-mz_002.001.070.20185809 -rw- 7936012 Apr 05 2001 06:28:54 rpm-js-mz.122-4.T104857600 bytes total (83068928 bytes free)Step 6
Router#show flash:-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name1 .. image F596869A 296D88 27 2452744 Feb 28 2001 03:16:05 rpm-boot-mz_002.001.070.20130315128 bytes available (2452872 bytes used)Step 7
Router#copy c:rpm-boot-mz_122-4.T bootflash:Destination filename [rpm-boot-mz_122-4.T]?CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCC2334044 bytes copied in 35.768 secs (66686 bytes/sec)
Tips
Step 8
Step 9
Router#del bootflash:Delete filename []? rpm-js-mzDelete bootflash:rpm-js-mz? [confirm]Router#
Tips
Step 10
Router(boot)#squeeze flash:All deleted files will be removed. Continue? [confirm]ySqueeze operation may take a while. Continue? [confirm]Squeeze of bootflash completeStep 11
Caution
Tip
Tip
Once in rommon mode, you can enter the dir bootflash: command to display the images in bootflash. To boot one of the images, enter a boot command the following format: boot bootflash:filename.
See Using XModem to Download Flash to RPM Cards.This ends the boot software upgrade procedure for the primary card. The following steps are for upgrading the runtime software. If you do not want to upgrade the runtime software for the primary card, skip steps 12 through 24 and go to step 25 to upgrade the boot software on the secondary card.
Step 12
Step 13
8950_LA.8.PXM.a > copy rpm-js-mz_122-4.T rpm-js-mzStep 14
Step 15
Step 16
pop20two.7.PXM.a > cc 9(session redirected)Router>The switch displays the IOS prompt for the router on the RPM-PR card. From this point on, all commands are Cisco IOS commands.
Note
Step 17
Router>enablePassword:Router#Step 18
Router# boot config e:auto_config_slot#Step 19
Router#show bootvarBOOT variable = e:rpm-js-mz,12;CONFIG_FILE variable = c:auto_config_slot09BOOTLDR variable does not existConfiguration register is 0x2In the example above, the startup runtime software file is e:rpm-js-mz_122-4.T, and it has a version number attached to it. Another way to view the boot list is to enter the show startup-config command and look for the boot system commands.
Step 20
Router#config terminalEnter configuration commands, one per line. End with CNTL/Z.Step 21
Router(config)# no boot systemStep 22
Router(config)# boot system e:filenameReplace the filename variable with the name of the new runtime file that was previously transferred to the E:RPM directory on the switch. For example:
Router(config)# boot system e:rpm-js-mzIf you want to enter additional boot system commands, enter them in the order in which you want the RPM card to use them. The following example adds a statement to load from bootflash if the runtime file is not found on the PXM45 hard disk:
Router(config)# boot system bootflash:rpm-js-mz_122-4.T
Note
Step 23
Router(config)#^ZRouter#copy run startDestination filename [startup-config]?Building configuration...[OK]Step 24
Step 25
Router#cc 8(session redirected)Step 26
8950_LA.8.PXM.a > softswitch <fromSlot> <toSlot>Replace <fromSlot> with the slot number of the primary card. Replace <toSlot> with the slot number of the secondary card.
This step makes the secondary card active and resets the primary RPM-PR card. When the Primary card resets, it loads the upgraded software.
Step 27
Step 28
This ends the boot software upgrade on the secondary card. If you do not want to upgrade the runtime software, go to step 30.
The following steps are for upgrading runtime software on the secondary card.
Step 29
Step 30
8950_LA.8.PXM.a > softswitch <fromSlot> <toSlot>Replace <fromSlot> with the slot number of the secondary card. Replace <toSlot> with the slot number of the primary card.This step makes the primary card active and resets the secondary RPM-PR card. When the reset is complete, the secondary card is ready to run the upgraded software.
Step 31
Step 32
Using XModem to Download Flash to RPM Cards
Use the xmodem feature to download the flash to an RPM/B or RPM-PR card. During this process, the card should be connected to a target machine through HyperTerminal with settings of 9600, n, 8, and 1.
Step 1
rommon 1> privYou now have access to the full set of monitor commands. Warning: some commands will allow you to destroy your configuration and/or system images and could render the machine unbootable.Step 2
rommon 2 > xmodemusage: xmodem [-cys]-c CRC-16-y ymodem-batch protocol-s<speed> Set speed of download, where speed may be1200|2400|4800|9600|19200|38400rommon 3 >The command line options for xmodem are as follows:
Note
Note
For example:
rommon 4> xmodem -cys 38400Do not start sending the image yet...Invoke this application for disaster recovery. Do you wish tocontinue? y/n [n]: yNote, if the console port is attached to a modem, both theconsole port and the modem must be operating at the same baudrate. Use console speed 38400 bps for download [confirm]Step 3
Note
The console will display the following message:
Download will be performed at 38400. Make sure your terminalemulator is set to this speed before sending file. Ready toreceive file ...Step 4
In the Filename box, browse and choose the image file to be downloaded. Also since we used the "y" option while invoking the xmodem, set the transfer protocol to ymodem or use Xmodem protocol by not specifying the -y option on the command line.
The transfer screen comes up and transfer starts. (The transfer may not start immediately; wait for some time and it should start.)
After the transfer is completed (it should typically take about 10-15 minutes), the following messages are displayed on HyperTerminal console:
Returning console speed to 9600.Please reset your terminal emulator to this speed...Step 5
Usually, due to time lag between changing HyperTerminal speed back to 9600, you might see a bunch of garbage. To avoid this, disconnect and reconnect the HyperTerminal to get the console back again.
The system will reset itself from here and will boot with new software image.
Troubleshooting Upgrade Problems
Table 19 lists symptoms of upgrade problems and suggestions on how to correct them.
Tips
Documentation
Release notes ship with the switch. You can also download the release notes and other documentation from http://www.cisco.com/univercd/cc/td/doc/product/wanbu/index.htm, or you can order printed manuals (see "Ordering Documentation").
Related Documentation
The following Cisco publications contain additional information related to the operation of this product and associated equipment in a Cisco WAN switching network.
Cisco WAN Manager Release 10.5 Documentation
The product documentation for the Cisco WAN Manager (CWM) network management system for Release 10.5 is listed in Table 20.
Cisco MGX 8850 Release 2.1 Documentation
The product documentation for the installation and operation of the MGX 8850 Release 2.1 switch is listed in Table 22.
Table 22 Cisco MGX 8850 Switch Release 2.1 Documentation
Cisco MGX 8850 Routing Switch Hardware Installation Guide, Release 2.1
DOC-7812561=
Describes how to install the MGX 8850 switch. It explains what the switch does, and covers site preparation, grounding, safety, card installation, and cabling.
Cisco MGX 8850 and MGX 8950 Switch Command Reference, Release 2.1
DOC-7812563=
Describes how to use the commands that are available in the CLI1 of the MGX 8850 and MGX 8950 switches.
Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Release 2.1
DOC-7812551=
Describes how to configure the MGX 8850 and the MGX 8950 switches to operate as ATM edge and core switches. This guide also provides some operation and maintenance procedures.
Cisco MGX 8850 and MGX 8950 SNMP Reference, Release 2.1
DOC-7812562=
Provides information on all supported MIB2 objects, support restrictions, traps, and alarms for the AXSM, PXM45, and RPM. PNNI is also supported.
Cisco MGX and SES PNNI Network Planning Guide
DOC-7813543=
Provides guidelines for planning a PNNI network that uses the MGX 8850 and the MGX 8950 switches and the BPX 8600 switches. When connected to a PNNI network, each BPX 8600 series switch requires a Service Expansion Shelf (SES) for PNNI route processing.
Cisco MGX Route Processor Module Installation and Configuration Guide, Release 2.1
DOC-7812510=
Describes how to install and configure the MGX Route Processor Module (RPM-PR) in the MGX 8850 and MGX 8950 Release 2.1 switch. Also provides site preparation, troubleshooting, maintenance, cable and connector specifications, and basic IOS configuration information.
1 CLI = command line interface
2 MIB = Management Information Base
Cisco MGX 8950 Release 2.1 Documentation
The product documentation for the installation and operation of the MGX 8950 Release 2.1 switch is listed in Table 23
Table 23 Cisco MGX 8950 Switch Release 2.1 Documentation
Cisco MGX 8950 Switch Hardware Installation Guide, Release 2.1
DOC-7812564=
Describes how to install the MGX 8950 switch. It explains what the switch does, and covers site preparation, grounding, safety, card installation, and cabling.
Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Release 2.1
DOC-7812551=
Describes how to configure the MGX 8850 and the MGX 8950 switches to operate as ATM edge and core switches. This guide also provides some operation and maintenance procedures.
Cisco MGX 8850 and MGX 8950 Switch Command Reference, Release 2.1
DOC-7812563=
Describes how to use the commands that are available in the CLI of the MGX 8850 and MGX 8950 switches.
Cisco MGX 8850 and MGX 8950 SNMP Reference, Release 2.1
DOC-7812562=
Provides information on all supported MIB objects, support restrictions, traps, and alarms for the AXSM, PXM45, and RPM. PNNI is also supported.
Cisco MGX and SES PNNI Network Planning Guide
DOC-7813543=
Provides guidelines for planning a PNNI network that uses the MGX 8850 and the MGX 8950 switches and the BPX 8600 switches. When connected to a PNNI network, each BPX 8600 series switch requires a SES1 for PNNI route processing.
Cisco MGX Route Processor Module Installation and Configuration Guide, Release 2.1
DOC-7812510=
Describes how to install and configure the MGX Route Processor Module (RPM-PR) in the MGX 8850 and MGX 8950 Release 2.1 switch. Also provides site preparation, troubleshooting, maintenance, cable and connector specifications, and basic IOS configuration information.
1 SES = Service Expansion Shelf
.
SES PNNI Release 1.1 Documentation
The product documentation that contains information for the understanding, the installation, and the operation of the Service Expansion Shelf (SES) PNNI Controller is listed in Table 24.
Cisco WAN Switching Software, Release 9.3 Documentation
The product documentation for the installation and operation of the Cisco WAN Switching Software Release 9.3 is listed in Table 25.
MGX 8850 Multiservice Switch, Release 1.1.40 Documentation
The product documentation that contains information for the installation and operation of the MGX 8850 Multiservice Switch is listed in Table 26.
MGX 8250 Edge Concentrator, Release 1.1.40 Documentation
The documentation that contains information for the installation and operation of the MGX 8250 Edge Concentrator is listed in Table 27.
MGX 8230 Multiservice Gateway, Release 1.1.40 Documentation
The documentation that contains information for the installation and operation of the MGX 8230 Edge Concentrator is listed in Table 28.
Ordering Documentation
Cisco documentation is available in the following ways:
•
http://www.cisco.com/cgi-bin/order/order_root.pl
Starting with MGX 2.1.60 and its associated releases, printed documentation is offered through the "Printed Information Ordering" site, which can be accessed through:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
•
http://www.cisco.com/go/subscription
•
Documentation on the World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following sites:
•
•
•
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription as mentioned above.
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com or msspubs-feedback@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Attn: Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to http://www.cisco.com
Technical Assistance Center
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
Contacting TAC by Using the Cisco TAC Website
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
http://www.cisco.com/tac
P3 and P4 level problems are defined as follows:
•
•
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
Note
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at http://www.cisco.com/tac/caseopen
Contacting TAC by Telephone
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
•
•
Caveats
This section provides the following information:
•
•
•
•
Caution
Known Anomalies in Release 2.1.79
Note
Table 29 lists the anomalies and known workarounds for release 2.1.79.
Anomalies Resolved in Release 2.1.79
CSCdw84032; S1; Master Agent got suspended on PXM45 Node, causing SNMP to fail
CSCdx02666; S1; AXSM card reports all ports to be down even though they are up.
CSCdx22691; S1; Intercard Communication Loss Redundant PXM-45 Stuck In Init
CSCdx28666; S1; After resetcd, both axsm e/b go into empty/reserved state.
CSCdx31305; S1; Secondary RPM IPC seat gets deleted when it NAKs the GO-ACTIVE req
CSCdx32411; S1; System crashed after executing a switchcc followed by softswitch
CSCdx38360; S1; RPM-PR went into failed/discovering state after multiple swithcc
CSCdx44536; S1; switchredcd for RPMs shouldnt be allowed for cards in discovering
CSCdx46620; S1; Boot hangs on power-on after printing reset reason
CSCdw39431; S2; cpro task hogging semaphores - resulting in CWM sync problems
CSCdw39878; S2; iisp links stuck in DOWN IN PROGRESS
CSCdw67724; S2; after power cycle links went into attempt mode.
CSCdw72425; S2; Switchcc in middle of addred causes Standby AXSM to go FAILED state
CSCdw76856; S2; AXSM reset/coredump while running offline diag
CSCdw84990; S2; Device Driver error core dumped on MGX45
CSCdw85933; S2; Online diag went into pause state,detected PXM unavailable
CSCdw87648; S2; Connections stuck with spurious ais alarm after switchredcd
CSCdw89623; S2; JANPN: PXM resets during dspchans on FRSM with 2000 slave endpoints
CSCdw89650; S2; AXSMs cards went to failed state
CSCdw90728; S2; MGX45 remote loop option when doing a addlnloop is invalid.
CSCdw91807; S2; <power failure> dspclkalms reported false alarms.
CSCdw94012; S2; Recommit of Vc-Merge and multicast connections causes problem.
CSCdw94623; S2; ftp daemon dead on node
CSCdx07520; S2; restorealclnf should delete D:DB2 before unzipping
CSCdx10240; S2; SHM: Add functionality to automatically set cellbus clkrates
CSCdx13146; S2; restoreallcnf does not update IP address
CSCdx14616; S2; QE SAR performance issue
CSCdx17118; S2; Routing does not work properly between PGs w/trk errors
CSCdx17155; S2; partial GEN files on FTP
CSCdx17519; S2; Clock alarm does not clear after restoring pri&sec clock
CSCdx18339; S2; P2MP_DT: Standby pxm45b stucks in dbsvr init for unknown reason
CSCdx20457; S2; performance improvements for reroute-rate
CSCdx27654; S2; Control VC not working properly between LSC and RR
CSCdx28774; S2; SLT:cmRat process died on an MGX2 node
CSCdx29829; S2; Core dump and AXSM reset caused by repeated add/del feeder.
CSCdx29840; S2; AXSMs unable to communicate with the standby PXM after system reset
CSCdx35909; S2; Control VC not working properly between LSC and RR
CSCdx36869; S2; REG3.0: 250k node can not sync standby PXM45B
CSCdx37619; S2; P2MP_DT: Can not find route after crankback
CSCdx38921; S2; Change The On-line Diag Rev Key on HUMVEE
CSCdx40079; S2; UPG:Traffic loss up to 130s while upgrade 2.0 to 2.1 image
CSCdx46282; S2; PIO reset hold timers set to 0 after upgrade from 2.1.71 to 2.1.76
CSCdx53603; S2; AXSM SCT says tagging for 2nd bucket but program as discard
CSCdv59423; S3; dspchancnt does not work for vc-merge connections
CSCdv76791; S3; dspcd command output does not display card information for RPM
CSCdw43588; S3; After switchover,RPM_PR red card data not exist in config file
CSCdw90614; S3; APS popup message after swithcredcd, and addapsln.
CSCdw92415; S3; Feeder information contains unprintable characters
CSCdx04870; S3; SNMP Get on Feeder Table returns invalid mibobjects
CSCdx21274; S3; AXSM fails to generate RDI-P on a non-APS line with LOF condition
CSCdx47919; S3; Enhacement: Make the timer values more flexible
Anomalies Known in Release 2.1.76
There were no anomolies known in MGX 8950 release 2.1.76.
Known RPM-PR/MPLS Anomalies
lists the anomalies that pertain to the route processor module and the MPLS feature.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
AccessPath, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, and Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, PIX, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other brands, names, or trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0104R)
Copyright © 2002, Cisco Systems, Inc.
All rights reserved.
