Technical Assistance Center ............................ .................................. ................................. ...117
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
2
OL-2914-01 Rev D0, July 3, 2003
About Release 3.0.10
These release notes describe the system requirements, new features, and limitations that apply to
Release 3.0.10 of the MGX 8850 and the MGX 8830 multiservice switch. These notes also contain Cisco
support information.
Release 3.0.00 introduced the MGX 8850 (PXM45 ) to both PNNI scaling via an enhanced connection
count (up to 250K connections) and IP/MPLS scaling with the MGX-RPM-XF-512. Release 3.0.10
strengthens the low- and mid-range MGX routing nodes (PXM1E and PXM45) through an increase in
the available T1/E1 ATM port density with a 16-port card for the PXM1E and a 32-port card for the
PXM45, both with IMA capability.
These release notes accompany the technical manuals listed in the “Related Documentation” section on
page 108 .
For information about MGX 8950 Release 3.0.10, see the Release Notes for Cisco MGX 8950 Software Release 3.0.10.
Type of Release
About Release 3.0.10
Release 3.0.10 is a hardware and software release for the MGX 8830 PNNI routing switch.
Release 3.0.10 is a hardware and software release for the MGX 8850 (PXM1E) switch.
Release 3.0.10 is a hardware and software release for the MGX 8850 (PXM45) switch.
Locating Software Updates
Software updates are located at Cisco Connection Online (CCO) at the following location:
Thes e c h a n g e s h av e been m a d e t o t h i s d o c u m e n t s i n c e the Rev. B0, October 24, 2002 revision.
• Fixed typographical errors.
• Removed non-supported SRM-3T3/C card from hardware tables and from Limitations section.
• Added the caution about replacing T1 or T3 cards with E1 or E3 cards (or vice versa) to use the
clrsmcnf command.
• Added syntax for enableaxsmbaps command to clarify usage.
• Added limitation about when configuring virtual interfaces on AXSM cards, that the physical
interface must be of the same ATM header type.
• Added missing SMB-4-155 back card for the AXSM-8-155-E front card.
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
OL-2914-01 Rev D0, July 3, 2003
3
New Features and Enhancements in Release 3.0.10
New Features and Enhancements in Release 3.0.10
Release 3.0.10 contains these new features:
• AXSM-E Double Density
• PXM1E-16-T1E1 with PNNI-IMA Trunking
• AXSM-32-T1E1-E with PNNI-IMA Trunking
• PXM1E Online Diagnostics
• FRSM12 Online Diagnostics
• MGX-SRME
• MGX-VISM-PR-8T1/8E1
• Alarm Filtering
AXSM-E Double Density
This feature doubles the number of ports pr eviously av ailable with each AXSM-E Service Module. Each
AXSM-E Service Module supports up to two back cards. Prev ious to Release 3.0.10, only one was
supported. The actual bandwidth supported by each card remains constant at 622 Mbps, but the
additional ports allow better scaling of service provider networks using ABR with VS/VD support and
per-connection traffic shaping.
This feature is supported on the MGX 8850 (PXM45) switch.
PXM1E-16-T1E1 with PNNI-IMA Trunking
PXM1E-16-T1E1 is a new PXM1E front card with support for two back cards RBBN-16-T1E1 and
MCC-16-E1. PXM1E will provide up to 16 T1 or E1 ports with IMA Versions 1.0 and 1.1 support for
PNNI trunking.
NoteUNI support for the interfaces will be provided in a future software release.
T1 or E1 links (but not a mix) can be grouped to form IMA groups of links 1 to 16 in a single group.
Both RBBN-16-T1E1 and the MCC-16-E1 back cards support 1:1 redundancy on PXM1E-16-T1E1 . The
maximum number of connections supported in a shelf with PXM1E-16-T1E1 as the processor card is
13,500 connections.
The PXM1E-16-T1E1 card is supported in the MGX 8830 and the MGX 8850 (PXM1E) switches.
AXSM-32-T1E1-E with PNNI-IMA Trunking
The AXSM-32-T1E1-E card is a double-height service module used on the PXM-45 based MGX 8850
platform. In this release, the AXSM-32-T1E1-E supports ATM cell transfer over a total of 32 T1/E1
interfaces. Up to two back cards of the same typ e (RBBN-16-T1E1 or MCC-16-E1) are supported with
16 T1/E1 interfaces per backcard. The AXSM-32-T1E1-E card supports a maximum of 32,096
connections. It supports enhanced traffic management capabilities with per-VC/VP traffic shaping and
ABR with VS/VD along with multilevel statistics.
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
4
OL-2914-01 Rev D0, July 3, 2003
In this release, IMA Versions 1.0 and 1.1 are supported (PNNI trunking only).
NoteUNI IMA will be available in a subsequent software release.
PXM-UI-S3/B Back Card
The PXM-UI-S3/B back card provides four serial ports and two Ethernet ports and Stratum-3 clock
functionality for the PXM1E front cards.
MCC-16-E1
The MCC-16-E1 back card has sixteen E1 miniature coaxial c onnector s.
RBBN-16-T1E1
The RBBN-16-T1E1 back card has a "ribbon" type connector that su pports sixtee n T1 or E1 ports.
New Features and Enhancements in Release 3.0.10
PXM1E Online Diagnostics
The feature provides the capability to configure a hardware-oriented test to check the health of the PXM
cards—both active and standby. The test can be run in the active, standby, or both modes at the same
time. The test is nonintrusive and r uns with minimum o ve rhead. The capability is provided as an option.
The failure of online diagnostics in the acti ve PXM1E card results in a switchover to the standby PXM1E
card. The failure of the online diagnostics in the standby PXM1E card resul ts in decl aring the st andby
PXM1E card as failed. The feature is available for all the different PXM1E cards:
• 4OC3/STM1
• 8 T3/E3
• 16 T1/E1
• T3E3/155
Table 1 describes the PXM1E online diagnostics feature support levels for devices within the PXM1E
cards.
Table 1PXM1E Devices and Online Diagnostic Feature Support
DeviceSupported by Online Diagnostics?
Atlas 0Yes
Atlas 1No
QE 0No
QE 1Yes
CBC 0No
CBC 1No
DiskNo
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
OL-2914-01 Rev D0, July 3, 2003
5
New Features and Enhancements in Release 3.0.10
Table 1PXM1E Devices and Online Diagnostic Feature Support (continued)
This feature provides the capability to configure a hardware-oriented test to check the he alth of the
FRSM-12-T3E3 card—both active and standby. The test can be run in active, standby, or both modes at
the same time. The test is nonintrusive and runs with minimum overhead. The capability is provided as
an option. The failure of online diagnostics in the act ive FRSM-12-T3E3 card results in a switchover to
the standby FRSM-12-T3E3 card. The failure of the online diagnostics in the standby FRSM-12-T3E3
card results in declaring the standby FRSM-12-T3E3 card as failed. The failure of the standalone
FRSM-12-T3E3 card results in the card being placed in the failed state but the card will not be reset.
MGX-SRME
This feature provides channelization and redundancy support for MGX-VISM-PR in a MGX 8850
(PXM45) chassis. The MGX-SRME card can take one OC-3 or one STM-1 as ingress, channelize the
signal to a T1 or an E1 and distribute to an MGX-VISM-PR 8T1 or an MGX-VISM-PR 8E1 card via a
distribution bus inside the MGX8850 (PXM45) chassis. For redundancy, a MGX-VISM-PR card can be
configured as a standby card, so if one active MGX-VISM-PR card fails, MGX-SRME reroutes the
traffic to the standby card. MGX-SRME also provi des automatic protection switching (APS) capabiliti es
on the ingress line. If one line fails, the other line ta kes over. APS protocols include GR-253, ITU-T
Annex A and Annex B.
MGX-VISM-PR-8T1/8E1
This feature provides support for the MGX-VISM-PR-8T1/8E1 card on the MGX 8830 platform, and
provides the capability for voice applications in this switch.
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
6
OL-2914-01 Rev D0, July 3, 2003
New Features and Enhancements in Release 3.0.10
Alarm Filtering
The Alarm Filtering feature works in conjunction with Cisco WAN Manager (CWM) 11.0.10 to display
a filtered integrated shelf alarm. The filtered integrated shelf alarm ignores all lines, ports, connections
and feeder alarms reported by a given node. When the CWM GUI displays a group of nodes in group
mode, the group's integrated alarm is the aggregation of all filtered alarms reported by the nodes in the
group, and all trunk/line alarms reported by these nodes.
Enhancements
The product enhancement requests (PERs) in Table 2 were introduced in Release 3.0.10.
Table 2List of Product Enhancement Requests in MGX Release 3.0.10
Enhancement
NumberPurpose
2291The persistent topology feature provides CWM with a persistent view of the network, regardless of the
current operational status of the nodes in the network. Topology information (IP address, node ID , feeder
port ID, etc.) is stored in the persistent topology da tabase for each node in the network. If a node is
disconnected from the network due to some error scenario (the link went down, the node rebooted, etc.),
CWM would still be able to retrieve information about this node from the persistent topology database.
Starting with this rele ase, th e per si st ent t opo lo gy da ta ba se co nta in s inf o rm atio n on t he rou tin g and f eede r
nodes in the network.
5055CLI commands provided to display VC/CoS thresholds in the AXSM-E QE.
5068dspport on AXSM-E card and dsppnport on PXM card should display the same number of SVCs.
5267Better clock resolution provided for tstdelay on AXSM-E cards.
Service Class Template File Information
This section contains service class template (SCT) file information for Release 3.0.10.
AXSM-E
The following are the new AXSM-E SCT files introduced for this release:
• SCT 52—Policing enabled, for ATM T1/E1 application, maximum VC/CoSB cell threshol d settin g
is the same between SCT 52 and 53.
• SCT 53—Policing disabled, for ATM T1/E1 application, maximum VC/CoSB cell threshold setting
is the same between SCT 52 and 53.
• SCT 54—Policing enabled, IMA group with 1 to 4 links, maximum VC/CoSB cell threshold setting
is the same between SCT 54 and 55.
• SCT 55—Policing disabled, IMA group with 1 to 4 li nks, maximum VC/CoSB cell threshold setti ng
is the same between SCT 54 and 55.
• SCT6—Policing disabled, used for trunks.
The following are checksums for the new AXSM-E SCT file:
• AXSME_SCT.PORT.52.V1—Check sum = 0x199550ec = 429215980
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
OL-2914-01 Rev D0, July 3, 2003
7
System Requirements
FRSM12
PXM1E
• AXSME_SCT.PORT.53.V1—Check sum = 0xf6d53485 = 4141167749
• AXSME_SCT.CARD.52.V1—Check sum = 0xde496f2 = 233084658
• AXSME_SCT.PORT.54.V1—Check sum = 0x2a96b5b9 = 714519993
• AXSME_SCT.PORT.55.V1—Check sum = 0x5403c5ac = 1409533356
• AXSME_SCT.PORT.6.V1—Check sum = 0xb69ce935 = 3063736629
The following is the new FRSM12 SCT file introduced for th is rele ase:
• SCT 7—Enable WFQ for all ATM service types as the default.
The following are checksums for the new FRSM12 SCT file:
• FRSM12_SCT.CARD.7.V1—Check sum = 0x587dd247 = 1484640839
• FRSM12_SCT.PORT.7.V1—Check sum = 0x58d9a42a = 1490658346
The following are the new PXM1E SCT files introduced for this release:
• SCT 52—Policing enabled.
• SCT 53—Policing disabled.
• SCT 54—Policing enabled.
• SCT 55—Policing disabled.
• SCT6—Policing disabled, used for trunks.
The following are checksums for the new PXM1E SCT files:
• PXM1E_SCT.PORT.52.V1—Check sum = 0x199550ec = 429215980
• PXM1E_SCT.PORT.53.V1—Check sum = 0xf6d53485 = 4141167749
• PXM1E_SCT.PORT.54.V1—Check sum = 0x2a96b5b9 = 714519993
• PXM1E_SCT.PORT.55.V1—Check sum = 0x5403c5ac = 1409533356
• PXM1E_SCT.PORT.6.V1—Check sum = 0xb69ce935 = 3063736629
System Requirements
This section describes software compatible with this release, and lists the hardware supported in this
release.
Software/Firmware Compatibility Matrix
Table 3 lists Cisco WAN or Cisco IOS products that are interoperable with Release 3.0.10.
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
10
1
YP
OL-2914-01 Rev D0, July 3, 2003
NoteThe PXM1E-COMBO card is also known as the PXM1E-T3E3-155 card.
Additional Notes
System Requirements
The SNMP MIB release for 3.0.10 is mgxmibs3010. tar.
Table 5 shows the various types of APS protocols that are supported on the AXSM/A and AXSM/B
cards, and the MGX release that provides the support.
Table 5APS Protocol Support
Card Types
Op Mode (APS Protocol)
Op_A mode (GR253)Release 2.1.x and
Op_B mode (GR253,
ITU-T Annex A/B)
AXSM/AAXSM/B
Release 2.1.x and
higher
—Release 3.0.00 and
higher
higher
Hardware Supported
This section lists:
• MGX 8850 (PXM45) Product IDs, 800 part numbers, and revision levels
• MGX 8850 (PXM1E) Product IDs, 800 part numbers, and revision levels
• MGX 8830 Product IDs, 800 part numbers, and revision levels
Front and back card types, and whether APS connectors are supported for
• MGX 8850 (PXM45)
• MGX 8850 (PXM1E)
• MGX 8830
New Hardware in Release 3.0.10
The following new hardware is supported by the Release 3.0.10 software. Features enabled by the
hardware are described in the “New Features and Enhancements in Release 3.0.10” section on page 4.
• PXM1E-16-T1E1 front card, PXM-UI-S3/B back card, MCC-16-E1 back card, RBBN-16-T1E1
back card
• AXSM-32-T1E1-E front card, MCC-16-E1 back card, RBBN-16-T1E1 back card
APS Connectors
Table 6 lists MGX 8850 (PXM45) APS connectors.
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
OL-2914-01 Rev D0, July 3, 2003
23
System Requirements
Table 16 lists the new commands for Release 3.0.10.
Table 16New Commands for Release 3.0.10
CommandDescription
clrspvcnonpersDeletes one or more non-persistent SPVC endpoints from a port.
cnfsvcoverrideSpecifies three node-level settings that relate to overriding an SVC’s or SVP’s
ownership of a VPI and VCI (in the case of an SVC).
cnftrftoleranceSpecifies a node-lev el setting to permit the addi tion of connections who se traf f ic
parameters may have a slight, unintentional mismatch between the master and
slave endpoints.
cnfuplinkbertSets up a BERT for a line on the PXM1E UNI/NNI back card.
dspsvcoverrideDisplays up to three node-level settings that relate to overriding an SVC’s or
SVP’s ownership of a VPI and VCI (in the case of an SVC).
dsptrftoleranceDisplays a node-level setting to permit the addition of connections whose traf fic
parameters may have a slight, unintentional mismatch between the master and
slave endpoints.
dspuplinkbertDisplays the configuration and current status for BERT on a line on the PXM1E
UNI/NNI back card.
startuplinkbertStarts a BERT on one of the lines on the PXM1E UNI/NNI back card.
stopuplinkbertSto ps the BER T that is running on one of the lines on the PXM1E UNI/N NI back
card.
Table 17 lists the changed commands for Release 3.0.10.
Table 17Modified Commands for Release 3.0.10
CommandDescription
addconAdd a connection on the PXM1E.
cnfpnportccConfigures certain call control parameters for a specific port.
cnfstatsmgrLets you configure multiple statistics managers. Index options 1 through 3 are
currently not used (or ignored) by CWM. Index option 4 (Master statistics
manager) was added in release 3.0.10. Use Inde x option 4 to specify the IP address
of the statistics master for the switch, which defines the IP address of the
workstation authorized to enable or disable statistics on the switch.
dspconDisplays priority routing for a nonpersistent endpoint.
dspconsDisplays priority routing for nonpersistent endpoints.
dsppnportDisplays priority routing.
dsppnportccDisplays certain call control parameters for a specific port.
Enable the FRSM, AUSM, and CESM Card cls and clr Commands
The FRSM, AUSM, and CESM cls and clr card commands that are supported by the PXM1E card, must
be enabled on the PXM1E card before they can operate on a service module card. Complete the following
steps to enable the cls and clr commands on a PXM1E card:
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
24
OL-2914-01 Rev D0, July 3, 2003
Step 1Access the PXM1E card prompt.
Step 2Type smclrscrn enable
The value of smClrscrn is now enabled. You can use the FRSM, AUSM, and CESM cls and clr
commands.
To disable the FRSM, AUSM, and CESM card commands, use the smclrscrn disable command.
Limitations, Restrictions, and Notes
This section includes information about limitations, restrictio ns, and notes pertaining t o Release 3.0.10.
Release 3.0.10 Limitations
AXSM-32-T1E1-E
Limitations, Restrictions, and Notes
• Only 10 SVC calls per second is guaranteed.
• FDL support for loopback code detection is not supported.
• Far-end line performance counters are supported only for the E1 interface. They are not supported
for the T1 interface.
• HMM support is not available for IMA-32 and the Framer devices.
• IMA link alarms, LIF and LODS integration times are not configurable.
• An IMA group configured for Version 1.1 does not f all back to Version 1.0 if the f ar -end IMA group
is configured with Version 1.0.
• Auto-restart (persistent Rx IMA ID) feature is not supported.
• When there is a switchover, it can take up to 3.5 seconds for the IMA groups to recover . Data is lost
until the groups recover.
• Support for UNI and virtual trunking on IMA groups is not available. But UNI and virtual trunking
on non-IMA T1/E1 ATM lines is available.
• Support for UNI IMA is not available.
• IMA group cannot have links from the upper and lower bays together.
• ITC clocking mode on IMA is not supported.
• Transmission delay of more than 500 ms on the T1/E1 IMA links is not supported.
• GTSM (Group Traf fi c State Machine) up and do wn integr ation times should be conf igured to v alues
of 0 (zero) only.
• There is a 5-ms fluctuation on IMA delay tolerance.
• While the IMA group accumulated delay is being removed with clrimadelay, the following apply:
–
Any changes to this IMA group configuration at NE are blocked.
–
Any changes in the FE IMA links in this group can cause the NE IMA group to restart.
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
OL-2914-01 Rev D0, July 3, 2003
25
Limitations, Restrictions, and Notes
• The VC and COSB thresholds are updated as and when the links are added or deleted from the IMA
groups. The thresholds for the connections added when th ere are N links in the group can dif fer from
the connections added when there are (N+1) links in the IMA group.
• Round trip propagation delay of more than 1 second on IMA links is not supported.
• The CLI clrimadelay or the corresponding SNMP set operation is issued to remove accumulated
delay from an IMA group. While delay is being remove d, the following CLIs must not be executed.
They will return error if issued. The corresponding SNMP set operations will also be rejected:
• Any of the following operations can extend the delay removal completion by 9 second s.
–
IMA link deletion at *FE*
–
IMA group restart at *FE*
–
IMA link transition into Unusable state at *FE*
–
IMA link entrance into LIF failure at *NE*
Then the group will be restarted and it may take another 3 secon ds to become operational. The group
will be restarted even if the delay process completes sooner and any of the operations listed above
occurs.
• GTSM (Group Traffic State Machine) UP and DOWN integration times should be configured to a
value of 0 for all IMA groups. Any positi v e v alue, especially the UP time, will delay the operational
state of any port(s), configur ed on t he IMA group , from becoming active. This can cause more than
desired traffic loss during a card switchover.
• BERT is supported only on the T1 interfaces. It is not supported on the E1 interfaces.
• Sub-slot and port identifiers do not correspond to the exact physical attribute for IMA and
channelized interfaces as they used to in the old unchannelized interfaces. Refer to the DDTs issue
CSCdy08500 for more information. The following apply to the AXSM-32-T1E1-E card in Release
3.0.10:
–
If the logical port on the SM is deleted, the corresponding pnport on the controller, that is,
PXM45, should be deleted.
–
The port number in the pnport (shelf.slot:subslot.port:subport) could be a random n umber. The
user should not interpret this number as line or IMA group number.
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
26
OL-2914-01 Rev D0, July 3, 2003
PXM1E-16-T1E1
Limitations, Restrictions, and Notes
• Only 10 SVC calls per second is guaranteed.
• FDL support for loopback code detection is not supported.
• Far-end line performance counters are supported only for the E1 interface. They are not supported
for the T1 interface.
• HMM support is not available for IMA-32 and the Framer devices.
• IMA link alarms, LIF and LODS integration times are not configurable.
• An IMA group configured for Version 1.1 does not f all back to Version 1.0 if the f ar -end IMA group
is configured with Version 1.0.
• Auto-restart (persistent Rx IMA ID) feature is not supported.
• When there is a switchover, it can take up to 3.5 seconds for the IMA groups to recover . Data is lost
until the groups recover.
• Support for UNI IMA, virtual trunking on IMA groups, and T1/E1 ATM lines are not available.
• Support for UNI is not available.
• ITC clocking mode on IMA is not supported.
• Transmission delay of more than 500 ms on the T1/E1 IMA links is not supported.
• GTSM (Group Traffic State Machine) up and do wn integration times should be confi gured to a value
of 0 (zero) only.
• There is a 5-ms fluctuation on IMA delay tolerance.
• While the IMA group accumulated delay is being removed with the clrimadelay command, the
following apply:
–
Any changes to this IMA group configuration at NE are blocked.
–
Any changes in the FE IMA links in this group can cause the NE IMA group to restart.
• The VC and COSB thresholds are updated as and when the links are added/deleted from the IMA
groups. The thresholds for the connections added when there are N links in the group can differ from
connections added when there are (N+1) links in the IMA group.
• Round trip propagation delay of more than 1 second on IMA links is not supported.
• The CLI clrimadelay or the corresponding SNMP set operation is issued to remove accumulated
delay from an IMA group. While delay is being remov ed, the fo llowing CLIs must not be executed.
They will return error if issued. The corresponding SNMP set operations will also be rejected:
–
delimagrp
–
cnfatmimagrp
–
cnfimagrp
–
upimagrp
–
dnimagrp
–
rstrtimagrp
–
addimalnk
–
clrimadelay
–
startimalnktst
–
cnfimalnktst
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
OL-2914-01 Rev D0, July 3, 2003
27
Limitations, Restrictions, and Notes
–
–
• Any of the following operations can extend the delay removal completion by 9 second s.
–
–
–
–
Then the group will be restarted and it may take another 3 secon ds to become operational. The group
will be restarted even if delay process completes sooner and any of the operations listed above
occurs.
• GTSM (Group Traffic State Machine) UP and DOWN integration times should be configured to a
value of 0 for all IMA groups. Any positi v e v alue, especially the UP time, will delay the operational
state of any port(s), configur ed on t he IMA group , from becoming active. This can cause more than
desired traffic loss during a card switchover.
• BERT is supported only on the T1 interfaces. It is not supported on the E1 interfaces.
stopimalnktst
delimalnk
IMA link deletion at *FE*
IMA group restart at *FE*
IMA link transition into Unusable state at *FE*
IMA link entrance into LIF failure at *NE*
PXM1E
• The maximum number of connections on the PXM1E cards (except for the PXM1E-16-T1E1 card)
is 27K, and the maximum number of ports on these cards (except for the PXM1E-16-T1E1 card) is
4K.
• The dspapsbkplane command does not work for the PXM1E-4-155 card.
• An LOS condition on an APS line will not be reported by the dspalms command if both the
following are true:
–
The PXM1E card has SONET lines, and
–
Either the APS line with the LOS condition is the Protection lin e for intracard A PS, or the APS
line with the LOS condition is the adjacent back card line for intercard APS. For example, if
line 1 on slot 7 is the Working line and line 1 on slot 8 is the Protection line, then an LOS on
line 1 in slot 8 will not be reported when dspalms is issued on slot 7, assuming slot 7 has the
Active front card. The dspadjlnalm command will also not report LOS in this situation.
All other conditions (LOF, OOF, etc.) are reported correctly (refer to caveat CSCdy30310).
• For uplink ports on all PXM1E cards, the standby co ntroller card is not able to derive clock signals
from the standby uplink port (daughter card) due to a hardware limitation. No data signals can be
received on the standby card and clock signals cannot be recovered. On switchovers, the uplink
clock sources will be requalified (refe r to caveat CSCdy68971).
• When a back card is inserted or removed, verify that the back card is accessible by reading a re gister
on the back card. If the front card is not able to read the register, the back card will be put into the
mismatch state. If the problem happens on the active card and if the standby card is available, card
will be switched over. O therwise the back card is put into mismatch state. If the problem also
happens on the standby card, the backcard will be put into mismatch state. A message will be put
into dsplog to show that the back card is not considered to be in a healthy state. This message should
be ignored when it is logged when the card is in the Init (I) state. Only messages logged in either the
Active (A) or Standby (S) states are valid.
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
28
OL-2914-01 Rev D0, July 3, 2003
When intercard APS is configured, the active front card takes control of the standby back card. The
standby front card will not be able to determine the local back card health because it does not have
control of its own back card. When intercard APS is configured for the PXM1E-COMBO (also
known as PXM1E-T3E3-155) card, and if all the SONET lines on the standby card displays an
alarm, the shellcon function dspAdjBcHealth(0) should be used to determine the alternate back
card's health. This back card health detection is available only for the P XM1E-COMBO card (refer
to caveat CSCdy39859).
PXM1E Online Diagnostics
• Online diagnostics uses VPI=32 and VCI=31 for a connection setup. No other connection (data or
control) should use this VPI/VCI pair . Using this VPI/VCI pair may result in the failure of the online
diagnostics (if enabled) and the card will subsequently be placed in the failed state.
MGX-SRME
• MGX-SRME APS provisioning will be blocked on all unsupported PXM45 cards and a proper
warning message displayed.
• This feature provides the capability to guard against fiber cut and line failures. It minimizes the
traffic loss by switching to the protection line when it detects a problem on the working line.
• This feature relies on the interrupt line coming from the MGX-SRME card to the PXM45B.
PXM45B boards have an interrupt line to MGX-SRME card. MGX-SRME APS will work only on
PXM45/B having 800-level part number equal or greater than 800-09266-03.
Limitations, Restrictions, and Notes
FRSM-12-T3E3
• On an FRSM-VHS, all connections on a port with LMI enabled will have those connection statuses
initialized to okay. If the connection is actually in LMI abit alarm, then the connection alarm will
be updated to the correct state (LMI abit alarm) via asynchronous updates or the periodic full state
update. On a resetcd on an FRSM-12-T3E3 card, all connections on a port with LMI enabled will
have those connection statuses initi alized to LMI abi t alarm. If the connection is actually okay, then
the connection alarm will be updated to the correct state (okay) via asynchronous updates or the
periodic full state update. In either case, the connection alarm will be updated to the correct, current
state. For the FRSM-VHS card, it starts in the okay state, and for FRSM-12-T3E3 card, it starts in
the LMI abit alarm state (refer to caveat CSCdy28727).
• For the cnfchanstdabr command, because of a hardware limitation, the NRM (number of cells per
forward RM) range is now 4 to 256 (refer to caveat CSCdy05769).
FRSM-12-T3E3 Online Diagnostics
• Online diagnostics can only detect problems; it does not have the capability to isolate problems.
AXSM-E Double Density
• With the AXSM-E double density feature, the total bandwidth supported by each Service Module
without blocking is 622 Mbps.
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
OL-2914-01 Rev D0, July 3, 2003
29
Limitations, Restrictions, and Notes
AXSM Cards
• Do not enable offline diagnostics on AXSM cards in the APS 1+1 Op A mode. A possible loss of
signal will occur when offline diagnostics are run on t he AXSM cards in this conf igurat ion (refer to
caveat CSCdy62950).
• For AXSM OC-3 cards running in the Op B mode, a remote card switchover can occur by doing
setrev on a local node. This problem occurs when more than twelve lines are configured for APS
and the setrev command is issued. The mode of the AXSM card can be found by issuing the dspcd
command. The card switchover on the remote node is happening because of flooding of several
interrupts occurring on all the lines. The cause of the interrupt was the reset of both the cards on
local node (refer to caveat CSCdy09027).
• APS is supported on AXSM-1-2488/B after upgrading the card to Release 3.0.00 and up, and
enabling the card to operate in the Op B mode.
• The dspapsln/dspapslns/dspalms/dspalm commands on a standby AXSM card do not show the
results consistent with an active card. When the cards are operating in the Op B mode (which can
be found by issuing the dspcd command on an AXSM card), the standby card does not perform the
alarm integration and APS is also not enabled on the standby card. All the defects or failures and
statistics are dynamic events which are not sent to the standby card—the standby card is unable to
show the correct faults as shown b y the activ e card. These commands are not block ed on the standby
card as these are useful for debugging purposes (refer to caveat CSCdx63098).
PNNI Limitation
• When there is an APS line between an AXSM card in the Op A mode and an AXSM card in the Op B
mode, the working and protected lines can go into the SD (signal degraded) mode if the cards are
set up for 1:1 intracard APS and SD is set to –7 upward. The problem is seen because of the behavior
of the AXSM card in the Op A mode, and the problem exists only between an AXSM card in the
Op B mode and an AXSM card in the Op A mode; it does not exist if both AXSM cards are in the
Op B mode or in the Op A mode.
• Whenever a switch is made on the AXSM card in the Op A mode, it does the bridging to the other
line on which a switch is goin g to happen. In this duration, the AXSM card in t he Op B mode notices
the change in the BER count and although the BER count is very small, it is sufficient to declare
Signal Degraded (SD) because of having the SD threshold set at –7 (refer to caveat CSCdy31269).
• A standby AXSM card cannot sync up with an active AXSM card after loadrev to Release 3.0.10 if
the redundant AXSM card has NNI ports and 40k connections configured, and both cards the
2.0(15.2) image. In the 2.0.x release, th e LCN could be 0 but in later releases the A TLAS LCN 0 has
been taken out from the pool. So for the cards with 4 ATLASs, the problem will be seen for the
following LCNs while upgrading to Release 3.0.10 (refer to caveat CSCdy36202):
–
0
–
32 * 1024 = 32768
–
64 * 1024 = 65536
–
96 * 1024 = 98304
• There is a limitation in the ATM Forum PNNI specification on how the crankbacks are handled by
the entry border nodes. If the entry border of a peer group canno t route a call to the destination no de
and if the cause of blocking was within the peer group, then the entry cranks back to the ne xt hig her
level (page 246, point b.1.2 in the ATMF PNNI specification). This higher level crankback is
translated to a blocked node of the logical group node and so the source node processing this
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
30
OL-2914-01 Rev D0, July 3, 2003
Loading...
+ 88 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.