Table Of Contents
Release Notes for Cisco MGX 8880 Software Release 5.3.10
Revised: June 14, 2009, OL-11148-02
The content of this document is arranged into the following major sections:
About This Release
These release notes describe the system requirements, new features, and limitations that apply to Release 22.214.171.124 of the Cisco Multiservice Switch (MGX) 8880 Media Gateway, and provide Cisco support information.
As part of this release package, VXSM 5.3.30 is compatible with PXM 5.4.10.
Note To verify that you have the latest version of Cisco IOS required to support the new features included in this release, please check Cisco IOS availability status at Cisco.com.
For information about new Cisco Voice Switch Service Module (VXSM) features, refer to the Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.3.30.
For information about new Cisco Voice Inernetworking Service Module (VISM)-Premium (PR) features, refer to the Release Notes for the Cisco Voice Interworking Service Module (VISM), Release 3.3.30.
Type of Release
Release 5.3.30 is a VXSM release for the Cisco MGX 8880 media gateway.
Locating Software Updates
Release 5.3.10 software is located at:
Route processor module (RPM) Cisco IOS software images are located at:
Enhancements in VXSM Release 5.3.30
Maintenance Release 5.3.30 does not introduce new Cisco MGX 8880 features or enhancements. For more information, refer to the Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.3.30.
Enhancements in Release 5.3.10
Release 5.3.10 includes the following new features and warnings.
Enhanced VXSM Card Support
Release 5.3.10 supports the Processor Switch Module Hard Disk Voice (PXM-HDV) back card, which supports four or more VXSM cards on an MGX 8880 media gateway. The size of the D partition on the PXM-HDV back card is 2000 Mb.
Non-redundant Upgrade Procedure
To migrate from PXM-HD to PXM-HDV back cards in a non-redundant configuration, perform the following steps:
Step 1 Upgrade the PXM boot and runtime images to release 5.3.10 using the normal upgrade procedure.
Step 2 Upgrade boot and runtime to 5.3.10.
Step 3 Enter the saveallcnf command, and ftp the saved configuration file to another host.
Step 4 Replace the PXM-HD back card with the PXM-HDV back card.
Step 5 Retrieve the saved configuration file using ftp.
Step 6 Enter the restoreallcnf command.
Redundant Upgrade Procedure
To migrate from PXM-HD to PXM-HDV back cards in a redundant configuration, perform the following steps:
Step 1 Upgrade the PXM boot and runtime images to release 5.3.10 using the normal upgrade procedure.
Step 2 Replace the standby card back card with a PXM-HDV back card and wait for the PXM-HDV back card to retrieve configuration information from the active PXM-HD back card.
Step 3 Enter the switchcc command to force a switchover.
Step 4 Replace the remaining back card with a PXM-HDV back card.
Cisco MGX 8800 Series Operating and Storage Environment
This section describes the operating and storage environments for the Cisco MGX 8880 media gateway, and explains how to prevent oxidation and corrosion problems.
Guidance for Operating and Storage Environments
Dew points indicate the amount moisture in the air. The higher the dew point, the higher the moisture content of the air at a given temperature. Dew point temperature is defined as the temperature to which the air would have to cool (at constant pressure and constant water vapor content) in order to reach saturation. A state of saturation exists when the air is holding the maximum amount of water vapor possible at the existing temperature and pressure
When the Relative Humidity is high, the air temp and dew point temperatures are very close. The opposite it true when the Relative Humidity is low. When the dew point temperature and air temperature are equal, the air is saturated with moisture. Locations with high relative humidities have air that is close to being saturated with moisture. When saturated air cools it cannot hold as much moisture and can cause moisture migration and penetration into the system. This moisture can cause corrosion of internal components.
A storage environment that experiences temperature and/or humidity variations over a short period of time can create a condensing environment, and this is considered an uncontrolled environment. An environment that maintains constant temperature and humidity is considered and climate controlled environment. A temperature and humidity controlled operating and storage environment is required at all times to prevent condensation that can subsequently lead to oxidation of plated metal parts. Cisco recommends that both long term and short term storage environments be climate controlled to prevent humidity and temperature variations that create condensation. Buildings in which climate is controlled by air-conditioning in the warmer months and by heat during the colder months usually maintain an acceptable level of humidity for system equipment.
Note Consult your facilities engineers to evaluate and ensure your storage environment meets the definition of a non-condensing environment.
To prevent oxidation, avoid touching contacts on boards and cards, and protect the system from extreme temperature variations and moist, salty environments.
Operating Environment Specifications
The following specifications define the operating environment:
– Minimum Temperature: 32 degrees Fahrenheit (0 degrees Celsius)
– Maximum Temperature: 104 degrees Fahrenheit (40 degrees Celsius)
• Humidity, ambient (non-condensing)
– Minimum: 10%
– Maximum: 85%
– Minimum: Sea level
– Maximum: 10,000 feet (3,050 meters)
Non-operating and Storage Environment Specifications
The following specifications define the non-operating and storage environments:
–Minimum: -4 degrees Fahrenheit (-20 degrees Celsius)
– Maximum: 149 degrees Fahrenheit (65 degrees Celsius)
• Humidity, ambient (non-condensing)
– Maximum: 95%
–Minimum: Sea level
– Maximum: 10,000 feet (3,050 meters)
Release 5.3.00 Features and Enhancements
This release includes the following new features for the Cisco MGX 8880 platform:
For information about VXSM enhancements, refer to Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.3.30.
This release introduces the following security enhancements:
•PXM45—Secure File Transfer (SFTP)
•RPM-XF—Secure Shell (SSH) for RPM-XF
SFTP and SSH Features
Cisco MGX switches currently support the following remote access applications and protocols:
•Telnet, FTP, and SSH on the PXM45 controllers
•Telnet and FTP on the RPM-XF and RPM-PR cards
This release adds SFTP to the PXM45 card and SSH to the RPM-XF card. SFTP is an alternative to FTP that provides for secure (and authenticated) file transfer between a PXM card and a remote host.
For more information about managing Telnet and SSH features, see the following:
•Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.1
–Managing Telnet Access Features section
–Starting and Managing Secure (SSH) Access Sessions Between Switches section
•Release Notes for Cisco MGX Route Processor Module (RPM-XF) Cisco IOS Release 12.4(6)T for PXM45-based Switches, Release 5.3.00
–Secure Shell (SSH) section
Disabling Telnet and FTP
By default, the PXM45 permits unsecured access from Telnet and FTP clients, as well as secure access from SSH and SFTP clients. A new option (16) of the cnfndparm command, along with an existing option (15), disables unsecured Telnet and FTP access from remote hosts, while permitting secure SFTP and SSH sessions.
If you plan to use SFTP and SSH on the PXM45, you should consider disabling FTP and Telnet access to improve security. Telnet and FTP transfer all user ID, password, and session management information between the client and the PXM45 using clear text. Clear, or unencrypted, text can be read by network analysis and snooping tools.
Upgrading PXM software is not sufficient to initialize and enable the SFTP feature. You must initialize the sshd_config file and reset the MGX chassis. Because resetting a chassis can interrupt traffic, you should initialize SFTP before upgrading software so you don't need to reset it later.
To initialize SFTP, perform the following steps:
Step 1 Initiate an FTP session with the PXM card.
Step 2 Change to the F:/SSHD directory.
Step 3 Get the sshd_conf file from the F:/SSHD directory.
Step 4 Append the line subsystem sftp sftp to the file.
Step 5 Put the sshd_conf file into the F:/SSHD directory.
Step 6 Proceed with the normal software upgrade procedure. Alternatively, enter the resetsys command to reset the chassis.
Note The resetsys command interrupts all traffic on the MGX chassis.
Remote IP Management Connection Enhancements
You can manage an MGX 8850 node directly from an Ethernet or console port on the PXM, or you can configure a remote path to the PXM through a service module or route processor module. The following management paths are supported in prior releases:
•AXSM or MPSM to PXM
•RPM-XF or RPM-PR to PXM
Earlier releases supported intranode connections only, and you could only have one PVC between an RPM and PXM. Release 5.3.00 enhances the atm0 feature to internode connections, where an RPM on one MGX switch connects to PXMs on other MGX switches using PNNI. And now you can manage multiple PXMs from a single RPM.
Management Connection Limitations
The IP addresses of hosts accessing the MGX 8850 node are stored in a RAM cache. Because this cache has a limit of 50 entries, only 50 IP hosts can actively access the node at one time. New IP hosts are blocked until the cache clears (as result of inactivity from some hosts) to make room for new entries.
Multiple RPMs can connect to the same PXM, but each RPM can have only one connection to the PXM. This is because the PXM has a single atm0 address.
Note If you are connected to the MGX switch using the RPM and accidentally delete the SPVC, the connection drops. To restore RPM access, you must re-add the SPVC using the console port or Ethernet port.
Note The clrallcnf, clrcnf, or clrsmcnf commands clear management connections. To restore RPM access, you must reconfigure the RPM and PXM cards for IP connectivity using the console port or Ethernet port.
Configuring an RPM Management Connection
The following quick start procedure summarizes the RPM configuration procedure. This procedure assumes the RPM already has a switch partition configured for the management connection.
The following quick start procedure summarizes the PXM configuration procedure.
Example Management Configuration
This example shows how to configure a management connection between an RPM-XF on one switch and the PXM on another switch. In this example, the RPM-XF switch partition and the PXM atm0 interface are already available.
The following example configures the RPM-XF switch interface, adds a slave connection, and displays the NSAP address.Router(config)#interface switch1.100 point-to-pointRouter(config-subif)#ip address 10.10.10.200 255.255.255.0Router(config-subif)#pvc 0/100Router(config-if-atm-vc)#ubr 1544Router(config-if-atm-vc)#switch connection vcc 0 100 master remoteRouter(config-if-swconn)#endRouter#show switch connection vcc 0 100----------------------------------------------------------Alarm state : No alarmLocal Sub-Interface : 100Local VPI : 0Local VCI : 100Remote NSAP address : defaultLocal NSAP address : 47.0091810001040000ABCD7777.000001011802.00Remote VPI : 0Remote VCI : 0
The following example configures the atm0 interface of the PXM card, adds a master connection to the RPM-XF, and verifies that the connection is state is up. The NSAP address and VPI/VCI entered are the values previously displayed at the RPM-XF.LA.8.PXM.a > ipifconfig atm0 10.10.10.144 netmask 255.255.255.0LA.8.PXM.a > svcifconfig atm0 remote 47.0091810001040000ABCD7777.000001011802.00 pvc 0.100LA.8.PXM.a > dspsvcifM8850_LA System Rev: 05.02 Apr. 25, 2006 16:36:38 PSTMGX8850 Node Alarm: NONEIP CONNECTIVITY SVC CACHE--------------------------------------------------------------------atm (unit number 0):Remote AESA: 47.0091.8100.0104.0000.abcd.7777.0000.0101.1802.00SPVC VPI.VCI: 0.100 (PCR=3642 cps)Flags: (0x6) ATMARP,LLCENCAPState: (0x1) UPRxLCN: 1505 TxLCN: 1505LCNindex: 766 LCNcallid: 0x80000001Input Frames: 1 Output Frames: 1Input Errors: 0 Output Errors: 0Input ArpReq: 0 Output ArpReq: 0Input ArpRply: 0 Output ArpRply: 0Input InArpReq: 0 Output InArpReq: 0Input InArpRply: 1 Output InArpRply: 0...
This release adds the following MGX platform enhancements.
•DB Server/Client enhancement
The server automatically copies database tables to the new directory for a release.
•Software FPGA upgrade on PXM45/C
Cisco uses this feature to upgrade hardware (Field Programmable Gate Array) FPGA images without introducing new hardware versions. This simplifies the process of adding or changing features and can reduce hardware costs for both Cisco and customers.
•PXM to MPSM QoS enhancement
Currently, traffic sent to the MPSM-T3E3-155 and MPSM-16-T1/E1 cards is managed by the class of service only. For example, the CBR traffic class is always given priority over the VBR.RT traffic class, even if VBR.RT connections are committed and data received is within the SCR limit.
Through this QoS enhancement, the PXM QE1210 is programmed using information from the MPSM so it can manage traffic dynamically based on the committed rate of the connections and interface policy.
RPM-PR Ethernet Backcard
The MGX-RJ45-5-ETH is a single-height back card for the RPM-PR that provides five RJ-45 connectors for Gigabit Ethernet, Fast Ethernet, or Ethernet lines. Figure 1 shows the MGX-RJ45-5-ETH faceplate.
Figure 1 MGX-RJ45-5-ETH Back Card
•Green—The back card is active.
•Off—The back card is not active.
Port 0 status LED
•Green—Data present (flashing).
•Orange—The link is up.
Port 0 speed LED
•Orange—10 Mbps or 100 Mbps.
AXSM-8-622-XG Service Module
The AXSM-8-622-XG Service Module is supported on the MGX 8880 in Release 5.3.00.
The Cisco® 8-Port OC-12/STM-4 Channelized/Unchannelized ATM Switch Service Module is a line card for use in the Cisco MGX® 8800 Media Gateway in combination with the Cisco PXM-45 Processor Switch Module . This ATM switch service module has eight physical 622 Mbps interfaces that can be used to deliver high-density OC-12 or STM-4 trunking/User-Network Interface (UNI) or aggregation of sub-OC-12 traffic through port channelization.
Up to 12 Cisco 8-port OC-12/STM-4 ATM switch service modules can reside in the MGX 8880 to provide support for up to 96 OC-12c/STM-4 interfaces for service providers that require both high bandwidth and high network availability.
The AXSM-8-622-XG service module is used in conjunction with the SFP-4-622 back card. This card is a 4-port SFP back card for OC-12/STM-4 interfaces.
•Individual port channelization down to DS-3 and OC-3c/STM-1
•Per-virtual path and per-virtual circuit traffic shaping and available-bit-rate (ABR) with virtual source and virtual destination
•APS (1:1 and 1+1) port redundancy, plus APS 1+1 card redundancy
•Up to four million cell buffers
•Up to 16 classes of service (CoSs) that can be used to support IP or ATM services
•Support for standards-based Private Network-Network Interface (PNNI), switched virtual circuit (SVC) and switched virtual path (SVP), soft permanent virtual connection (SPVC) and soft permanent virtual path (SPVP), and Multiprotocol Label Switching (MPLS) services
Release 5.2.10 Features
Maintenance Release 5.2.10 does not introduce new Cisco MGX 8880 features or enhancements.
Release 5.2.00 Features
Release 5.2.00 introduced the following hardware:
•MGX-VXSM-T3 front card
•VXSM-BC-3T3 back card
Cisco MGX 8880 Release 5.2.00 introduced a third VXSM card for the support of T3 lines. The card consists of a front card with six T3 ports and a half-height back card with three T3 ports. The front card can be configured with either one back card or two back cards.
Table 1 lists Cisco WAN or Cisco IOS products that are compatible with Release 5.3.10.
MGX and RPM Software Version Compatibility Matrix
Table 2 lists the software that is compatible for use in a switch running Release 5.3.10 software.
SNMP MIB Release
The SNMP MIB release for Release 5.3.10 is mgx8XXXrel5310mib.tar.
Note SNMP user guides are replaced by the online MIB tool at: http://tools.cisco.com/ITDIT/MIBS/jsp/index.jsp.
This section lists the MGX 8880 product IDs, 800 part numbers, and revision levels.
Release 5.3.10 Hardware
Release 5.3.10 introduces the following PXM45/C hardware:
•PXM-HDV—Back card with 2000 mb hard disk partition
Release 5.3.00 introduced the following RPM-PR back card:
•MGX-RJ45-5-ETH—Five-port Ethernet back card
MGX 8880 Product IDs and Card Types
Table 3 lists product IDs, minimum 800 part numbers, and the minimum revision levels for the MGX 8880.
Service Class Template Files
This section contains Service Class Template (SCT) file information for Release 5.3.10.
AXSM and AXSM/B
The AXSM and AXSM/B SCTs have the following characteristics:
•SCT 2—Policing enabled, PNNI
•SCT 3—Policing disabled, PNNI
•SCT 4—Policing enabled, MPLS and PNNI
•SCT 5—Policing disabled, MPLS and PNNI
The file names and checksums for the SCT files are as follows:
•AXSM_SCT.PORT.0.V1: Checksum is = 0x6aadd6c6= 1789777606
•AXSM_SCT.PORT.2.V1: Checksum is = 0x78ccfb22= 2026699554
•AXSM_SCT.PORT.3.V1: Checksum is = 0x987919a7= 2558073255
•AXSM_SCT.PORT.4.V1: Checksum is = 0x775bfaa2= 2002516642
•AXSM_SCT.PORT.5.V1: Checksum is = 0xe84c696a= 3897321834
•AXSM_SCT.CARD.0.V1: Checksum is = 0x6aadd6c6= 1789777606
•AXSM_SCT.CARD.2.V1: Checksum is = 0x78ccfb22= 2026699554
•AXSM_SCT.CARD.3.V1: Checksum is = 0x987919a7= 2558073255
•AXSM_SCT.CARD.4.V1: Checksum is = 0x775bfaa2= 2002516642
•AXSM_SCT.CARD.5.V1: Checksum is = 0xe84c696a= 3897321834
To confirm that the checksum of the SCT file and the file on the node match, enter dspsctchksum <filename>.
The AXSM-E SCTs have the following characteristics:
•CARD and PORT SCT 5—Policing enabled for PNNI, disabled for MPLS
•PORT SCT 6—Policing disabled, used for PNNI ports.
•CARD and PORT SCT 52—Policing enabled on PNNI, disabled on MPLS
•PORT SCT 53—Policing disabled on PNNI and MPLS
•PORT SCT 54— Policing enabled on PNNI, disabled on MPLS
•PORT SCT 55—Policing disabled on PNNI and MPLS
The following are checksums for the new AXSM-E SCT file:
•AXSME_SCT.PORT.5.V1: Checksum is = 0x793c56d0= 2033997520
•AXSME_SCT.PORT.6.V1: Checksum is = 0xe92db9a5= 3912087973
•AXSME_SCT.PORT.52.V1: Checksum is = 0x51241b7a= 1361320826
•AXSME_SCT.PORT.53.V1: Checksum is = 0x34bdf8b9= 884865209
•AXSME_SCT.PORT.54.V1: Checksum is = 0xb5df2c5c= 3051301980
•AXSME_SCT.PORT.55.V1: Checksum is = 0xc5d355c8= 3318961608
•AXSME_SCT.CARD.5.V1: Checksum is = 0x793c56d0= 2033997520
•AXSME_SCT.CARD.52.V1: Checksum is = 0x972810ac= 2535985324
Limitations, Restrictions, and Notes for 5.3.10
This section includes information about limitations, restrictions, and notes pertaining to MGX Release 5.3.10.
•Due to granularity limitations in the AXSM-E hardware, cell traffic does not reach the configured peak cell rate (PCR) rate when weighted fair queuing (WFQ) is enabled. You must configure connections that have WFQ enabled with a PCR of 101 percent of the actual required rate. Available bit rate (ABR) has the same Qbin priority as the unspecified bit rate (UBR) in the SCT tables. In this case, ABR and UBR share excess bandwidth if WFQ is enabled.
•The VXSM cards, when installed for the first time or after clearing the slot configuration, create a default configuration. The creation of a default configuration involves writing large amount of data to the hard disk in the node.
When multiple VXSM cards are installed simultaneously or the configuration of multiple VXSM slots are cleared simultaneously, one or more VXSM cards could fail to be installed. This potential failure results in following recommendations (refer to CSCed12646):
–Install VXSM cards, using the setrev command, one at a time. Install another VXSM after the earlier one is completely installed and is Active.
–Clear the VXSM slot configuration using the clrsmcnf command (with no option where the slot primary software version is preserved) one at a time. Wait until the VXSM rebuilds after clearing its slot configuration (without clearing the slot primary software version) before clearing the slot configuration of another VXSM slot.
Upgrading the VISM-PR Image
If you are upgrading the VISM-PR image to Release 3.2.1x or later and the PXM1E or PXM45 image from Release 4.x or earlier to Release 5.x, first upgrade the VISM-PR cards. Then, upgrade the PXM1E or PXM45 cards in the same node.
Do not configure the new VISM features until you have fully upgraded the network. After you upgrade your network to PXM1E or PXM45 Release 5.x or later and VISM-PR to Release 3.2.1x or later, apply the standard upgrade process.
Higher Level Logical Link Limits
The numbers of logical links in the higher levels of the PNNI hierarchy is limited to 30 per level when the complex node configuration is turned on. The limit is essential to reduce the processing time involved in finding the bypasses between the logical links. Each time a significant change occurs in bandwidth in one of the links within the peer group, the bypass calculation is triggered and the bypasses are usually found from one logical link to another.
If there are n logical links, the calculation involves finding n*n bypasses.
If the number of logical links n is large, a lot of processing time is used to calculate the bypasses. Limit the number of logical links per level to 30. To control the number, configure the appropriate number of aggregation tokens for the outside links for that peer group.
The following notes apply:
•Inverse multiplexing over ATM (IMA) version fall-back is part of IMA group operation. If a group is configured with Version 1.1 and it is connected to a far end group which is configured with Version 1.0, this group falls back to Version 1.0.
•The IMA link Loss of IMA Frame (LIF) and Link Out of Delay Synchronization (LODS) defect integration times are configurable.
•ATM layer configuration for line and IMA ports takes an additional parameter: Alarm Indication Signal (AIS) enable. It is enabled by default.
•In T1 mode, payload scrambling is disabled by default and in E1 mode it is enabled by default on all lines and IMA groups.
•Only 10 switched virtual circuit (SVC) calls per second are guaranteed.
•Facilities Data Link (FDL) support for loopback code detection is not supported.
•Far End Line Performance counters are supported only for E1. They are not supported for the T1 interface.
•Hidden Markov Method (HMM) support is not available for the IMA and the Framer devices. When a switchover occurs, it can take up to 3.5 seconds for the IMA groups to recover. Data is lost until the groups recover.
•IMA Autorestart (persistent RX IMA ID) feature is supported.
•The IMA group cannot have links from upper and lower bays configured together.
•Independent Transmit Clock (ITC) clocking mode on IMA is not supported.
•1-way transmission delay of more than 500 milliseconds (ms) on the T1/E1 IMA links is not supported.
•There is 5 ms fluctuation on IMA delay tolerance.
•While the IMA group accumulated delay is being removed using the clrimadelay command, the following applies:
–Any changes to this IMA group configuration are temporarily blocked.
–Any changes in the FE IMA links in this group can cause the NE IMA group to restart.
•The Virtual Circuit (VC) and COSB thresholds are updated when the links are added/deleted from the IMA groups.
•The thresholds for the connections added when there are N links in the group can differ from connections added when there are (N+1) links in the IMA group.
•Bit error rate testing (BERT) is only supported on T1 interfaces. BERT is not supported on E1 interfaces.
•The port number in the pnport (shelf.slot:subslot.port:subport) could be a random number. Do not interpret this number as line or IMA group number. Refer to CSCdy08500.
•Private Network-to-Network Interface (PNNI) requires:
–Sustainable cell rate (SCR) = 453 cells per second and
–Peak cell rate (PCR) = 969 cells per second for the control connection
•Service-Specific Connection-Oriented Protocol (SSCOP) requires an SCR = 126 cells per second and PCR = 2000 cells per second.
AXSM-E Operation, Administration, and Maintenance Cells
The following notes apply to AXSM-E operation, administration, and maintenance (OAM) cells:
•Any connection can receive E2E/OAM loopback cells up to the line rate (as long as the policing policy permits).
•If the connection is not in the loopback mode and is operating in the normal mode, then the AXSM-E card can receive up to 1,500 segment OAM loopback cells per second. Any excessive segment OAM loopback cells are dropped. This limitation applies for all the connections on a card.
For example, if only one connection exists, that connection can receive 1,500 segment OAM loopback cells per second. If 2,000 connections exist on an AXSM-E card, and one segment OAM loopback cell per second is being channeled through on each connection, then there can only be up to 1,500 connections to receive loopback cells at any given second. The additional 500 connections are not received for that second.
•The limitation is 1,500 segment OAM loopback cells per card and not per connection. The 1,500 cps assumes an even flow rate.
Command Line Interface Access Levels
The following notes pertain to configuring command access levels:
•Not all command line interface (CLI) commands are changeable, and a command cannot be changed to CISCO_GP group access level.
•Only the switch software is allowed to generate the binary file. This binary file has an authentication signature which has to be validated before the binary file can be used. Any manual changes to the file make the file void.
•If the binary file becomes corrupted, then the command access levels revert back to the default values during the card bring-up. To recover, repeat the installation process or retain a copy of the binary file and execute a cnfcli accesslevel install command on that service module.
•Currently, command names are verified, but an invalid command name might be parsed and added to the binary file. However, this invalid name is ignored later.
•If replication to standby failed, the installation process failed.
•The cnfcli accesslevel default command restores all command access levels to default for the service module that this command is executed on. This command does not remove the binary file, and this change is not persistent. If the command is executed on the active card of a redundancy pair, the standby card is not affected. When the card is reset and the binary file exists, it configures from the binary file when it is brought up.
Disk Space Maintenance
Because the firmware does not audit the disk space usage nor remove unused files, the disk space in C: and E: drives must be manually monitored.
Manually delete any unused saved configuration files, core files and firmware files, and the configuration files of the MGX-RPM-PR-512 and MGX-RPM-XF-512 cards to avoid a shortage of disk space required to store event logs: configuration upload files in the C: drive and the configuration of MGX-RPM-PR-512 and MGX-RPM-XF-512 cards in the E: drive.
The following steps are recommended to remove files on the system from the active controller card:
Step 1 Change to the directory that needs grooming.CLI cc <directory_name>
Step 2 List the directory to identify old files that can be removed and available disk space.CLI ll
Step 3 Remove any old files (you may also use wild cards in the filename).CLI rm <complete_filename>
Step 4 List the directory to see if the file was removed and disk space is available.CLI ll
The system keeps only the two most recent copies of the saved system configuration under the C:/CNF directory. You can use FTP to transfer all of the saved configurations under C:/CNF to their local server for future reference. All files under C:/CNF are not replicated over to the standby controller card under any circumstances.
Using the clrsmcnf Command
These notes pertain to the clrsmcnf command:
•We do not recommend executing clrsmcnf on more than one card at a time
•For the clear service module configuration feature, if there is a controller card switchover before the clear service module configuration operation is complete, the clrsmcnf command must be re-issued to ensure that the configuration is completely cleared to avoid an incomplete cleanup.
•For the clear service module configuration feature, using the clrsmcnf command might result in discrepancy in the PNNI configuration. For example, some connections might be in the mismatch state.
•If the clrsmcnf command is given with the <all> option to clear the software version for the slot as well, then the card enters the boot/empty state after the operation is complete.
•If the clrsmcnf command is given with the <all> option, for cell bus service module, the card enters boot/empty state. For a broadband service module (for example, AXSM or MPSM-155-T3E3), the card enters fail/active state.
•While using the clrsmcnf command, the card in the specified slot is not usable until the operation is successfully completed.
AXSM Card Automatic Protection Switching Limitations
These notes pertain to the Automatic Protection Switching (APS) feature:
•For AXSM APS, the back card of the active card must be present for APS to function.
•AXSM cards need the back card of the active front card for the APS to work. This implies that AXSM cards do not support the cross backcard removal—the upper backcard of one AXSM and lower backcard of another AXSM.
•If you remove the upper back card of the active front AXSM, it triggers switching active card. The APS is OK. However, if the lower back card of the current active AXSM is removed at this time, it does not trigger switching the active card because the standby card is missing one of the back cards. The lower backcard APS does not work because the back card of the active front card is missing.
•Port LED lights on AXSM-E front cards indicate the receive status of the physical line connected to it only when the card is in active state. For standby AXSM-E cards, the LEDs always remain green when the lines are in loss of signal (LOS) irrespective of which lines are active (refer to anomaly CSCdv68576).
Path and Connection Trace Features
These notes pertain to the path and connection trace features:
•Path trace is not supported on the control port.
•Path trace does not have the accurate information when there is a crankback on the connect path.
•Path and connection trace support point to point connections.
•Path and connection trace support MPG (multiple peer group) and SPG (single-peer group).
Priority Routing Feature
These notes pertain to the priority routing feature:
Prioritized reroute of soft permanent virtual connection (SPVCs) is not guaranteed if the SPVCs originate on a signaling port. SPVCs might get routed out of order. In-order routing of SPVCs is guaranteed on non-signaling ports.
•RPM does not support configuration of routing priority. All RPM mastered SPVCs are assigned a routing priority of 8 by the PXM.
•Changing the routing priority for DAX connections does not change the priority of the associated SVCs. The SPVCs are not derouted and rerouted if just the endpoint parameters are changed, and routing priority is an endpoint parameter. Also, because DAX connections are never derouted even if the user-network interface (UNI) port stops responding and the rrtcon command is not supported for DAX connections, the routing priority change is never reflected. The only way for the routing priority change to be reflected is to execute the dncon and upcon commands. Because DAX connections are never derouted, the effect of this limitation is voided.
•Priority routing operates in a best effort manner for the following reasons:
–Two in-order releases can still arrive out of order at the master node if they take two different paths.
–Under congestion scenarios releases can be expected to be transmitted out-of-order. This is because releases of other calls must not be held up if you are not able to send releases on one of the interfaces because it is congested. The calls that were not released could be higher priority calls.
–Lower priority SPVCs can be routed ahead of higher priority SPVCs. This can happen if you have repeatedly failed to route higher priority SPVCs. To prevent starvation of lower priority SPVCs, the software starts to route lower priority SPVCs. The software eventually addresses the higher priority SPVCs later.
Soft Permanent Virtual Connection Interoperability
These notes pertain to SPVC interoperability:
•Network-to-Network Interface (NNI) SPVC Addendum Version 1.0 is not supported.
•CC (Continuity Check) is not available at the slave end of a single-end SPVC.
•Reporting AIS detection to Cisco Wide Area Network Manager (CWM) is not available at the slave end of a single-end SPVC.
•The slave end of a single-end SPVC is not visible to CWM.
•If single-end SPVCs originated from MGX switches, they can only be configured through CLI and not from CWM in the current release.
•Single-end provisioning is not supported for DAX connections.
•SPVC statistics are not available for the slave endpoint of a single-end SPVC because this endpoint is non persistent.
•When the persistent slave endpoint of an existing SPVC connection is deleted and the master endpoint is allowed to remain, the connection might become established as a single-end SPVC connection. In this case, CWM shows the connection as Incomplete.
•Override of SVC connections on a virtual path identifier (VPI) due to an incoming SPVP request for that VPI is not supported. The following override options are supported only:
When resetcd is invoked, the primary and secondary (if configured) clock sources are recommitted. However, the clock to which the node is latched is not requalified. Only the backup clock is qualified if present. Recommitted means that the primary and secondary are requalified, and the node temporarily latches onto the internal oscillator. After the clock is requalified, the node locks onto the primary clock source once again.
Enabling Priority Bumping
When you enable priority bumping on the node, you cannot change the booking factor for AXSM signaling ports. You can change the booking factor for non-signaling ports.
Other Limitations and Restrictions
Other limitations and restrictions are as follows:
•When configuring virtual interfaces (for example, VUNI, VNNI, EVUNI, EVNNI), the physical interface must be of all one ATM header type, either UNI or NNI. The signaling that is applied to a virtual port is independent of the actual virtual port ATM header. The only limit is that the VPI value must be within the UNI ATM header limitations.
•If command clrchancnt is executed while a dspchancnt command is currently active, the displayed data is incorrect. To display correct data, restart the dspchancnt after the previous one is complete.
•The clrsmcnf command does not work:
–For redundant service modules.
–If an upgrade is in progress.
•If RPM-XF is configured as a Label Switch Controller (LSC), execution of clrsmcnf command on those LSC slots is rejected.
•Configuration information is not synchronized between processor switch modules (PXMs) during upgrades. If any changes are made to the configuration during upgrades, the standby PXM must be rebooted. The standby PXM must be rebooted when it is in a stable state.
Clearing the Configuration on Redundant PXM45 Card
These notes apply to redundant cards.
•Due to checks to prevent an inserted card from affecting the system, an additional step might be required when inserting two non native PXM45 cards in a shelf. Insert the first PXM45, use the clrallcnf command, and allow this to become active before inserting the second PXM45.
•After a clrallcnf, explicitly clean up stale SCT files (see anomaly CSCdw80282).
Known MGX 8880 Media Gateway Anomalies
For information about anomalies in MGX Release 5.3.00 on other platforms, refer to the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.3.10.
For information about anomalies with the VXSM card, refer to Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.3.30.
For information about anomalies with the VISM card, refer to Release Notes for the Cisco Voice Interworking Service Module (VISM), Release 3.3.30.
Known Route Processor Module Anomalies
For information about anomalies with the MGX-RPM-XF-512 card, refer to Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.4(6)T1 for PXM45-based Switches, Release 5.3.00.
For information about anomalies with the MGX-RPM-PR-512 card, refer to Release Notes for Cisco MGX Route Processor Module (RPM-PR) IOS Release 12.4(6)T1 for MGX Releases 1.3.14 and 5.3.00.
A Guide to Cisco Multiservice Switch Documentation ships with your product. That guide contains general information about how to locate Cisco MGX, broadband and packet exchange (BPX), service expansion shelf (SES), and CWM documentation online.
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website 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. (0903R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2008 Cisco Systems, Inc. All rights reserved.