Table Of Contents
New Features and Enhancements in Release 4.0.00
Preferred Routes for PNNI Multipeer Group Networks
Point-to-Multipoint SVC/SPVC Support
Increased Number of Signaling Interfaces
PXM1E-Related Hardware (the PXM1E-8-155 card)
Modular Transceiver Support in the New 8-port OC3/STM1 Back Card
UNI connection support in PXM1E-16-T1E1
Cell Bus Service Module Support
Virtual Trunks Support in PXM1E
AXSM-E as Upstream to Feeder Nodes
Cell Bus Service Modules on PXM45
Service Class Template (SCT) File Information
Software/Firmware Interoperability Matrix
MGX and RPM Software Version Compatibility Matrix
New Hardware in Release 4.0.00
MGX 8850 (PXM45) Product IDs and Card Types
MGX 8850 (PXM1E) Product IDs and Card Types
MGX 8830 Product IDs and Card Types
MGX 8950 Product IDs and Card Types
New and Changed PXM45 and PXM1E Commands
AXSM-4-2488-XG Channelization Commands
Limitations, Restrictions, and Notes for 4.0.00
Point to Multipoint SVC/SPVC Support
Narrow Band Service Modules and RPM-PR
AXSM-E as Upstream to Feeder Nodes
Maximum Threshold Accuracy for PXM45 and PXM1E
Controller Card Mastership Sanity Verification
Serial Bus Path Fault Isolation
Cell Bus Path Fault Isolation and Recovery
Non-native Controller Front Card and PXM-HD Card
Simple Network Timing Protocol (SNTP)
AXSM-32-T1E1-E and PXM1E-16-T1E1
Other Limitations and Restrictions
Clearing the Configuration on Redundant PXM45 and PXM1E Cards
Limitations and Restrictions for 2.1.x
General Limitations, Restrictions, and Notes
Limitations for rteopt via parallel links
Installation and Upgrade Procedures
Cisco MGX 8850 (PXM45) Multiservice Switch Release 4
Cisco MGX 8850 (PXM1E) Multiservice Switch Release 4
Cisco MGX 8950 Multiservice Service Release 4
Cisco MGX 8830 Multiservice Switch Release 4
Cisco WAN Switching Software Release 9.4
MGX 8850 (PXM1) Edge Concentrator Release 1.2.20
MGX 8250 Edge Concentrator Release 1.2.20
MGX 8230 Edge Concentrator Release 1.2.20
How to Find Multiservice Switch Customer Documents Online
If the Part Number is Not Known
Documentation on the World Wide Web
Contacting TAC by Using the Cisco TAC Website
MGX 8850, MGX 8830, and MGX 8950 Anomalies
Known Anomalies in Release 4.0.00
Known Route Processor Module or MPLS Anomalies
Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830, Software Version 4.0.00
Contents
These release notes are part OL-3245-01 Rev. D0, January 21, 2004.
About Release 4.0.00
These release notes describe the system requirements, new features, and limitations that apply to Release 4.0.00 of the MGX 8850 and the new MGX 8830 multiservice switch. These notes also contain Cisco support information.
MGX Release 4.0.00 helps fulfill the original MGX feature expectation of direct cell bus service module (CBSM) support on both feeder and routing nodes, while positioning the high end of the product line for next-generation broadband networking.
With this release, most of the Narrow Band Service Modules currently supported on the MGX 8850 (PXM1) are now supported on the MGX 8830 and MGX 8850 (PXM1E) and MGX 8850 (PXM45). This brings to service providers unparalleled flexibility in the way they choose to terminate service access in their networks.
MGX Release 4.0.00 also brings to the industry the first true next-generation multiservice platform with a new set of Service Modules that put the MGX 8950 switch's powerful backplane throughput at the fingertips of network architects. An MGX 8950 chassis can now be configured with the highest broadband port density available in the industry and up to 10G bandwidth available from each of the 12 Service Module slots.
In support of this unprecedented multiservice throughput, a slew of PNNI features are also being released to facilitate continued expansion of MGX networks.
These release notes complement the technical manuals listed in the "Related Documentation" section.
Note
Release notes for MGX 8950, Release 4.0.00, are combined with these release notes.
Type of Release
Release 4.0.00 is a software and hardware release for all MGX switches:
•
•
•
•
Locating Software Updates
This is the location for the MGX 8850 and MGX 8830 4.0.00 software:
•
Note
New Features and Enhancements in Release 4.0.00
Note
Refer to the "Acronyms" section for definitions of acronyms used in these release notes.Release 4.0.00 contains the following new features:
•
•
•
•
•
•
•
•
•
•
•
•
•
Table 1 lists which switch supports which new feature.
Table 1 MGX Release 4.0.00 Feature Support by Switch
Closed User Groups (CUG)
NO
YES
YES
YES
YES
YES
Preferred routes for PNNI Multipeer Group Networks
YES
YES
YES
YES
YES
YES
Point to Multipoint SVC/SPVC support (P2MP)
NO
YES
YES
YES
YES
NO
Increased number of Signaling Interfaces
NO
YES
YES
YES
N/A
N/A
Virtual trunks support in PXM1E
NO
NO
NO
NO
YES
YES
Virtual UNI support in PXM1E
N/A
N/A
N/A
NO
YES
YES
PXM1E as Upstream to Feeder Nodes
N/A
N/A
N/A
NO
YES
YES
AXSM-E Upstream to Feeder Nodes
YES
YES
YES
NO
NO
NO
Narrow Band on PXM451
NO
YES
YES
NO
NO
NO
Additional Narrow Band on PXM1E
N/A
N/A
N/A
NO
YES
YES
AXSM-32-T1E1-E UNI with IMA
NO
NO
NO
NO
N/A
N/A
PXM1E-16-T1E1 UNI with IMA
N/A
N/A
N/A
NO
YES
YES
PXM1E-8-155
N/A
N/A
N/A
N/A
YES
YES
PXM45/C
NO
NO
YES
YES
NO
NO
AXSM-1-9953-XG
NO
NO
NO
YES
NO
NO
AXSM-4-2488-XG
NO
NO
NO
YES
NO
NO
Closed User Groups
The Closed User Groups (CUG) supplementary service enables network users to form groups, to and from which access is restricted. A network user may be associated with one CUG, multiple CUGs, or no CUG. Members of a specific CUG can communicate typically among themselves, but in general not with network users outside of the CUG. Specific network users can have additional restrictions preventing them from originating calls to, or receiving calls from, network users of the same CUG (Outgoing Calls Blocked or Incoming Calls Blocked). In addition, a network user can be further restricted in originating calls to, or receiving calls from, network users outside of any CUG membership defined for the network user (Outgoing Access or Incoming Access.).
The feature is based on the ITU-T Q.2955.1 recommendation.
Platforms
Closed User Groups is supported on:
•
•
•
•
References
ITU-T Q.2955.1
Preferred Routes for PNNI Multipeer Group Networks
Preferred routing of connections provides the network operator a means of bypassing the PNNI route selection, and configuring a specific path through the network which a connection will follow. Preferred routes can be configured as either Preferred or Directed routes. A Preferred route is one which will follow the configured path if available, but will revert to a PNNI-selected route if the preferred route is not available. A Directed route is one which will follow only the configured path; if the configured path is not available, the connection will remain unrouted.
Preferred routes can be specified for SPVCs from source switch to the destination switch end-to-end using CLI or SNMP. The end-to-end preferred route for connections can span across multiple peer groups. The implementation is based on PNNI 1.1 specification.
Platforms
This feature is supported on:
•
•
•
•
References
PNNI 1.1
Point-to-Multipoint SVC/SPVC Support
The SVC/SPVC point-to-multipoint (P2MP) feature offers the ability for one root SVC/SPVC connection to establish a simple tree topology to one or more leaf connections. The data traffic is uni-directional from root multicast to all leaves, i.e., what is sent from the root data channel is received by all leaves. From the root, leaves can be added to the connection using SETUP/ADD_PARTY signaling messages. Point-to-multipoint is a mandatory feature described in UNI 3.0, UNI3.1 and UNI4.0 specs. The implementation is compliant with in Q2971.
Platforms
This feature is supported on:
•
•
•
Note
References
UNI 3.0, UNI3.1, UNI4.0, Q2971
Increased Number of Signaling Interfaces
Support for up to 192 PNNI routing/signaling interfaces on MGX 8850 (PXM45/B and PXM45/C). Prior to this release, the platform supports only 99 signaling interfaces. The features enables increased signaling interfaces for interconnecting with other switches or DSLAMs.
Platforms
This feature is supported on:
•
•
PXM1E-Related Hardware (the PXM1E-8-155 card)
•
•
•
•
Redundancy Support
The PXM1E PNNI Controller offers redundancy, offer hitless operation, and Y-Redundancy (1:1) will be supported in PXM1E for the 155 interface.
Service Modules will have 1:N redundancy and 1:1 redundancy as supported by the individual service modules
Automatic Protection Switching Support
Automatic Protection Switching (APS) 1:1 and1+1 for both the Bellcore GR-253 and ITU-T G.783 Annex-A and Annex-B standards will be supported for the OC3 and STM1 interfaces. The MGX-8850-APS-CON plane is required for APS functionality.
Modular Transceiver Support in the New 8-port OC3/STM1 Back Card
The PXM1E will support a single universal back card capable of supporting single-mode and multi-mode fiber connectors for the different reaches in OC3 and STM1.
External field-replaceable transceivers for SMF-IR, SMF-LR and MMF, purchased by the customer, will be supported.
UNI connection support in PXM1E-16-T1E1
In a previous software release (3.0.10), the PXM1E-16-T1E1 card provided support for IMA trunking. In the MGX 4.0.00 release, the same card will support both native ATM UNI and IMA UNI endpoints. Sixteen T1/E1 ports can be mixed and matched for either native UNI or NNI ports and IMA UNI or NNI ports.
ATM Routing in PXM1E
The PXM1E-based switches support the ATM Forum standard PNNI routing/signaling based on the same baseline used for MGX 8850 (PXM45) and BPX/SES systems. It can be a peer to the PXM45-based switches in the single peer group and participate in multipeer groups.
Connection Management
Supports different types of connections—SVC, SVP, S-PVC, and S-PVP. UNI 3.X/4.0 signaling and ILMI are used to setup SVCs and SVPs.
PXM1E will support 13,500 local switching connections and 27,000 routed connections.
Cell Bus Service Module Support
A cell bus service module is an MGX service module that uses the MGX cell bus to transport customer traffic between that service module and other services modules or PXM uplinks. Traditionally, the CBSMs were called narrow band service modules (NBSMs).
For a summary of service modules supported in MGX 8830 and MGX 8850 (PXM1E), please refer to Table 2
Virtual Trunks Support in PXM1E
Virtual trunks will be supported in the PXM1E ports. A maximum of 31 (physical and virtual) trunks can be supported in a PXM1E card. The feature will be supported in 4-port OC3/STM1, 8-port T3/E3, 8-port OC3/STM1, 16- port T1/E1 and the combo PXM1E cards. SVC, SPVC and SPVP connections can be routed over the virtual trunks.Virtual trunks can originate and terminate between PXM1E, AXSM/A, AXSM/B, AXSM-XG and AXSM-E cards.
Virtual UNI Support in PXM1E
A new port type called Virtual UNI (VUNI) and Enhanced Virtual UNI(EVUNI) is defined in addition to the already defined port types UNI, NNI, VNNI (Virtual Trunk). This feature benefits both the MPLS and PNNI control plane.
Feeder Trunk support in PXM1E
PXM1E ports can accept feeder trunks in any port. IGX 8400, MGX 8230, MGX 8250 and MGX 8850 (PXM1) can be added as feeders to MGX 8830 and MGX 8850 (PXM1E).
PXM1E Diagnostics
Both HMM and online diagnostics report alarms in the Hardware Alarm category under the card alarms.
•
•
POST test results printed to the console immediately after execution may display failures. These may be due to tests being attempted for devices not present on the particular PXM1E-board (such as the second ATM policing device on the PXM1E-4-155). The tests are based purely on device offsets and can display spurious results. To confirm/rule-out real and relevant tests, please use the following examples:
Example 1 PXM1E-4-155: ATM policing device 2 and framers 2 and 4 do not exist: Following shows all relevant test cases passed. Although framers 2 and 4 show passed below, those two cases must be ignored.
Power On Self Test Results
Test Name Result Description
BRAM Checksum PASS
QE Ram PASS
CBC Ram PASS
Ethernet Reg PASS
PCI-IDE Reg PASS
Clock Mux PASS
Framer 1 Access PASS
Framer 2 Access PASS
Framer 3 Access PASS
Framer 4 Access PASS
ATLAS 1 Ram PASS
ATLAS 2 Ram FAIL Ingress SRAM: Pattern Not Matched
Hard Disk Access PASS
Example 2 PXM1E-8-T3E3: ATM policing device 2 and framers 3 and 4 do not exist: Following shows all relevant test cases passed.
Power On Self Test Results
Test Name Result Description
BRAM Checksum PASS
QE Ram PASS
CBC Ram PASS
Ethernet Reg PASS
PCI-IDE Reg PASS
Clock Mux PASS
Framer 1 Access PASS
Framer 2 Access PASS
Framer 3 Access FAIL Framer 3 Access 1 Fail
Framer 4 Access FAIL Framer 4 Access 1 Fail
ATLAS 1 Ram PASS
ATLAS 2 Ram FAIL Ingress SRAM: Pattern Not Matched
Hard Disk Access PASS
Example 3 PXM1E-T3E3-155: Following shows all relevant test cases passed.
Power On Self Test Results
Test Name Result Description
BRAM Checksum PASS
QE Ram PASS
CBC Ram PASS
Ethernet Reg PASS
PCI-IDE Reg PASS
Clock Mux PASS
Framer 1 Access PASS
Framer 2 Access PASS
Framer 3 Access PASS
Framer 4 Access PASS
ATLAS 1 Ram PASS
ATLAS 2 Ram PASS
Hard Disk Access PASS
Example 4 PXM1E-8-155: Following shows all relevant test cases passed. For the 8OC3, the ethernet controller test is not done, since the controller is part of the system controller which is not tested in this release.
Power On Self Test Results
Test Name Result Description
BRAM Checksum PASS
QE Ram PASS
CBC Ram PASS
Ethernet Reg NOT_DONE Ethernet Controller Test Not Required.
PCI-IDE Reg PASS
Clock Mux PASS
Framer 1 Access PASS
Framer 2 Access PASS
Framer 3 Access PASS
Framer 4 Access PASS
ATLAS 1 Ram PASS
ATLAS 2 Ram PASS
Hard Disk Access PASS
Example 5 PXM1E-16-T1E1: ATM policing device 2 and framers 1,2,3 and 4 do not exist: Following shows all relevant test cases passed.
Power On Self Test Results
Test Name Result Description
BRAM Checksum PASS
QE Ram PASS
CBC Ram PASS
Ethernet Reg PASS
PCI-IDE Reg PASS
Clock Mux PASS
Framer 1 Access FAIL Framer 1 Access 1 Fail
Framer 2 Access FAIL Framer 2 Access 1 Fail
Framer 3 Access FAIL Framer 3 Access 1 Fail
Framer 4 Access FAIL Framer 4 Access 1 Fail
ATLAS 1 Ram PASS
ATLAS 2 Ram FAIL Ingress SRAM: Pattern Not Matched
Hard Disk Access PASS
AXSM-E as Upstream to Feeder Nodes
Previously supported only with AXSM and AXSM/B cards, the feeder upstream capability will now be supported using the AXSM-E card as well. This feature enables PXM1 and IGX 8400 feeder nodes to be directly connected to the AXSM-E cards on the PXM45 nodes.
Platform
•
Cell Bus Service Modules on PXM45
This feature allows key Cell Bus Service Modules to be supported on the MGX 8850 (PXM45). Where necessary, these cards can be used in conjunction with the SRME or SRM-3T3/C Service Resource Module for distribution and redundancy purposes. Please see Table 2 for details.
Platform
•
Note
Table 2 Cell Bus Service Modules (CBSMs) Supported in Release 4.0.00
Note
Note
AXSM-32-T1E1-E UNI with IMA
This feature allows the AXSM-32-T1E1-E to support the IMA capability on a UNI, VUNI, and EVUNI interface. This is in addition to the IMA trunking feature already supported in a previous release.
Platforms
•
PXM45/C
The PXM45/C is a combination ATM switching fabric/processor card. The switching fabric provides 45 Gbps of non-blocking switching capacity, while the processor provides the control plane that delivers ATM networking software, diagnostics, and performance monitoring.
Platforms
•
•
AXSM-1-9953-XG
The AXSM-1-9953-XG ATM Switch Service Module is a high-density, double-height Service Module for use in the Cisco MGX 8950 Next Generation Multiservice Switch in combination with the high-capacity PXM45 processor switching module and the XM-60 switching module, to deliver OC-192c/STM-64 trunk connectivity.
Up to 12 AXSM-XG service modules can be accommodated in the Cisco MGX 8950.
Platforms
•
AXSM-4-2488-XG
The AXSM-4-2488-XG ATM Switch Service Module is a Quad OC-48/STM-16, double-height service module for use in the Cisco MGX 8950 Next Generation Multiservice Switch. Used in combination with the high-capacity PXM45 processor and the XM-60 switching module it delivers high density connectivity of 4 interfaces of OC-48/STM-16, either in a clear-channel format or as channelized to OC-12/STM-4, OC-3/STM-1, and DS-3.
Up to 12 AXSM-4-2488-XG service modules can reside in the Cisco MGX 8950, to provide up to 48 OC-48/STM-16 interfaces to support service providers that require both high bandwidth and highest network availability. When used in the channelized mode, each service module can carry alternatively up to 64 DS-3 channels, 64 OC-3/STM-1 channels, 16 OC-12/STM-4 channels, or any combination of these 3 types adding up to 64 channels.
Platforms
•
Frame Discard Feature
New developments have occurred in the CLI for the Frame Discard feature in connection provisioning. Starting with releases 3.0.23 and 4.0.10, two types of frame discard became available. For a detailed explanation, see the addcon or cnfcon description in either the Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 Command Reference (Release 3 or 4) or the Cisco ATM Services (AXSM) Software Configuration Guide and Command Reference for MGX Switches (Release 3 or 4). Also see the Note in the Installation and Upgrade section of these release notes.
Enhancements
The product enhancement requests (PERs) in Table 3 were introduced in Release 4.0.00.
Service Class Template (SCT) File Information
This section contains SCT file information for Release 4.0.00.
PXM1E
The Service Class Template (SCT) bundle in Release 4.0.00 includes updates:
•
•
The default SCTs provided with Release 4.0.00 are as follows:
•
•
PXM1E_SCT.PORT.5.V1:Check sum is = 0x18a4fdad= 413466029
PXM1E_SCT.PORT.6.V1:Check sum is = 0x2cb30eb7= 749932215
PXM1E does not support CARD SCT. See CSCdx55759 for details.
ABR VSVD parameters are not supported due to hardware limitation.
The above PXM1E SCT files apply to MGX 8850 (PXM1E) and MGX 8830.
The Service Class Template (SCT) bundle in Release 4.0.00 includes updates:
•
•
•
AXSM and AXSM/B
•
•
•
•
The check sum for the SCT files are as follows
•
•
•
•
•
•
•
•
A user can do dspsctchksum <filename> to confirm that the checksum of the Cisco-released SCT file and the file on the node match.
AXSM-E
These are the new AXSM-E SCT files:
•
•
•
•
•
•
•
The following are checksums for the new AXSM-E SCT file:
•
•
•
•
•
•
•
•
AXSM-4-2488-XG
These are the new AXSM-4-2488-XG SCT Files:
•
•
•
•
•
The checksum is:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
FRSM-12-T3E3
The SCT file for FRSM-12-T3E3 has the following changes:
•
•
•
•
•
•
The checksum is:
•
•
System Requirements
This section describes software compatible with this release, and lists the hardware supported in this release.
Software/Firmware Interoperability Matrix
Table 4 lists Cisco WAN or IOS products that are interoperable with Release 4.0.00.
MGX and RPM Software Version Compatibility Matrix
Table 5 lists the software that is compatible for use in a switch running Release 4.0.00 software. Note that the AXSM/B cards use the same software as AXSM cards.
Note
http://www.cisco.com/cgi-bin/Software/Iosplanner/Planner-tool/printsa.pl?geget_crypto=&data_from=&hardware_name=&software_name=&release_name=12.2.15T&majorRel=12.2&state=:RL&type=Early%20Deployment&file=12.2.15T.c.html.
Guest
