Table Of Contents
1.1.32 Version Software Release Notes Cisco WAN MGX 8850, 8230, and 8250 Software
About These Release Notes
About the 1.1.32 Release
Features Introduced in Release 1.1.32
Stratum 3 Clocking Support
Feature Descriptions
Support for Multiple RPM Card Types
Support for RPM-PR Module with MGX-PXM1
Support for RPM/B in MGX 8230
Features Introduced in Release 1.1.31
Feature Descriptions
CoS Map for FRSM-8
DS3 Loopback on PXM-T3
ForeSight and Standard ABR Coexistence Guidelines
Independent Service Rate on FRSM-HS1/B
Online Diagnostics for PXM
SRM in MGX 8230
Standard ABR on AUSM
Standard ABR on FRSM-8 and FRSM8-C Modules
Stratum-3 Clocking
VBR-rt on AUSM
VISM 1.5.5 on MGX 8250/8850
VISM 2.0.0 on MGX 8230/8250/8850
Features Introduced in Release 1.1.25
Features Introduced in Release 1.1.24
MGX 8230
MGX 8250
Continued Support for the MGX 8850
Features Introduced in Release 1.1.23
Release 1.1.32 MGX 8850, MGX 8230, and MGX 8250 Hardware
MGX 8220 Hardware Not Supported on Release 1.1.32 of the MGX 8850
MGX 8220 Hardware That Has Been Superseded on the MGX 8850 by MGX 8850-Specific Hardware
MGX 8220 Hardware Not Supported on the MGX 8850
Software Platform Features
Features Not Supported in This Release
Major Network Management Features
Connection Limits
SNMP MIB
Notes & Cautions
ForeSight and Standard ABR Coexistence Guidelines
CLI Modification and Changes in this Release
Node Related
RPM Related
Limitations
restoreallcnf
clrsmcnf
Core Dump Mask
Problems Fixed in Release 1.1.32
Problems Fixed in Release 1.1.31
Problems Fixed in Release 1.1.25
Problems Fixed in Release 1.1.24
Problems Fixed in Release 1.1.23
Compatibility Notes
MGX 8230/8250/8850 Software Interoperability with Other Products
Firmware File Names and Sizes
MGX 8850 Firmware Compatibility
RPM IOS Compatibility (MGX 8850)
MGX 8250 Firmware Compatibility
RPM IOS Compatibility (MGX 8250)
MGX 8230 Firmware Compatibility
RPM IOS Compatibility (MGX 8230)
Compatibility Matrix
Special Installation and Upgrade Requirements
Single PXM Installation Procedure
Installation Procedure for Redundant PXMs
Service Module Firmware Download Procedure
Manual Configuration of Chassis Identification
MGX as a Standalone Node
Chassis Identification During a Firmware Upgrade
Service Module Installation/Upgrade and Flash Download Requirements.
Service Module Upgrades
Known Anomalies for Platform Software and Service Module Firmware
Known Anomalies for RPM release 12.1(1)T
Known Anomalies for RPM Release 12.0(5)T1
RPM Configuration Examples for MPLS-based Virtual Private Networks
One PE - Two CE Configuration
One PE - Two CE Configuration - OSPF & IBPG Between PEs & EBGP between PE-CE
CE1 Configuration:
CE2 Configuration
CE3 Configuration:
PE1 Configuration:
PE2 Configuration:
One PE - Two CE Configuration - OSPF & IBPG Between PEs & RIP between PE-CE
CE1 Configuration
CE2 Configuration
CE3 Configuration
PE1 Configuration
PE2 Configuration
One PE - Two CE Configuration - OSPF & IBPG Between PEs & STATIC ROUTES between PE-CE
CE1 Configuration
CE2 Configuration
CE3 Configuration
PE1 Configuration
PE2 Configuration
Route Processor Module (RPM) Addendum
About the Cisco IOS 12.1(5.3)T_XT Release
RPM Compatibility Matrix
Special Upgrade Requirements for RPM
General Upgrade/Downgrade Guidelines
Upgrade the RPM Firmware
Upgrade a RPM/B Module to RPM-PR
Install an RPM-PR Module in a Fresh Slot
Operate an RPM/B or RPM-PR in an MGX 8230 Chassis
New CLI Commands for RPM
Notes and Cautions (RPM)
RPM-PR Back Ethernet Card Support
RPM/B Ethernet Back Card Support
Limitations
Known Anomalies (RPM)
Problems Fixed with IOS 12.1(5.3)T_XT
Known Anomalies from Previous Releases
Obtaining Documentation
World Wide Web
Documentation CD-ROM
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco.com
Technical Assistance Center
Contacting TAC by Using the Cisco TAC Website
Contacting TAC by Telephone
1.1.32 Version Software Release Notes Cisco WAN MGX 8850, 8230, and 8250 Software
About These Release Notes
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
About the 1.1.32 Release
This is a maintenance release including all features supported up to release 1.1.25.
Features Introduced in Release 1.1.32
RPM features that require 1.1.32 bundled with IOS 12.1(5.3)T_XT
|
Feature
|
Availability
|
IOS
|
CWM
|
Support for Multiple RPM Card Types
|
Release 1.1.32
|
12.1(5.3)T_XT
|
10.4
|
Support for RPM-PR module for MGX-PXM1
|
Release 1.1.32*
|
12.1(5.3)T_XT
|
10.4
|
Support for RPM/B in MGX 8230
|
Release 1.1.32
|
12.1(5.3)T_XT
|
10.4
|
|
|
Stratum 3 Clocking Support
Support for Stratum 3 Clocking, including the PXM-UI-S3 back card, is GA with Release 1.1.32 (this feature was supported in field trials only with Release 1.1.31). Refer to Stratum-3 Clocking, for additional information and descriptions.
Feature Descriptions
Note 
Please refer to the "Route Processor Module (RPM) Addendum" section for additional information and special instructions on the installation of RPM modules with Release 1.1.32.
Support for Multiple RPM Card Types
When multiple RPM card types are present in the network, the PXM1 will recognize and display the correct RPM card type. The current RPM card types are RPM/B and RPM-PR. The MGX 1.1.32 Release contains PXM code base changes that recognize the multiple RPM card types.
Support for RPM-PR Module with MGX-PXM1
The RPM-PR provides the following features:
•More than twice the forwarding performance of the RPM/B.
•Supports up to 512 Mbytes SDRAM.
•Provides integrated ATM SAR with OC-6 cell bus rates to the PXM1.
•Flash memory increased to 32M.
The higher-performance RPM requires Software Release 1.1.32, IOS version 12.1(5.3)T_XT and a minimum CWM version of 10.4.
Support for RPM/B in MGX 8230
Installation of the RPM/B in the MGX 8230 requires Release 1.1.32 and IOS version 12.1(5.3)T_XT.
Note Customers planning to use RPM/B in the MGX 8230 should upgrade to MGX Software Release 1.1.32 and CWM 10.4.
Features Introduced in Release 1.1.31
The following Features are available for the MGX 8850, MGX 8250, and MGX 8230 with Release 1.1.31 and IOS 12.1(3)T:
Features that require 1.1.31 bundled with IOS 12.1(3)T
|
Feature
|
Availability
|
CoS Map for FRSM-8
|
Release 1.1.31
|
DS3 Loopback on PXM-T3
|
Release 1.1.31
|
ForeSight and Standard ABR Coexistence Guidelines
|
Release 1.1.31
|
Independent Service Rate on FRSM-HS1/B
|
Release 1.1.31
|
Online Diagnostics for PXM
|
Release 1.1.31
|
SRM in MGX 8230
|
Release 1.1.31
|
Standard ABR on AUSM
|
Release 1.1.31
|
Standard ABR on FRSM-8 and FRSM8-C Modules
|
Release 1.1.31
|
Stratum-3 Clocking
|
Field Trial Only with Release 1.1.31
|
VBR-rt on AUSM
|
Release 1.1.31
|
VISM 1.5.5 on MGX 8250/8850
|
Release 1.1.31
|
VISM 2.0.0 on MGX 8230/8250/8850
|
Release 1.1.31
|
Feature Descriptions
For descriptions of the features introduced in Release 1.1.31, see the following sections:
•CoS Map for FRSM-8.
•DS3 Loopback on PXM-T3.
•ForeSight and Standard ABR Coexistence Guidelines.
•Independent Service Rate on FRSM-HS1/B.
•Online Diagnostics for PXM.
•SRM in MGX 8230.
•Standard ABR on AUSM.
•Standard ABR on FRSM-8 and FRSM8-C Modules.
•Stratum-3 Clocking.
•VBR-rt on AUSM.
•VISM 1.5.5 on MGX 8250/8850.
•VISM 2.0.0 on MGX 8230/8250/8850.
CoS Map for FRSM-8
This feature implements the ATM Class of Service (CoS) on the FRSM-8 Module. This feature maps the connection with ATM Class of Service parameters to the appropriate queue in the ingress side of the FRSM-8 and PXM.
Previous versions do not support any CoS type of connections; only ForeSight and non-ForeSight type connections are supported. By mapping the CoS parameters, the connections can then be scheduled in the appropriate queue on the PXM.
The following service types are added to the existing service types: UBR, VBR, VBR-RT, VBR-nRT, and STD-ABR. The current limit on connection count is to be retained as far as possible. This feature is supported by CWM 10.3 (which is not targeted for General Availability).
DS3 Loopback on PXM-T3
This feature enables the active PXM to initiate the DS3 loopback code (program the T3 framers to generate the sequence of 16 bit FEAC codes, or Far End Alarm and Control codes). The main functions are:
•Send alarm or status information from the far-end terminal back to the near-end terminal.
•Initiate DS3 loopbacks at the far-end terminal from the near-end terminal.
The active PXM will initiate this code, which will also run on the standby PXM. This feature has CLI support and is supported by CWM 10.3 (which is not targeted for General Availability).
ForeSight and Standard ABR Coexistence Guidelines
With Release 1.1.31, both ABR TM4.0 and ForeSight congestion control are supported on the FRSM and AUSM modules. This document contains the following:
•Description of the major differences between the TM 4.0-compliant standard ABR and ForeSight ABR.
•Guidelines for coexistence of ForeSight with standard ABR connections on the same network.
•Example configuration of the two different connection types to have similar characteristics.
Independent Service Rate on FRSM-HS1/B
This feature provides the capability to configure a connection service rate in the ingress direction. Users can also specify EIR if connection is "0" of CIR. This feature is already implemented in FRSM-8 and FRSM-VHS.
This functionality is the same as that provided in FRSM-8 and FRSM-VHS. This feature is not supported by CWM 10.3 (which is not targeted for General Availability).
Online Diagnostics for PXM
This feature provides hardware tests to check the health of the SRM and PXM modules (both active and standby). This test is non-intrusive and operates with minimum overhead while the shelf is running. Connections, states and tasks are not affected.
The Online Diagnostics are optional tests operated through CLI and SNMP interfaces. The test is invoked from the active PXM. If a standby PXM exists and is in standby state, it also will be tested. When the test is executed, each component is checked and the results are presented on the screen. The results of the diagnostics are written to a log file so they can be viewed and analyzed offline.
Initially, intelligence is not provided, but built-in intelligence may be considered as a future enhancement. The hardware and software components selected for running the diagnostics will be selected from field experience. The targets are hard disk and memory components. Although the intent is to check the health of the hardware, a switchover should not occur except under severe circumstances.
SRM in MGX 8230
This feature provides SRM support in the MGX 8230. Only the newest version of the SRM, MGX-SRM-3T3/C, is supported in the 8230 chassis. This feature is not supported by CWM 10.3 (which is not targeted for General Availability), but is planned for a future release.
Standard ABR on AUSM
This feature involves implementing the standards-based TM 4.0 ABR congestion control loop. The current AUSM-8 card only supports ForeSight, which is pre-standards-based. Standard ABR is required on AUSM cards in order for them to interoperate with third-party devices that support standard ABR and AXSM cards.
Support for standard ABR calls for implementing the RM cells to perform the flow control. All three modes are considered: EFCI, ER, and RR. Only modes that can be supported on the existing hardware are implemented. In addition, all appropriate behaviors are implemented. These behaviors include Source, Destination, and Switch. Connections with the standard ABR parameter are mapped to the appropriate queue. This feature includes new CLI and MIB support. Also expected for the CWM support is the appropriate formula. Due to current hardware limitation, VS/VD is not considered. This feature is supported by CWM 10.3 (which is not targeted for General Availability).
Standard ABR on FRSM-8 and FRSM8-C Modules
The feature implements TM 4.0 ABR service on the FRSM card. The current FRSM supports ForeSight, a pre-standard version of congestion control. This feature provides standards-compliant ABR congestion mechanism in addition to ForeSight. The module will generate RM cells to dynamically increase or decrease bandwidth rate. This includes all applicable modes of behavior: Source, Destination, and Switch. Only relevant modes need be considered. Connections with the standard ABR parameter will be mapped to the appropriate queues and will co-exist with ForeSight connection types.
This feature is implemented via appropriate MIBS and CLI. This feature is supported by CWM 10.3 (which is not targeted for General Availability). ABR license (similar to ForeSight license) is created and is a billable feature. One common license is available for either ForeSight or standard ABR on FRSM. Standard ABR fulfils the standards-compliance part of TM 4.0.
Stratum-3 Clocking
Standard clocking in the MGX is supported with a built-in Stratum-4 clock source. For network applications that require a higher clock accuracy, the PXM-UI back card used with the Stratum-4 can be replaced with an optional PXM-UI-S3 back card that carries a Stratum-3 clock. This clock reference conforms to AT&T T1.5 and ITU G.824 specifications. A provision is also made for a Service Provider to connect an external clock source, if necessary.
Both holdover and fail-over modes are supported by the PXM-UI-S3. That is, if all clock sources fail, the Stratum-3 clock will hold the last best-known clocking frequency.
The default clock is the internal Stratum-4. Pertinent CLI and MIB support are provided for Stratum-3 configuration. The PXM-UI-S3 back card is also recognized by the Cisco WAN Manager.
Hardware Changes
A new PXM-UI-S3 back card replaces existing PXM-UI-B cards.
The new PXM-UI-S3 supports both T1 and E1 interfaces through an RJ-45/48 connector.
CLI
A new CLI cnfclklevel permits the user to set the STRATUM level desired.
Default Settings
The default clock source is set to be the Internal Oscillator. Subsequently, an External/Inband/SM clock can be configured to be the primary/secondary clock driving the node.
Limitations
There are two physical ports on the PXM-UI-S3 back card for providing External clock. However, only "Ext Clk 1" is currently supported. There are 2 physical LAN ports on the PXM-UI-S3 back card. However, only "LAN port 1" is currently supported.
Warning If an External clock was configured to drive the node in Stratum-4 clocking with the old UI back card, and this UI card is replaced with the new PXM-UI-S3 back card, the Stratum-3 clocking must be explicitly configured on the node to continue using the External clock source. The following CLI's must be executed:
* cnfclklevel 3
* cnfextclk (with T1/E1 option)
VBR-rt on AUSM
This feature involves implementing the standard Class of Service on the AUSM-8 Module. VBR-rT CoS is required for video and real time voice applications. In terms of conformance definition it is same as VBR-nRT, which is already supported. The connection parameters will be bounded by Peak Cell rate (PCR), Sustainable Cell Rate (SCR) and Maximum Burst Size (MBS). Cell Delay Variation Tolerance (CDVT) will be parameter to characterize the PCR.
This new CoS requires scheduling the appropriate queue in both the ingress and egress direction. It has lower priority than CBR but higher than VBR-nRT.
Appropriate CLI commands to configure the parameters are implemented. This feature is supported by CWM 10.3 (which is not targeted for General Availability).
VISM 1.5.5 on MGX 8250/8850
VISM 1.5.5 is supported on MGX 8250/8850. For VISM on MGX 8230, please use VISM 2.0.0 listed below. CWM 10.3 (which is not targeted for General Availability) supports VISM 1.5.5. VISM is not targeted for General Availability.
VoIP using RTP (RFC 1889)
VISMR1.5 supports standards-based VoIP using RTP (RFC1889) and RTCP protocols. This allows VISM to interwork with other VoIP Gateways.
VoAAL2 (With sub-cell multiplexing) PVC
The VISM supports standards-compliant AAL2 adaptation for the transport of voice over an ATM infrastructure. AAL2 trunking mode is supported.
Codec Support
G.711 PCM (A-law, Mu-law), G.726, G.729a/b
8 T1/E1 Interfaces
The VISM supports 8 T1 or 8 E1 interfaces when G.711 PCM coding is used. For higher complexity coders such as G.726-32K and G.729a-8K, the density drops to 6 T1 or 5 E1 interfaces (max 145 channels).
1:N redundancy using SRM.
T3 Interfaces (via SRM Bulk Distribution)
T3 interfaces are supported using the SRM's bulk distribution capability. In this case, the T3 interfaces are physically terminated at the SRM module. The SRM module breaks out the individual T1s and distributes the T1s via the TDM backplane bus to the individual VISM cards for processing.
Echo Cancellation
The VISM provides on-board echo cancellation on a per-connection basis. Up to 128 msec user-configurable near-end delay can be canceled. The echo cancellation is compliant with ITU G.165 and G.168 specifications.
Voice Activity Detection (VAD)
VISM uses VAD to distinguish between silence and voice on an active connection. VAD reduces the bandwidth requirements of a voice connection by not generating traffic during periods of silence in an active voice connection. At the far-end, comfort noise is generated.
Fax/Modem Detection for ECAN and VAD Control
The VISM continually monitors and detects fax and modem carrier tones. When carrier tone from a fax or modem is detected, the connection is upgraded to full PCM to ensure transparent connectivity. Fax and modem tone detection ensures compatibility with all voice-grade data connections.
CAS Tunneling via AAL2 (For AAL2 Trunking Mode)
The VISM in AAL2 mode facilitates transport of CAS signaling information. CAS signaling information is carried transparently across the AAL2 connection using type 3 packets. In this mode, VISM does not interpret any of the signaling information.
PRI Tunneling via AAL5 (For AAL2 Trunking Mode)
VISM supports transport of D-ch signaling information over an AAL5 VC. The signaling channel is transparently carried over the AAL5 VC and delivered to the far-end. In this mode, VISM does not interpret any of the signaling messages.
Voice CAC
VISM can be configured to administer Connection Admission Control (CAC) so that the bandwidth distribution between voice and data can be controlled in AAL2 mode.
Type 3 Packet for DTMF
The VISM in AAL2 mode facilitates transport of DTMF signaling information. DTMF information is carried transparently across the AAL2 connection using type 3 packets.
Dual (Redundant) PVCs for Bearer/Control
The VISM provides the capability to configure two PVCs for bearer/signaling traffic terminating on two external routers (dual-homing). VISM continually monitors the status of the active PVC by using OAM loopback cells. Upon detection of failure, the traffic is automatically switched over to the backup PVC.
64 K Clear Channel Transport
The VISM supports 64 Kbps clear channel support. In this mode, all codecs are disabled and the data is transparently transported through the VISM.
DTMF Relay for G.729
In VoIP mode, DTMF signaling information is transported across the connection using RTP NSE (Named Signaling Event) packets
MGCP 0.1 for VoIP with Softswitch Control
VISM supports Media Gateway Control Protocol (MGCP) Version 0.1. This open protocol allows any Softswitch to interwork with the VISM module.
Resource Coordination via SRCP
Simple Resource Control Protocol (SRCP) provides a hearbeat mechanism between the VISM and the Softswitch. In addition, SRCP also provides the Softswitch with gateway auditing capabilities.
Full COT Functions
VISM provides the capability to initiate continuity test as well as provide loopbacks to facilitate continuity tests when originated from the far-end.
Courtesy Down
This feature provides a mechanism for graceful upgrades. By enabling this feature, no new calls are allowed on the VISM while not disrupting the existing calls. Eventually, when there are no more active calls, the card is ready for a upgrade and/or service interruption.
VISM 2.0.0 on MGX 8230/8250/8850
VISM 2.0.0 supports all of the VISM 1.5.5 features listed above. VISM 2.0.0 is supported on MGX 8230/8250/8850. CWM 10.3 (which is not targeted for General Availability) supports VISM 2.0.0. VISM is not targeted for General Availability.
PRI Backhaul to the Softswitch Using RUDP
The PRI backhaul capability provides PRI termination on the VISM with the Softswitch providing call control. ISDN Layer 2 is terminated on the VISM and the layer 3 messages are transported to the Softswitch using RUDP.
Latency Reduction (<60 ms round-trip)
Significant improvements have been made to bring the round-trip delay to less than 60 ms.
Codecs Preference
VISM provides the capability to have the codecs negotiated between the two end-points of the call. The VISM can be configured, for a given end-point, to have a prioritized list of codecs. Codec negotiation could be directly between the end-points or could be controlled by a Softswitch
31 DS0 for E1 with 240 Channels Only
While all 31 DS0s on a E1 port can be used, there is a limitation of 240 channels per card.
Features Introduced in Release 1.1.25
None.
Features Introduced in Release 1.1.24
While no new features are incorporated into Software Release 1.1.24, this software release does provide support to two new wide area switches, the MGX 8230 and the MGX 8250, as well as continued support for the MGX 8850 switch.
MGX 8230
The MGX 8230 functions as a feeder to the IGX, BPX, or MGX 8850 switches, or can be used for bringing in service. It has a seven slot (double-height) chassis, and the slots are oriented in the following manner:
•Two slots are reserved for PXMs.
•Two single-height (which equals one double-height) slots are reserved for SRM.
•The remaining slots can be configured with four double-height or eight single-height slots, supporting service modules.
Figure 1 shows the MGX 8230 with its door attached. Note that there are light pipes in the door that display the status of the processor models (PXMs). Figure 2 is a conceptual drawing of an MGX 8230 showing the dimensions and the slot numbering. The slot numbering is as it appears from the front of the MGX 8230; slots 8 and 9 refer to back card slots only.
Note that the following features are not supported in this release, but are planned for future releases:
•Service Resource Module (SRM)
•Route processor module (RPM)
•Voice Interface Service Module (VISM)
•PNNI (some CLI commands may show options for PNNI, but this feature is not supported)
Figure 1 MGX 8230 with Door Attached
Figure 2 MGX 8230 Dimensions
Note Even though the card slots in an MGX 8230 are horizontal and would more appropriately be called single-width and double-width, this manual still refers to the card slots, and the processor and service modules, as single-height and double-height. This is for consistency because the PXM and service module cards are a subset of the MGX 8850 cards that are installed vertically in an MGX 8850 chassis.
Main Features
Release 1.0 of MGX 8230 includes:
•PXM1 with 4-port OC3-C/STM-1.
–MMF, SMFLR, and SMFIR back cards are supported.
–PXM1 ports are used as ATN UNI or feeder trunks.
–Core redundancy for PXM1.
–Environmental monitoring.
–PXM-1 with one OC-12 port.
•PXM1-2-T3E3 provides interfaces for up to two T3 (each at 44.736 Mbps) or two E3 lines (each at 34.368 Mbps).
•ATM, Frame Relay, and Circuit Emulation service modules.
–AUSM-8T1/E1/B with RJ48-T1/E1 and SMB E1 back card with UNI and IMA support.
–FRSM-8T1/E1 with RJ48-T1/E1 and SMB E1 back cards.
–FRSM-2T3E3 with BNC-2T3/E3 back cards.
–FRSM-HS2 with 2-port HSSI back card.
–FRSM-2CT3 with BNC-2T3 back card.
–CESM-8T1/E1 with RJ48-T1/E1 and SMB E1 back cards.
–CESM-T3E3
•1:1 redundancy for T3/E3 cards.
•1:N redundancy for T1/E1 service modules.
•Graceful upgrade.
•1000 connections per card, 4000 connections per shelf (T1 service modules).
The MGX 8230 backplane supports a minimum of 1.2 Gbps of non-blocking switching and has a high-end limit of 21 Gbps with the PXM1. Individual line rates can range from DS0 through OC-3.
The MGX 8230 can also support a wide range of services over narrowband and mid-band user interfaces. It maps all the service traffic to and from ATM circuits based on standardized interworking methods.
The MGX 8230 supports up to 64 channelized or non-channelized T1 and E1 interfaces on a single IP + TM multiservice gateway. These interfaces support:
•Frame Relay UNI and NNI
•ATM UNI, NNI, and FUNI
•Frame Relay-to-ATM network interworking
•Frame Relay-to-ATM service interworking
•Circuit emulation services
Frame-based services on T3 and E3 high-speed lines are also supported.
The MGX 8230 also supports Inverse Multiplexing for ATM (IMA) to provide ATM connectivity below T3 or E3 rates via the AUSM-8T1/E1 (AUSM/B).
The modular, software-based system architecture enables it to support new features through downloadable software upgrades or new hardware modules.
The Service Resource Module-3T3 (MGX-SRM-3T3/B), when supported in a future release, will be able to support up to 64 T1 interfaces over its three T2 lines and provide 1:N redundancy for the T1 and E1 cards. This feature is described in the MGX 8230 switch documentation, but is currently not supported by the hardware.
Standards-Based Conversion to ATM
The MGX 8230 converts all user-information into 53-byte ATM cells by using the appropriate ATM Adaptation Layer (AAL) for transport over the ATM backbone network. The individual service modules segment and reassemble (SAR) cells to eliminate system bottlenecks. The following list shows the applicable AAL for each service:
•Circuit emulation services uses AAL1.
•Frame Relay-to-ATM network interworking uses AAL5 and Frame Relay Service Specific Convergence Sub-layer (FR-SSCS).
•Frame Relay-to-ATM service interworking uses both transparent and translation modes to map Frame Relay to native ATM AAL5.
•Frame forwarding uses AAL5.
Refer to the Cisco MGX 8230 Installation and Configuration Guide for further installation and physical descriptions for the MGX 8230 switch.
MGX 8230 Cards
MGX 8230 Processor Switch Module (PXM1)
The MGX 8230 Processor Switch Module (PXM1) performs shelf control and shared-memory switching functions. It also serves as a data processing and ATM interface card. The PXM1 processor module for the MGX 8230 is identical to the PXM1 for the MGX 8250.
Primarily, the MGX 8230 PXM1 controls the switch and provides 1.2 Gbps of non-blocking, shared memory ATM switching and ATM trunking up to OC-12 speed. In addition, the PXM features:
•A 4.0-Gigabyte hard disk drive that holds software, firmware for all the cards, and a substantial amount of other information.
•Environmental monitoring (cabinet temperature, fan speed, and power supply voltages).
•Hot swappable, 1:1 redundancy.
The PXM1 and its two types of back cards make up the required control card set. The following are model numbers of cards supported by the MGX 8230 for this release:
The following are model numbers of cards supported by the MGX 8230 for this release:
•PXM1-4-155, PXM1-1-622, and PXM1-2-T3E3
•PXM-UI (user interface back card)
•MGX-MMF-4-155 (uplink back card)
•MGX-SMFIR-4-155 (uplink back card)
•MGX-SMFLR-4-155 (uplink back card)
•MGX-BNC-2-T3 (uplink back card)
•MGX-BNC-2-E3 (uplink back card)
•MGX-SMFIR-2R-1-622 (uplink back card)
•MGX-SMFLR-1-622 (uplink back card)
PXM1 User Interface Back Card
The PXM1 User Interface card (PXM-UI) provides the MGX 8230 with the several user- interface ports. It mates with an PXM1 through the backplane and is installed in a back card slot (slot 8 or 9). As seen from the back of the MGX 8230, the PXM-UI will plug into the slot that is on the right side of its corresponding PXM1. The user-interface ports provide the following functions:
•User and management interface to an ASCII terminal or workstation
• Network synchronization for the shelf
•Central office-compatible major/minor alarm interface
The PXM UI has the following physical connectors and interfaces:
•RJ-45 T1 clock input—BITS clock source
•RJ-45 Maintenance port—RJ-45 connector, EIA/TIA 232, DTE mode, asynchronous interface, 19200 bits per second, 1 start bit, 1 stop bit, no parity bits.
•RJ-45 Control port— EIA/TIA 232, DTE mode, asynchronous interface, 9600 bits per second, 1 start, 1 stop, no parity.
•RJ-45 LAN port—10BaseT, 802.3 Ethernet
•SMB connector E1 clock input—BITS clock source
•DB-15 female connector for alarm outputs
MGX 8230 OC-3 Uplink Back Card
The MGX 8230 Uplink back card, which mates with a corresponding PXM1 through the backplane, provides the feeder trunk to the MGX switch. This uplink back card can provide either a multi-mode or single-mode fiber OC-3 interface:
•MGX-MMF-4-155 (multi-mode fiber uplink back card)
•MGX-SMFIR-4-155 (single-mode fiber intermediate reach uplink back card)
•MGX-SMFLR-4-155 (single-mode fiber long reach uplink back card)
FRSM Cards
The primary function of the FRSM is to convert between the Frame Relay-formatted data and ATM/AAL5 cell-formatted data. It converts the header format and translates the address for Frame Relay port/DLCIs, ATM-Frame UNI (FUNI) port/frame address, or frame forwarding port, and the ATM virtual connection identifiers (VPI/VCIs).
The MGX 8230 supports the following FRSM models:
•Frame Service Module for T1 (FRSM-8T1)
The FRSM-8T1 card provides interfaces for up to eight T1 lines, each of which can support one
56 Kbps or one Nx64 Kbps FR-UNI, FR-NNI port, ATM-FUNI, or a frame forwarding port.
Note that this unchannelized card cannot be configured to support sub-T rates.
•Frame Service Module for T1, channelized (FRSM-8T1-C)
The FRSM-8T1-C card provides interfaces for up to eight T1 lines, each of which can support up to twenty-four 56 Kbps or Nx64 Kbps FR-UNI, FR-NNI, ATM-FUNI, or frame forwarding ports.
•Frame Service Module for E1 (FRSM-8E1)
The FRSM-8E1 card provides interfaces for up to eight E1 lines, each of which can support one
56 Kbps or one Nx64 Kbps FR-UNI, FR-NNI, ATM-FUNI, or frame forwarding port.
•Frame Service Module for E1, channelized (FRSM-8E1-C)
The FRSM-8E1-C card provides interfaces for up to eight E1 channelized Frame Relay lines, each of which can support multiple (up to thirty-one) 56 Kbps or Nx64 Kbps FR-UNI, FR-NNI, ATM-FUNI, or frame forwarding ports.
•Frame Service Module for T3 and E3 (FRSM-2E3T3)
The FRSM-2E3/T3 card provides interfaces for up to two T3 or E3 Frame Relay lines, each of which can support either two T3 lines (each at 44.736 Mbps) or two E3 lines (each at 34.368 Mbps) FR-UNI, FR-NNI, ATM-FUNI, or frame forwarding ports.
•Frame Service Module for channelized T3 (FRSM-2CT3)
The FRSM-2CT3 card supports interfaces for up to two T3 channelized Fame Relay lines, each of which supports 56 Kbps, 64 Kbps, Nx56 Kbps, Nx64 Kbps, T1 ports for a total of 256 ports that can be freely distributed across the two T3 lines.
•FRSM-HS2
The FRSM-HS2 provides unchannelized Frame Relay service for up to 1000 user-connections over two HSSI lines on the SCSI2-2HSSI back card. The maximum rate for the card is 104 Mbps. Each port can operate in either DTE or DCE mode with incremental rates of N x T1 or N x E1 up to
52 Mbps.
OC-12 Uplink Back Card
For Automatic Protection Switching (APS) requires the "B" model—an SMFLR-1-622/B.
SMFIR-1-622 Back Card
For Automatic Protection Switching (APS) requires the "B" model—an SMFIR-1-622/B.
BNC-2T3 Back Card
BNC-2E3 Back Card
Two versions of the BNC-2E3 card are available. The BNC-2E3A applies to Australia only, and the BNC-2E3 applies to all other sites that require E3 lines on the PXM uplink card.
ATM Universal Service Module
AUSM/B Front Card
AUSM/B Back Cards
The MGX-AUSM/B-8T1 and MGX-AUSM/B-8E1 use the generic 8-port T1 or E1 line modules that operate with the 8-port service modules. The standard T1 version of the back card has eight RJ-48 connectors. The standard versions of the E1 back card have either eight RJ-48 connectors or eight pairs of SMB connectors. The following back cards are compatible with the AUSM/B:
•RJ48-8T1 back card for T1
•RJ48-8E1 back card for E1
•SMB-8E1 back card for E1
Circuit Emulation Service Module 8T1E1
CESM Models
The MGX 8230 supports the following CESM models:
•Circuit Emulation Service Module for T1 (CESM-8T1)
The CESM-8T1 card provides interfaces for up to eight T1 lines, each of which is a 1.544 Mbps structured or unstructured synchronous data stream.
•Circuit Emulation Service Module for E1 (CESM-8E1)
The CESM-8E1 card provides interfaces for up to eight E1 lines, each of which is a 2.048 Mbps structured or unstructured synchronous data stream.
•Circuit Emulation Service Module for T3/E3 (CESM-T3E3)
The CESM-8T1E1 card set consists of the CESM-8T1E1 front card and one of the following back cards:
•RJ48-8T1-LM
•RJ48-8E1-LM
•SMB-8E1-LM
Redundancy Architecture
Since the MGX 8230 chassis is a smaller form factor MGX 8850, most of the redundancy features available in MGX 8850 are available in MGX 8230 chassis. The following is a list of available redundancy features on the MGX 8230 chassis.
•Dual PXM
•Y-cable redundancy on PXM uplink ports
•1:N redundancy for T1/E1 service modules
•Eight cell buses per PXM
•N+1 cooling fan redundancy
•N+1 AC or DC power redundancy (optional)
•1:1 Y-cable redundancy for T3/E3 interfaces
MGX 8230 Management
To give you access for control purposes, the MGX 8230 switch supports high- and low-level user interfaces. You can use the Cisco WAN Manager application (formerly StrataView Plus) for connection management, the CiscoView application for hardware configuration, and a command line interface for low-level control of hardware functionality and connection control. An assortment of ports and protocols supports these user-interfaces. For communicating with the MGX 8230 switch, the control port (SLIP protocol only), the LAN (Ethernet) port, and the in-band ATM connection (feeder application only) all support access by the command line interface (CLI) via Telnet, TFTP, and SNMP protocols.
The downloadable firmware on each card determines the functionality, and you can upgrade functionality by downloading new firmware through a TFTP application on a workstation or a PC.
The current status and configuration parameters of the MGX 8230 modules reside in a Management Information Base (MIB). The firmware on each card updates the MIB as changes in status and configuration occur.
MGX 8250
The Cisco MGX 8250 wide-area edge switch supports:
•Integrated IP+ATM services
•Frame Relay
•IP-based virtual private network
•Video
•Circuit emulation services for private line replacement
It does not support PNNI, despite the fact that some CLI commands may show options for PNNI.
This chapter contains a brief outline of the features of the Cisco MGX 8250 switch. An illustration of the AC-powered version of the switch appears in Figure 3.
Figure 3 MGX 8250 Switch
The Applications of the MGX 8250 Switch
The MGX 8250 switch operates in two operational applications:
•As a feeder, the MGX 8250 switch concentrates narrow-band and medium-band ATM, Frame Relay, and voice into a single, wide-band ATM feeder trunk to an BPX 8600 series switch.
•As a stand-alone node, the MGX 8250 switch concentrates narrow-band and medium-band ATM, Frame Relay, and voice into a single ATM line to at third-party switch. The MGX 8250 interface in this application is a UNI or an NNI.
For a description of how to configure the switches for a particular application, see the MGX 8250 Switch Installation and Configuration Guide.
The switch is also capable of supporting Cisco Multiprotocol Label Switching (MPLS).
Universal Edge Architecture
The MGX 8250 switch can support a wide range of services over narrowband and mid-band user interfaces. It maps all the service traffic to and from ATM by using standardized interworking methods.
The supported interfaces for user-traffic are:
•Frame Relay UNI on T3, E3, HSSI, T1, and E1 lines
•ATM UNI and FUNI and optional inverse multiplexing for ATM (IMA)
•Frame Relay to ATM network interworking and service interworking
•Circuit emulation services (T1/E1 and T3/E3)
The optional Service Resource Module-3T3 (MGX-SRM-3T3/B) can support up to 80 T1 interfaces over its three T3 lines and provide 1:N redundancy for the T1 and E1 cards.
The modular, software-based system architecture enables the switch to support new features through downloadable software upgrades or new hardware modules.
The MGX 8250 backplane supports a minimum of 1.2 Gbps of non-blocking switching. Individual line rates range from DS0 through OC-12.
Standards-Based Conversion to ATM
The MGX 8250 switch converts all user information into 53-byte ATM cells by using the appropriate ATM Adaptation Layer (AAL) for transport over the ATM backbone network. The individual service modules segment and reassemble (SAR) cells to eliminate system bottlenecks. The following list shows the applicable AAL for each service:
•Circuit emulation services uses AAL1.
•Frame Relay-to-ATM network interworking uses AAL5 and Frame Relay Service Specific Convergence Sub-layer (FR-SSCS).
•Frame Relay-to-ATM service interworking uses both transparent and translation modes to map Frame Relay to native ATM AAL5.
•Frame forwarding uses AAL5.
MGX 8250 Cards
The MGX 8250 switch supports core cards and service modules. The Processor Switching Module (PXM) and optional Service Resource Module (SRM) are core cards. In addition to the PXM being a core card, it is also part of a a card set. A card set consists of a front card, a back card, and a daughter card. Service modules are not combined in this manner and are never part of a card set. Instead, service modules provide the interface to the transport technologies of the CPE—Frame Relay, ATM, and so on. The MGX 8250 enclosure contains up to 24 service modules (I/O cards) and 4 optional Service Redundancy Modules (SRMs) provide redundancy. A card set consists of a front card with its attached daughter card and a back card (or line module). The front card contains the processing intelligence and, on the daughter card, the firmware that distinguishes the interface (OC-3, T3, E3, and so on). The back card is a simple card that provides the electrical interface for one or more lines of a particular type. The MGX 8250 front and back cards are the:
•Processor Switching Module (PXM1)
This front card controls the switch and supports external interfaces for user-access and trunking or UNI ports. The back cards consist of a user interface card (PXM-UI) and a broadband network module (see subsequent list items).
•Processor Switch Module User Interface (PXM1-UI)
The PXM1-UI is the user interface card that has various types of ports to let you access and control the switch.
•Broadband Network Module (MGX-SMFIR-1-622 and MGX-SMFLR-1-622)
The SMFIR-1-622 is a broadband network module for the PXM and provides a SONET OC12/STM4 ATM interface at 622 Mbps.
•Broadband Network Module (MGX-MMF-4-155)
The MMF-4-155 is a broadband network module for the PXM and provides four SONET OC3/STM1 ATM interfaces at 155 Mbps.
•Broadband Network Module (MGX-BNC-2T3)
The MGX-BNC-2T3 is a broadband network module for the PXM and provides two T3 ATM interfaces.
•Broadband Network Module (MGX-BNC-2E3)
The MGX-BNC-2E3 is a broadband network module for the PXM and provides two E3 ATM interfaces. A version for Australia, New Zealand, and elsewhere is available (MGX-BNC-2E3A).
•Frame Service Module for T3 and E3 (MGX-FRSM-2E3T3)
The MGX-FRSM-2E3/T3 provides interfaces for up to two T3 or E3 Frame Relay lines, each of which can support either two T3 lines (each at 44.736 Mbps) or two E3 lines (each at 34.368Mbps) FR-UNI, ATM-FUNI, or frame forwarding port.
•Frame Service Module for channelized T3 (MGX-FRSM-2CT3)
The MGX-FRSM-2CT3 supports interfaces for up to two T3 channelized Frame Relay lines, each of which supports 56 Kbps, 64 Kbps, Nx56 Kbps, Nx64 Kbps, T1 ports for a total of 256 ports that can be freely distributed across the two T3 lines.
•Frame Service Module for unchannelized HSSI (MGX-HS2/B)
The MGX-HS2/B supports interfaces for 2 unchannelized HSSI lines, each of which supports approximately 51 Mbps. With both lines operating, maximum throughput is 70 Mbps.
•Frame Service Module for T1 (AX-FRSM-8T1)
The AX-FRSM-8T1 provides interfaces for up to eight T1 lines, each of which can support one
56 Kbps or one Nx64 Kbps FR-UNI, ATM-FUNI, or a frame forwarding port. Note that this unchannelized card cannot be configured to support sub-T rates.
•Frame Service Module for T1, channelized (AX-FRSM-8T1c)
The AX-FRSM-8T1c provides interfaces for up to eight T1 lines, each of which can support up to 24 56 Kbps or N x 64 Kbps FR-UNI, ATM-FUNI, or frame forwarding port.
•Frame Service Module for E1 (AX-FRSM-8E1)
The AX-FRSM-8E1 provides interfaces for up to eight E1 lines, each of which can support one
56 Kbps or one N x 64 Kbps FR-UNI, ATM-FUNI, or frame forwarding port.
•Frame Service Module for E1, channelized (AX-FRSM-8E1c)
The AX-FRSM-8E1c provides interfaces for up to 8 E1 channelized Frame Relay lines Each line can support N x 64-Kbps or (up to 31) 56-Kbps FR-UNI, ATM-FUNI, or frame forwarding ports.
•ATM UNI Service Module for T1 (MGX-AUSM/B-8T1)
The MGX-AUSM/B-8T1 provides interfaces for up to eight T1 lines. You can group N x T1 lines to form a single, logical interface (IMA).
•ATM UNI Service Module for E1 (MGX-AUSM/B-8E1)
The MGX-AUSM/B-8E1 provides interfaces for up to eight E1 lines. You can group N x E1 lines to form a single, logical interface (IMA).
•Circuit Emulation Service Module for T1 (AX-CESM-8T1)
The AX-CESM-8T1 provides interfaces for up to eight T1 lines, each of which is a 1.544 Mbps structured or unstructured synchronous data stream.
•Circuit Emulation Service Module for E1 (AX-CESM-8E1)
The AX-CESM-8E1 provides interfaces for up to eight E1 lines, each of which is a 2.048 Mbps structured or unstructured synchronous data stream.
•Route Processor Module (RPM)
The RPM is a Cisco 7200 series router redesigned as a double-height card. Each RPM uses two single-height back cards. The back-card types are single-port Fast Ethernet, four-port Ethernet, and single-port (FDDI).
•Service Resource Module (MGX-SRM-3T3/B)
The optional MGX-SRM-3T3/B provides bit error rate testing (BERT), 1:N redundancy for T1 and E1 service modules, and a demultiplexing function for T1 service called bulk mode.
•Smart Serial Interface FRSM-HS1/B 12IN1
A multipersonality back card that supports either X.21 or V.35 interface.
MGX 8250 Management
To give you access for control purposes, the MGX 8250 switch supports high- and low-level user interfaces. You can use the Cisco WAN Manager application (formerly StrataView Plus) for connection management, the CiscoView application for hardware configuration, and a command line interface for low-level control of hardware functionality and connection control. An assortment of ports and protocols supports these user-interfaces. For communicating with the MGX 8250 switch, the control port (SLIP protocol only), the LAN (Ethernet) port, and the in-band ATM connection (feeder application only) all support access by the command line interface (CLI) via Telnet, TFTP, and SNMP protocols.
The downloadable firmware on each card determines the functionality, and you can upgrade functionality by downloading new firmware through a TFTP application on a workstation or a PC.
The current status and configuration parameters of the MGX 8250 modules reside in a Management Information Base (MIB). The firmware on each card updates the MIB as changes in status and configuration occur.
Continued Support for the MGX 8850
The Cisco MGX 8850 wide area edge switch supports:
•Integrated IP+ATM services
•Frame Relay
•IP-based virtual private network
•Video
•Circuit emulation services for private line replacement
It does not support PNNI, despite the fact that some CLI commands may show options for PNNI.
An illustration of the AC-powered version of the switch appears in Figure 4.
Figure 4 MGX 8850 Switch
The Applications of the MGX 8850 Switch
The MGX 8850 switch operates in two operational applications:
•As a feeder, the MGX 8850 switch concentrates narrow-band and medium-band ATM, Frame Relay, and voice into a single, wide-band ATM feeder trunk to an BPX 8600 series switch.
•As a stand-alone node, the MGX 8850 switch concentrates narrow-band and medium-band ATM, Frame Relay, and voice into a single ATM line to at third-party switch. The MGX 8850 interface in this application is a UNI or an NNI.
For a description of how to configure the switches for a particular application, see the MGX 8250 Switch Installation and Configuration Guide.
The switch is also capable of supporting Cisco Multiprotocol Label Switching (MPLS).
Universal Edge Architecture
The MGX 8850 switch can support a wide range of services over narrowband and mid-band user interfaces. It maps all the service traffic to and from ATM by using standardized interworking methods. When the MGX 8850 switch operates as a feeder, it uses a single port to communicate the aggregated traffic over an ATM interface with an MGX 8850 or BPX 8600 series switch.
The supported interfaces for user-traffic are:
•Frame Relay UNI on T3, E3, HSSI, T1, and E1 lines
•ATM UNI and FUNI and optional inverse multiplexing for ATM (IMA)
•Frame Relay to ATM network interworking and service interworking
•Circuit emulation services
The optional Service Resource Module-3T3 (MGX-SRM-3T3/B) can support up to 80 T1 interfaces over its 3 T3 lines and provide 1:N redundancy for the T1 and E1 cards.
The modular, software-based system architecture enables the switch to support new features through downloadable software upgrades or new hardware modules.
The MGX 8850 backplane supports a minimum of 1.2 Gbps of non-blocking switching up to
45 Gbps. Individual line rates range from DS0 through OC-12.
Standards-Based Conversion to ATM
The MGX 8850 switch converts all user-information into 53-byte ATM cells by using the appropriate ATM Adaptation Layer (AAL) for transport over the ATM backbone network. The individual service modules segment and reassemble (SAR) cells to eliminate system bottlenecks. The following list shows the applicable AAL for each service:
•Circuit emulation services uses AAL1.
•Frame Relay-to-ATM network interworking uses AAL5 and Frame Relay Service Specific Convergence Sub-layer (FR-SSCS).
•Frame Relay-to-ATM service interworking uses both transparent and translation modes to map Frame Relay to native ATM AAL5.
•Frame forwarding uses AAL5.
MGX 8850 Cards
The MGX 8850 switch supports two types of card sets: the core cards (or core modules) and service modules. The Processor Switching Module (PXM) and optional Service Resource Module (SRM) are core cards. The service modules provide the interface to the transport technologies of the CPE—Frame Relay, ATM, and so on. The MGX 8850 enclosure contains up to 24 service modules (I/O cards) and 4 optional Service Redundancy Modules (SRMs) provide redundancy. A card set consists of a front card with its attached daughter card and a back card (or line module). The front card contains the processing intelligence and, on the daughter card, the firmware that distinguishes the interface (OC-3, T3, E3, and so on). The back card is a simple card that provides the electrical interface for one or more lines of a particular type. The MGX 8850 front and back cards are the:
•Processor Switching Module (PXM1)
This front card controls the switch and supports external interfaces for user-access and trunking or UNI ports. The back cards consist of a user interface card (PXM-UI) and a broadband network module (see subsequent list items).
•Processor Switch Module User Interface (PXM1-UI)
The PXM1-UI is the user interface card that has various types of ports to let you access and control the switch.
•Broadband Network Module (MGX-SMFIR-1-622 and MGX-SMFLR-1-622)
The SMFIR-1-622 is a broadband network module for the PXM and provides a SONET OC12/STM4 ATM interface at 622 Mbps.
•Broadband Network Module (MGX-MMF-4-155)
The MMF-4-155 is a broadband network module for the PXM and provides four SONET OC3/STM1 ATM interfaces at 155 Mbps.
•Broadband Network Module (MGX-BNC-2T3)
The MGX-BNC-2T3 is a broadband network module for the PXM and provides two T3 ATM interfaces.
•Broadband Network Module (MGX-BNC-2E3)
The MGX-BNC-2E3 is a broadband network module for the PXM and provides two E3 ATM interfaces. A version for Australia, New Zealand, and elsewhere is available (MGX-BNC-2E3A).
•Frame Service Module for T3 and E3 (MGX-FRSM-2E3T3)
The MGX-FRSM-2E3/T3 provides interfaces for up to two T3 or E3 Frame Relay lines, each of which can support either two T3 lines (each at 44.736 Mbps) or two E3 lines (each at 34.368Mbps) FR-UNI, ATM-FUNI, or frame forwarding port.
•Frame Service Module for channelized T3 (MGX-FRSM-2CT3)
The MGX-FRSM-2CT3 supports interfaces for up to two T3 channelized Frame Relay lines, each of which supports 56 Kbps, 64 Kbps, Nx56 Kbps, Nx64 Kbps, T1 ports for a total of 256 ports that can be freely distributed across the two T3 lines.
•Frame Service Module for unchannelized HSSI (MGX-HS2/B)
The MGX-HS2/B supports interfaces for two unchannelized HSSI lines, each of which supports approximately 51 Mbps. With both lines operating, maximum throughput is 70 Mbps.
•Frame Service Module for T1 (AX-FRSM-8T1)
The AX-FRSM-8T1 provides interfaces for up to eight T1 lines, each of which can support one
56 Kbps or one Nx64 Kbps FR-UNI, ATM-FUNI, or a frame forwarding port.
•Frame Service Module for T1, channelized (AX-FRSM-8T1c)
The AX-FRSM-8T1c provides interfaces for up to eight T1 lines, each of which can support up to 24 56 Kbps or N x 64 Kbps FR-UNI, ATM-FUNI, or frame forwarding port.
•Frame Service Module for E1 (AX-FRSM-8E1)
The AX-FRSM-8E1 provides interfaces for up to eight E1 lines, each of which can support one
56 Kbps or one N x 64 Kbps FR-UNI, ATM-FUNI, or frame forwarding port.
•Frame Service Module for E1, channelized (AX-FRSM-8E1c)
The AX-FRSM-8E1c provides interfaces for up to eight E1 channelized Frame Relay lines Each line can support N x 64-Kbps or (up to 31) 56-Kbps FR-UNI, ATM-FUNI, or frame forwarding ports.
•ATM UNI Service Module for T1 (MGX-AUSM/B-8T1)
The MGX-AUSM/B-8T1 provides interfaces for up to eight T1 lines. You can group N x T1 lines to form a single, logical interface (IMA).
•ATM UNI Service Module for E1 (MGX-AUSM/B-8E1)
The MGX-AUSM/B-8E1 provides interfaces for up to eight E1 lines. You can group N x E1 lines to form a single, logical interface (IMA).
•Circuit Emulation Service Module for T1 (AX-CESM-8T1)
The AX-CESM-8T1 provides interfaces for up to eight T1 lines, each of which is a 1.544 Mbps structured or unstructured synchronous data stream.
•Circuit Emulation Service Module for E1 (AX-CESM-8E1)
The AX-CESM-8E1 provides interfaces for up to eight E1 lines, each of which is a 2.048 Mbps structured or unstructured synchronous data stream.
•Route Processor Module (RPM)
The RPM is a Cisco 7200 series router redesigned as a double-height card. Each RPM uses two single-height back cards. The back-card types are: single port Fast Ethernet, four port Ethernet, and single-port (FDDI).
•Service Resource Module (MGX-SRM-3T3/B)
The optional MGX-SRM-3T3/B provides bit error rate testing (BERT), 1:N redundancy for T1 and E1 service modules, and a demultiplexing function for T1 service called bulk mode.
•Smart Serial Interface FRSM-HS1/B 12IN1
A multi-personality back card that supports either X.21 or V.35 interface.
MGX 8850 Management
To give you access for control purposes, the MGX 8850 switch supports high- and low-level user interfaces. You can use the Cisco WAN Manager application (formerly StrataView Plus) for connection management, the CiscoView application for hardware configuration, and a command line interface for low-level control of hardware functionality and connection control. An assortment of ports and protocols supports these user-interfaces. For communicating with the MGX 8850 switch, the control port (SLIP protocol only), the LAN (Ethernet) port, and the in-band ATM connection (feeder application only) all support access by the command line interface (CLI) via Telnet, TFTP, and SNMP protocols.
The downloadable firmware on each card determines the functionality, and you can upgrade functionality by downloading new firmware through a TFTP application on a workstation or a PC.
The current status and configuration parameters of the MGX 8850 modules reside in a Management Information Base (MIB). The firmware on each card updates the MIB as changes in status and configuration occur.
Features Introduced in Release 1.1.23
MGX 8850 Release 1.1.23 is a maintenance release of Release 1.1.22. In addition, it introduces the following new features:
•Dynamic subrate FRSM-T3E3.
•Clrsmcnf/savesmcnf/restoresmcnf feature support for VISM.
•Switchcc and Softswitch performance enhancement (See Problems Fixed).
•New database integrity check commands.
•Model # recognition for MGX 8230 and MGX 8250.
Release 1.1.32 MGX 8850, MGX 8230, and MGX 8250 Hardware
MGX 8850 is a 45 Gbps backplane with 1.2 Gbps switching fabric for Release 1.1.32. The same backplane is used with different switching fabric cards (1.2, 45 Gbps) to achieve scalability. MGX 8850 Release 1.1.21 hardware components and their revisions that are supported are as follows:
Front Card Model #
|
Rev #
|
Back Card Model #
|
Rev #
|
MGX 8850 Chassis
|
A
|
|
|
MGX 8230 Chassis
|
A
|
|
|
MGX 8250 Chassis
|
A
|
|
|
MGX-DC power supply
MGX-AC1 power supply
MGX-AC2-2 power supply
PS-1200-AC power supply
|
A
A
A
A
|
|
|
MGX-SRM-3T3/B
|
B
|
MGX-BNC-3T3-M
|
A
|
PXM1
|
H
|
PXM-UI
|
A
|
PXM 1-2-T3E3
|
H
|
PXM-UI
MGX-BNC-2E3
MGX-BNC-2E3A
MGX-BNC-2T3
|
A
A
A
A
|
PXM 1-4-155
|
J
|
PXM-UI
MGX-MMF-4-155
MGX-SMFIR-4-155
MGX-SMFLR-4-155
|
A
A
A
A
|
PXM 1-1-622
|
H
|
PXM-UI
MGX-SMFIR-1-622
MGX-SMFLR-1-622
|
A
A
A
|
MGX-RPM 64M/B
|
A
|
MGX-RJ45-FE
MGX-MMF-FE
MGX-RJ45-4E
MGX-MMF-FDDI
MGX-SMF-FDDI
MGX-MMF-FDDI/FD
MGX-SMF-FDDI/FD
|
A
A
A
A
A
A
A
|
MGX RPM-128M/B
|
A
|
MGX-RJ45-FE
MGX-MMF-FE
MGX-RJ45-4E
MGX-MMF-FDDI
MGX-SMF-FDDI
MGX-MMF-FDDI/FD
MGX-SMF-FDDI/FD
|
A
A
A
A
A
A
A
|
AX-CESM-8E1
|
B
|
AX-SMB-8E1
AX-RJ48-8E1
AX-R-SMB-8E1
AX-R-RJ48-8E1
|
B
C
B
B
|
AX-CESM-8T1
|
B
|
AX-RJ48-8T1
AX-R-RJ48-8T1
|
B
B
|
MGX-AUSM-8E1/B
|
A
|
AX-SMB-8E1
AX-RJ48-8E1
AX-R-SMB-8E1
AX-R-RJ48-8E1
|
B
C
B
B
|
MGX-AUSM-8T1/B
|
A
|
AX-RJ48-8T1
AX-R-RJ48-8T1
|
B
B
|
AX-FRSM-8E1
|
B
|
AX-SMB-8E1
AX-RJ48-8E1
AX-R-SMB-8E1
AX-R-RJ48-8E1
|
B
C
B
B
|
MGX-VISM-8T1
|
B
|
AX-RJ48-8T1
AX-R-RJ48-8T1
|
B
B
|
MGX-VISM-8E1
|
B
|
AX-SMB-8E1
AX-RJ48-8E1
AX-R-SMB-8E1
AX-R-RJ48-8E1
|
B
C
B
B
|
AX-FRSM-8E1-C
|
B
|
AX-SMB-8E1
AX-RJ48-8E1
AX-R-SMB-8E1
AX-R-RJ48-8E1
|
B
C
B
B
|
AX-FRSM-8T1
|
B
|
AX-RJ48-8T1
AX-R-RJ48-8T1
|
B
B
|
AX-FRSM-8T1-C
|
B
|
AX-RJ48-8T1
AX-R-RJ48-8T1
|
B
B
|
MGX-FRSM-HS2/B
|
B
|
MGX-SCSCI2-2HSSI/B
|
A
|
MGX-FRSM-2CT3
|
C
|
MGX-BNC-2T3
|
A
|
MGX-FRSM-2T3E3
|
C
|
MGX-BNC-2E3
MGX-BNC-2E3A
|
A
A
|
MGX-FRSM-HS1/B
|
A
|
MGX-12IN1-4S
|
A
|
MGX-CESM-T3E3
|
C
|
MGX-BNC-2T3
MGX-BNC-2E3
MGX-BNC-2E3A
|
A
A
A
|
Support for embedded Cisco IOS router (Router Processor Module - [RPM])
•The RPM is an embedded Cisco IOS router with integrated ATM Deluxe Port Adapter and cell bus controller ASIC for internal connections to the backplane cell bus. A number of port adapters (back cards) can be configured with the RPM front card (FDDI, Ethernet, Fast Ethernet).
–4E Adapter
–FE Adapter (UTP, MMF)
–FDDI Adapter (full duplex, half duplex, SMF, MMF)
MGX 8220 Hardware Not Supported on Release 1.1.32 of the MGX 8850
The following cards are not supported in Release 1.1.32:
•AX-SRM-T1E1
•AX-SMB-8E1
•AX-R-SMD-8E1
•AX-RJ48-8E1
•AX-R-RJ48-8E1
MGX 8220 Hardware That Has Been Superseded on the MGX 8850 by MGX 8850-Specific Hardware
• AX-SRM-3T3-A and AX-BNC-3T3 card set
The MGX-SRM-3T3-C front card replaces the original AX-SRM-3T3-A front card and the MGX-BNC-3T3 back card replaces the original AX-BNC-3T3 back card. This change allows the use of slots 9, 10, 25, and 26 for 1:N redundancy and BERT in the MGX 8850 chassis. Both the AX-SRM-3T3-A/AX-BNC-3T3 card set and the MGX-SRM-3T3-C/MGX-BNC-3T3 card set are supported on the MGX 8220.
New card should have enabled use of bulk distribution in slots 9 and 10. 1:N redundancy should have been supported in those slots with the model A card.
•AX-SCSI2-2HSSI
Superseded by the MGX-SCSCI2-2HSSI/B, which works with the MGX-FRSM-HS2 front card. A V.35 interface is supported on the MGX-FRSM-HS1/B in this release.
•AX-IMATM
Superseded by MGX-AUSM-8T1/B and MGX-AUSM-8E1/B.
•AX-IMATM-B
Superseded by MGX-AUSM-8T1/B and MGX-AUSM-8E1/B.
MGX 8220 Hardware Not Supported on the MGX 8850
•AX-FRASM-8T1
•All four-port MGX 8220 cards
•AX-AUSM-8T1
•AX-AUSM-8E1
Software Platform Features
MGX 8850 provides high-speed native ATM interfaces, which can be configured as ATM UNI ports or trunks.
Support for 1:N and 1:1 Service Module Redundancy, as indicated in the following table:
Front Card Model #
|
Redundancy Supported
|
MGX-RPM-64M/B
|
No redundancy
|
MGX-RPM-128M/B
|
No redundancy
|
MGX-AUSM-8E1/B
|
1:N redundancy
|
MGX-AUSM-8T1/B
|
1:N redundancy
|
AX-CESM-8E1
|
1:N redundancy
|
AX-CESM-8T1
|
1:N redundancy
|
MGX-CESM-2T3E3
|
1:1 redundancy
|
AX-FRSM-8E1
|
1:N redundancy
|
AX-FRSM-8E1-C
|
1:N redundancy
|
AX-FRSM-8T1
|
1:N redundancy
|
AX-FRSM-8T1-C
|
1:N redundancy
|
MGX-FRSM-HS2
|
1:1 redundancy
|
MGX-FRSM-2CT3
|
1:1 redundancy
|
MGX-FRSM-2T3E3
|
1:1 redundancy
|
MGX-FRSM-HS1/B
|
No redundancy
|
MGX-T3E3
|
1:1 redundancy
|
MGX-VISM-8T1
|
1:N redundancy (bulk mode support for T1 lines only)
|
MGX-VISM-8E1
|
1:N redundancy (bulk mode support for T1 lines only)
|
Support for Bulk Distribution using SRM-3T3-C card.
Service module and PXM upgrades.
Features Not Supported in This Release
•RPM 1:1 redundancy
•RPM statistics
•Layer 2 support as an AutoRoute routing node
•SRM T1E1
•IPX end-points with the MGX 8850
•E1 users circuits
•T1/CAS backhaul
•Interworking with SGCP 1.1+ compliant call agent (Bellcore CA SM1.5)
•Interworking with Cisco 3810
•G.726 and G.729 voice compression
•G729b voice activity detection
•Voice Circuit Admission Control (CAC)
•Bearer continuity testing
•Ring back tone on Ground Start
•Separate PVCs for signaling and bearer channels
Note Code for the above features may be included in the VISM code image. However, no specific mechanism has been included to prevent the use of these unsupported features. If the user attempts to use these unsupported features, there is no guarantee that the features will operate correctly.
Major Network Management Features
•CWM Connection Management
•CiscoView support for equipment management
•CLI support
•Service MIB support
•Connection Management for connections to RPM with associated CM GUI support
•Topology subsystem enhancements to support the MGX 8850 as a stand-alone switch
•Statistics
For more details refer to the CWM Release 9.2.07 release notes part number 78-6659-07.
Connection Limits
•Up to 4000 connections per VHS card.
•Up to 1000 connections per eight-port card (up to 898 per port with LMI enabled).
•Up to 200 connections per HS1 card.
•Up to 12000 connections per shelf.
SNMP MIB
The SNMP MGX 8850 MIB is being provided with the delivery of Release 1.1.32 of the MGX 8850 software on CCO. The MIB is in standard ASN.1 format and is located in the same directory within CCO. These files may be compiled with most standards-based MIB compilers. For changes in this MIB from Release 1.1.25, please refer to the MIB release notes on CCO. The following files are required:
•BASIS-GENERIC-MIB.my
•BASIS-MIB.my
•CISCO-WAN-AXIPOP-MIB.my
•BASIS-RAS-DISK-MIB.my
•BASIS-SHELF-MIB.my
•CISCO-WAN-MG-MIB.my
•cardGeneric1.my
•errStatus.my
•CISCO-MGX82XX-DSX1-MIB.my
•GENERICOBJECT-MIB.my
•CISCO-MGX82XX-DSX3-MIB.my
•RTM-MIB.my
•CISCO-MGX82XX-SONET-MIB.my
•vismLapd.my
•CISCO-MGX82XX-TRAPS-MIB.my
•vismRudpSession.my
Notes & Cautions
In Release 1.1.32, the default UPC connection parameters on the PXM have changed. The default PCR is 50 cps, and the default for policing is "enabled." These settings are insufficient for running RPM ISIS protocol over the connection, and with such settings, the ISIS protocol will fail. The PCR value needs to be increased, depending upon the number of interfaces configured for ISIS on the RPM. CLI modification and changes in this release.
Depending upon your connection type, you can use the following CLIs to modify the PCR parameter.
•cnfupccbr
•cnfupcvbr
•cnfupcabr
•cnfupcubr
ForeSight and Standard ABR Coexistence Guidelines
ForeSight is similar to the rate-based ABR control system in TM 4.0 in that they both use Rate up and Rate down messages sent to the source of the connection to control the rate a connection runs at, based on congestion within the switches along that connections path. Both systems use Resource Management (RM) cells to pass these messages. There are differences between the two systems that need to be considered.
RM Cell Generation
ForeSight is a destination-driven congestion notification mechanism. The destination switch is responsible for generating the RM cells, which defaults to every 100 ms. This means that any rate modifications at the source end happen approximately every 100 ms, and the time delay between the actual congestion at the destination and the source getting to know about it could be 100 ms.
In standard ABR a source generates FRM cells every (nRM) cell intervals, where n is configurable. These are used to pass congestion information along to the destination switch, which then uses this information to generate BRM (Backward RM cells) back to the source A further consideration is that the actual user data flow will be lower for an equivalent rate due to the additional RM cells. Therefore, the more traffic being generated on a connection at any one time, the faster the feedback will be to the source.
There is also a TRM parameter which states that if no RM cells have been generated after this time has passed then one will automatically be sent. Depending upon the speed it is running at, an ABR connection may therefore react faster or slower to congestion than the equivalent ForeSight connection. (for example, if an ABR connection runs at 100 cells per second, and nRM is 32, then approximately three RM cells will be generated per second, or once every 300 msecs. If it runs at 1000 cps then an RM cell would be generated approximately every 30 msecs. In both cases, the equivalent ForeSight connection would generate an RM cell every 100 msec.)
Reaction to Feedback Messages - Rate Up
In ForeSight, in response to a Rate Up cell from the destination, the source increases its rate by a percentage of the MIR for that connection. If we call this percentage the rate increase percentage (RIP), then RIP is configurable at the card level (the default is 10 percent). In the case where MIR is low, the ForeSight rate increase will be slow as it has to increase as a percentage of MIR (rather than CIR).
On a standard ABR connection, in the event of available bandwidth (no congestion) the source increases its rate by a factor of (RIF*PCR). This means the rate increase step sizes are much bigger than for ForeSight for larger values of RIF (RIF has a range of 1/2, 1/4,....,1/32768). If RIF is not configured properly then standard ABR will ramp up its rate much faster and to a higher value. This is aided by the fact that the step sizes are bigger and the step frequency is higher in comparison with ForeSight.
Reaction to feedback messages - Rate Down
In ForeSight on receiving a Rate Down cell from the remote end, the source reduces its current rate (actual cell rate) by 13 percent. The rate decrease percentage (RDP). RDP is configurable at the card level.
In standard ABR, rate decrease is by an amount (RDF*ACR). Currently, the default value of RDF is 1/16 (6.25 percent). This means when this connection co-exists with ForeSight connections, in the event of congestion ForeSight connection reduces its rate by 13 percent whereas standard ABR connection reduces its rate by only 6.25 percent. Therefore, in the case of co-existence, if we need to approximate the same behavior across the two connection types, then RDF should be changed to 1/8, so that both connections ramp down by the same amount (13 percen).
Fast-Down
In ForeSight if the destination egress port drops any data due to congestion then the destination sends a Fast Rate Down cell. Also, if a frame cannot be reassembled at the egress due to a lost cell somewhere in the network, a Fast-down will be generated. On reception of Fast Rate Down the source reduces its current rate by 50 percent (this is again a card-level configurable parameter).
Standard ABR does not distinguish between drops and the ECN/EFCI threshold being exceeded. This means that, in case of drops in the egress port queue, a standard ABR connection rate reduces by only (RDF*ACR) but the ForeSight connection rate reduces by (ACR*0.5). Therefore, in the case of co-existence, if we need to approximate the same behavior across the two connection types then Fast Down could be effectively disabled by configuring the reaction to be 13 percent rate down instead of 50 percent.
Guidelines
The two systems will work together within the network, but as the above description suggests, if the differences between the two systems are not taken into consideration, then a ForeSight connection and an ABR connection with the same configuration parameters will not behave the same way within the network.
ABR and ForeSight provide a mechanism for distributing excess bandwidth between connections over and above the minimum rate, therefore if these guidelines are not taken into consideration then the allocation of this excess bandwidth may be biased toward connections running one of these algorithms over connections running the other.
If this is a requirement, the following guidelines may be useful, assuming ForeSight is set to defaults except for Fast Rate Down which is set for 13 percent.
1. Nrm: Nrm needs to be set at a value whereby the approximate RM cell generation is
100 milliseconds, to match that of ForeSight. This calculation is based on the expected average, or sustained, cell rate of the connection. However, if the (potential) fast-down messages from ForeSight are left to equate to 50 percent rate down, then an estimate of how often this may occur needs to be made and factored into the equation. If the connection receives Fast-down messages, then this would make the ForeSight connection react faster than the equivalent ABR connection to congestion. To compensate for this, Nrm needs to be set at a value of less than 100 msecs, a suggested value to aim for is between 60-70 msecs (this would be approximate as n is configurable in steps of 2**n). This would mean that, in the event of congestion, the ABR connection would start to react faster.
2. RIF: Rate increase factor is a factor of PCR in ABR and MCR in ForeSight. The default RIF for ForeSight is MCR*.10. Therefore, RIF should be configured so that (PCR*RIF) approximates MCR*0.1. If Fast-Down is still effectively enabled, then PCR*RIF should approximate MCR*0.62 to compensate.
3. RDF: (Rate Decrease Factor) RDF should be 1/8. This approximates to 13 percent that ForeSight uses.
The following worked examples may help explain this further
Assume a network is currently running ForeSight with default parameters, and supports the following four connection type, where CIR = MIR, PIR = port speed, and QIR = PIR:
T1 Port Speed 64K CIR
Example:
CIR = MIR = 64K
PIR = QIR = port speed = 1544
Fastdown = 13%
(The calculation used to convert between frame based parameters (CIR, PIR, and so on.) and their equivalent cell-based parameters is FR_param *3/800. This allows for cell overheads, and so on. based on frame sizes of 100 octets.)
CIR = MIR = (64000*3/800) = 240 cps
PIR = QIR = (1544 *3/800) = 5790 cps
ForeSight ABR
Rate-up equals (240*.1) = 24 cps RIF equals x where (1590/x) = 24 cps
X needs to be approx 200
RIF equals 256 (nearest factor of 2)
RDF equals 13% RDF = 1/8
Nrm equals 100 msecs Nrm equals 32
RM cells will be generated somewhere between 6 (5790 cps approx equal to 32 cells per 6 msecs) and 133 msecs (240 cps approx equal to 32 cells every 133 msecs) depending on ACR.
CLI Modification and Changes in this Release
dspfail <slotno>
shows all failed connections per slot basis
dspfabit <slotno>
shows all A-bit failed connections per slot basis
dsplmiloop
shows if LMI loop is present
chkslotcon <slotno>
checks database consistency per slot basis
chkportcon <slotno> <portno>
checks database consistency per slot basis
Chkcon <slot.port.vpi.vci>
checks database consistency per connection basis
dspbecnt
displays bit error count
CLI modification and changes in previous releases:
•A few modifications have been made to the IP configuration commands. (cnfifip and bootChange) See CLI Change section:
–the cnfifip command has an additional option to up/down one of the IP interfaces (Ethernet, SLIP, ATM) dynamically. No reboot is required to up/down interface. Turned-down interfaces are persistent across resets.
–cnfifip is now an active only command.
–dspifip will now display the state of each interface and indicate if it is up or down.
–bootChange now checks the IP values set and will complain if it detects incorrect values.
–bootChange values are sent and updated on standby card automatically. Both bootlines are kept in sync.
–bootChange command is now an active-only command from CLI.
–cnfenetgw command has been added to establish the Ethernet gateway route permanently (command is active only).
–dspenetgw command will display Ethernet gateway address set.
–A shelf can now either have one or two IP addresses for Ethernet. The shelf IP address set using cnfifip will always be the active card IP address. The bootChange IP address will be used for the standby card and backup boot if it is different than the shelf IP address. If the bootChange IP address is same as the shelf IP address, then the Ethernet interface on the standby card or in backup boot will be left in the down state.
–If the "255.255.255.252" netmask is used for the SLIP interface, the PXM will automatically add host route for its peer whenever the interface is turned ON
–If the FW fails to reach the CLI prompt or comes up in backup boot, the Ethernet interface could be down if the shelf IP address and boot change address are the same. In this case the bootChange command could be used from the shell to set another IP address and then usrEnetEnable should be called to activate that address (see example).
–Commands and Examples
–cnfifip:
Syntax:
cnfifip "Interface IPaddr [NetMask [BroadcastAddr]]"
or cnfifip "Interface Flag"
Interface -- 26/28/37 (26:Ethernet 28:SLIP 37:ATM)
or Ethernet/SLIP/ATM
IP_Addr -- <n>.<n>.<n>.<n> (<n>: integer 0..255)
Net_Mask -- <n>.<n>.<n>.<n> (<n>: integer 0..255)
BroadcastAddr -- <n>.<n>.<n>.<n>
(<n>: integer 0..255)
Flag -- a string "UP" or "DOWN"
Example:
> cnfifip atm 192.9.200.1 255.255.255.128
This configures the ATM interface and brings it UP.
> cnfifip atm up
This will bring up the ATM interface with current information in the database.
> cnfifip atm down
This will bring down the ATM interface and preserve the information in the database.
–delifip
Syntax:
delifip Interface
Interface -- 26/28/37 (26:Ethernet 28:SLIP 37:ATM) or Ethernet/SLIP/ATM
Example:
> delifip 37
This will bring down the ATM interface and delete the information in the database.
–dspifip:
Example:
Interface Flag IP Address Subnetmask Broadcast Addr
--------------- ---- --------------- --------------- ---------------
Ethernet/lnPci0 UP 172.29.37.77 255.255.255.0 172.29.37.255
SLIP/sl0 DOWN 172.29.36.253 255.255.255.252 (N/A)
ATM/atm0 UP 192.9.200.1 255.255.255.128 0.0.0.0
This command shows the current condition of all three interfaces. The data shown for the SLIP interface will apply when it is turned UP with, for example, cnfifip slip on.
–cnfenetgw
Syntax:
cnfenetgw IPAddr
Example:
This command will set the default gateway and add the appropriate routes necessary to it.
– dspenetgw
Example:
Enet Gateway: 172.29.37.1
– bootChange:
Several lines are essential for the network to function:
- boot device : lnPci
(The only Ethernet interface)
- inet on ethernet (e) : 172.29.37.40:ffffff00
(IP address and subnetmask)
- gateway inet (g) : 172.29.37.1
(Default Ethernet gateway)
The PXM will try to correct bad entries when it boots up. This information will be copied to the standby card and if different than the shelf IP address it will up the interface on the standby with the bootChange IP address. The shellconn version of this command only updates the local bootline values and is not copied to the other card.
–usrEnetEnable:
Used to bring up the Ethernet interface when CLI prompt is not there or in backup boot if it's not enabled.
The following commands are related to FRSM-2CT3 line-level loopbacks.
•Remote Loopback at DS3:
This loopback can be configured in FRSM-2CT3 using the following commands:
addds3rmtloop <lineno>
xcnfln -ds3 <lineno> -e 3 -lpb 2
•Local Loopback at DS3:
This loopback can be configured in FRSM-2CT3 using the following commands:
addds3loop <lineno>
xcnfln -ds3 <lineno> -e 3 -lpb 3
DS3 Loopback status will be displayed with following commands:
dspds3ln <lineno>
dspalm -ds3 <lineno>
dspalms -ds3
FEAC codes monitoring and Inband loopbacks for DS3 are not supported in FRSM-2CT3
•Remote Loopback at DS1:
This loopback can be configured in FRSM-2CT3 using the following commands:
cnfbert (from PXM)
addrmtloop <lineno>
xcnfln -ds1 <lineno> -e 3 -lpb 2
•Local Loopback at DS1:
This loopback can be configured in FRSM-2CT3 using the following commands:
cnfbert (from PXM)
addlnloop <lineno>
xcnfln -ds1 <lineno> -e 3 -lpb 3
DS1 Loopback status will be displayed with following commands:
dspln <lineno>
dspalm -ds1 <lineno>
dspalms -ds1
•Inband loopback for DS1 are supported only using BERT diagnostics. The status of inband loopbacks are displayed with dspalm and dspalms commands. It is not displayed with dspln command. Before configuring the DS1 line in Inband loopback from BERT diagnostics, user should use the following command to enable code detection on FRSM-2CT3:
xcnfln -ds1 <lineno> -e 3 -detect 2
•Ctrl-X has been disabled from resetting PXM on the firmware.
•This release has the fix to meet the Bellcore jitter specs. The way to fix the jitter problem is to have FW disable the force_signal_detect_enable register and let the optical receiver to control the signal-detect input. The OC-3 transmit data jitter now measures below 0.10UI.
•Due to the concerns about the too frequent message exchanging between the two PXM cards, the current command dspbecnt is limited by following:
–dspbecnt displays only the bit error counts after the last APS switch,in other words, every APS switch will clear the counts for both working and protection line.
–dspbecnt displays the active line bit error counts correctly. The bit error counts for non-active line is inaccurate and requires a state change (since the last state) in the protection line for display of any bit error counts.
–A state change indicates a change of line status, such as from SD to SF.
Node Related
A maximum of one BERT test can be performed per shelf at any point in time. BERT can be activated only through the CLI.
Do not execute the restoreallcnf command in the middle of the installation process. If you follow the steps below, the dsplns command will display a line as disabled, but you cannot run an addln command. Do not execute the restoreallcnf command until the install and newrev commands have completed
The correct order for the restore procedure is:
Step 1 saveallcnf
Step 2 install
Step 3 newrev
Step 4 restoreallcnf
Note For more information, refer to CSCdm57683.
Addln should be issued before issuing addapsln.
The following line and alarm-related commands have been modified to allow slots 8, 16, and 32 as valid arguments if PXM at slot 8 is active:
•addln
•delln
•cnfln
•dspln
•dsplns
•addlnloop
•dellnloop
•cnfsrmclksrc
•dspsrmclksrc
•dspalm
•dspalms
•dspalmcnt
•clralmcnt
•clralm
•dspalmcnf
Full SRM redundancy requires redundant SRMs. There must be SRMs in BOTH slot 15 and 16 to ensure service module redundancy for the upper shelf and SRMs in BOTH slot 31 and 32 to ensure service module redundancy for the lower shelf. Lack of the second SRM in either shelf may result in mismatch conditions.
For service module redundancy support, if the active service module is physically removed from the slot then a switchcc would cause the now active service module to be inaccessible. The workaround is to make sure that both the active and standby cards are physically present in their slots. If the active card does need to be removed, then at shellconn type: pmmStartScmPolling(slotnumber) after the switchcc.
If you are moving service modules from an existing MGX 8220 platform to the MGX 8850, the MGX 8220 service modules (AX-FRSM-8T1/E1, and AX-CESM-8T1/E1) need to have the boot flash upgraded to MGX 8220 Release 5.0.00 common boot code (1.0.01 version) before they can be plugged in to the MGX 8850 chassis. All MGX 8220 service module versions that use Release 4.0.xx of boot code and earlier are not supported in the MGX 8850.
If loading of the correct common boot code image is required then it will have to be performed on an MGX 8220 chassis, and cannot be performed on an MGX 8850 chassis. Please refer to the procedure below, which is also outlined in the Cisco MGX 8850 Installation and Configuration publication on the documentation CD.
Step 1 Use ftp to port the Axis 5 common boot image for the service module to a workstation.
Step 2 Plug in the card into the MGX 8220 shelf.
Step 3 Download the proper MGX 8220 shelf Release 5.0 boot image using the following commands from the workstation:
tftp <ip address of the MGX 8220 shelf >
put <boot filename> AXIS_SM_1_<slot#>.BOOT
Insure that TFTP downloaded the appropriate boot code by verifying the flash checksums.
Step 1 Log into the shelf.
Step 2 Verify that the two checksums are the same.
If not, repeat the process until they are the same. If they are the same, then you can safely remove the card. At this point the service module can be used in the MGX 8850 shelf.
Caution If the checksums are not the same when you remove the service module, then the service module will not boot when it is plugged in and the service module will have to be returned using the Cisco Returned Material Authorization process.
Whenever an MGX 8850 is added as a feeder to a BPX 8600, SWSW automatically programs a channel with a VPI.VCI of 3.8 for use as the IP Relay channel. IP Relay is used to send IP data between nodes via the network handler, allowing every node in the domain to be directly addressable via IP addressing and CWM workstations to communicate with every node (especially feeders) using TELNET, SNMP and CWM protocols. If the user tries to add a channel with a VPI.VCI of 3.8, the BPX 8600 does not prevent the user channel from being added, but the MGX 8850 rejects it. To delete the added channel on the BPX 8600, and to get IP relay working you need to reset the BXM card.
In addition to clearing the entire configuration, clrallcnf clears the network IP addresses. IP addresses and netmasks stay the same (dspifip). However, it's recommended by engineering to reconfigure them using the cnfifip command. Network IP is gone (dspnwip), and must be reconfigured using the cnfifip command. Refer to the entry on cnfifip in the Cisco MGX 8850 Command Reference publication on the documentation CD for syntax.
•The copychan command does not work on the MGX 8850.
A minimum of two and up to four IP addresses are needed to be configured for MGX 8850 (one or more of the following: Ethernet, ATM, SLIP) and the boot IP address. The user should use bootChange to set up IP gateway when the PXM card is just installed. The IP default gateway should be on the same subnet as the PXM board. Use the bootChange command to set correct IP address, netmask, and default gateway.
Do not install a Y-cable on the UIA CP port for PXMs. If you do, both serial ports will be enabled and you will not be able to communicate with the shelf through the console ports. If after switchcc the standby PXM loses the down-level port, it is most likely due to a downlevel Beta version of UIA back card that was shipped during field-trial only. Upgrading the UIA back card to the latest version should fix this problem.
To configure the external clock source, use the interface label 7.35. Do not use 0.33 or 7.33.
There are also routeShow/routeAdd/routeDelete commands for modifying routing tables.
You must reboot your PXM after each modification with "bootChange" for it to take effect. Also make sure the subnet mask is 255.255.0.2
- Only enter the ethernet IP address, netmask and default gateway.
- Type "." to erase incorrect entries.
tigers.1.7.PXM.a > bootChange
'.' = clear field; '-' = go to previous field; ^D = quit
host name :C <-- Please put "C".
inet on ethernet (e) :172.29.37.40:ffff00 <-- Ethernet IP Addr/Netmask
gateway inet (g) :172.29.37.1 <-- Default Gateway
ftp password (pw) (blank = use rsh):
- Type in reboot, after this the command "" will work:
tigers.1.7.PXM.a > 171.71.54.53 1
Configuration save-and-restore is supported only through the CLI (CWM does not support configuration save-and-restore). Service module upgrades error handling is not provided. If the user skips any of the steps during upgrade or if a power failure happens in the middle of the upgrade, results will be unpredictable. See the Special Installation and Upgrade requirements section for service module upgrades. To recover from procedural errors contact your TAC support personnel.
The MGX 8850 supports 15 simultaneous Telnet sessions and 10 TFTP sessions.
You must use the following Y-cables for FRSM-HS2 and FRSM-CT3 redundancy as specified in the Product Orderability Matrix (Straight Cable: 72-0710-01, Crossover Cable: 72-1265-01, Straight Y-cable: FRSM-HS2: CAB-SCSI2-Y, FRSM-CT3: CAB-T3E3-Y). Other cables are not supported.
Y-cable redundancy for FRSM-HS2, FRSM-2CT3, FRSM-2T3, FRSM-2E3 is supported only for adjacent slots.
Statistics are not supported for the RPM.
There is no need to issue the syncdisk and shutdisk commands before removing the PXMs. The system quiesces the disk by detecting the removal of the PXM board and flushes the write buffers to the disk and puts the PXM in sleep mode. This disables any further hard disk access since it locks the actuator. When the card is reinserted the PXM automatically comes out of sleep mode.
Syntax of addlink command has changed as follows:
New Syntax:
Syntax: addlink <T3LineNum> <T1Slot> <NumberOfT1s> <TargetSlotNum>
<TargetSlotLineNum>
<T3LineNum> where = Slot.Line
Slot = 15,31
Line = 1 - 3
<T1Slot> where T1Slot = 1 - 28
<NumberOfT1s> where NumberOfT1s = 1-8
<TargetSlotNum> where TargetSlotNum = 1-6|11-14|17-22|27-30
<TargetSlotLineNum> where TargetSlotLineNum = 1-8
PAR command cnfnwip has been disabled in this release, please use cnfifip instead.
If you lose power, or remove the online PXM you lose the broadcast address. Use the "cnfifip" command to configure the broadcast address. To redefine your ATM address and IP address that are in the same subnet, you have to change the ATM address to a temporary address not in the same subnet, then add back your IP address with the original Broadcast address, then go back and correct your ATM address.
Cooling and Power limitations: Customer should be aware of the need for extra power supplies and fans beyond certain limitations. A single fan tray will support all configurations that draw between 1200 and 1400 watts. For power requirements, the MGX 8850 requires a minimum of one power supply per line cord to support the power requirement for five cards.
| |
0-5 Cards
|
6-10 Cards
|
11 and Above
|
Single Line Cord (N+1):
|
2
|
3
|
4
|
Dual Line Cord (2N):
|
2
|
4
|
6
|
This is based on an estimated worst-case power requirement of 190W plus margin per card slot.
Connection Management Related
The name of the node cannot be changed if there are PVCs. The node name must be changed from the default value before adding connections, since it cannot be changed later. Use the cnfname command to change the node name.
Only one feeder trunk can be configured. No BNI trunk to MGX 8850 as a feeder is supported.
The slave end of a connection must be added first.
The slave end cannot be deleted and re-added back by itself. If you delete the slave end, the entire connection must be completely torn down and re-added back. If the slave end of the connection is deleted and re-added back by itself, then unpredictable results will happen.
For user connections, VCI 3 and VCI 4 on every VPI are reserved for VPC OAMs.
The actual number of feeder connections you can provision on the PXM is always two less than you have configured. The dsprscprtns command shows max connections as 32767, but you can only use 32767 - 2 = 32765. One connection is used for LMI and another one for IP relay.
There is no error handling detection while provisioning through the CLI. Invalid endpoints and unsupported connection types (such as connections between FRSM-CESM ports or connections between structured and unstructured connections) are permitted using the CLI. The user should not configure these connections.
The sum of CIR of all channels of a port can be greater than port speed as long as CAC is disabled. However, it is not acceptable for one channel's CIR to be greater then port speed even if CAC is disabled. Two channels added up can exceed port speed. This means you cannot oversubscribe a port if only one channel is configured.
When trying to add a port on DS0 slot 32 of a CESM-8E1 line using an SNMP set or the CiscoView Equipment Manager, the SNMP agent in CESM will time out, without adding the port. The SNMP libraries treat the 32 bit DS0 slotmap (cesPortDs0ConfigBitMap) as an integer. The value for the last DS0 is treated as the sign value. This causes a corruption in the packet coming to the agent. As the agent does not receive a complete SNMP packet, it does not respond and times out. Use the command line interface to add a port on DS0 slot 32 of a CESM-8E1 line.
The cnfport command does not allow VPI ranges to be reduced. The cnfport command only allows the VPI range to expand. The correct sequence is to delete all connections on the partitions, delete the partitions, delete the port, and add the port with new VPI range.
On an FRSM-2CT3, one can add 128 ports on a group of 14 T1 lines as indicated below.
• lines 1 to 14: 128 ports (A)
• lines 15 to 28: 128 ports (B)
• lines 29 to 42: 128 ports (C)
• lines 43 to 56: 128 ports (D)
So, to add 256 ports on one T3: add 128 ports on the first 14 T1 lines and the remaining 128 on the next 14 T1 lines.
Note that (A) and (D) are connected to first FREEDM and (B) and (C) are connected to the second FREEDM. Each FREEDM supports only 128 ports. If 128 ports are added on one T3 as in (A), then there cannot be any more ports as in (D). The 129th port should be on lines 15 to 42 (as in B or C).
If the user adds a connection between an RPM and a PXM and then deletes the connection, the RPM shows no connection but the PXM still has the connection. The MGX was designed and implemented in such a way that only the connections that have the master end show up on PXM (by dspcons command). Consider these three connections:
•c1: has only slave end
•c2: has only master end
•c3: has both master and slave end
When using the dspcons command, c2 and c3 will be displayed, not c1. The connection will not show up once the master end (PXM) is deleted. Recommendation: When adding a connection, if one end of the connection is PXM, always configure the PXM side to be the slave. Thus when deleting the RPM side, which is the master, the connection will not show up on the PXM. However, keep in mind that the slave end (PXM) still exists. This also provides a side benefit. When a connection exists with only the slave side, no bandwidth is occupied. The bandwidth is reserved only if the master end exists (with or without the slave).
The MGX-FRSM-HS1/B is capable of supporting a total throughput (card-level) of 16 Mbps. However, it is possible to configure four lines each supporting up to 8 Mbps, thus oversubscribing the card. This has been raised in bug #CSCdm71476 and a restriction/warning will be added in a future release.
Addlnloop on an FRSM-HS1/B line works only when there is a (valid) cable plugged in to the back card on that line. This is a hardware limitation on the back card and has been mentioned in the Release Notes in bug# CSCdm44993.
RPM Related
With MGX Release 1.1.32, two Route Processor Modules (RPMs) are supported; the RPM/B and the RPM-PR.
The RPM/B is a NPE-150 based router card capable of sustaining 150,000 pps. The RPM-PR is an NPE-400 based router capable of sustaining over 350,000 pps. The RPM-PR will only operate with IOS 12.1(5.3)T_XT or later. For the following section "RPM" will refer to both the RPM/B and the RPM-PR, (unless specifically called out) even though some software versions and limitations are not applicable to the RPM-PR because it doesn't support IOS versions before 12.1(5.3)T_XT.
With RPM/B versions earlier than 12.O.7T1, some limitations in Inter-Process Communication when the RPM/B is at high loads can cause the PXM to declare that the RPM/B has Failed . To avoid this with RPM/B, software releases earlier than 12.0.7T1, throughput is limited to 62,000 pps, and it is recommended that MPLS configurations are limited to 100 interfaces. With RPM software releases from 12.0.7T1, those limitations are removed. In a separate limitation, the number of directly connected OSPF networks supported by an RPM is currently limited to 27. This means that any or all of the subinterfaces supported by the RPM can run OSPF, but the number of distinct OSPF networks supported is limited to 27. (A work around is available and is discussed below.) The limit of 27 arises because of the overheads of supporting separate link-state databases for separate networks.
In an application where the RPM is a Provider Edge Router in an MPLS Virtual Private Network service, a much better solution in any case is to use a distance-vector routing protocol between the customer routers and the RPM. A distance-vector routing protocol provides exactly the information required for this application: reachability information, and not link-state information. The distance-vector routing protocols supported by the RPM are BGP, RIP v1 and RIP v2, as well as static routing. With RPM software releases from 12.0.7T1, distance-vector routing protocols can be used with as many different networks as subinterfaces.
Note that if the RPM is acting as a Provider Edge Router in an MPLS Virtual Private Network service, and even if OSPF is running in a customer network, it is not necessary to run OSPF between the customer router and the RPM. If the customer edge devices run Cisco IOS, they can redistribute OSPF routing information into RIP using the IOS commands, redistribute RIP in the OSPF configuration, and redistribute OSPF in the RIP configuration. Similar configurations are possible for BGP. (For more information on readvertisement, see the "Configuring IP Routing Protocol-Independent Features" chapter in the Cisco IOS Release 12.0 Network Protocols Configuration Guide, Part 1). Redistribution is not unique to Cisco CPE, and other vendors' equipment also supports redistribution.
Recommendations for Booting:
The current implementation provides the following options:
•From PXM Disk
•NetBoot (TFTP server)
•Booting from PXM Disk is faster than NetBoot
Recommendations for saving RPM configuration:
The current implementation provides the following options:
•Save on flash/boot-flash.
•Save on PXM disk.
•Save on network (TFTP server)
•Save on RPM NVRAM (comes up faster; only for limited configuration size)
It is recommended to save the configuration on flash and on the PXM Disk, as well as on the network server. This ensures that the configuration can be restored, even in the case of multiple failures.
For example, if an RPM card has problems, you can copy the configuration from either the PXM disk or from the network to new RPM card. In case of multiple hardware failures (both RPM and PXM cards have problems) you can copy the configuration from the network server.
Replacing the existing RPM with a new card or a card with old configuration in flash
The existing configuration (of the old card) can be restored on the newly inserted card by following the instructions given below:
Step 1 Insert the new card into an unreserved empty slot. A previously used slot can be unreserved by giving the clrsmcnf command.
Step 2 Copy the old RPM's configuration (from the PXM disk or the network server) to the new card's bootflash. For example, copying from PXM disk: "copy c: <image name> bootflash:".
Step 3 Configure the new card to use the configuration in its bootflash using the boot config bootflash: <config-file-name> command.
Step 4 Save the changes using write mem command.
Step 5 Insert the new card into the old slot.
Please note that in RPM context the "config save/restore" feature of the PXM restores only the PXM part of the RPM configuration/connections. The RPM part of the configuration should also be saved from RPM CLI through copy command. For example, copy run c: <config-filename> for saving to PXM Disk for future restoration.
RPM Connection Resynchronization
The RPM Connection Resync process is supported in the 12.04T and higher releases. This feature checks for consistency between the RPM and PXM connection databases.
Limitations
restoreallcnf
Do not execute the restoreallcnf command in the middle of the installation process. If you do, the dsplns command will display a line as disabled, but you cannot run an addln command. Do not execute the restoreallcnf command until the install and newrev commands have completed.
The correct order for the restore procedure is:
Step 1 Execute the saveallcnf command.
Step 2 Execute the install command.
Step 3 Execute the newrev command.
Step 4 Execute the restoreallcnf command
Note For more information, refer to CSCdm57683.
Please also note the following:
•The Service MIB does not support resource partitions.
•LIP is supported on the maintenance port, but there is no PPP support on the maintenance port.
•BIS messages are constantly being sent from BPX to various nodes. This affects the frequency of TFTP updates, which may affect CWM performance and/or CWM database consistency.
•Unable to provision virtual trunks in SWSW 9.1.10.
clrsmcnf
As a speedy way to wipe out all configuration on an SM, you can use clrsmcnf. This command works in the following scenarios:
•1.1 SM not in slot
•1.2 SM in slot and in active (good) state
•1.3 SM in slot but in failed state, boot state or another state.
To be able to use an SM of a different type from the current one in a slot you can also use clrsmcnf for example, if there is a FRSM8T1/E1 in the slot with some configuration and the customer wants to use this slot for an AUSM8T1/E1 card.
The clrsmcnf cannot delete a port or channel due to corruption or error locally on the SM. It is able to delete the port/channel from within the PXM, but it cannot delete a port or channel due to corruption/error on the PXM itself. You can save an SM configuration and restore it back to the same slot on the same node. If the SM configuration is corrupted on disk, but the run-time image is okay and the file contented is corrupted, this is supported.
The following are NOT supported on the MGX 8850:
•Saving a configuration of an SM from one shelf and restoring it to the same slot on another shelf.
•Saving a configuration of an SM in a slot and restoring it to another slot of the same card type.
•If the SM configuration is corrupted on disk, but the run-time image is okay and the FAT is corrupted.
If you have more than 500 connections on a service module, before issuing clrsmcnf you need to change the session timeout default value.
Use CLI command timeout 0 (no timeout)
clrsmcnf
After it is done, use the CLI command timeout 600 (to set the timeout value back to the default).
Note The clrsmcnf does not work with the VISM card.
Core Dump Mask
There are no system performance implication unless you take a core dump, currently the default error mask to take core dump is attached,. You can change the mask or take it manually.
Set the core dump mask to its default value. If you enable core dumps with power on reset and shell reset core dumps enabled you will end up with a PXM that continuously dumps the core and resets. The only way out is to use a download boot that does not have the core dump feature.
ON 0002 DRAM Parity Error
ON 0004 WatchDog Timeout Reset
ON 0008 Resource Overflow
OFF 0010 Clear All Configuration
ON 0040 Reset because of PXM Low Voltage
ON 0080 Reset By Event Log Task
OFF 0100 Reset from Shell
OFF 1000 Switch Core Card
ON 2000 Secondary Cache Error
ON 4000 Software Error Reset
OFF 8000 S/W reset due to upgrade
OFF 10000 Restore All Configuration
ON 20000 Device Driver Error
NODENAME.1.8.PXM.a > core hot-dump
Do you want to proceed (Yes/No)? y
..........................................................................................
......................................
NODENAME.1.7.PXM.s > core save 2 core.zip
.................................
There are two steps to save a core dump.
1. The system will store a raw core dump image on the disk (this image is
on a portion of the disk that is not used for the filesystem).
2. After the raw core dump image is saved on the disk, use the cli command
"core" to zip the image and save it in a file on the disk.
Use the "core mask" command to display and to set the mask which determines
which conditions will cause an autmatic core dump.
NODENAME.1.7.PXM.s > core mask
Automatic Core Dum is enabled..
The Current Core slot is 0
The Current Core mask is 0x4004
OFF 0002 DRAM Parity Error
ON 0004 WatchDog Timeout Reset
OFF 0008 Resource Overflow
OFF 0010 Clear All Configuration
OFF 0040 Reset because of PXM Low Voltage
OFF 0080 Reset By Event Log Task
OFF 0100 Reset from Shell
OFF 1000 Switch Core Card
OFF 2000 Secondary Cache Error
ON 4000 Software Error Reset
OFF 8000 S/W reset due to upgrade
OFF 10000 Restore All Configuration
OFF 20000 Device Driver Error
NODENAME.1.7.PXM.s > core mask 0x2e2ee
Automatic Core Dum is enabled..
The Current Core slot is 0
The Current Core mask is 0x2e2ee
ON 0002 DRAM Parity Error
ON 0004 WatchDog Timeout Reset
ON 0008 Resource Overflow
OFF 0010 Clear All Configuration
ON 0040 Reset because of PXM Low Voltage
ON 0080 Reset By Event Log Task
OFF 0100 Reset from Shell
OFF 1000 Switch Core Card
ON 2000 Secondary Cache Error
ON 4000 Software Error Reset
ON 8000 S/W reset due to upgrade
OFF 10000 Restore All Configuration
ON 20000 Device Driver Error
Use the "core mask default" command to set the mask back to the default.
NODENAME.1.7.PXM.s > core mask default
Automatic Core Dum is enabled..
The Current Core slot is 0
The Current Core mask is 0x262ee
ON 0002 DRAM Parity Error
ON 0004 WatchDog Timeout Reset
ON 0008 Resource Overflow
OFF 0010 Clear All Configuration
ON 0040 Reset because of PXM Low Voltage
ON 0080 Reset By Event Log Task
OFF 0100 Reset from Shell
OFF 1000 Switch Core Card
ON 2000 Secondary Cache Error
ON 4000 Software Error Reset
OFF 8000 S/W reset due to upgrade
OFF 10000 Restore All Configuration
ON 20000 Device Driver Error
Use the "core enable" command to enable autmatic core dumps.
NODENAME.1.7.PXM.s > core enable
Automatic Core Dum is enabled..
Use the "core disable" command to disable automatic core dumps.
NODENAME.1.7.PXM.s > core disable
Automatic Core Dum is disabled..
Use the "core hot-dump" to dump the raw image to the disk.
NODENAME.1.7.PXM.s > core hot-dump
Do you want to proceed (Yes/No)? y
..........................................................................................
......................................
Use the "core" command to list the current list of raw core dumps save on
NODENAME.1.7.PXM.s > core
Slot Reset Reason Dump Time
-------------------------------------------------------------
0 Unknown WED DEC 29 09:38:30 1999
1 WatchDog Timeout Reset FRI DEC 10 08:51:52 1999
2 WatchDog Timeout Reset TUE DEC 14 08:01:39 1999
3 WatchDog Timeout Reset TUE DEC 14 12:38:01 1999
4 Reset from Shell TUE DEC 14 14:45:30 1999
5 WatchDog Timeout Reset WED DEC 22 08:20:26 1999
Automatic Core Dum is enabled.
The Current Core slot is 0
Use the "core save" command to save the specified raw image to the
NODENAME.1.7.PXM.s > core save 0 ccc
.................................
To upload the zip file, you must use FTP (TFTP has a limit of 16 MBytes
NODENAME.1.7.PXM.s > shellConn
Set the and enable the user name:
The user name is "cisco" and the password is "ciscoinc".
Now you can FTP the image. Be sure to use binary mode.
After the image has been uploaded, disable the user name:
->
Problems Fixed in Release 1.1.32
Bug ID
|
Description
|
CSCdp38293
|
Symptom:
dspcd on the SRM will show the 800 number from the back card in the front card FabNumber field.
Workaround:
Added a new field to show the SRM front card's fab number. Renamed the old field to be the fab number for the SRM back card.
|
CSCds09448
|
Symptom:
The CWM does not display the correct values of:
•Ingress Percentage Utilization
•Egress Percentage Utilization
•Connection Percentage Utilization
•Connection Remote Percentage Utilization
Conditions:
These MIB objects are not included in the TFTP config upload file.
Workaround:
None.
|
CSCds24381
|
Symptom:
PXM7 switched to PXM8.
Condition:
Memory corruption.
Workaround:
None.
|
CSCds25261
|
Symptom:
SNMP trap to indicate ILMI failure on AUSM card causes HP OpenView to crash.
Conditions:
When ILMI is disabled or fails, (after being enabled), an SNMP trap #50915 is sent to CWM. This trap causes HP OpenView to crash with the following message:
"xnmevents lost contact with pmd.
No new events will be received.
Lost connection with pmd/ovEvent process (application disconnected)"
Workaround:
None.
|
CSCds31371
|
Symptom:
Active card automatically switches to standby card.
Condition:
Unknown.
Workaround:
None.
|
CSCds37482
|
Symptom:
BERT for a port/line on CESM-8 fails intermittently with a general error. A resetcd is required to make the port/line operational.
Conditions:
This happens when BERT is configured on the CESM-8 port/line. The bug is applicable to all CESM-8 releases up to and including 10.0.21.
Workaround:
Depending on which phase of the BERT configuration the error occured, it might be possible to recover the port/line state with a delbert.
|
CSCds38566
|
Symptom:
The SCM queue reports an overflow error log message for the slots containing RPM card.
Conditions:
The problem occurred when the customer was running the script to add a connection.
Workaround:
The log message should be simply ignored for RPM cards. The build-up in the SCM queue does not impact service.
Further Description:
Messages put into the queue are not supposed to be sent to the RPM card. When a connection is added to a Service Module, a task sends some information to the Service Module related to those connections. This information is not applicable for the RPM card.
|
CSCds43238
|
Symptom:
The dsploads CLI command does not display load from rt-vbr connections.
Conditions:
This occurs when the dsploads CLI command is executed.
Workaround
None.
|
CSCds43415
|
Symptom:
Telnet session lost after clrsmcnf CLI, several SMs in Boot states.
Condition:
Unknown
Workaround:
None.
|
CSCds48811
|
Symptom:
If a manual refresh is performed from CiscoView on the MGX 8230 chassis after a switchcc, the Standby PXM removes itself and resets.
Conditions:
This occurs when CiscoView is started or a manually refreshed.
Workaround:
None.
|
CSCds52286
|
Symptom:
Infinite loop on the Telnet input task, causing PXM switchovers.
Conditions:
The customer was using a shareware software for Telnet to the node.
Workaround:
Use Solaris machines for Telnet to the node.
Further Problem Description:
Telnet through the shareware software and leave that window untouched for approximately 13 minutes. To ensure that the session doesn't timeout, use the command sesntimeout 0 after you login. This will reproduce the problem.
|
CSCds55580
|
Symptom:
"dir c": shows no files in the directory when running PXM 1.1.32 and an earlier image with the RPM 12.1(5.X)T image.
Conditions:
PXM 1.1.32 and an earlier image with the RPM 12.1(5.X)T image causes this problem.
Workaround:
When running the RPM 12.1(5.X)T image, the PXM image containing the fix for this problem should be run hand-in-hand with the new RPM image.
|
CSCds60208
|
Symptom:
Shelf sometimes reboots on switchcc.
Conditions:
During redundancy testing in the lab, back cards were pulled out to check if core card switchover occured. When switchcc was entered, the shelf rebooted.
Workaround:
None.
|
CSCds65330
|
Symptom:
After PXM was upgraded from 1.1.24 to 1.1.31Aa, some of the RPMs went into Failed state and some went into Not Responding state.
Conditions:
Some RPMs were running very old images, some RPMs were running a later boot image and an older IOS image. Officially only the last two RPM releases are supported with any PXM release.
Workaround:
Reset the RPM card where the cc is failing.
Further Problem Description:
In the node on which the upgrade was tried, some of the RPMs were running very old IOS images. With any PXM release only the last two IOS releases are supported. Documented upgrade procedures should be followed for upgrading the RPM nodes.
|
CSCds66048
|
Symptom:
Bit errors occur on the CESM during BERT testing.
Conditions:
Bit errors occured when testing the CESM in an MGX 8850:
•using synchronous clocking on the CESM channel
•with the BERT tester set for internal clocking
Workaround:
There are no problems passing data and getting a pattern sync without bit loss when using a simple pattern (2^11-1 and lower ). Use of Adaptive clocking and SRTS also improves the results.
|
CSCds66176
|
Symptom:
Cannot utilize entire FRDM buffers after Softswitch ports deleted for db.
Conditions:
FRSM-ct3 connection within max limit window.
Workaround:
Configure up to 105 ports.
|
CSCds67365
|
Symptom:
PREFIX : Resolve warnings reported by prefix tool.
Workaround:
None.
|
CSCds71795
|
Symptom:
Routine check of core dump showed several errors on standby PXM. Standby is in Minor alarm. Errors caused reset of standby card.
Conditions:
•PXM-0C3 1.1.31
•DSPERR -EN 1149
•Core dump shows error 1149: 1149 software error reset.
Workaround:
None.
|
CSCds72478
|
Symptom:
Routine check of core dump showed several errors on standby PXM. Standby is in Minor alarm. Errors caused reset of standby card. This problem seems to be similar to CSCds71795 (above), although a different node.
Conditions:
•PXM-0C3 1.1.31
•DSPERR -EN 121
•Core dump shows error 121: 121 software error reset.
Workaround:
None.
|
CSCds72620
|
Symptom:
During upgrade of SMs, Softswitch from secondary to primary puts the card to failed state.
Conditions:
Occurs with 1.1.31
Workaround:
Resetcd the primary card.
|
CSCds73092
|
Symptom:
RPMs show the message "PXM does not support RSRCPRTN resynch" while booting up.
Condition:
A PXM rebuild occurs during a PXM switchover or when an RPM is reset.
Workaround:
None.
|
CSCds73935
|
Symptom:
FRSM VHS cards OAM-receive buffer overflows. This causes the received OAM buffers to be dropped.
Conditions:
This problem occurs when OAM is enabled for the connections.
Workaround:
Softswitch to the hot standby, or disable the OAM.
Further Problem Description:
In the FRSM VHS cards, the OAM receive buffers overflow causing the received OAM cells to be droped. The free buffer list is being corrupted. This corruption is triggered by the incorrect CRC in the OAM cells received. Softswitch temporarily solves the problem. A second solution is to disable the OAM.
|
CSCds75559
|
Symptom:
ABR connection with SrcDstBehavior on AUSM card stops forwarding traffic when the queue depth becomes equal to the number of RM cells sent across.
Condition:
Every time an ABR connection is configured to SrcDstBehavior.
Workaround:
None.
Further Problem Description:
The ICSE-SAR interface is enhanced so that the ICSE can generate another service decision for every RM cell that was sent instead of the data cell. This way, the data cell (which was not sent due to the RM cell) is sent out and there is no problem in the data flow.
|
CSCds76985
|
Symptom:
After an upgrade from 1.1.24 to 1.1.31, the chassis model number is automatically changed to 8250. This causes the sync up with CWM to stop.
Conditions:
This occurs when a node connected to CWM is upgraded from 1.1.24 to 1.1.31.
Workaround:
Delete the node from the CWM configurator and re-add it.
|
CSCds81247
|
Symptom:
dspclkinfo shows current ClockSetReq to be primary while current ClockHwStat is secondary. The node is not synced up to the valid primary clock.
Conditions:
Inband from PXM line is configured to be the primary clock source. When the inband line fails and recovers the node, it does not sync up to the primary clock source. This problem was seen in 1.1.31 but not in 1.1.25.
Workaround:
None.
|
CSCds82530
|
Symptom:
RPM gets stuck in Go Active/Go Standby on doing resetsys/resetcd.
Condition:
The problem happens when five or more RPM cards in a shelf come up at the same time. This problem is typically seen:
•after a resetsys
•when resetcd has either been issued to all cards simultaneously or to one after the other.
Workaround:
Reset each stuck RPM card twice. Wait for each card to come up to a stable state before resetting the next card. Follow this proceedure one stuck card at a time
Example: If two cards are stuck, reset one of the cards. It will gets stuck while waiting for bootack state. Then, reset the same card a second time until it comes up OK. Once the first card is up, repeat the proceedure for the second card.
|
CSCdt00463
|
Symptom:
Card type of -32600 is sent for RPM-PR instead of 2001.
Condition:
After upgrading an RPM/B with an RPM-PR, the PR card does not sync up with CWM. That happens because the PXM is sending the wrong card type to CWM and CWM cannot recogonize the card.
Workaround:
Perform a node resync from CWM to clear the problem.
|
Problems Fixed in Release 1.1.31
Bug ID
|
Description
|
CSCdk82484
|
Symptom:
The RPM incorrectly identifies the physical slot position when it is placed in an MGX 8230 node. This causes communication with the PXM to fail.
Conditions:
PXM and/or RPM software is running on an 8230 or other Sweet Pea node.
Workaround:
PXM and RPM software should be upgraded to versions that support the 8230 slot numbering scheme. The minimum level of software should be 1.1.31 on the PXM and Cisco IOS Release 121-4.1(T).
|
CSCdk94100
|
Symptom:
When ILMI signaling and polling is enabled at one port and not enabled at the other end the port on which signaling was configured does not go into the failed state.
Condition:
This happens when address registration is also configured along with the ILMI signaling and polling at one end and the other end is not configured for any signaling.
Workaround:
Do not configure address registration along with ILMI signaling and polling only at one end.
|
CSCdm06097
|
Symptom:
While SM is in a mismatch state, and switchcc occurs, the log file gets cluttered.
Condition:
When switchcc occurs and SM goes in mismatch state, SM logs same message more than once to PXM. Message that gets logged is like this:
02/01/1999-14:28:42 12 cmm FRSM-6-4167 ASC sent slot number to
SM : Old S.N.= 12 New S.N.=12
02/01/1999-14:28:41 11 cmm FRSM-6-4167 ASC sent slot number to
SM : Old S.N.= 11 New S.N.=11
02/01/1999-14:28:41 12 cmm FRSM-6-4167 ASC sent slot number to
SM : Old S.N.= 12 New S.N.=12
Workaround:
This log file is not going to affect the functionality of the card or any performance of the card. This log message simply can be ignored because this is useful for debug purposes only.
|
CSCdm20583
|
Symptom:
When the dspcd command gets executed on the active PXM, with standby SRM card number or vice versa, the error message is confusing.
Conditions:
When the dspcd command is executed with the other SRM slot numbers.
Workaround:
No work around is available. This is just an unclear error message problem. No logical errors.
Further Problem Description:
When the dspcd command gets executed on the active PXM and when the argument for the command is the standby SRMs slot number, the above error message is displayed. That is because from slot 7 PXM only slot 15 and 31 SRMs are accessible. Similarly for slot 8 PXM only 16 and 32 are accessible.
|
CSCdm31793
|
Symptom:
When you configure a BERT on any line, all the channels on the local as well as remote are going into alarm. But connections on the PXM on both end does not indicate any alarm.
Conditions:
Configure BERT on any line which is having some connections.
Workaround:
No workaround for this.
|
CSCdm41079
|
Symptom:
When you configure CESM T1 D4/AMI Lingcod and framing, the line will not come up. The card is not generating a T1 signal.
Conditions
When configuring CESM T1 D4/AMI line.
Workaround:
None other than use ESF/B8ZS.
|
CSCdm55480
|
Symptom:
While "downloadflash" is executing on the PXM or while the TFTP of the flash image to SM is in progress, if the PXM or the respective SM is reset, it leaves the flash in an unknown state. The card that was reset will not bootup the next time.
Conditions:
The problem will happen when the PXM or the respective SM is reset using the resetcd or switchcc commands, while the flash is being written.
Workaround:
No workaround. Make sure that the flash is intact before executing the resetcd or switchcc commands or any other command which will result in the reset of the card.
Further Problem Description:
If the card is reset when the flash is being written, it leaves the flash in the corrupted state and the card does not boot up. All the soft reset commands like switchcc, resetcd, or addred do not check if any flash write is going on before resetting the card.
|
CSCdm69318
|
Symptom:
If a switchcc is performed at the same time that an FRSM-2CT3 is going through a reboot, the FRSM gets stuck in boot state.
Conditions:
If a switchcc is performed at the same time that an FRSM-2CT3 is going through a reboot, the FRSM gets stuck in boot state.
Workaround:
Do switchcc only after FRSM-CT3 is comes up.
|
CSCdm84982
|
Symptom:
The CLI tstdelay displays time in micro seconds in stead of milliseconds.
Condition:
CLI shows delay in microseconds and GUI shows in milliseconds but the values are almost same.
Workaround:
Convert the displayed time using this formula:
Time in milliseconds = (time displayed + 1000 - 1) / 1000.
The above formula converts the time in milliseconds with a round off. After converting the time, consider the time in milliseconds.
|
CSCdp03640
|
Symptom:
The dspshelfalm command displays power supplies and fans for MGX 8830 that are non-existent. Also, the fan unit numbers 1 to 8 are displayed as 10 to 17 in the fan traps.
Conditions:
This occurs when the dspshelfalm command is executed. When the fan traps occur, the unit numbers are displayed as 10 to 17 instead of 1 to 8.
Workaround:
None.
|
CSCdp11502
|
Symptom:
In case of any failure in modifying the channel parameters, such as when a modify fails due to over-subscription, the backoff fails with "Wrong Egress Service rate Value" as the error.
Conditions:
When there are AUSM UBR-1 connections through Proxy.
Workaround:
None.
|
CSCdp15496
|
Symptom:
Doesn't ask for the password to protect platform feature (CLI: dspfeature).
Description:
This is a CLI enhancement, not a bug.
Condition:
Not applicable.
Work around:
Currently not available.
|
CSCdp17122
|
Symptom:
Softswitch and switchback commands accept invalid slot numbers
Workaround:
None. Before executing the Softswitch or switchback commands make sure that the slot numbers are valid by executing the dspred command and verifying the slot numbers and their states.
Further Problem Description:
The Softswitch and switchback commands do not check for valid slot numbers before executing the command. Therefore, the slot might get reset even though the slot is not the primary of the redundancy group or the secondary of the redundancy group for the switchback command.
|
CSCdp23328
|
Symptom:
Inconsistency in the syntax used for dsplns vs addln/delln/dspln conditions:
The commands that are used to configure the PXM physical interfaces have inconsistency in their syntax. Some commands require a "-" sign before the line type parameter. The others do not.
Workaround:
Check the help text for the commands or refer to the command help in the manual before using the command.
Further Problem Description:
Some commands expect the '-' sign before the line type parameter; other commands do not. After the fix, all commands will have a consistent parameter syntax.
|
CSCdp30538
|
Symptom:
When memShow command is displaying the detailed memory statistics on all partitions, the PXM hangs when when <ctrl>C is pressed in the middle of the display.
Conditions:
When executing memShow with a non-zero argument from the CLI prompt (for example, memShow 1), memShow without any argument works fine. But that will display only the summary information on the memory blocks. The detailed display can be executed only with a non-zero argument.
Also, while recreating the problem, it was observed that when the pagemode is OFF, the user has more chances of hitting the problem.
Workaround:
Do not execute memShow with arguments from the CLI prompt. From the VxWorks shell the command works fine. Also, do not execute the command with arguments when the PAGEMODE is OFF.
Further Problem Description:
When memShow with arguments is issued, either the process that is handling the output or the memShow routine infinitely waits. The reason for this infinite wait is currently unknown. After the problem occurs, the shelf cannot be pinged or telneted into. The active PXM has to be rebooted by pulling out the card.
|
CSCdp31043
|
Symptom:
dspalm on the FRSM-HSSI card needs the x21 as the interface type for HSSI interface.
Condition:
The alarms for the FRSM-HSSI card for the line require x.21 instead of HSSI as the interface type for dspalm command.
The CLI dspalm should except option -hssi on the card FRSM-HSSI but it accepts x.21 option.
Workaround:
-x.21 option can be used for HSSI interface. Be sure to use the appropriate MIB object to display the required info for the CLI dspalm.
|
CSCdp35123
|
Symptom:
When adding a fiftieth user to a single node, the last user becomes a "Not a valid user" after a short time (and/or before that user gets a chance to login into that node).
Workaround:
None
Description:
Array that keep all valid users' password (userPassword[ ]) was overflowing because of coding error. Since the password was not getting saved, the newly added user ID was also getting dropped from the valid user list. Fixing the bounds of the array fixed this problem.
|
CSCdp37528
|
Symptom:
At Softswitch for FRSM-VHS cards (hotSatndby case) two traps are seen—primary to secondary trap number is 50045, secondary to primary trap number is 50046. Duplicate 50045 traps sent when Softswitch executed on FRSM-2CT3
Conditions:
Softswitch "from" "to"
Workaround:
None.
Further Problem Description:
If switchover occurs due to fault condition, there is only one trap sent out, which is correct functionality. Only when Softswitch is done manually through CLI or SNMP will traps 50045 or 50046 be sent twice.
|
CSCdp38293
|
Symptom:
The dspcd on SRM will show the 800 number from the back card in the FrontCard FabNumber field.
Workaround:
None.
Further Problem Description:
In CLI session, if a user issues a dspcd command on any SRM slot, besides getting other useful information it used to list 800 fabnumber of the back card as the fabnumber of the SRM front card.
Fix:
Added a new field that will show the SRM front card's fab number. Renamed the old field to be the fab number for the SRM back card.
|
CSCdp41488
|
Symptom:
The secLineModuleMismatchTrap is not generated.
Conditions:
When two halfs height back cards are inserted that the full-height front card doesn't support, such as when PXM (full-height) card is inserted with 2 FRSM-8T1 back cards (half height).
Workaround:
This does not have any workaround. This needs further investigation and currently does not have any impact on the functionality. This is a negative test condition.
|
CSCdp42525
|
Symptom:
The dspfwrevs command does not display boot code versions.
Conditions:
Happens always.
Workaround:
Currently no workaround.
|
CSCdp43643
|
Symptom:
Under the condition given below you cannot add any configuration, but the PXM does not show any the card or even slot to be present through dspcds.
Conditions:
After pulling out PRM slot and then if a half-height card (SM) is inserted in the bottom half of that slot it comes up.
Workaround:
Currently not available. Has been fixed in 1.1.31
|
CSCdp45431
|
The dspcurclk does not update from external clock to internal OSC when the external clock fails.
|
CSCdp46345
|
Symptom:
When the active PXM back card is pulled out, the active PXM does not switchover to the standby.
Conditions:
When the active PXM back card is pulled out.
Workaround:
None.
Further Problem Description:
Intelligence needs to be put in, so that for T3/E3 back cards, or if there is no APS protection, we cause a switchover on back card removal.
|
CSCdp51956
|
Symptom:
No online diagnostics are available to check the health of PXMs and SRMs in the system.
Conditions:
Any.
Workaround:
None.
|
CSCdp57090
|
This needs further investigation and currently does not have any impact on the functionality.
|
CSCdp57673
|
Symptom:
RPM removal trap will show incorrect functionModuleState (ACTIVE).
Conditions:
RPM removal.
Workaround:
None.
|
CSCdp60418
|
This needs further investigation and currently does not have any impact on the functionality. There is no known workaround for this.
|
CSCdp66005
|
Symptom:
PXM UNI connections added on a port that is in alarm remain in alarm even after the port alarm is cleared.
Conditions:
This problem is reproducible. If connections already existing on a clear port are put in alarm by causing a port alarm, the alarms get cleared on clearing the port alarm. Only connections added on a port in alarm remain in alarm state even after clearing the port alarm. This problem was first seen in image 1.1.21Lc.
Workaround:
Before adding UNI connections originating from any SM, make sure that the ports at the two endpoints are clear of any alarms. Alarms on a connection can also be cleared by doing an SM reset.
|
CSCdp69136
|
Access Violation errors reported during TFTP of ComMat.dat file.
|
CSCdp69188
|
Symptom:
SNMP query "get" on "mibVersionNumber" returns incorrect value. Invalid response issued when an SNMP query is performed on an 8850.
Conditions:
SNMP query "get" on "mibVersionNumber" returns incorrect value. Invalid response issued when an SNMP query is performed on 8850.
Workaround:
Get MIB version number from platform firmware version by CLI command version. Cisco CCO has details of which MIB version goes with which firmware version number.
|
CSCdp70729
|
Symptom:
None.
Conditions:
A new feature to provide SNMP set switchCoreCard. This feature was added to the (POP1PRET5) 1.1.31 release.
Workaround:
None.
|
CSCdp71073
|
Symptom:
Customer has performed a Softswitch with redundancy setup between slot 22 and slot 30. After reviewing the logs, they noticed that the wrong slot numbers are referenced in the log. They believe that axis slots are being referenced rather then PXM1 slots.
Conditions:
This bug can be reproduced after doing a Softswitch or a normal reset of the card.
Workaround:
There is no workaround for this bug.
Further Problem Description:
The desplog shows the wrong slot number for some of the log messages, this is because the slot number has not been updated from the PXM at this point .
|
CSCdp77492
|
Inconsistency in behavior of port status reporting when local loops put up on line. In one case, the port came out of alarm, and stayed that way even when loop removed. In another, port stayed in alarm when loop put up.
|
CSCdp91401
|
Symptom:
Customer cannot execute a BERT test on an AUSM card that has an IMA port defined on it. Only after the port is deleted can a BERT test take place. There are physical T3 loopbacks placed on the SRM cards and all links are defined.
Conditions:
Configure BERT test on any line with IMA port defined on it.
Workaround:
No workaround.
|
CSCdp97387
|
When the dspegrqs command was issued to display the egress ports of the FRSM-2T3 slot on popfnj46 MGX node, the system displayed. This command is valid only when egress service type is Weighted Fair Queueing.
|
CSCdp99436
|
Symptom:
On the FRSM-VHS2T3 shows dspportstats as command but there is no such command.
Condition:
Happens always.
Workaround:
Do not use the CLI dspportstats for FRSM-VHS2T3 and FRSM-VHSHS2 cards.
|
CSCdr05045
|
Symptom:
Trap varbinds missing in ChanOAMLpbkStatus Trap 50311. As per the MIB trap, 50311 is defined with 16 varbinds but received trap shows only 14 varbinds. The two varbinds functionModuleType and genericTimeStamp are missing.
Conditions:
Configure the RasOam loopback, status change will generate the trap.
Workaround:
No workaround for this.
|
CSCdr07250
|
Symptom:
APS lower priority external request asserted after higher priority req clears.
Workaround:
None
|
CSCdr08987
|
This problem is observed when no line is added on the BPX side and APS is added on the MGX side. Also the sigD threshold has to be of the order of 8 or 9. SigD levels of 7 or under do not result in this problem. No known workarounds.
|
CSCdr09138
|
Symptom and Problem description:
Whenever a yellow alarm is sent on the line side—whenever a line is alarm because of RcvRAI—the port remains in Active state. The port is expected to go in alarm.
Fix and Unit test: When the line is in alarm in RcvRAI state, the port is now put in alarm.
To test this, Unit Test:
1) a) Bring a line to RCV_RAIS state. (Connect a CERJAC or HP tester to the line and generate RAI). b) Add a port to that line. On dspport, this port should be in "Line alarm" state and not in active state.
2) a) Add a line such that it is active. b) Add a port on that line and check if its active. c) Bring a line to RCV_RAIS state (same method as in 1). On dspport, this port should be in "Line alarm" state and not in active state.
|
CSCdr09927
|
Symptom:
AUSM configured with an IMA port sends the trap 50231 on Softswitch. The trap contains the varbind imaPortState.0 (Integer): failedDueToImaSigFailure. The description for 50231 says "Indicates that IMA group is active" that contradicts with the value of the varbind imaPortState seen in the trap.
Conditions:
AUSM is in 1:N redundancy and it has an IMA port configured.
Workaround:
No workaround.
Further Problem Description:
50231 is sent when an IMA port is added. But the description for 50231 "Indicates that IMA group is active" leads to misinterpretation by the user. On Softswitch, secondary AUSM downloads the configuration and adds the lines, ports, IMA groups, and so on. Hence, this trap is sent.
|
CSCdr12555
|
Symptom:
Required Support for ZERO CIR connections on FRSM-HS1.
Condition:
Present HS1 SM does not support Zero CIR connections and does not provide to configure Service rate and EIR of the zero CIR connections.
Workaround:
None.
|
CSCdr15892
|
The addlnloop on the PXM causes SONET line alarms, which sometimes do not clear when the loop is removed.
|
CSCdr17560
|
Symptom:
Shelf reset while executing a switchcc command or if executing an SNMP get. This was due to (the creation of) a null pointer in the SNMP system data structure.
Conditions:
You will run into this problem only if you are running the PXM image from the 1.1.22Ll or 1.1.22Lo (internal) Releases.
Resolution:
A fix for CSCdr17560 was checked in to both 1.1.23 and 1.1.31 Releases. This fix provides the check of the return code of the function querying the shelf model number and thus allows the correct data to be registered for use later on. The SNMP system data structure is then initialized based on the model number found. The defaults are provided just in case an error occurs during the query of the system model number.
|
CSCdr18819
|
Symptom:
PXM prompt gets misaligned after adding a connection.
Fixed-in: 1.1.24
Workaround:
None
|
CSCdr19336
|
Symptom:
Unable to configure service rate after reducing the line rate using cnflnsubrate.
Conditions:
Reduce PortSpeed (which is same as LineSpeed for unchannelized cards) using cnflnsubrate. Unable to modify the service rate after a line subrate modification. This applies only to Zero CIR connections.
Workaround:
Per -connection policing parameters are not adjusted when the port speed is reduced dynamically. For correct policing parameter, the s card has to be rebooted and then modify using cnfchaneir.
|
CSCdr21154
|
Symptom:
The time on the FRSM-8 card shows day as 00.
Conditions:
In the year 2000, on the last day of every month, the day will show up as 0.
Workaround:
There is no workaround, the date will get corrected the next day.
|
CSCdr22345
|
Symptom:
Voice call gets dropped, line alarm is seen on SM after a PXM switchover.
Conditions:
Happens only when the SRM has link to the SM, the secondary SM is Active and there is an SRM/PXM switchover.
Workaround:
Switch back the SM so that the Primary SM is Active before doing the PXM switchover .
Further Problem Description:
HotStandby SRM's link points to the Primary SM until the new SRM becomes Active.
|
CSCdr22910
|
Customer is concerned that the dspfst text does not match the cnffst text exactly. The dspfst output is missing the word "interval" after RTD.
|
CSCdr23908
|
Connection failures are not indicated in the system event log.
|
CSCdr33265
|
Symptoms:
After copying the new bootflash to the bootflash directory, the command "dir bootflash:" is used to find out whether the new bootflash is loaded correctly. The date is incorrectly shown as the old date, which may lead to confusion for the user. Also, if show clock is used on the RPM, then the wrong date and time is displayed.
Description:
Currently there is no real-time synchronization between the RPM and the PXM card. Because of this, the RPM always sets to some default time whenever it resets and the same time is reported as the time of modification for the File. The solution to this bug required sending the current date and time from PXM as a part of HELLO_BOOT_ACK message. RPM, upon receiving the date and time from PXM will set its own date and time to that of PXM and hence it gets synchronized to PXM's date and time.
Workaround:
Set the date and time at RPM using clock set hh:mm:ss command.
|
CSCdr35833
|
Symptom:
Both active and standby AUSM cards in a 1:N red config reset after a Softswitch
Conditions:
Statistics collection should be enabled.
Workaround:
This problem doesn't occur always, user has to try Softswitch once again, if it fails again disable stats and do Softswitch.
|
CSCdr36153
|
Creating an LOS condition on APS line caused multiple event log entries and traps.
|
CSCdr38808
|
Available as a part of 1.1.31. No workarounds.
|
CSCdr41646
|
Symptom:
No traps indicating SRM in Standby state is sent.
Conditions:
This occurs when PXM comes to Standby state after reset.
Workaround:
No workaround.
Further Problem Description:
After the Standby PXM card is reset and comes back up, traps are generated to indicate that the PXM card is back in Standby. However, no traps are received for the associated SRM cards to indicate status.
|
CSCdr42000
|
Symptom:
Many error messages showing on the screen after clrsmcnf command.
Conditions:
If you have an SM with many connections on the MGX 8850 shelf, then after the clrsmcnf command, this problem will happen.
Workaround:
None. However, those error messages are harmless; user should simply ignore them.
|
CSCdr43004
|
Symptom:
The IMA group goes down as soon as a local loop is initiated.
Conditions:
This happens when one of the lines on the side that is configured for loop timing is put into local loop.
Workarounds:
Resetting the card.
Further Problem Description:
This is because the loopback programming for the LIU was not being done in case of BERT.
|
CSCdr43525
|
Symptom:
Error Messages: CAN'T decrement portLcnUsed[cntrlType], already 0, slot 7, port 0 CAN'T decrement port lcnUsed, already 0, slot 7, port 0 appear after delchan of a management conn.
Conditions:
Seen in 1.1.24.
Workaround:
None.
|
CSCdr45284
|
Symptom:
While executing the command clrsrmcnf, there is no check before prompting user confirmation. The error checking is done at a later stage.
Conditions:
When the command clrsrmcn is executed with wrong SRM slot number.
Workaround:
Should enter valid SRM slot number. It has been fixed in 1.1.31.
|
CSCdr46692
|
Symptom:
Queue Engine on PXM1 hardware supports programmable values for minimum rate and maximum rate for the virtual interface (VI is mapped to a port) .
Currently, maximum rate is default to 100 percent of line bandwidth.
Conditions:
This is always the case, A new parameter has to be added in CLI/MIB to make this configurable.
Workaround:
None.
|
CSCdr46699
|
Symptom:
PXM1 has T3 interface. one conn. is added from VHS card at full T3 rate to PXM1 Line1. Another conn. is added from FRSM8t1 card at full T1 rate to PXM1 Line1 when data was sent at full rate on both connections, since PXM1 Line1 is congested, cells are dropped. But cells were dropped only for T3 full-rate connection; all cells for T1 rate connection went through. To be fair, a proportional amount of cells should get dropped from both connections.
Conditions:
This is always the case for the above setup.
Workaround:
None.
Further Problem Description:
By modifying the VI, Qbin, VC thresholds, some amount of fairness can be achieved.
|
CSCdr47445
|
Symptom:
Ethernet netmask reverts back to 255.255.255.0 after switchcc
Conditions:
Happens whenever the netmask in bootChange and cnfifip are different
Workaround:
Set the bootChange IP address to have same netmask by adding a colon followed by a hex netmask. Example: '172.29.36.99:ffffff80' The default netmask in the boot line is 'ffffff00' which is equivalent to 255.255.255.0
|
CSCdr48918
|
Symptom:
The PXM will not be able to clock from the T1s in the IMA group.
Conditions:
When configuring clock using cnfclksrc on the PXM from a line in an IMA group in AUSM, you must select the line with the same number as the label of the IMA group. If the IMA group label is not the same as one of the lines in the group, then the PXM will not be able to clock from the T1s in the IMA group.
Workaround:
Configure the IMA group such that its label is the same as one of the lines being used (example, IMA group 1 with lines 1, 2, 3, and 4). Then configure the PXM to clock from line 1.
|
CSCdr50184
|
Description:
The clrsmcnf on RPM resets RPM.
Condition:
Not applicable.
Workaround:
Clearing RPM config. can be done in two steps.
1. Erase NVRAM config. on RPM.
2. Use clrsmcnf for RPM.
|
CSCdr56159
|
Symptom:
CWM EM may show a physical line on PXM, even if the line is deleted.
Description:
No physical line delete trap is sent to CWM when the line is manually deleted by CLI or SNMP.
Workaround:
Currently not available.
|
CSCdr58168
|
Symptom:
Some of the lines in IMA group become unavailable.
Conditions:
This happens when the AUSM card was in bulk mode.
Workaround:
None.
Further Problem Description:
After a switchcc on PXM, the AUSM-8T1 card started displaying Minor Alarm. On further investigation, it was found that some of the lines configured as a part of the IMA group became unavailable. The respective AUSM-8T1 card was in bulk mode.
|
CSCdr58663
|
Symptom:
The CLI command restoresmcnf will not work after SM redundancy is deleted (in bulk mode).
Description:
When the SM is in bulk mode, restoresmcnf won't go through.
Conditions:
Same as the above description.
Workaround:
Currently not available. This bug has been fixed in 1.1.31
|
CSCdr59398
|
Symptom:
PVCs get deleted after the CLI cnfportrscprtn.
Conditions:
This condition results on use of the CLI cnfportrscprtn if the new VPI range specified is shrinked beyond the existing values of the resource partition and existing PVCs use VPI values that lie between the old range and the new range. Seen in 1.1.23
Workaround:
No workaround. Care should be taken to provide a "proper" VPI range so that all PVCs lie within.
|
CSCdr59813
|
Symptom:
The FRSM T1/E1 module has an egress HDLC queue scheduler that scheduled frames onto the logical egress queue. The rate at which this runs is not aligned with the logical port speed.
Workaround:
Further Problem Description:
Suggested fix is to have the queue scheduler schedule traffic out onto the HDLC framer queue at a rate aligned with the logical port speed.
|
CSCdr61374
|
Symptom:
1. The idle flag in dspchans seems to constantly toggle from Yes to No (even though Detection and suppression is disabled).
2. The on/offhook indicator seems to toggle when dspchancnt is viewed.
3. The throughput of the channels go down.
Conditions:
The situation is triggered when idle suppression related cells are received by CESM under the erroneous behavior of the network.
Workaround:
Deleting the erroneous connection and re-adding should solve the problem.
|
CSCdr61803
|
Symptom:
While clrsmcnf is in progress, entering control-c to stop the CLI will cause subsequent clrsmcnf on that same slot being aborted.
Description:
While clrsmcnf is in progress, entering control-c to stop the CLI will abort the clrsmcnf process and leave the slot in reserved state. After reseting the SM in the slot and card comes back to active, clrsmcnf cannot be resumed (aborted).
Workaround:
Wait until the clrsmcnf to complete and do not issue control-c to stop.
|
CSCdr63304
|
Symptom:
On the reception of segment loopback OAM cells on the AUSM port the counter gets incremented (PortXmtSgmtLpbkCells). On clearing the port counters this counter does not clear.
Conditions:
When segment loopback OAM cells are received on the AUSM port.
Workaround:
None.
Further Problem Description:
This counter was not being cleared. This has been fixed in the fix.
|
CSCdr63533
|
Symptom:
When a line is configured in remote loopback, dspcd does not indicate remote loopback.
Condition:
Happens every time remote loopback is configured.
Workaround:
No workaround.
|
CSCdr69994
|
Problem:
ForeSight parameters do not get modified on the standby card.
Symptom:
Standby card MIR/PIR/QIR do not get changed when they are changed on the active card.
Workaround:
Do a Softswitch and switch back
|
CSCdr70797
|
Symptom:
When a line is put in remote loopback the port is put into alarm and hence the connections, in which case AIS as well as data traffic, are sent to the CPE.
Conditions:
This happens when the line is put into remote loopback.
Workaround:
No workaround.
Further Problem Description:
Due to a hardware limitation the data traffic cannot be stopped from going to the CPE, hence the AIS transmission will be stopped in case the line is put into remote loopback. We will not put the port and connection into alarm just like local loopback.
|
CSCdr70820
|
Symptom:
In 1.1.24 PXM, chassis came up as MGX 8830 and as a routing node.
Description:
This has been fixed, so that it comes up as MGX 8230 and the default configuration is changed to be feeder node.
Workaround:
If dspswfunc shows the node to be routing node it can be configured to feeder using cnfswfunc.
|
CSCdr72963
|
Symptom:
When PSU fails, alarm event does not appear in dsplog. It appears on Eventlog of CWM.
Conditions:
This occurs when there is a power supply failure.
Workaround:
Get the PSU failure information from NMS, CWM. Also CLI command dspshelfalm gives status of PSU.
Further Problem Description:
Only trap is sent to CWM, the event is not logged.
|
CSCdr74393
|
Symptom:
APS bidirection non-revertive mode interoperability with Sentient does not work.
Condition:
APS interoperability with the Sentient.
Workaround:
None.
|
CSCdr76747
|
Symptom:
When using CNFBERT local loop or no loop due to having a hardware loop on the physical ports of a FRSM 8E1, it is observed that the BERT test does not run error free. Tests show that the local loop BERT test errors when using 1.1.23 but in previous 1.1.12 has zero bit error count. Test was reperformed using AUSM in 1.1.23 and zero bit errors were recorded.
Conditions:
Lab environments of both heavily loaded nodes or nodes with only PXM, FRSM, SRM.
Workaround:
None.
|
CSCdr76819
|
No known workaround. Fixed in 1.1.31.
|
CSCdr77088
|
Symptom:
Node hangs due to the back card going bad.
Conditions:
Sometimes when the back card is going bad, the line oscillate between OK and LOS condition. When this happen, there are flood of messages between the active and standby PXM.
Workaround:
Remove the bad back card.
|
CSCdr80198
|
Symptom:
The oldiags fails the framer test when run on a PXM1 with an OC-3 daughter card and debug level 3 is used.
Conditions:
PXM1 with OC-3 daughter card and oldiags is invoked with debug level 3.
Workaround:
Do not run oldiags with debug level 3. Use debug level 0-2.
|
CSCdr81334
|
Symptom:
VxWorks heap may have some leaks and some allocations of memory will fail.
Conditions:
This problem occurs only when there is a memory corruption or the memory partitions are full (or nearly full).
Workaround:
Reset the PXM.
|
CSCdr83869
|
Symptom:
There is no command to display trunk utilization.
Condition:
Applies to PXM release prior to 1.1.31.
Workaround:
None.
Further Info:
The command that has been introduced is dspportutil <port#>. The output of the command looks like this:
mgx524.1.7.PXM.a > dspportutil 1 Avg CPS Rcv to XmtQ = 1 Utilization = 0% Avg CPS Xmt to Port = 1 Utilization = 0%
Note that due the h/w limitations, the CPS and %util are only available for the egress direction. The first line is for the egress cells coming to the switch fabric and the second is for the egress cells leaving the switch fabric toward the physical ports. For a description of the h/w limitation refer to bug CSCdp03385.
The %util is with respect to the physical line cell rate.
To clear the counts use the existing commands: clrportcnt or clrportcnts.
There is no MIB support to access the counters. The counters are displayed only via the CLI command.
|
CSCdr86099
|
Symptom:
The clrportcnt does not clear the counter EgressPortQFullDiscardCells.
Condition:
When there is EgressPortQFullDiscardCells in the rt-vbr connection.
Workaround:
No workaround.
Further Problem Description:
This counter was not being cleared, this has been cleared in the fix.
|
CSCdr86885
|
Symptom:
Frames get DE Tagged even though DE Tagging is disabled.
Conditions:
When user pumps traffic greater than CIR, and Bc bucket becomes full, frames get DE tagged even though DE tagging is disabled.
Workaround:
There is no workaround.
|
CSCdr87800
|
Problem Description:
PVCs could be added on reserved VCCs, for example, with VPI = 0 and VCI between 0 and 31, without an appropriate warning message.
Fix:
A warning message is displayed now whenever a PVC is added on a reserved VCC.
Unit test:
Add a connection with VPI = 0 and VCI between 0 and 31. See that appropriate warning message is displayed, but channel addition goes through.
|
CSCdr88653
|
Symptom:
The chanDEtoCLPmap resets to default value whenever channel configuration is changed.
Conditions:
This will occur when ever user modifies the channel configuration after configuring chanDEtoCLPmap to the required value.
Workaround:
Whenever user wants to modify the channel configuration, chaneDEtoCLPmap has to be included in the channel configuration.
Further Problem Description:
This occurs because whenever the user modifies the channel configuration, chanDEtoCLPmap is reset to default values when user does not provide value to this object. So whenever user modifies other channel configuration, this object also has to be set to required value.
|
CSCdr89017
|
Symptom:
The oldiags will eventually use up all file descriptors on the system when run in a loop.
Conditions:
Run oldiags in a continuous loop.
Workaround:
None.
|
CSCdr90273
|
Symptom:
Connection gets added even though DLCI for the remote FR Port is not specified. This connections gets added with remote end's DLCI taken as 0.
Conditions:
This occurs when addcon command is executed without specifying the remote end's DLCI.
Workaround:
User has to enter the remote end's DLCI while adding the connection.
|
CSCdr90635
|
The xcnfcon displays the range of VPI/VCI as VPI 1-4095 (sometimes 0-255) and VCI 1-65536. Sometimes the display is Hex based as 0xff and 0xffff. The info needs to be correct and made consistent throughout.
|
CSCdr90909
|
Symptom:
The oldiags running on an MGX 8230 refers to slots 7 and 8 as PXM slots. Should be slots 1 and 2.
Conditions:
Issue oldclralm and the usage message is: USAGE: oldsplog <slot_number (7, 8)
Workaround:
None.
|
CSCdr95869
|
Symptom:
Programming the new Novram fails.
Condition:
The new Novram(AT93C66) required a different programming sequence.
Workaround:
None.
|
CSCdr98433
|
Symptom:
The PXM log is required for addition and deletion of SM redundancy.
Condition:
No logs while adding and deletion redundancy for SM.
Workaround:
Made changes to the code so that the logging will take place whenever addition or deletion of SM redundancy happens (files changed redUI.c and cliRedundancy.c in POP1PRET5 branch).
|
CSCdr98519
|
Symptom:
Login, logout, and all user commands must be logged.
Condition:
Rate limit was there for all the commands, so login, logout, and all user commands were not logged everytime.
Workaround:
The login, logout, and all user commands will be logged from now on. Files changed to cli_msgs.h in pop1pret5 branch.
|
CSCds00987
|
Symptom:
The display format for CLI dspchans was misaligned.
Condition:
Happens when the CLI dspchans executes in the presence of rt-VBR connections.
Workaround:
None.
|
CSCds01023
|
Symptom:
The xcnfportq with the option qa=0 disables the corresponding egress port Q.
Condition:
This display inconsistency exists in all firmware releases prior to 1.1.31.
Workaround:
Use cnfportq instead of xcnfportq.
Further Problem Description:
Even though an option of 0 is not displayed for the "-qa" option in xcnfportq, a value of 0 if specified is taken and the specified port queue is disabled. This seems to be conflicting with the range specified in the help. The help has now been fixed in 1.1.31 to display the extra option of setting qa to 0 to disable the queue.
|
CSCds01417
|
Symptom:
There is no range checking for port and queue numbers in case of CLI dspportq.
Condition:
When executing the CLI dspportq.
Workaround:
No workaround. The fix is taking care of range checking for port and queue numbers in CLI dspportq.
|
CSCds01472
|
Symptom:
The help string shows that the MaxLcn parameter for the CLI's cnfrscprtn, cnfportrscprtn, and xcnfrscprtn has a range of 1 to 1000, but 0 is accepted.
Conditions:
This happens whenever cnfrscprtn, cnfportrscprtn, and xcnfrscprtn are configured with MaxLcn as 0.
Workaround:
Do not use MaxLcn as 0 while configuring cnfrscprtn, cnfportrscprtn, and xcnfrscprtn.
|
CSCds03756
|
Symptom:
The object chanServType is missing in the TFTP config upload file.
Conditions:
When user uploads the TFTP config file, chanServType object is missing.
Workaround:
There is no workaround.
|
CSCds03905
|
Symptom:
Prior to the 1.1.31 release the default display for the shelf banner upon booting up is as following:
SES for SES-IGX product
MGX 8830 for MGX 8230 or MGX 8830
MGX 8850 for MGX 8250 or MGX 8850
Conditions:
With the 1.1.31 release onward, the default display for the shelf banner upon booting up is as following:
SES for SES-IGX product
MGX 8230 for MGX 8230 or MGX 8830
MGX 8250 for MGX 8250 or MGX 8850
The reason for changing the default banners from MGX 8830/MGX 8850 to MGX 8230/MGX 8250 in the 1.1.31 release is because the PNNI is required to be available in the 1.X release in order for the MGX 8250 and MGX 8850 products to be available. The PNNI is not currently available in the 1.X release, so it makes sense to default the shelf banner to the currently existing products (hence using 1.X image).
Workaround:
None.
|
CSCds04145
|
Symptom:
FRF.5 NIW frames may get dropped in the egress direction, because incoming DLCI is not set to 1022.
Condition:
When the FRF.5 NIW Interworking function switch looks for incoming DLCI and if it is not 1022, then it may drop the NIW frame.
Workaround:
None.
Problem Description:
While sending the FRF.5 NIW frame to the network, the DLCI is not set to 1022 as per the standard. So when the frame reaches the other end, NIW Interworking function may look for incoming DLCI, and it may drop if it is not set to 1022.
|
CSCds04697
|
Trap couldn't see beyond 700 connections because PXM allowed only up to 700 table entries. The size of this table now allows 2000 entries.
|
CSCds05006
|
Symptom:
If an SRM line with loopback is deleted, next time when this line is added again, the loopback value will not have the default "noloop". It will be the previous loopback value.
Condition:
Delete an SRM line and add it back again. The loopback value will be the previous value instead of default value.
Workaround:
Configure the desirable loopback value after adding a line.
|
CSCds05374
|
Symptom:
When user adds PVC on MGX service module to feeder trunk and leaves out the remote VPI.VCI in the syntax, the system accepts the command and adds a PVC with a remote VPI.VCI of 0.0.
The system should not accept this command and make the user add it again with correct syntax of: remote node.slot.port.VPI.VCI.
|
CSCds06755
|
Problem Description:
The AUSM xcnfilmi CLI command options do not match the "usage" message—the "mei" and "-ar" options are not displayed as available command line options. Also, option "-pti" is shown as usage option "-pt".
|
CSCds07411
|
Symptom:
FEAC DS3 OOF are seen at the far-end of a FRSM-2T3
Workaround:
Call the TAC. The workaround requires very experienced personnel.
|
CSCds09808
|
The rpmChanMidLow and rpmChanMidHigh are referred as to message ID for PVC connections. They are read-only numbers and are generated by addconn command. This is why you ca not change its content after it has been assigned by PXM.
0 is an invalid number, which is due to the connection unsuccessfully made across from one PXM to another PXM via a BPX. When you do dspconn, ABIT ALARM shown next to a connection is an indication that the connection was not made across.
|
CSCds11325
|
Symptom and Problem Description:
There were cases reported where the AUSM-8 card reset on its own mostly when SNMP sets were being done on the card. The AUSM-8 card used to report a "WatchDog Timeout Reset" to the PXM in these cases, which could be seen using the command dsplog on the PXM.
Conditions:
It was noted that in most cases, the WatchDog Timeout reset happened when SNMP scripts doing snmpsets were being run on the card. For example, when an SNMP script was continuously adding connections on the card using snmpsets.
Workaround:
None.
Detailed Problem Description and Attempted Fix:
The "WatchDog Timeout resets" were intermittent and did not happen very often. Though it could not be recreated in the lab premises, some potential causes were identified and were fixed accordingly. With these fixes, the problem is not expected to happen. Apart from these fixes, some additional logging utility has been added to the image so as to log additional information about the WatchDog reset if the reset happens again.
|
CSCds11410
|
Symptom:
The xcnfalmcnt command accepts any parameters and does not display any error messages.
Conditions:
When xcnfalmcnt command is executed with invalid parameters.
Workaround:
There is no workaround.
Problem Description:
The xcnfalmcnt command does nothing with the input parameters as this is feature is not implemented.
|
CSCds13806
|
Symptom:
Whenever an SM card is reset and the card remains stuck in boot state, even though the firmware versions of the SM are on disk.
Conditions:
This happens everytime a dspsmcnf command is issued on the PXM just before resetting an SM card.
Workaround:
Do not use the dspsmcnf command at any time. If it has to be used, then the shelf will have to be reset for the condition not to occur.
|
CSCds18765
|
The cnfupcabr on the AUSM-8 currently does policing on PCR(0+1) as the first leaky bucket and on SCR as the second leaky bucket. The second leaky bucket has to be changed to MCR, with an option of choosing the type of policing needed (already available).
Typically Standard ABR connections need to be policed only on one bucket i.e. the PCR(0+1) bucket. Currently VBR, rt-VBR and ForeSight ABR connections have two buckets each for policing - PCR(0+1) and SCR. Standard ABR policing needs to be done on PCR(0+1) only. But for consistency with the PXM (cnfupcabr), Std ABR policing will be done on PCR(0+1) as the first bucket and with ABR-MCR as the second bucket, with an option in cnfupcabr to turn second bucket policing off (as is with SCR for ForeSight ABR).
But it is important to note that during firmware Upgrade, especially for existing abr.1 connections (Transparent ABR connections with ForeSight disabled), policing will still be done based on SCR value immediately after Upgrade. This is to avoid sudden traffic pattern changes during Upgrade. The user should know that for all commands executed here after (after Upgrade) whenever the ABR MCR value is changed, the policing function will get affected since policing for Standard ABR connections will be done on MCR.
The command help for cnfupcabr has been modified. The new cnfupcabr has changes in the SCR parameter description.
|
CSCds22296
|
Symptom and Problem Description:
The atmfAtmLayerMaxVciBits object returns a value of 12 when queried from the CPE via ILMI. Because of this VCIs greater that 4095 cannot be added to interoperate with the CPE.
Workaround:
None.
Fix made:
Changed atmfAtmLayerMaxVciBits to 16 from 12.
Test setup:
1. Do an SNMP query on atmfAtmLayerMaxVciBits and check if it returns 16.
2. There should be no problems in adding a PVC on the router with VCI greater than 4095.
|
CSCds22476
|
Symptom:
The port takes a long time to come out of failure even though ILMI Keepalive polling is enabled on both ends.
Condition:
The incoming PDUs ID is not checked against the ILMI request ID.
Workaround:
No workaround.
|
CSCds22479
|
Symptom:
The port will not change state even though the Keepalive ILMI polling is enabled/disabled.
Condition:
When the ILMI Keepalive polling is enabled/disabled the port status does not change accordingly (it does not go into ILMI signaling failure/ come out of ILMI signaling failure).
Workaround:
No workaround.
|
CSCds22483
|
Symptom:
The address registration is not disabled when ILMI signaling is disabled.
Condition:
When disabling ILMI on a port using the cnfilmi CLI the address registration option is enabled (cnfilmi <portno> 2 0 16 2 1 2 2).
Workaround:
While disabling ILMI on a port also disable address registration (cnfilmi <portno> 2 0 16 1 1 1 1).
|
CSCds22489
|
Symptom:
If a port, down due to ILMI failure is deleted and added again, the ILMI failure on the port does not clear.
Condition:
The port alarm is not cleared when the ILMI is cleared.
Workaround:
The ILMI port alarm should be clear by enabling ILMI keepalive polling and then the port is to be deleted.
|
CSCds23602
|
Symptom:
The BERT pattern test for FRSM-8T1 and CESM-8T1 cards reports a high Bit Error Rate.
Conditions:
No specific conditions. Problem happens every time a BERT test is run on FRSM-8T1 and CESM-8T1 cards.
Workaround:
On Active PXM, inside shellConn set the flag newPxmWithOldSmPre1130 to 1.
|
CSCds23604
|
Symptom:
In AUSM, the xcnfilmi command has two display errors.
1. VPI <VirtualPathId> where VirtualPathId = 1 - 255. The VPI range should be 0-255.
2. PTI <PortNum> where PortNum = 1 - 8. The actual option should be -pt and -pti which is not accepted.
Condition:
This display error is present in all firmware releases prior to 1.1.31.
Workaround:
None.
|
CSCds24045
|
Symptom:
RPM connections are lost after an upgrade from 1.1.24 to 1.1.30(1.1.24Or)
Conditions:
It happens under all conditions.
Workaround:
None.
Further Description:
The customer upgraded a single PXM shelf from 1.1.24 to 1.1.24Or. After the upgrade dspcons shows connections but on RPM it shows that the connections exist only in RPM. Now a resetsys after this point causes all the connections to disappear.
|
CSCds24602
|
Symptom:
Data loss after an AUSM E1 card reset.
Condition:
This problem happens on all AUSM E1 cards with firmware version prior to 1.1.31.
Workaround:
Execute the cnfplpp command and disable the scramble option. Note that though dspplpp shows no scrambling, the actual framer programming is not done. The cnfplpp command takes care of that problem.
Unit test after fix:
One test that can be done is to have an IMA group active on the card with the lines in the IMA group configured in the "No Scramble" mode. Have connections on this IMA group with traffic flowing. Do a resetcd and confirm that the IMA group is not down, and traffic continues to flow on the connections.
|
CSCds25992
|
The command cnfplpp configures a line even when the line has not been added/enabled.
|
CSCds26096
|
Symptoms:
The dspplpp command asks the user to enter the "port_num" instead of "phy_port_num" as in xcnfportq. This can be confusing since the physical port number corresponds to the line number, and port number corresponds to the logical port number (which can be different from physical port number).
Conditions:
This is a display error, and is present in all firmware releases except prior to 1.1.31.
Workaround:
None.
Further Problem Description:
Since the dspplpp command prompts the user to enter port_num, it is possible that the user enters the logical port number, and does not get the expected display. This has been corrected now to display "phys_port_num".
|
CSCds27682
|
Symptom:
The dspalmcnt on an AUSM/B on an 8250 does not seem to register code errors on the physical line.
Conditions:
Happens on 1.1.25 AUSM firmware.
Workaround:
None.
|
CSCds32838
|
Information on this anomaly is unavailable at this time.
|
CSCds35958
|
O/p drivers are getting disabled when rd_bcE2prom is invoked.
|
CSCds38406
|
Symptom:
After a switchcc the prompt still shows "s" (for standby), when the card is actually active.
Conditions:
When using the console port for accessing the node.
Workaround:
Cc to any other card and cc back.
Further Problem Description
This problem does not occur when the node is accessed during Telnet sessions.
|
CSCds49185
|
The dspcds commands occasionally hang, causing access to the Telnet and maintenance ports to be blocked. This bug was resolved in Release 1.1.31.
|
Problems Fixed in Release 1.1.25
Bug ID
|
Description
|
CSCdr19456
|
Symptom:
The CLI of the AUSM card hangs and then the AUSM card reboots when a number of ILMI (atmfVpcVpi) requests are received by the card.
Condition:
The time gap between two ILMI (atmfVpcVpi) requests arriving at the card is too small (the rate at which the ILMI requests arriving is high).
Workaround:
The rate at which the ILMI (atmfVpcVpi) requests to be received by the card should be less than two requests per second.
|
CSCdr42989
|
Symptom:
The AUSM card generates excessive traps.
Condition:
PLPP, port, and IMA link traps are generated in excess for small bit errors on the line.
Workaround:
None.
|
CSCdr45128
|
If the primary clock is configured as inband, the dspclkinfo hardware status may shows the clock as internal even though it is inband.
|
CSCdr61335
|
Symptom:
The card gets reset.
Conditions:
The card gets reset when a continuous getnext operation on the atmfVccEntry MIB group is done via the ILMI protocol from the CPE side.
Workaround:
None.
Further Problem Description:
This is happening because one of the semaphores was not being released. Another thing was that the maxilmicells was changed from 100 to 6. This was done in order to prevent the ILMI task from hogging the CPU.
|
CSCdr63753
|
Symptom:
The Stratacom Axis Shelf correctly translates Q.933 PDUs from ATM to FR. The Axis shelf correctly translates an X.25 PDU ATM to FR to pass. X.25 PDUs with I Frame values of 0x03 0x08 FR to ATM are incorrectly translated to Q.933 PDUs. The Axis Shelf discards all X.25 1490 PDUs with and I-Frame not equal to 0x03 0x08. When PDUs are discarded, Stratacom View (9.0.03.SOL.Patch1) does show PDUs were received/transmitted but fails to show that they were discarded. Using the CLI command dspchancnt, the statistics Frames Discarded: and RcvFramesUnknownProtocols/XmtFramesUnknownProtocols were pegged on the Axis Shelf.
Conditions:
Workaround:
|
CSCdr72788
|
Symptom:
When an ATM port is added with different line and port numbers, the ATM cell delineation alarm never clears.
Condition:
This occurs when the ATM port is added with different line and port numbers.
Workaround:
Use the same number for both the line and port numbers. This has been corrected in the fix.
|
CSCdr82101
|
Symptoms:
On an ABR.1 connection (ABR with ForeSight disabled), the PCR(0+1) was changed (after adding the connection to something lower than the value it currently holds), further operations on this channel (via CLI or snmpset) fail.
Conditions:
On an ABR.1 connection (ABR with ForeSight disabled), the PCR(0+1) was changed after adding the connection to something lower than the value it currently holds, further operations on this channel (via CLI or snmpset) would fail. This is because the PCR(0+1) change would change the values of ForeSightPIR and ForeSightQIR, but leave the value of ForeSightMIR unchanged. ForeSightMIR used to have a higher value than ForeSightPIR and ForeSightQIR (after the snmpset) thereby causing further commands on this channel to fail.
Workaround:
This problem has been corrected. When PCR(0+1) is changed, it will be reflected in all three values (ForeSightPIR, ForeSightQIR, and ForeSightMIR).
|
CSCdr82560
|
Symptom:
When FRSM-2CT3 and FRSM-8 are connected on the line side and CLLM is enabled between them, FRSM-8 drops the CLLM messages sent by FRSM-CT3. Also FRSM-2CT3 cannot support CLLM timers as low as 40 ms.
Conditions:
The CLLM messages FRSM-8 drops do not carry congestion information. Hence it does not affect anything. But if the FRSM-8 is sending in CLLM messages at 100 ms then FRSM-2CT3 starts drop LMI/CLLM messages as the queue for both is common. This may lead to port alarm transitions.
Workaround:
For the first issue of FRSM-8 drop the CLLM messages there is no workaround but this problem is fixed in 1.30. For the case where FRSM-2CT3 cannot handle CLLM messages at 100 ms, the CLLM timer has to be set at least 250 ms as 2CT3 cannot support anything less.
|
CSCdr86692
|
Symptom:
The PXM is stuck in the initialized state due to a bad back card and a PXM7 cold solder problem.
Workaround:
None.
|
CSCdr89759
|
Symptom:
Traps are sent with reversed VPI and VCI values.
Conditions:
This occurs when a VCC is setup or deleted.
Workaround:
None. This has been fixed.
|
CSCdr89898
|
Symptom:
Card gets reset during connection provisioning using SNMP.
Conditions:
Back-to-back SNMP connection ADD requests will cause a reset to the FRSM-2CT3.
Workaround:
There is no concrete workaround. Introduce enough delay in the SNMP connection provisioning script.
|
CSCdr90170
|
This happens only when data flow is required between RPM and PXM over IPC channels, such as dir c: file transfer type of activities. This error message posts a warning due to IPC master and slave but does not impact IPC operations. The message appears on the console but not on the PXM syslog.
|
CSCdr92751
|
Symptom:
The card gets reset.
Conditions:
In case of Softswitch.
Workaround:
None.
Further Problem Description:
We are ignoring the config change trap when the card is not active. Also, the addimagrp trap is not sent during any card rest/Softswitch. Note that statistic requests are processed only after the card is active.
|
CSCds01770
|
Symptom:
During a manual switchCC, as the standby PXM is active, a few nonreentrant APIs are called by tasks that were waiting to go ACTIVE on standby PXM. SnmpFeRx is an example. This task calls system_initialize(). During this period, if an SNMP request is made by NMS for the MIB-2 SYstem group, the request calls the same API. As the API is nonreenterant, it causes an exception and the snmpAgent task is suspended, which causes PXM to reset.
Workaround:
None.
|
CSCds02301
|
Symptom:
None
Workaround:
A new feature to provide SNMP set switchCoreCard. This feature was backported from the 1.1.31 release to the 1.1.25 so that the PXM image can be built successfully.
|
CSCds16745
|
Symptom:
GR253 standards are not adhered to in APS unidirection mode mismatch conditions.
Workaround:
None
|
CSCds24088
|
Symptom:
Memory leaks on the hot standby card leads to the resetting of the standby.
Conditions:
Channel row status is CHAN_ADD and a connection resync starts on active.
Workaround:
1. Before you run out of memory, use a channel modify to change the chanRowStatus from CHAN_ADD to CHAN_MOD. This should be done immediately after adding the connection.
2. If you are already out of memory or have very low memory, then do a Softswitch and switchback.
|
Problems Fixed in Release 1.1.24
Bug ID
|
Description
|
CSCdp55281
|
Symptom:
Missing RPM resource partition (rpmrscprtn) line in configuration file.
Conditions:
When trying to add PVCs to an RPM module, you may be prevented from doing so. This is caused by a missing rpmrscprtn line in the configuration file running the configuration. This problem can occur if the PXM is busy when it receives an rpmrscprtn command update from the PXM. If the RPM times out after a request to the PXM, the rpmrscprtn configuration line will be missing from the running configuration file. This problem does not affect traffic or the addition of new connections.
Workaround:
Ensure that the rpmrscprtn configuration line is present in the running configuration file before resetting the RPM card, then save the running configuration file to the startup configuration. This will avoid the confusion of this line not being present in the running configuration. This command can be reexecuted on the RPM if it is missing. Please ensure that the parameters match with the PXM side. This can be checked by displaying the resource partition view on the PAR.
|
CSCdr05630
|
Symptom:
MGX 8850 Switch shelf resets with an TlbLoadException error from tDispatch as follows:
Exception Program Counter: 0x80127fac
Status Register: 0x3000ff01
Cause Register: 0x00000008
Access Address : 0xc8787854
Task: 0x82a485b0 "tDispatch"
Conditions:
The shelf resets when the RPM is stressed; specifically, 3000-byte UDP packets loaded at -9.8 MB on e1/4 and approximately 170 kbps worth of s on e1/1.
Workaround:
None.
|
CSCdr19633
|
Symptom:
On an AUSM-8T1/E1, the IMA group name matched to an individual line forces the group to go down.
Conditions:
When a line is configured with the IMA group name, then the entire IMA group goes down if the line goes down.
Workaround:
Do not use the same name for the IMA group as the name given to the lines used.
Evaluation:
For AUSM card, when a line goes down, if there is a port(s) within the line, AUSM always send a porttrap to PXM. If the line is one of the links in an IMA GROUP, there is no porttrap except if the available number of links is less than the configured minimum.
This means that when PXM receives linetrap, for AUSM card, it does not need to generate porttrap, which will fix the problem.
|
CSCdr34252
|
Symptom:
Management PVC between the MGX 8850 and remote equipment fails after Softswitch of AUSM cards.
Conditions:
After Softswitch is performed the PVC that passes management traffic between devices stops passing through the PXM.
Workaround:
None.
Further Problem Description:
Management IP connections added from service modules to 7.34 fail to pass data after a switch over occurs from the primary to the secondary.
|
CSCdr35117
|
Symptom:
The PXM shelf resets when the RPM is under stress.
Condition:
This problem occurs when the RPM is loaded with an enclosed configuration and traffic is generated toward CARed interfaces with CBWFQ.
Workaround:
None.
Further Problem Description:
The IOS IPC code on PXM was not handling NAK messages from RPM correctly. The code was not checking to see if the port (polling port) the NAK is received for still exists or not (checking for NULL pointer). This cause access to invalid address and eventually shelf reset.
|
CSCdr38391
|
Symptom:
Running the clrsmcnf command on a CESM and resetting the standby PXM causes the card to come up in cardinit state.
Workaround:
None. The code has been modified to pass LCN index zero instead of firstdatalcn.
|
CSCdr42987
|
Symptom:
End-to-end OAM cells are dropped by the AUSM-8T1/E1 card.
Conditions:
As of Release 5.0.11, AUSM-8T1/E1 dropped end-to-end loopback cells other than AIS, RDI, and Loopback function types in Fault Management OAM cell type. This problem is now corrected so that the end-to-end OAM cells pass through the AUSM-8T1/E1 card though the card does not monitor all of them.
Workaround:
None.
|
CSCdr49478
|
Symptom:
After a sequence of adding and deleting service module redundancy and issuing the clrsmcnf command, and connection deletion/addition, the command tstcon does not pass on certain connections.
Conditions:
This problem occurs when a 1:1 redundancy is configured between VHS cards in
slot 1 and slot 2. Card 1 is active, and card 2 is standby. Connections are added from 1 to 5. Then, redundancy deleted and connections deleted both on slot 1 and on slot 5 using the clrsmcnf command. Redundancy was then added between slots 1 and 5, and subsequently deleted.
Note that the connection addition was done in an environment wherein no connections existed either on slot 5, slot 1, or slot 2.
Workaround:
1. Use CWM or the CLI to delete connections on both slots when a service module is configured with redundancy.
2. Then issue the command clrsmcnf to clear the port/line configuration.
|
CSCdr51248
|
Symptom:
A mismatch is reported due to a MIB corruption since the new versions of VISMs need larger allocation of memory for the MIB.
Workaround:
None.
|
CSCdr55023
|
Symptom:
ARP translation doesn't work on FRSM-2CT3. Both the destination and the source IP addresses get corrupted in the ARP reply.
Conditions:
This problem occurs when ARP request is initiated from the ATM side. This problem does not occur if ARP request is initiated from the FR CPE side.
Workaround:
One of the following:
1. Use a static IP address instead of ARP.
2. Initiate ARP request from FR CPE.
|
CSCdr61548
|
Symptom:
The card resets/fails when more than 600 connections are added when LMI is configured on the port.
Condition:
LMI packets gets corrupted after 600 connections, and subsequently leads to problems during the ESE-SAR handshake. This causes ESE to stop.
Workaround:
No workaround for more than 600 connections.
|
CSCdr62285
|
Symptom:
The CESM module generates a general error.
Conditions:
When the command cnfbert is issued, the causes the CESM module to generate the error.
Workaround:
None.
|
Problems Fixed in Release 1.1.23
Bug ID
|
Description
|
CSCdp80130
|
The dspapsln shows both APS lines to be OK when alarm exists.
|
CSCdp88046
|
Slow TFTP GET and corrupted CF file checksum for SM with 3920 active chans.
|
CSCdm12468
|
PXM CLI cannot read NVRAM data for UI back card and trunk back card.
|
CSCdm73868
|
New IMA link failure trap 50251 is generated.
|
CSCdm82756
|
The MGX 8850 stores user passwords in clear text. Any person with IP connectivity to the MGX 8850 can TFTP the userPassword.dat file from the MGX 8850 and view all the passwords. Password are encrypted before saving in the database.
|
CSCdm83076
|
IMA Group failure status is Ne start up, whereas Ne is operational.
|
CSCdp12290
|
When deleting port, no trap should be sent if RSC partition diskupdate fails. Return value for resource partition deletion diskupdate message, as part of port deletion, is not checked before sending out the subsequent resource partition config change trap. Also, when one of the resource partition diskupdate fails, the port deletion process should stop.
|
CSCdp14073
|
A dspabit type command.
|
CSCdp20616
|
Cell-loss on PXM-UNI conn on switchover caused by SRM back card removal.
|
CSCdp43334
|
The BERT on the FRSM-VHS require the xcnfln, which has misleading parameters for the FRSM-T3 and FRSM-E3 service module. Although some parameters like -ds3enb (dsx3LineBERTEnable) also appear under the xcnfln for the FRSM-E3 card, but BERT could not be started with this parameter and it requires a different parameter -ds3ben (dsx3LineBERTEnable).
Some other times when BERT is enabled on one line, you could not delete the BERT from this line using deldsx3bert and hence forth BERT cannot be enabled on any other line.
|
CSCdp46146
|
Cannot delete RPM-RPM connection from the PXM.
|
CSCdp47079
|
Policing defaulted to off on certain PXM connection (VBR and ABR).
|
CSCdp50541
|
PXM-trunk-clocking goes bad on PXM-switchover. Periodic cell loss on FDR-conns.
|
CSCdp51846
|
INCS1.5: Slot failure on SRM brings down voice services CSCdp52180 MGX SRM fail/switchover outage time is unacceptable. CSCdp53887 Feeder connections could not be added via SNMP on AUSM.
|
CSCdp54765
|
Cannot add a port to a slot until card reset on FRSM-8T1/E1.
|
CSCdp57974
|
Need varbind for Configured Links in certain IMA traps.
|
CSCdp58707
|
The dspbecnt command does not work correctly for the non-active line currently.
|
CSCdp62456
|
Database integrity commands do not catch incomplete master conns.
|
CSCdp62652
|
No updated information about IMA Rx grp ID on AUSM.
|
CSCdp63757
|
FunctionModuleFailed Trap 50006 keeps repeating twice.
|
CSCdp65370
|
The port on the CESM-T3/E3 is in active state but the line is in RcvLOS alarm. When a T3 or E3 line indicates an alarm condition, the corresponding port state is not updated correctly. Port state is still displayed as active instead of failed due to line.
|
CSCdp65557/
CSCdp75117
|
Softswitch on AUSM causes 29 sec. channel outage. When you perform a Softswitch from Primary AUSM to Secondary AUSM in non-bulk mode, if system is very busy, the remote equipment may notice LOF or LOS. It is intermittent.
|
CSCdp65651
|
Need to support a new VSI force Del passthru to handle connection timeout. During the connection addition, if the timeout occurs in VSI slave, SPM will clean up all the resources allocated for the connection. It then sends HD Update Fail message to the SM. Both SM & SPM do not have the connection anymore but PAR still has the connection in its database. If the user try to read the connection, PAR will reject the request. The user can not delete the connection either since there is none in the SM.
|
CSCdp69367
|
Need to disable CLI session timeout when issuing clrsmcnf. The fix involves disabling the session timeout before clrsmcnf or restoresmcnf commands are carried out and re-enabling the session timeout period when complete.
|
CSCdp69416
|
Removal of back card on active APS line causes trunk and conn failure.
|
CSCdp70976
|
Arbitrary number of voice calls are dropped due to switchcc on PXM.
|
CSCdp75827
|
Values specified via cnflmitimer not preserved after switchcc/resetsy.
|
CSCdp75844
|
LMI timeout values specified via the cnflmitimer value not correct. Prior to this fix LMI timers had to be configured (using cnflmitimer command) to double the desired value of LMI timeout.
|
CSCdp75879
|
Signaling bits toggle in case of voltage disturbance on T1 input lea.
|
CSCdp76372
|
FRSM-2CT3 dspchancnt does not have KbpsAIR field.
|
CSCdp77244
|
Support port rate modification without deleting connections.
|
CSCdp80104
|
The dspapsln shows both lines in R_AM after alarm on one line was cleared.
|
CSCdp80154
|
The dspapsln shows one line in R_AM when both are.
|
CSCdp81205
|
When Protection Line was unplugged, it went into P_B state.
|
CSCdp81859
|
Introduce dspfail command to display failed connections.
|
CSCdp82888
|
PXM reset/switchcc causes the AUSM port to fail.
|
CSCdp84676
|
When the service module tries to do graceful upgrade PXM crashes.
|
CSCdp84773
|
Symptom:
The resource partition does not get registered on the PXM card.
Conditions:
The resource partitioning of the AUSM card on the PXM is registered as zero instead of a value of three. This process takes place automatically with the AUSM card. On the VISM, it is done by issuing the command addrscprtn.
|
CSCdp87088
|
CESM-8T1/E1 clock change to async mode on line causes bit errors on another line.
|
CSCdp88526
|
FRSM-2CT3 cards fail when script run to add 4000 conns.
|
CSCdp91587
|
The dsx3LineXmtClockSrc cannot be set to localClk on PXM T3.
|
CSCdp92627
|
Cannot add redundancy from primary AUSM slot 19 to 30.
|
CSCdp96495
|
FRSM-2E3 does not support G.751 clearchannel format.
|
CSCdp99561
|
Cannot disable policing on the FRSM-2CT3 if Bc & Be set to max.
|
CSCdp99581
|
FRSM-CT3 egress queue build up causing the ingress VCQ to start discard even though traffic was being generated at PIR, with no other VCs active.
|
CSCdp99795
|
The k:dspservrate does not show correct values.
|
CSCdr07429
|
The restoresmcnf not completely working.
|
CSCdr07460
|
The addlnloop on the PXM causes a bidirectional loop.
|
CSCdr08552
|
Not able to delete connections from SM after switchcc. In case of UNI connections, able to delete connections but dspcons still shows the connections.
|
CSCdr09310
|
VxWorks Ping hangs on receiving ICMP unreachable message from NMS.
|
CSCdr11405
|
PVC alarms on FRSM-2CT3 cleared by Softswitch.
|
CSCdr12167
|
Pulling active SRM causes IMA PVC to lose traffic w/o alarm.
|
CSCdr15904
|
Frames drop on FR-ATM PVCs.
|
CSCdr15904
|
Frames are getting dropped on FR-ATM PVC, reason is not shown.
|
CSCdr25595
|
/vob/psm/switchmgm/rmeptsm.c
In func rmRebindLcnEpt(), modified the code not to init the pEptBlk->state, pEptBlk->lmiStatus, pEptBlk->lmiChangeFlag if EptBlk already exists.
|
Compatibility Notes
MGX 8230/8250/8850 Software Interoperability with Other Products
Platform Software:
|
PXM 1.1.32
|
MGX 8220 Firmware:
|
Rev: 4.1.09 or 5.0.15 (Refer to the MGX 8220 Release Notes)
|
Compatible Switch Software:
|
Switch Software Release 9.2.33 for BPX and BXM firmware—MFF (Refer to the Switch Software Release Notes)
|
Network Management Software:
|
CWM 10.4. Refer to the CWM 10.4 Release Notes.
|
|
CiscoView:
|
CV 10.4. Refer to the CWM 10.4 Release Notes.
|
The MGX 1x feeder to MGX 2x:
|
MGX 2.0.12
|
Firmware File Names and Sizes
The following table displays the file names and file sizes for the Release 1.1.32 Firmware and IOS files. These files correspond to the compatibility charts on the following pages:
File Name
|
File Size (in bytes)
|
pxm_1.1.32.fw
|
2241996
|
pxm_bkup_1.1.32.fw
|
1301128
|
pxm_sc_1.1.32.fw
|
2241488
|
ausm_8t1e1_AU8_BT_1.0.02.fw
|
377836
|
ausm_8t1e1_AU8_BT_1.0.02.hex
|
1054496
|
cesm_8t1e1_CE8_BT_1.0.02.fw
|
264592
|
cesm_8t1e1_CE8_BT_1.0.02.hex
|
735986
|
cesm_t3e3_CE8_BT_1.0.02.fw
|
303936
|
cesm_t3e3_CE8_BT_1.0.02.hex
|
846641
|
frsm_8t1e1_FR8_BT_1.0.02.fw
|
297988
|
frsm_8t1e1_FR8_BT_1.0.02.hex
|
829946
|
frsm_hs1_HS1_BT_1.0.02.fw
|
293052
|
frsm_hs1_HS1_BT_1.0.02.hex
|
816041
|
frsm_vhs_VHS_BT_1.0.02.fw
|
467156
|
frsm_vhs_VHS_BT_1.0.02.hex
|
1305731
|
ausm_8t1e1_10.0.21.fw
|
1195740
|
cesm_8t1e1_10.0.21.fw
|
677872
|
cesm_t3e3_10.0.21.fw
|
606240
|
frsm_8t1e1_10.0.21.fw
|
821064
|
frsm_hs1_10.0.21.fw
|
763692
|
cesm_8t1e1_10.0.21.hex
|
1898336
|
cesm_t3e3_10.0.21.hex
|
1696871
|
frsm_vhs_10.0.22.fw
|
935860
|
rpm-boot-mz.121-5.3.T_XT
|
2448740
|
rpm-js-mz.121-5.3.T_XT
|
7895412
|
vism_8t1e1_002.000.001.001.fw
|
2159384
|
vism_8t1e1_VI8_BT_2.0.01.fw
|
245136
|
MGX 8850 Firmware Compatibility
System Release 1.1.32
PCB Description
|
CW2000 Name
|
Latest F/W
|
Min F/W
|
File Name
|
File Size
(in bytes)
|
PXM1
|
PXM-1
|
1.1.32
|
1.1.32
|
pxm_1.1.32.fw
|
2241996
|
PXM1-2-T3E3
|
PXM1-2T3E3
|
1.1.32
|
1.1.32
|
pxm_1.1.32.fw
|
2241996
|
PXM1-4-155
|
PXM1-4OC3
|
1.1.32
|
1.1.32
|
pxm_1.1.32.fw
|
2241996
|
PXM1-1-622
|
PXM1-OC12
|
1.1.32
|
1.1.32
|
pxm_1.1.32.fw
|
2241996
|
MGX-SRM-3T3/B
|
SRM-3T3
|
n/a
|
n/a
|
n/a
|
n/a
|
AX-CESM-8E1
|
CESM-8E1
|
10.0.21
|
10.0.21
|
cesm_8t1e1_10.0.21.fw
|
677872
|
AX-CESM-8T1
|
CESM-8T1
|
10.0.21
|
10.0.21
|
cesm_8t1e1_10.0.21.fw
|
677872
|
MGX-AUSM-8E1/B
|
AUSMB-8E1
|
10.0.21
|
10.0.21
|
ausm_8t1e1_10.0.21.fw
|
1195740
|
MGX-AUSM-8T1/B
|
AUSMB-8T1
|
10.0.21
|
10.0.21
|
ausm_8t1e1_10.0.21.fw
|
1195740
|
MGX-CESM-T3
|
CESM-T3
|
10.0.21
|
10.0.21
|
cesm_t3e3_10.0.21.fw
|
606240
|
MGX-CESM-E3
|
CESM-E3
|
10.0.21
|
10.0.21
|
cesm_t3e3_10.0.21.fw
|
606240
|
AX-FRSM-8E1/E1-C
|
FRSM-8E1
|
10.0.21
|
10.0.21
|
frsm_8t1e1_10.0.21.fw
|
821064
|
AX-FRSM-8T1/T1-C
|
FRSM-8T1
|
10.0.21
|
10.0.21
|
frsm_8t1e1_10.0.21.fw
|
821064
|
MGX-FRSM-HS2
|
FRSM-HS2
|
10.0.22
|
10.0.22
|
frsm_vhs_10.0.22.fw
|
935860
|
MGX-FRSM-2CT3
|
FRSM-2CT3
|
10.0.22
|
10.0.22
|
frsm_vhs_10.0.22.fw
|
935860
|
MGX-FRSM-2T3E3
|
FRSM-2T3
|
10.0.22
|
10.0.22
|
frsm_vhs_10.0.22.fw
|
935860
|
MGX-FRSM-2T3E3
|
FRSM-2E3
|
10.0.22
|
10.0.22
|
frsm_vhs_10.0.22.fw
|
935860
|
MGX-FRSM-HS1/B
|
FRSM-HS1/B
|
10.0.21
|
10.0.21
|
frsm_hs1_10.0.21.fw
|
763692
|
MGX-VISM-8T1
|
VISM-8T1
|
2.0(1.1)
|
1.5.05
|
vism_8t1e1_002.000.001.001.fw
|
2159384
|
MGX-VISM-8E1
|
VISM-8E1
|
2.0(1.1)
|
1.5.05
|
vism_8t1e1_002.000.001.001.fw
|
2159384
|
RPM IOS Compatibility (MGX 8850)
RPM IOS version requirements (with Release 1.1.32):
PCB Description
|
CW2000 Name
|
Latest IOS
|
Min IOS
|
MGX-RPM-128M/B
|
RPM
|
12.1(5.3)T_XT
|
12.1(5.3)T_XT
|
MGX-RPM-PR
|
RPM-PR
|
12.1(5.3)T_XT
|
12.1(5.3)T_XT
|
Each RPM card requires the following two files (with Release 1.1.32):
RPM File Type
|
File Name
|
File Size (in bytes)
|
Boot File
|
rpm-boot-mz.121-5.3.T_XT
|
2448740
|
Firmware File
|
rpm-js-mz.121-5.3.T_XT
|
7895412
|
MGX 8250 Firmware Compatibility
System Release 1.1.32
PCB Description
|
CW2000 Name
|
Latest F/W
|
Min F/W
|
File Name
|
File Size
(in bytes)
|
PXM1
|
PXM-1
|
1.1.32
|
1.1.32
|
pxm_1.1.32.fw
|
2241996
|
PXM1-2-T3E3
|
PXM1-2T3E3
|
1.1.32
|
1.1.32
|
pxm_1.1.32.fw
|
2241996
|
PXM1-4-155
|
PXM1-4OC3
|
1.1.32
|
1.1.32
|
pxm_1.1.32.fw
|
2241996
|
PXM1-1-622
|
PXM1-OC12
|
1.1.32
|
1.1.32
|
pxm_1.1.32.fw
|
2241996
|
MGX-SRM-3T3/B
|
SRM-3T3
|
n/a
|
n/a
|
n/a
|
n/a
|
AX-CESM-8E1
|
CESM-8E1
|
10.0.21
|
10.0.21
|
cesm_8t1e1_10.0.21.fw
|
677872
|
AX-CESM-8T1
|
CESM-8T1
|
10.0.21
|
10.0.21
|
cesm_8t1e1_10.0.21.fw
|
677872
|
MGX-AUSM-8E1/B
|
AUSMB-8E1
|
10.0.21
|
10.0.21
|
ausm_8t1e1_10.0.21.fw
|
1195740
|
MGX-AUSM-8T1/B
|
AUSMB-8T1
|
10.0.21
|
10.0.21
|
ausm_8t1e1_10.0.21.fw
|
1195740
|
MGX-CESM-T3
|
CESM-T3
|
10.0.21
|
10.0.21
|
cesm_t3e3_10.0.21.fw
|
606240
|
MGX-CESM-E3
|
CESM-E3
|
10.0.21
|
10.0.21
|
cesm_t3e3_10.0.21.fw
|
606240
|
AX-FRSM-8E1/E1-C
|
FRSM-8E1
|
10.0.21
|
10.0.21
|
frsm_8t1e1_10.0.21.fw
|
821064
|
AX-FRSM-8T1/T1-C
|
FRSM-8T1
|
10.0.21
|
10.0.21
|
frsm_8t1e1_10.0.21.fw
|
821064
|
MGX-FRSM-HS2
|
FRSM-HS2
|
10.0.22
|
10.0.22
|
frsm_vhs_10.0.22.fw
|
935860
|
MGX-FRSM-2CT3
|
FRSM-2CT3
|
10.0.22
|
10.0.22
|
frsm_vhs_10.0.22.fw
|
935860
|
MGX-FRSM-2T3E3
|
FRSM-2T3
|
10.0.22
|
10.0.22
|
frsm_vhs_10.0.22.fw
|
935860
|
MGX-FRSM-2T3E3
|
FRSM-2E3
|
10.0.22
|
10.0.22
|
frsm_vhs_10.0.22.fw
|
935860
|
MGX-FRSM-HS1/B
|
FRSM-HS1/B
|
10.0.21
|
10.0.21
|
frsm_hs1_10.0.21.fw
|
763692
|
MGX-VISM-8T1
|
VISM-8T1
|
2.0(1.1)
|
1.5.05
|
vism_8t1e1_002.000.001.001.fw
|
2159384
|
MGX-VISM-8E1
|
VISM-8E1
|
2.0(1.1)
|
1.5.05
|
vism_8t1e1_002.000.001.001.fw
|
2159384
|
RPM IOS Compatibility (MGX 8250)
RPM IOS version requirements (with Release 1.1.32):
PCB Description
|
CW2000 Name
|
Latest IOS
|
Min IOS
|
MGX-RPM-128M/B
|
RPM
|
12.1(5.3)T_XT
|
12.1(5.3)T_XT
|
MGX-RPM-PR
|
RPM-PR
|
12.1(5.3)T_XT
|
12.1(5.3)T_XT
|
Each RPM card requires the following two files (with Release 1.1.32):
RPM File Type
|
File Name
|
File Size (in bytes)
|
Boot File
|
rpm-boot-mz.121-5.3.T_XT
|
2448740
|
Firmware File
|
rpm-js-mz.121-5.3.T_XT
|
7895412
|
MGX 8230 Firmware Compatibility
System Release 1.1.32
PCB Description
|
CW2000 Name
|
Latest F/W
|
Min F/W
|
File Name
|
File Size
(in bytes)
|
PXM1
|
PXM-1
|
1.1.32
|
1.1.32
|
pxm_sc_1.1.32.fw
|
2241488
|
PXM1-2-T3E3
|
PXM1-2T3E3
|
1.1.32
|
1.1.32
|
pxm_sc_1.1.32.fw
|
2241488
|
PXM1-4-155
|
PXM1-4OC3
|
1.1.32
|
1.1.32
|
pxm_sc_1.1.32.fw
|
2241488
|
PXM1-1-622
|
PXM1-OC12
|
1.1.32
|
1.1.32
|
pxm_sc_1.1.32.fw
|
2241488
|
MGX-SRM-3T3/B
|
SRM-3T3
|
n/a
|
n/a
|
n/a
|
n/a
|
AX-CESM-8E1
|
CESM-8E1
|
10.0.21
|
10.0.21
|
cesm_8t1e1_10.0.21.fw
|
677872
|
AX-CESM-8T1
|
CESM-8T1
|
10.0.21
|
10.0.21
|
cesm_8t1e1_10.0.21.fw
|
677872
|
MGX-AUSM-8E1/B
|
AUSMB-8E1
|
10.0.21
|
10.0.21
|
ausm_8t1e1_10.0.21.fw
|
1195740
|
MGX-AUSM-8T1/B
|
AUSMB-8T1
|
10.0.21
|
10.0.21
|
ausm_8t1e1_10.0.21.fw
|
1195740
|
MGX-CESM-T3
|
CESM-T3
|
10.0.21
|
10.0.21
|
cesm_t3e3_10.0.21.fw
|
606240
|
MGX-CESM-E3
|
CESM-E3
|
10.0.21
|
10.0.21
|
cesm_t3e3_10.0.21.fw
|
606240
|
AX-FRSM-8E1/E1-C
|
FRSM-8E1
|
10.0.21
|
10.0.21
|
frsm_8t1e1_10.0.21.fw
|
821064
|
AX-FRSM-8T1/T1-C
|
FRSM-8T1
|
10.0.21
|
10.0.21
|
frsm_8t1e1_10.0.21.fw
|
821064
|
MGX-FRSM-HS2
|
FRSM-HS2
|
10.0.22
|
10.0.22
|
frsm_vhs_10.0.22.fw
|
935860
|
MGX-FRSM-2CT3
|
FRSM-2CT3
|
10.0.22
|
10.0.22
|
frsm_vhs_10.0.22.fw
|
935860
|
MGX-FRSM-2T3E3
|
FRSM-2T3
|
10.0.22
|
10.0.22
|
frsm_vhs_10.0.22.fw
|
935860
|
MGX-FRSM-2T3E3
|
FRSM-2E3
|
10.0.22
|
10.0.22
|
frsm_vhs_10.0.22.fw
|
935860
|
MGX-FRSM-HS1/B
|
FRSM-HS1/B
|
10.0.21
|
10.0.21
|
frsm_hs1_10.0.21.fw
|
763692
|
MGX-VISM-8T1
|
VISM-8T1
|
2.0(1.1)
|
2.0(1.1)
|
vism_8t1e1_002.000.001.001.fw
|
2159384
|
MGX-VISM-8E1
|
VISM-8E1
|
2.0(1.1)
|
2.0(1.1)
|
vism_8t1e1_002.000.001.001.fw
|
2159384
|
RPM IOS Compatibility (MGX 8230)
RPM IOS version requirements (with Release 1.1.32):
PCB Description
|
CW2000 Name
|
Latest IOS
|
Min IOS
|
MGX-RPM-128M/B
|
RPM
|
12.1(5.3)T_XT
|
12.1(5.3)T_XT
|
MGX-RPM-PR
|
RPM-PR
|
12.1(5.3)T_XT
|
12.1(5.3)T_XT
|
Each RPM card requires the following two files (with Release 1.1.32):
RPM File Type
|
File Name
|
File Size (in bytes)
|
Boot File
|
rpm-boot-mz.121-5.3.T_XT
|
2448740
|
Firmware File
|
rpm-js-mz.121-5.3.T_XT
|
7895412
|
Compatibility Matrix
This multiservice gateway comparison matrix is designed to identify capabilities supported in the MGX 8220, 8230, 8250, and 8850 platforms.
Feature
|
MGX 8220
|
MGX 8230
|
MGX 8250
|
MGX 8850, PXM1
|
Slot Capacity
|
|
|
|
|
Total Number of Slots
|
16 single-height
|
14 single-height/
7 double-height, or combination
|
32 single-height/
16 double-height, or combination
|
32 single-height/
16 double-height, or combination
|
Slots for Processor cards (PXM1s)
|
2 single-height (plus 2 slots reserved for BNM)
|
2 double-height
|
2 double-height
|
2 double-height
|
Slots for Service Modules (SMs)
|
10 single-height
|
8 single-height/
4 double-height or combination
|
24 single-height/ 12 double-height, or combination
|
24 single-height/
12 double-height combination
|
Slots for SRM Cards
(Service Resource Modules)
|
2 single-height
|
2 single-height
|
4 single-height
|
4 single-height
|
| |
Physical Attributes
|
8220
|
8230
|
8250
|
8850
|
Height (in inches)
|
8.75
|
12.25
|
26.25 to 29.75
|
26.25 to 29.75
|
Width (in inches)
|
17.45
|
17.72
|
17.72
|
17.72
|
Depth
|
20.0
|
23.5
|
21.5
|
21.5
|
| |
Services
|
8220
|
8230
|
8250
|
8850
|
MPLS (IP +ATM)
|
No
|
4
|
4
|
4
|
Voice
|
No
|
4
|
4
|
4
|
ATM
|
4
|
4
|
4
|
4
|
Frame Relay
|
4
|
4
|
4
|
4
|
Frame Relay-to-ATM network interworking
|
4
|
4
|
4
|
4
|
Frame Relay-to-ATM service interworking
|
4
|
4
|
4
|
4
|
Circuit Emulation
|
4
|
4
|
4
|
4
|
| |
Local Switching
|
8220
|
8230
|
8250
|
8850
|
| |
No
|
4
|
4
|
4
|
| |
PNNI Routing
|
8220
|
8230
|
8250
|
8850
|
| |
No
|
Future—will require upgrade
|
Future—will require upgrade
|
Future on PXM1
|
| |
BPX Feeder
|
8220
|
8230
|
8250
|
8850
|
Feeder to BPX 8600
|
4
|
4
|
4
|
4
|
Feeder to MGX 8850 PXM-45
|
No
|
4
|
4
|
4
|
Feeder to IGX
|
No
|
4
|
No
|
No
|
| |
Automatic Protection Switching
(APS 1+1)
|
8220
|
8230
|
8250
|
8850
|
| |
No
|
4
|
4
|
4
|
| |
Switching Capacity
|
8220
|
8230
|
8250
|
8850
|
| |
320 Mbps
|
1.2 Gbps
|
1.2 Gbps
|
1.2 Gbps
|
| |
Trunk/Port Interfaces
|
8220
|
8230
|
8250
|
8850
|
T3/E3
|
1
|
2
(one feeder trunk)
|
2
(one feeder trunk)
|
2
|
OC-3c/STM-1
|
1
|
4
(one feeder trunk)
|
4
(one feeder trunk)
|
4
|
OC-12c/STM-4
|
No
|
1
|
1
|
1
|
OC-48c/STM-16
|
No
|
No
|
No
|
No
|
n x T1/E1
|
4
|
4
|
4
|
4
|
| |
Service Module Front Cards
|
8220
|
8230
|
8250
|
8850
|
AX-FRSM-8T1
|
4
|
4
|
4
|
4
|
AX-FRSM-8E1
|
4
|
4
|
4
|
4
|
AX-FRSM-8T1-C
|
4
|
4
|
4
|
4
|
AX-FRSM-8E1-C
|
4
|
4
|
4
|
4
|
MGX-FRSM-HS2
|
4
|
4
|
4
|
4
|
AX-FRSM-HS1
|
4
|
No
|
No
|
No
|
MGX-FRSM-HS1/B
|
4
|
4
|
4
|
4
|
MGX-FRSM-2T3/E3
|
No
|
4
|
4
|
4
|
MGX-FRSM-2CT3
|
No
|
4
|
4
|
4
|
AX-AUSM-8T1
|
4
|
No
|
No
|
No
|
MGX-AUSM-8T1/B
|
4
|
4
|
4
|
4
|
AX-AUSM-8E1
|
4
|
No
|
No
|
No
|
MGX-AUSM-8E1/B
|
4
|
4
|
4
|
4
|
AX-IMATM-8T1/B
|
4
|
No
|
No
|
No
|
AX-IMATM-8E1/B
|
4
|
No
|
No
|
No
|
AX-CESM-8T1
|
4
|
4
|
4
|
4
|
AX-CESM-8E1
|
4
|
4
|
4
|
4
|
MGX-CESM-T3E3
|
No
|
4
|
4
|
4
|
AX-SRM-T1E1/B
|
4
|
No
|
No
|
No
|
AX-SRM-3T3
|
4
|
No
|
No
|
No
|
MGX-SRM-3T3/B
|
4
|
No
|
4
|
4
|
MGX-SRM-3T3/C
|
Future
|
4
|
4
|
4
|
MGX-VISM-8T1
|
No
|
4
|
4
|
4
|
MGX-VISM-8E1
|
No
|
4
|
4
|
4
|
MGX-RPM-128/B
|
No
|
4
|
4
|
4
|
MGX-RPM-PR
|
No
|
Future
|
Future
|
Future
|
PXM1
|
No
|
8230PXM1
|
8250PXM1
|
PXM1
|
PXM1-2T3E3
|
No
|
8230PXM1-2T3
8230PXM1-2E3
|
8250PXM1-2T3
8250PXM1-2E3
|
PXM1-2T3E3
|
PXM1-4-155
|
No
|
8230PXM1OC3-SIR
8230PXM1OC3-SLR
8230PXM1OC3-MMF
|
8250PXM1OC3-SIR
8250PXM1OC3-SLR
8250PXM1OC3-MMF
|
PXM1-4-155
|
PXM1-1-622
|
No
|
8230PXM1OC12-SIR
8230PXM1OC12-SLR
|
8250PXM1OC12-SIR
8250PXM1OC12-SLR
|
PXM1-1-622
|
PXM45
|
No
|
No
|
No
|
No
|
| |
Back Cards
|
8220
|
8230
|
8250
|
8850
|
AX-SMB-8E1
|
4
|
4
|
4
|
4
|
AX-RJ48-8E1
|
4
|
4
|
4
|
4
|
AX-RJ48-8T1
|
4
|
4
|
4
|
4
|
AX-R-SMB-8E1
|
4
|
4
|
4
|
4
|
AX-R-RJ48-8E1
|
4
|
4
|
4
|
4
|
AX-R-RJ48-8T1
|
4
|
4
|
4
|
4
|
MGX-SCSI2-2HSSI/B
|
4
|
4
|
4
|
4
|
MGX-12IN1-4S
|
4
|
4
|
4
|
4
|
MGX-BNC-2T3
|
No
|
4
|
4
|
4
|
MGX-BNC-2E3
|
No
|
4
|
4
|
4
|
MGX-BNC-2E3A
|
No
|
4
|
4
|
4
|
MGX-BNC-3T3-M
|
Future
|
4
|
4
|
4
|
PXM1-UI
|
No
|
4
|
4
|
4
|
PXM-UI-S3
|
No
|
4
|
4
|
4
|
MGX |
