Resetting MPSM Cards When PPP Links Go Down

MPSM cards support PPP mode as one of the deployable solutions. In rare cases, all the PPP links go down operationally even though their Admin state and Lower layer status is UP. Usually, the operational state of the PPP links goes down when either the Lower layer or the Admin state is down.

In Release 5.5.10, this feature resolves the issue by resetting the MPSM card. This enhancement enables the system to monitor the events received from the Admin and Lower layer. When all the PPP links are down and their corresponding Lower layer is UP, the system sends a trap, and an event is logged on the PXM. Also, the system triggers a configurable timer. When the timer expires, the card reset is triggered. If any of these PPP links recover to the operational UP state before the timer expires, then the timer is canceled and no reset action is taken.

You can enable this feature by using the command cnfcdresetppp. By default, this feature is enabled. The default value of the timer is three seconds. For more information about the commands, refer to the section New and Changed Commands.

Note You have to disable this feature if you are doing any administration or maintenance activity on a MPSM links or peer node.

Limitations

•This enhancement enables the system to detect only the link failures, not the reasons for failure. The links might also go down due to administrative activity.

•This enhancement does not resolve the outage problems completely. The switchover happens only if all the PPP links go down. The new active card may face the same problem even after the card resets.

Displaying a Banner Message Before the Login Prompt

In Release 5.5.10, enhancements are made to display a banner message before the login prompt when a user logs in to MGX through Telnet, FTP, SSH, or SFTP. You can configure the path of the banner file. The procedure to configure the path differs for SSH, SFTP, Telnet, and FTP.

SSH and SFTP

For SSH and SFTP sessions, you have to update the sshd_config file with the path of the banner file. To update the path:

Step 1 Copy the file sshd_config to your local directory.

Step 2 Append the following line in the config file using any text editor:

banner "path of bannerfile"

Step 3 Copy the updated config file from your local directory to the active PXM.

Step 4 Put the banner file in the specified path.

Step 5 Reset the standalone PXM. Execute the switchcc command twice if you have both the active and standby card on your MGX node.

Telnet and FTP

A new command, cnfloginbanner, is added to specify the path of the banner file. MGX reads the banner file from the specified path and sends it to the Telnet or FTP client. If no banner file exists in the specified path, then the system creates a banner file with empty content. You have to update this file with the login message. For more information about the commands, refer to the section New and Changed Commands.

Limitations

•Login banner needs to be configured in F:/SSHD directory, or any directory which sync between active and standby PXM. Otherwise, login banner will be lost after doing a swithcc or resetting of the active PXM card.

SFTP Support on NBSM Cards

Before Release 5.5.10, when the NMS sent an IOCTL request to the PXM for the configuration file, alarm file, and statistic file from the NBSM, the PXM returned the same value (-1). In Release 5.5.10, when the NMS sends an IOCTL request to the PXM for the configuration file, alarm file, and statistic file, the PXM returns the actual size of the file.

Persistent Support for RPM DPC

Before Release 5.5.10, the data-path check (DPC) running on an RPM-XF card detects the health of the data path and sends the results to the PXM45 through alarms and logs, but does not send any information to diagnostic module on the PXM. Because of this, no traps are sent to the NMS for data-path check failure, and the PXM45 does not take any recovery action when a standby RPM-XF card fails.

In Release 5.5.10, enhancements are made to report the data-path failure on an RPM-XF card. The PXM45 sends traps to the NMS when data-path check failure occurs on an RPM-XF card.

Enabling Data-path Checking on Standby RPMs

When data-path check failure occurs, the PXM45 takes the following actions:

1. Puts the standby RPM-XF card in the failed state and blocks the redundancy switchover

2. Puts the active and standalone cards in the Active-F state

When the failure is cleared, you have to restore the active and standby cards. To restore the cards, run the following commands on the PXM:

resetcd -fslot no for the active card

resetcdslotno for standby card

A new command, cnfstdbyrpmdpc, is added for enabling the data-path check feature on standby RPM-XF cards. The command dspstdbyrpmdpc displays the status of data-path check on standby RPM-XF cards.

Traps and Alarms

The following traps are sent to the NMS:

cwModuleSelfTestFail

When diagnostics on an RPM-XF card fail.

cwModuleFailed

When the PXM45 puts the standby RPM-XF card in the failed state.

No new alarms are added for this feature. The following existing alarms are used:

Configuring the J1 Byte TxTrace Option on AXSM-XG Cards

The default value of the J1 byte (STS path trace string in SONET frames) inserted by AXSM-XG card is 62NULL+CR+LF. That is, the default value consists of 62 NULL ASCII characters, followed by a <CR>, and then a <LF> ASCII character, thus making the total length of the J1 byte 64 characters. For AXSM-A/B/E cards, the default J1 byte inserted in a SONET frame is 64 NULL ASCII characters. Some of the switches in the network require the J1 byte sent from the peer to be 64 NULL ASCII characters. Due to this mismatch in the J1 byte, the interoperability fails on the AXSM-XG cards with these switches. You can resolve this issue by setting the default value of J1 byte to 64 NULL ASCII characters during hardware upgrade from AXSM-A/B/E to AXSM-XG card.

To enable J1 byte TxTrace, set the value to 1. In the following example, the user enables the J1 byte TxTrace:

Note The parameter modified using the command cnftxtraceopt is at card level, and all line and path will follow the same configuration. You cannot configure TxTrace option for individual line or path.

Support for Daylight Saving

Prior to Release 5.5.00, the feature Daylight Saving was not available on the Cisco MGX 88xx switch controller, even though it was available on RPM cards. Due to this, when the daylight saving starts, the time shown in the logs was different for the RPM and MGX 88xx switch controller. Also, the time shown by the switch controller card was different from the wall clock time.

In Release 5.5.00, CLI and SNMP support is provided to configure daylight saving time on MGX 88xx switch controller.

The following commands are introduced to configure and display the daylight saving settings:

SNMP Support

CISCO-SYSTEM-MIB is used to enable the Daylight Saving feature. A trap is sent to indicate the timezone change. The following objects are reused:

•csySummerTimeStatus

•csySummerTimeRecurringStart

•csySummerTimeRecurringEnd

•csyClockDateAndTime

Limitations

•If there is a node in a different time zone with the Daylight Saving feature disabled, correlating the events between those nodes becomes difficult.

•If an application has an event scheduled in the future, and the event time and the scheduled change in time zone are the same, then the application may not get enough time to reschedule that event. In that case, the application will not run. The following applications fall under this category:

–Diag

–optRoute

Disabling SSHV1, FTP, and Telnet on MGX

The MGX switch can be accessed using Telnet, FTP, Secure Shell Protocol Version 1(SSHV1), Secure Shell Protocol Version 2 (SSHV2), and Secure File Transfer Protocol (SFTP). Prior to release 5.5.00, there was no option to disable the feature SSHV1 through CLI and SNMP.

In Release 5.5.00, options are provided to disable the SSHV1 using the CLI and SNMP. Also, FTP and Telnet can be disabled using SNMP. After you disable these protocols, MGX does not allow new sessions. The old session continues to run.

The following commands are updated to include the node-wide parameters for disabling SSHV1:

SNMP Support

One new MIB FTP-SERVER-MIB is introduced for FTP. For Telnet, the scalar ctsTelnetActivation, which is part of MIB CISCO-TELNET-SERVER-CAPABILITY is used. For SSHV1, the scalar cssServiceActivation which is part of the MIB CISCO-SECURE-SHELL-MIB is used.

These MIB elements are part of the configuration upload. MGX sends traps when SSHV1, FTP, and Telnet are enabled or disabled.

Limitations

•If you disable SSHV1, the system disables Telnet access, as well.

•If SSHV1 is enabled, the system enables only SSHV1. You have to enable the Telnet session separately.

Power Supply Enhancement

Prior to Release 5.5.00, the command dspenvalms displays the voltage level as "Below Normal" if the power supply unit (PSU) in slot one is missing even though PSUs are present in other slots. In Release 5.5.00, the command dspenvalms displays the voltage level as "Indeterminate" if one slot is missing and PSUs are present in other slots.

SNMP and STATS Support for Card Uptime

SNMP and STATS support are provided to the command dspcduptime. The command dspcduptime displays the time elapsed since the last reboot of a card. The following cards support SNMP:

•AXSMXG

•MPSM-16-T1E1

•MPSM-T3E3-155

•PXM1E

•PXM45

•RPM-PR

•RPM-XF

•VISM

•VXSM

The following cards support STATS:

•AXSMXG

•MPSM-16-T1E1

•MPSM-T3E3-155

•PXM1E

•PXM45

•VXSM

MIBs Used

CISCO-ENTITY-FRU-CONTROL-MIB is used for supporting this feature.

SNMP Support for resetcd, switchcc, and switchredcd

In Release 5.5.00, Cisco MGX 88xx and MGX 89xx support SNMP for the following commands:

•resetcd

•switchcc

•switchredcd

SNMP support enables you to execute the commands through NMS Manager.

MIBs Used

For the resetcd command, the shelfTable in BASIS-SHELF-MIB.my is used. For switchredcd and switchcc commands, the CISCO-ENTITY-REDUNDANCY-MIB.my and CISCO-ENTITY-REDUNDANCY-TC-MIB.my are used. The tables used inthe CISCO-ENTITY-REDUNDANCY-MIB.my are:

•ceRedunCommandTable

•ceRedunGroupTypesTable

•ceRedunMbrConfigTable

•ceRedunGroupTable

Limitations

•The option clear history in the resetcd commandis not supported. Using the command resetcd -f, you cannot clear the failure history of the card through SNMP.

•Access to ceRedunGroupTable and ceRedunMbrConfigTable is read-only.

Grouping MGX Commands

In Release 5.5.00, a new command is added to group the output of a series of commands. The command showtech displays all the configuration and run-time status information. The command helps a user to avoid the time spent on executing each command one by one. Also, the detailed output of the command helps a user to debug the problems easily. This command is available only on PXM, MPSM-155-PPP, and 16T1E1-PPP.

Command for Grouping the Output of Existing Commands

The command showtech groups the output of a series of commands. On a PXM45, the command displays the output of the following commands:

dspcdalms

dspcderrs

dspcds

dspchassis

dspclkalms

dspclksrcs

dspcons -state fail

dspcontrollers

dspdeverrhist (for all devices XBARCORE,DISK,CBC,HUMVEE,QE1210)

dspdisk

dspenvalms

dsperrhist -<slot #> (for all slots with cards)

dsphwalms

dspipif

dspndalms

dsppnni-node

dspprf <t> < m | n | q | r>

dspprfhist

dspred

dsprevs

dsprmalms

dspswalms

ipcMblkShow

logConsoleShow

ssiMemTaskStatShow

On an MPSM, the command displays the output of the following commands:

Limitations

This command is available only on PXM45 and MPSM-16T1E1PPP. The cards should not be in the failed state.

Grouping MPSM Commands

In Release 5.5.00, new commands are added to group the output of a series of commands. These commands help a user to collect the configuration information by executing a single command. The advantages of this feature are:

•Reduces the time taken to collect the information by correlating multiple outputs

MultiVC Access to PXM Through Nonredundant RPM-XF

In Release 5.5.00, controlled access to the PXM is enabled. For enabling this feature, in-band connectivity through RPM is used. In-band connectivity through RPM requires establishment of SVC between atm0 interface on the PXM and slave endpoints on RPM. RPM routes packets received on the PVC through its Fast Ethernet (FE) interface to the external IP world. You can configure an access control list (ACL) on this FE interface for controlled access to the PXM.

Limitations

•The feature works only if the atm0 interface is configured as default.

•PXM will dump all the IP packets to RPM even if a destination does not exist.

•All the RPMs and the managed PXM should be in the same chassis.

•IP address of the FEs of all RPMs used for controlled access to a PXM should be in the same subnet.

•On resetting the RPM card, the IP cache entries are not deleted for the SVC connections (which are used for IP connectivity) and will be down till RPM boots up. Therefore, the default VC is not used for these IP entries till aging of the entry happens or connection comes up.

Hardware and Resource Monitoring on MPSM-155 Cards

Hardware Monitoring

Hardware Monitoring Module (HMM) monitors the hardware devices on a card and detects the device error conditions. HMM reports the error type to the PXM. Depending on the availability of a redundant card and the severity of the error conditions, PXM determines the corrective action. For instance, if an active card of a redundant pair reports a major error, PXM initiates a card switchover. However, in the absence of a standby card, the active card is put in the failed state. HMM runs on both active and standby cards. HMM functionality is split into two parts:

Resource Monitoring

Resource monitoring (RM) monitors various system resources such as memory, CPU, IPC buffers, hard disk, timers, and so on. In Release 5.5.00, a new resource, Winpath Ingress/Egress buffer, is added for MPSM-PPP mode.

Commands for Hardware and Resource Monitoring

The following commands are introduced in this release for hardware monitoring:

•dspdeverr

•dspdeverrhist

No new commands are added for Resource Monitoring. The output of the existing commands are updated with the Winpath resources. You can use the following commands for resource monitoring:

Whenever both cards fail, a traffic outage occurs until one of the cards becomes active. In Release 5.5.00, the probability of dual AXSM failure is reduced by actively detecting the error on the standby card.

Note This feature does not require any configuration by the user. As soon as the standby AXSM card is upgraded to the new image, the feature comes into effect.

Note Only AXSM B supports this feature.

Refreshing the AXSM Virtual Connection Table

On an AXSM card, the queuing engine QE48 maintains the virtual connection table (VCT). In rare instances, parity errors occur in VCT memory. The hardware monitoring module (HMM) monitors these parity errors and resets the card if the number of parity errors exceeds a predefined threshold value. If the customer does not have a redundant card, the slot either fails or resets when the number of errors crosses the threshold value.

In Release 5.5.00 and later releases, if the parity error is caused by the VCT memory bit flip, then the VCT memory is refreshed so that it corrects the bit flip. The VCT memory refresh avoids resetting of the card and prevents the outage. The VCT refresh cycle time for 128K connections is close to 12 minutes. A new command cnfvctrefresh is added to enable this feature. For more information about the commands introduced, refer to the section New and Changed Commands.

Note Only AXSM B supports this feature.

Limitations

The following limitations apply:

•The outages due to transient hardware errors cannot be resolved using this feature.

•Point-to-multipoint connections are not refreshed.

•This feature may introduce a maximum of 600 ms of delay in connection provisioning and re-routing.

Adding Additional VXSM Cards

You can add additional VXSM cards to a Cisco MGX 8850 chassis as primary cards. Adding of additional cards may result in insufficient disk space. To create the required disk space, previous versions of database on the existing slots must be deleted. A new command delprevdbs is added to enable users to delete the previous versions of the database.

This command can be executed on the following card types: PXM45, PXM1E, AXSM, AXSME, AXSMXG, VXSM, MPSM T3E3, and MPSM 16T1E1.

Note When the delprevdbs command is run on the PXM card, it deletes the unused databases of both shelf manager and disk database. But on a service module card, only the disk databases are deleted.

Support for Back Card Status Message

Prior to Release 5.5.00, the dspcds command displays the status of front card and only one back card available. The status of other cards was not available and the user has to run dspcds command to see the status of all the back cards for a slot. In Release 5.5.00, an option all is added to the dspcds command to display the status of all back cards. This command is supported only on PXM45 and PXM1E.

The following example displays the output of the command:

n210.7.PXM.a > dspcds all

n210 System Rev: 05.05 Nov. 02, 2008 22:22:42 GMT

Chassis Serial No: SAA03320190 Chassis Rev: B0 GMT Offset: 0

Node Alarm: CRITICAL

Card Front/Back Card Redundant Redundancy

Slot Card State Type Slot Type

--- ------------------ -------- ------- -----

01 Failed/Active/Empty AXSM_16OC3_B NA NO REDUNDANCY

02 Empty --- --- ---

03 Empty --- --- ---

04 Empty --- --- ---

05 Empty --- --- ---

06 Failed/Empty/Empty AXSM_16OC3 NA NO REDUNDANCY

07 Active-U/Active/Active PXM45C 08 PRIMARY SLOT

08 Empty Resvd-U/Empty Resvd/Empty --- 07 SECONDARY SLOT

09 Active/Active FRSM_2T3 NA NO REDUNDANCY

10 Active/Active MPSM-T3E3-155-PPP NA NO REDUNDANCY

11 Failed/Active/Empty AXSM-8-622-XG NA NO REDUNDANCY

12 Empty --- --- ---

13 Active/Empty/Active RPM_XF NA NO REDUNDANCY

14 Failed/Empty/Empty AXSME_2OC12 NA NO REDUNDANCY

15 Empty --- --- ---

Type <CR> to continue, Q<CR> to stop:

n210 System Rev: 05.05 Nov. 02, 2008 22:22:42 GMT

Chassis Serial No: SAA03320190 Chassis Rev: B0 GMT Offset: 0

Node Alarm: CRITICAL

Card Front/Back Card Redundant Redundancy

Slot Card State Type Slot Type

--- ------------------ -------- ------- -----

16 Empty --- --- ---

18 Empty --- --- ---

19 Empty --- --- ---

20 Empty --- --- ---

21 Empty --- --- ---

25 Active/Active MPSM-T3E3-155 NA NO REDUNDANCY

26 Active/Active MPSM-T3E3-155 NA NO REDUNDANCY

28 Empty --- --- ---

31 Empty --- --- ---

32 Empty --- --- ---

Support for TACACS Challenge Messages

The TACACS challenge messages inform a user that the password has expired when the user tries to login through SSH. For more information about configuration, see the guide Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.5.10.

Support for AXSM-16-T3E3/B Card in 8830/B Chassis with PXM45C

With this release, support for the AXSM-16-T3E3/B cards in the MGX 8830/B chassis is added.

Features in Release 5.4.00

Release 5.4.00 includes the following new features for the Cisco MGX platforms:

Bidirectional Forwarding Detection Version 1

Bidirectional Forwarding Detection version 1 (BFDv1) improves protocol convergence times by rapidly detecting failures in the path between routers. This is especially important for media that does not provide failure signaling, such as Ethernet, because the OSPF protocol can take a second or more to detect a signaling loss using hello messages. This is too long for some applications and can result in excessive data loss, especially at gigabit rates. BFDv1 quickly detects a media failure so that the OSPF protocol can quickly update routes.

DSCP Marking on RPM-XF Management Interface

This release supports Differentiated Services Code Point (DSCP) or IP Precedence marking for quality of service (QoS) configurations on the RPM-XF management back cards. With this enhancement, the RPM-XF supports Layer 3 QoS on the Fast Ethernet management back card.

Limitations

The following limitations apply to the DSCP marking of management packets on the RPM_XF management back card:

•The RPM-XF does not support DSCP marking for the interface to the MGX switch cell bus.

•The RPM-XF management back card can be used for only management traffic, not data traffic.

Flash MIB Support

Network management systems (NMS) can manage software images stored in boot flash using SNMP when the device supports the CISCO-FLASH-MIB. The RPM-XF supports the CISCO-FLASH-MIB in this and later releases. For MGX 8800/8900 multiservice switches, the NMS can query objects defined in the CISCO-FLASH-MIB through the PXM management interface or the RPM-XF management interface.

SNMPv3

Simple Network Management Protocol Version 3 (SNMPv3) is a standards-based protocol for network management. SNMPv3 provides secure access to devices using a combination of authentication and encryption of packets over the network. This assures that data can be collected securely from SNMP devices and that configuration messages cannot be viewed or altered.

The security features provided in SNMPv3 are:

•Message integrity—Ensuring that a packet has not been tampered with in transit.

•Authentication—Determining that the message is from a valid source.

•Encryption—Scrambling the contents of a packet prevent it from being seen by an unauthorized source.

Trap Squelch Feature

The large number of traps a large system can degrade the performance of a network management system. The trap squelch feature helps limit the number of traps that Cisco MGX switches generate. You can either block all traps of a specific type or limit the rate of specified traps.

Limitations

The following limitations apply:

•The squelch list holds up to 200 trap types.

•The minimum value of the sampling interval is five minutes and the maximum value is 30 minutes.

Support for AXSM-1-2488/B Card in 8830/B Chassis with PXM45C

With this release, support for the AXSM-1-2488/B card in the MGX 8830/B chassis has been added. The AXSM-1-2488/B card is already supported in the MGX 8850 and 8950 chassis.

Features in Release 5.3.20

MPSM Licensing Changes

Release 5.3.20 enforces licenses through sales and support, rather than through software locks. Table 1 lists the MPSM licenses that are required for MPSM services and features. You must purchase licenses for the services and features that you plan to use on each MPSM card.

Release 5.3.20 removes the PXM commands that support software locks and license alarms, and changes the commands that display alarm information. The following commands are removed or changed:

•Removed PXM commands:

–cnflic

–dsplicalms

–dspliccd

–dspliccds

–dsplicnodeid

–dsplics

•Changed PXM commands:

–clrallcnf—No longer has the clrLicense argument

–dspcdalms—No longer displays license alarms

–dspndalms—No longer displays license alarms

The MIB for Release 5.3.20 does not change, but returned license information is no longer valid.

Support for Clear Channel E1 Lines

Release 5.3.20 adds support for E1 clear channel on MPSM-16-T1E1 cards. Clear channel E1 dedicates the entire E1 bandwidth (2048 Kbps) to a single data stream, and does not contain DS0 channels. To implement this feature, a new line type (dsx1E1CLEAR) is added to the cnfln command. You can configure Frame Relay, ATM, or IMA ports on lines configured for E1 clear channel.

The addport command syntax does not change, but you must use the default values for ds0speed (64K), ds0beg (1), and ds0num (32) when adding a clear channel, even though the line is not actually channelized.

For example, the following commands configure line 1.10 for clear channel, add port 11 to the line with type frameRelayService and the default SCT, and then add a slave connection with DLCI 400, channel type frNIW, high-priority service, and CIR of 2048 Kbps. Notice that the default values for addport correctly configure the channelization parameters for clear channel operation.

M8850_SF.27.MPSM16T1E1[FR].a > cnfln 1.10 -lt 9

M8850_SF.27.MPSM16T1E1[FR].a > addport 11 1.10 1 0

M8850_SF.27.MPSM16T1E1[FR].a > addcon 11 400 1 1 2 2048000

For more information about configuring lines, see the Cisco ATM and Frame Relay Services (MPSM-T3E3-155 and MPSM-16T1E1) Configuration Guide and Command Reference, Release 5.2, "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication."

Support for BERT Tests on Clear Channel T3/E3 Lines

Release 5.3.20 adds support for BERT tests on clear channel T3/E3 lines on MPSM-T3E3-155 cards. To support this feature, the following commands now accept a line number (bay.line) for the bertifNum argument:

•addbert

•cnfbert

•delbert

•dspbert

•dspbertcap

•dspbertstats

•insbiterror

•startbert

•stopbert

Additionally, the dsplnalm and dsplnalms commands display the BERT status for a T3/E3 line.

For more information about configuring BERT tests, see Cisco ATM and Frame Relay Services (MPSM-T3E3-155 and MPSM-16T1E1) Configuration Guide and Command Reference, "Card Management on MPSM-T3E3-155 and MPSM-16-T1E1."

Features in Release 5.3.10

Release 5.3.10 includes the following new features and warnings.

Enhanced VXSM Card Support

Release 5.3.10 supports the Processor Switch Module Hard Disk Voice (PXM-HDV) back card, which supports four or more VXSM cards on a Cisco MGX 8850 switch. The size of the D partition on the PXM-HDV back card is 2000 Mb.

Non-Redundant Upgrade Procedure

To migrate from PXM-HD to PXM-HDV back cards in a non-redundant configuration, perform the following steps:

Step 2 Replace the standby card back card with a PXM-HDV back card and wait for the PXM-HDV back card to retrieve configuration information from the active PXM-HD back card.

Step 3 Enter the switchcc command to force a switchover.

Step 4 Replace the remaining back card with a PXM-HDV back card.

Cisco MGX 8800 Series Operating and Storage Environment

This section describes the operating and storage environments for the Cisco MGX 8800 series multiservice switches, and explains how to prevent oxidation and corrosion problems.

Guidance for Operating and Storage Environments

Dew points indicate the amount moisture in the air. The higher the dew point, the higher the moisture content of the air at a given temperature. Dew point temperature is defined as the temperature to which the air would have to cool (at constant pressure and constant water vapor content) in order to reach saturation. A state of saturation exists when the air is holding the maximum amount of water vapor possible at the existing temperature and pressure

When the Relative Humidity is high, the air temp and dew point temperatures are very close. The opposite it true when the Relative Humidity is low. When the dew point temperature and air temperature are equal, the air is saturated with moisture. Locations with high relative humidities have air that is close to being saturated with moisture. When saturated air cools it cannot hold as much moisture and can cause moisture migration and penetration into the system. This moisture can cause corrosion of internal components.

A storage environment that experiences temperature and/or humidity variations over a short period of time can create a condensing environment, and this is considered an uncontrolled environment. An environment that maintains constant temperature and humidity is considered and climate controlled environment. A temperature and humidity controlled operating and storage environment is required at all times to prevent condensation that can subsequently lead to oxidation of plated metal parts. Cisco recommends that both long term and short term storage environments be climate controlled to prevent humidity and temperature variations that create condensation. Buildings in which climate is controlled by air-conditioning in the warmer months and by heat during the colder months usually maintain an acceptable level of humidity for system equipment.

Multilink Point-to-Point Protocol Enhancements for CDMA2000 and EV-DO

CDMA2000 applications can use the Cisco MGX 8850 (PXM45) platform to aggregate traffic from several Base Transceiver Station (BTS) routers and transfer that traffic to an IP network. This application relies on the Multilink Point-to-Point Protocol (MLPPP), which carries traffic between the BTS routers and MPSM service modules. This capability was introduced in earlier releases; this release enhances the MLPPP features on the MPSM and RPM-XF cards.

The MLPPP feature for MPSM-16-T1E1 and MPSM-T3E3-155 cards includes:

•Support for multiple fractional point-to-point links on T1/E1 lines or paths. Each link can be part of a different bundle.

•Support for up to 8 PPP links per bundle.

•Support for up to 64 (MPSM-16-T1E1) or 256 (MPSM-T3E3-155) links per card.

•Support for up to 64 (MPSM-16-T1E1) or 128 (MPSM-T3E3-155) bundles per card.

•MLPPP load balancing for PPP links with unequal bandwidth.

•Support for the OC-3/STM1 back card in CDMA2000 solutions (MPSM-T3E3-155 only).

The RPM-XF supports:

•2000 Context IDs (CIDS). Each CID uniquely identifies a flow, which may be a voice call or a data stream.

MLPPP Configuration

The MLPPP features in Release 5.3 do not change the MLPPP configuration procedures and command syntax; only the valid ranges for links and bundles change (see Table 2). For more information about command updates, see the "Changed MPSM Commands" section.

For information about MLPPP configuration procedures and commands, see the following documents:

MLPPP Upgrade Considerations

Consider the following MLPPP characteristic when upgrading to software Release 5.3:

•Different speed PPP links on the same MLPPP bundle are not allowed in software Release 5.3.

Software Releases 5.1 and 5.2 permit different speed links, so existing bundles may exist with links that have mismatched speeds. After you upgrade to Release 5.3, the dspppplinks command still shows the mismatched links, but the links are down and the system logs the following error:

To restore PPP link operation, delete the mismatched links and add links of equal speeds to the bundle.

•64 Kbps PPP links on lines with alternate mark inversion (AMI) line coding are not allowed in software Release 5.3.

Software Releases 5.1 and 5.2 permit 64 Kbps links on lines with AMI coding, so your system may be configured with these links. After you upgrade to Release 5.3, the dspppplinks command still shows the links, but the links are down and the system logs the following error:

•The default normalized PVC bandwidth (normpvcbw) for a bundle with an E1 link changes from 8600 bps to 9200 bps in software Release 5.3. The default value for a bundle with T1 links is unchanged, and remains 8600 bps. In software Release 5.3, when a bundle is added, the normpvcbw is set to 8600. If the first link added to the bundle is E1, normpvcbw is modified to 9200 bps.

Bundles added before upgrading to software Release 5.3 have a default value of 8600 cps. For bundles with E1 links, modify the normpvcbw value manually using the cnfmpbundleparams command.

Fractional T1/E1 Links for ATM Services

The initial release of the MPSM-16-T1E1 card supported ATM services, but for full T1/E1 lines only. This release expands the ATM service capabilities to support both full and fractional T1/E1 ports.

Fractional T1/E1 Configuration

The configuration procedures for ATM services do not change for fractional T1/E1 ports. When you add a fractional T1E1 port, you specify the range of DS0s to use. The addport command has arguments to specify a range of DS0s, and the dspport command shows DS0 ranges. For more information about command updates, see the "Changed MPSM Commands" section.

For more information about ATM configuration procedures and commands, see the following documents:

Fractional T1/E1 Configuration Limitations

Fractional T1/E1 configurations have the following configuration restrictions:

•Virtual ports on fractional T1/E1 lines are not supported.

•Connecting fractional T1/E1 interfaces with V.35 and X.21 is not supported.

•Partition bandwidths cannot be less than 100 percent of the port rate.

•Cicso Wide Area Network Manager (CWM) inband configuration upload over a low bandwidth link is not supported. Without sufficient bandwidth, CWM may time out and never synchronize.

Fractional T1/E1 configurations have the following functional limitations:

•Each physical interface can be configured with only one NxDS0 port.

•A physical interface can be configured with one NxDS0 port for ATM service, or one NxDS0 port for Frame Relay service, but not both.

•The number of timeslots of an existing NxDS0 port cannot be changed using the cnfport command. Therefore, you cannot dynamically add additional DS0 timeslots to increase bandwidth.

•Network clock distribution protocol (NCDP) cannot distinguish the type of line a NNI trunk is using. This information is transparent to NCDP. Therefore, selecting the NXDS0 port as a NCDP clock source is not blocked by default. Use the cnfncdpport command on the PXM card to block the NxDS0 port from being used as a NCDP clock source. By default for a NNI trunk, this is not blocked.

•Integrated local management interface (ILMI) using about 5 percent of the port bandwidth. This limits the number of connections that can be supported on either side for ILMI autoconfiguration or address registration to succeed.

•For PNNI and service specific connection-oriented protocol (SSCOP), call setup and mutual status exchange for each connection require about 20 cells per second in bandwidth. Connection reroute or connection setup on a NxDS0 trunk with insufficient bandwidth for the number of connections supported can fail if SSCOP times out.

•With PNNI signaling enabled, you must configure the minimum bandwidth that PNNI requires. Otherwise, PNNI trunks may not come up. Use the dsppnctlvc command to display the required PNNI bandwidth.

Disabling Telnet and FTP

By default, the PXM45 permits unsecured access from Telnet and FTP clients, as well as secure access from SSH and SFTP clients. Option 16 of the cnfndparm command, along with option 15, disables unsecured Telnet and FTP access from remote hosts while permitting secure SFTP and SSH sessions.

Option 15

Type yes to disable Telnet access to this switch. Type no to enable Telnet access.

Default: no (Telnet access is enabled)

Option 16

Type yes to disable unsecured Telnet or FTP access to this switch. Changing this option from no to yes automatically changes Option 15 to yes. Changing from yes to no has no affect on Option 15.

Default: no (Unsecured access is enabled)

If you plan to use SFTP and SSH on the PXM45, you should consider disabling FTP and Telnet access to improve security. Telnet and FTP transfer all user ID, password, and session management information between the client and the PXM45 using clear text. Clear (or unencrypted) text can be read by network analysis and snooping tools.

Initializing SFTP

Upgrading PXM software is not sufficient to initialize and enable the SFTP feature. You must initialize the sshd_config file and reset the MGX chassis. Because resetting a chassis can interrupt traffic, you should initialize SFTP before upgrading software so you do not need to reset it later.

Remote IP Management Connection Enhancements

You can manage a Cisco MGX 8850 node directly from an Ethernet or console port on the PXM, or you can configure a remote path to the PXM through a service module or route processor module. The following management paths are supported in earlier releases:

•AXSM or MPSM to PXM

•RPM-XF or RPM-PR to PXM

Earlier releases supported intranode connections only, and you could only have one PVC between an RPM and PXM. Release 5.3.00 enhances the ATM0 feature to internode connections, where an RPM on one MGX switch connects to PXMs on other MGX switches using PNNI. And now you can manage multiple PXMs from a single RPM.

Management Connection Limitations

The IP addresses of hosts accessing the Cisco MGX 8850 node are stored in a RAM cache. Because this cache has a limit of 50 entries, only 50 IP hosts can actively access the node at one time. New IP hosts are blocked until the cache clears (as result of inactivity from some hosts) to make room for new entries.

Multiple RPMs can connect to the same PXM, but each RPM can have only one connection to the PXM. This is because the PXM has a single ATM0 address.

Note If you are connected to the MGX switch using the RPM and accidentally delete the SPVC, the connection drops. To restore RPM access, you must re-add the SPVC using the console port or Ethernet port.

Note The clrallcnf, clrcnf, or clrsmcnf commands clear management connections. To restore RPM access, you must reconfigure the RPM and PXM cards for IP connectivity using the console port or Ethernet port.

Configuring an RPM Management Connection

The following quick start procedure summarizes the RPM configuration procedure. This procedure assumes the RPM already has a switch partition configured for the management connection.

Command

Action

Step 1

switch partition

Create and configure a partition for switch 1, as necessary.

Step 2

interfacesw1.<subif> point-to-point

Configure a point-to-point subinterface on switch 1.

Step 3

ipaddress <address> <mask>

Assign an IP address to the switch subinterface. This IP address must be in the same subnet as the ATM0 port of the PXM card.

Step 4

pvc <vpi>/<vci>

ubr <rate>

Configure a PVC on the switch subinterface.

Note Specify 0 for the VPI.

Note In Release 5.3, the rate is configurable.

Step 5

switchconnectionvcc <vpi> <vci> masterremote

Add a slave endpoint to the switch subinterface.

Step 6

show switch connection vcc <vpi> <vci>

Display the slave connection parameters, which include the NSAP address.

The following quick start procedure summarizes the PXM configuration procedure.

Command

Action

Step 1

dspndparm

Verify that the PXM is configured for ATM0 as a switch management interface.

Step 2

ipifconfigatm0 <address> <mask>

Assign an IP address to the ATM0 port, as necessary. This IP address must be in the same subnet as the switch interface on the RPM card.

Step 3

svcifconfigatm0 remote <nsap> pvc <vpi>.<vci>

Add a master connection endpoint. Use the NSAP address and VPI/VCI of the slave endpoint.

Step 4

dspsvcif

Verify that the connection is up.

Step 5

routeshow

Verify that the RPM IP address is displayed in the route table.

Management Configuration—Example

This example shows how to configure a management connection between an RPM-XF on one switch and the PXM on another switch. In this example, the RPM-XF switch partition and the PXM ATM0 interface are already available.

The following example shows how to configure the RPM-XF switch interface, add a slave connection, and display the NSAP address.

Router(config)#interfaceswitch1.100 point-to-point

Router(config-subif)#ip address 10.10.10.200 255.255.255.0

Router(config-subif)#pvc 0/100

Router(config-if-atm-vc)#ubr 1544

Router(config-if-atm-vc)#switch connection vcc 0 100 master remote

Router(config-if-swconn)#end

Router#show switch connection vcc 0 100

----------------------------------------------------------

Alarm state : No alarm

Local Sub-Interface : 100

Local VPI : 0

Local VCI : 100

Remote NSAP address : default

Local NSAP address : 47.0091810001040000ABCD7777.000001011802.00

Remote VPI : 0

Remote VCI : 0

The following example shows how to configure the ATM0 interface of the PXM card, add a master connection to the RPM-XF, and verify that the connection is state is up. The NSAP address and VPI/VCI entered are the values previously displayed at the RPM-XF.

Platform Enhancements

This release adds the following MGX platform enhancements.

•Database server/client enhancement—The server automatically copies database tables to the new directory for a release.

•Software FPGA upgrade on PXM45/C—Use this feature to upgrade hardware (Field Programmable Gate Array) FPGA images without introducing new hardware versions. This simplifies the process of adding or changing features and can reduce hardware costs for both Cisco and customers.

•PXM to MPSM QoS enhancement—Currently, traffic sent to the MPSM-T3E3-155 and MPSM-16-T1/E1 cards is managed by the class of service only. For example, the CBR traffic class is always given priority over the VBR.RT traffic class, even if VBR.RT connections are committed and data received is within the sustainable cell rate (SCR) limit.

Through this QoS enhancement, the PXM QE1210 is programmed using information from the MPSM so it can manage traffic dynamically based on the committed rate of the connections and interface policy.

Cisco MGX 8830/B Enhancements

The Cisco MGX 8830/B is a 7-double-height horizontal slot chassis, where slots 1 and 2 are reserved for the PXM. The Cisco MGX 8830/B (PXM45/C) now supports the RPM-PR and RPM-XF cards.

RPM-PR Ethernet Back Card

The MGX-RJ45-5-ETH is a single-height back card for the RPM-PR that provides five RJ-45 connectors for Gigabit Ethernet, Fast Ethernet, or Ethernet lines. Figure 1 shows the MGX-RJ45-5-ETH faceplate.

Figure 1 MGX-RJ45-5-ETH Back Card

1

ENABLE LED

•Green—The back card is active.

•Off—The back card is not active.

3

Port 0 status LED

•Green

–Data present (flashing).

–The link is up.

2

Port 0 speed LED

•Orange—1000 Mbps.

•Green—100 Mbps.

•Off—10 Mbps

Table 3 lists the maximum cable length for each of the supported speeds on the MGX-RJ45-5-ETH card.

MGX-VXSM-T3 Card

Release 5.2.00 introduced a third VXSM card for the support of T3 lines. The card consists of a front card with six T3 ports and a half height back card with three T3 ports. The front card can be configured with either one back card or two back cards.

AXSM-8-622-XG Card

The AXSM-8-622-XG is an 8-port OC-12/STM-4 card that supports clear-channel OC-12c/STM-4 or OC-12/STM-4 channelized down to OC-3c/STM-1 and DS3. This card complements the family of AXSM-XG cards, which includes the AXSM-16-155-XG, AXSM-4-2488-XG, and AXSM-1-9953-XG.

•BPX product support—The AXSM-8-622-XG supports direct connection to BPX nodes with all ENNI functions available on AXSM and AXSM/B.

The AXSM-8-622-XG card has the following restrictions:

•All lines on the same bay must have the same SONET/SDH configuration

•Up to 1 millisecond of traffic loss after reconfiguration of lines/paths on the same bay

•The AXSM-XG does not support AutoRoute CoS queues

Graceful Upgrades to AXSM-XG Cards

You can gracefully upgrade AXSM, AXSM/B, and AXSM-E cards to AXSM-XG cards. The AXSM-16-155-XG and AXSM-8-622-XG cards have a higher port density than the equivalent AXSM-E cards, and the AXSM-16-155-XG and AXSM-8-622-XG have better traffic management support than their AXSM/B counterparts.

Graceful upgrades simplify the process of migrating to the newer AXSM-XG cards. During the upgrade, the MGX control processor transfers the configuration/connection database from the previously installed AXSM card to the new AXSM-XG, which preserves all connection configurations. The upgrade process might cause an outage of up to 4 minutes.

You can install and operate any number of AXSM-XG cards in conjunction with AXSM, AXSM/B or AXSM-E in a Cisco MGX 8850 chassis equipped with the PXM45 processor. You can install and operate any number of AXSM-XG cards in conjunction with AXSM/B in a Cisco MGX 8950.

Card redundancy is supported only between identical front and back card pairs. For example, an AXSM-16-155-XG can only be redundant to another AXSM-16-155-XG, where the two front cards use an identical set of back cards.

For more information about the upgrade procedure, see the Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.5.10.

Multilink PPP on the MPSM-T3E3-155 Card

This release adds Multilink PPP (MLPPP) to the MPSM-T3E3-155 card. MLPPP includes the following capabilities:

•Supported on the BNC-3-T3E3 back card only and only in channelized mode. In other words, MLPPP is not supported for E3 in any form or unchannelized T3.

PXM45/C Support in the Cisco MGX 8830/B Chassis

A PXM45/C controller in a Cisco MGX 8830/B chassis provides support for a selection of narrowband and broadband interfaces in an 8-slot chassis. The PXM45/C controller's 45 Gbps switch matrix makes it possible to aggregate and switch traffic from a mix of narrow-band, DS3/E3, OC-3c/STM-1, and OC-12/STM-4 ATM ports, and simplifies the process of scaling a network node as connection counts increase.

Mobile PNNI Support

This release adds the Mobile PNNI feature to the existing PNNI functionality. Generally a PNNI network has a fixed hierarchy where each element has a fixed point of attachment. Mobile PNNI extends a fixed network infrastructure to mobile ATM switches that are roaming in the network. To maintain connectivity when the location of the mobile ATM switch changes, mobile switches are allowed to dynamically change peer group membership. To implement this feature, you establish a link to the fixed network; the mobile network then finds the proper peer group and hierarchy and joins the network.

Mobile PNNI allows each mobile network to build its own PNNI hierarchy and integrate the hierarchy of the fixed network as a logical group node (LGN). In the context of mobile PNNI, it is called Mobile LGN. A mobile logical group node has the capability to dynamically change its membership from one peer group to another as it attaches to different fixed switches. A mobile logical group node is only permitted to join a parent peer group of one of the fixed switches.

The ATM forum describes mobile PNNI in publication AF-RA-0123.000, PNNI addendum for mobility extensions Version 1.0, which is available at the following location:

ftp://ftp.atmforum.com/pub/approved-specs/af-ra-0123.000.pdf

Compression and Multiplexing Support for RPM-PR Cards

The MGX-RPM-1FE-CP (one-port, Fast Ethernet-Co-processor) back card is a Cisco MGX 8850/RPM-PR back card that off-loads the following processes from the Route Processor Module (RPM-PR):

•Connections provisioned on the Cisco MGX 8850 PNNI control plane using the MSF switch architecture based Virtual Switch Interface (VSI)

•Licensing of the supported features

Multilink PPP Feature for CDMA2000 and EV-DO

The MPSM-16-T1E1 implements Multilink PPP, which is a key protocol in a larger application defined by CDMA2000. In this application, the Cisco MGX 8850 (PXM45) aggregates traffic from several BTS site routers (MWR) and transfers that traffic to an IP network. The aggregation point in the Cisco MGX 8850 (PXM45) is the RPM-XF. Traffic from all of the BTS routers are transported over PPP links (typically on T1/E1 links) and brought into the Cisco MGX 8850 (PXM45) through an MPSM-16-T1E1 card. The MPSM-16-T1E1 transforms the PPP payload into AAL5 cells, which it sends to the RPM-XF using ciscoPPPoAAL5 encapsulation.

With growth in traffic in the CDMA2000 application, you might need to add additional T1/E1 links between the MWR and the MPSM-16-T1E1. The MLPPP feature simplifies the process of adding incremental bandwidth because it can aggregate capacity of individual T1/E1 lines. Because the IP payloads are small (typically voice) and the overhead associated with PPP (MLPPP) packets increases with smaller payloads, PPPMUX functionality is utilized on the MPSM-16-T1E1. In EV-DO, multiplexing is not used.

The connection between MPSM and RPM-XF is setup as a PVC connection. The bandwidth of this PVC depends on the number of operation PPP links on an MP bundle. RPM-XF terminates the PPPoAAL5 data and routes the IP traffic to the backbone IP network.

MPSM-155-T3E3 and MPSM-16-T1E1 Online Diagnostics

The online diagnostic tests run on regular intervals for both on the active and standby state of the MPSM cards to check the health of the devices and data paths. The online diagnostics test the following devices and data paths:

•Data path from the CPU on the MPSM to the CBC slave loopback on the MPSM through Winpath 0

•Data path from the CPU on MPSM to the CBC master loopback on the PXM through Winpath 1

•Winpath memory access test (packet, parameter, host memory)

•Write/read memory access test for internal devices

•Validate front card NVRAM checksum

•Validate flash checksum

Private Network Node Interface Current Route Feature

The Current Route feature provides the path information for active Point-to-Point (P2P) SPVCs/SPVPs master-end connections. The path information contains the lowest level physical node and egress trunk information of the path on which the connection is currently routed.

This feature uses the ATM standards based connTrace message to obtain the current route information. CWM uses the configuration upload file mechanism to request available path information of connections on a periodic or an on-demand basis.

This feature works in single peer group and multiple peer group networks. The current path can be used by the network administrators and planners to engineer the trunk use and to direct how connections should be routed.

Operational and Redundancy Limitations

•Master ended connections have the current route information. Slave ended connections do not have this information.

•The configuration upload file contains a snapshot of the current route information at the time that the switch receives a configuration upload request from CWM. Therefore, the snapshot might not contain the latest information, and connection trace information that the switch receives after the file is created is not included in the file.

•If congestion occurs on a node, the connTrace message sent by the CLI and by the Current Route feature is dropped. The two connTrace messages are not distinguishable. This limitation also applies to connTrace ACK messages that are received on a congested node.

•After changing a node ID, disable and then re-enable the current route feature on each node in the network using the cnfndcurrte command.

This command flushes all existing current route information and starts collecting new information. After disabling the current route feature, wait at least 9 seconds (the time-out period for a connTrace message) before re-enabling it. This inhibits processing of stale conn-trace messages.

•The connection path information for a connection traversing more than 20 nodes is not stored in the current route path table. Therefore, such connections do not have current route information.

•The current route path does not include the destination termination port (normally slave endpoint UNI port). The destination port is set to zero in the current route path, which is similar to preferred route.

The current route feature has the following redundancy limitations:

•The current route feature provides redundancy. However, because the current route must not reduce routing performance, some connections might not have redundant current route information on the standby PXM.

For those connections that do not have redundant current route information at the time of a switchcc, their current route information is obtained through the normal scanning on the active card when the old standby becomes active.

•After a standby PXM card is inserted and reset, the active card sends the current route information to the standby card only after its state changes from Init to Standby. This avoids increasing the time it takes for the redundant card to come up to the Standby state, ready for switchcc.

The Standby state is not redundant until the current route update is completed. Therefore, a switchcc that occurs before all current route information is sent to the redundant card results in some connections not having current route information on the newly active card. The current route information for those connections is obtained during the normal current route scanning and processing.

•When inserting or resetting the standby PXM, enter the command dspndcurrte and verify that Bulk update is complete before performing a switchcc.

Feature Specifications

The current route feature has the following limitations:

•A maximum of 10K path entries per node are supported.

•A maximum of 5K node ID entries per node are supported.

•A maximum of 2K ports on PXM1E systems are supported when current route is enabled.

An attempt to enable the current route feature on a node which has more than 2K ports is not allowed and results in error. If the current route feature is enabled and more than 2K ports are subsequently added, this feature or other applications might not work properly.

•A maximum of 100K connections are supported PXM45/B systems when current route is enabled.

An attempt to enable current route on a node which has more than 100K connections results in error. If the current route feature is enabled and more than 100K connections are subsequently added, this feature or other applications might not work properly.

PNNI Product Enhancements

The Link Selection enhancement adds functionality to parallel links to which link selection criteria is provisioned to minAW (minAWlinks). Activate this feature through the CLI. If these enhancements are not activated, the existing `link selection' behavior is used.

This enhancement introduces a command (cnfpnni-svcc-rcc-param) to configure the connection parameters associated with SVCC-RCC connections at each level of the PNNI hierarchy.

PER 8281

Path bypass selection configuration

In a complex node multiple peer group topology, the path that has the highest available cell rate (AvCR) is advertised as the bypass. Typically this path has higher cost, so the calls routed over the pass bypass might always take the worst path. This enhancement adds an option to the cnfpnni-routing-policy command to specify the criteria for bypass path selection.

PER 8282

Administrative Weigh (AW) Pruning

Currently a trunk is included in the best path selection even if it has a single cell per second of AvCR. This enhancement introduces an AvCR threshold parameter to the cnfpnni-routing-policy command so that trunks with BW below the threshold are excluded from the best path search.

PER 8287

Consistent PNNI Link Selection

Allows application of the same link selection mechanism to connections of all service categories (ABR, UBR, CBR, and VBR) on minAW links.

Allows provisioning epsilon-equal AW parallel links among the minAW parallel links between two switches. The switch calculates the epsilon value based on user input.

If epsilon-equal AW parallel links exist between two switches along the selected shortest path, link selection applies. For epsilon-equal AW parallel links, the secondary link selection criteria is maxAvCR. If all links have the same AvCR, the connections are routed according to load balance criteria.

PER 8540

Preferred Route Enhancements

The cnfndidrtes command has a new parameter for indicating that the same node is being configured and that the preferred route status should not change. A connection that was on a preferred route before the change would not be groomed by route optimization.

PER 8660

Link Selection Enhancements for MPG

MPG (multipeer group) Pref Rt Conns

PER 8807

Routing Policy Enhancements

This enhancement adds a parameter value to the cnfpnni-routing-policy command that selects from equal administrative weight (AW) paths using the number of minimum hops. If multiple epsilon-equal AW paths with the same minimum-hops exist, a second load balance parameter specifies the tie break criteria.

PXM1E OAM Enhancement

The PXM1E processes the following OAM loopback cells:

•End-to-end OAM loopback cells—Used for background connection continuity verification. These cells might be sent by a VISM card or router.

•Segment OAM loopback cells—Used for diagnostic testing between segment endpoints. These cells are sent for the following CLI commands: tstdelay, tstconsegep, and tstpndelay.

This release moves the task of extracting and injecting OAM loopback cells at the PXM1E from the Atlas to the QE1210. Unlike with Atlas, the QE1210 can distinguish between segment and end-to-end OAM loopback cells. The QE1210 extracts only the segment OAM loopback cells, while transparently passing the end-to-end OAM loopback cells.

Because the end-to-end OAM loopback cells no longer require software processing, the previous limitations for the OAM loopback cell rate on the PXM1E no longer apply. These cells are now processed in the QE1210 hardware and are limited only by the available line bandwidth.

Each PXM1E segment endpoint has a polling-induced queue extraction delay of up to 10 ms for a segment OAM loopback cell. This delay is not imposed on end-to-end cells or segment cells at nonsegment endpoints.

System Requirements

This section describes software compatible with this release and lists the supported hardware.

4. Use SCTs with VC thresholds of at least 50000 microseconds for the VSI signaling service type. New SCTs 5,6 and 54, 55 (SCTs for the T3/E3, Combo cards, and IMA group links, respectively) update the VC threshold and have minor version = 1. Upgrade your custom SCTs to the new recommended VC thresholds and change the minor version. You can gracefully upgrade an SCT with a minor version change without interrupting traffic. The SCT chapter of the Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.5.10 explains how to upgrade a SCT file to a new minor version.

AXSM and AXSM/B SCT Files

The AXSM and AXSM/B SCTs have the following characteristics:

•SCT 2—Policing enabled, PNNI

•SCT 3—Policing disabled, PNNI

•SCT 4—Policing enabled, MPLS and PNNI

•SCT 5—Policing disabled, MPLS and PNNI

The file names and checksums for the SCT files are as follows:

•AXSM_SCT.PORT.0.V1:Cchecksum is = 0x6aadd6c6= 1789777606

•AXSM_SCT.PORT.2.V1: Checksum is = 0x78ccfb22= 2026699554

•AXSM_SCT.PORT.3.V1: Checksum is = 0x987919a7= 2558073255

•AXSM_SCT.PORT.4.V1: Checksum is = 0x775bfaa2= 2002516642

•AXSM_SCT.PORT.5.V1: Checksum is = 0xe84c696a= 3897321834

•AXSM_SCT.CARD.0.V1: Checksum is = 0x6aadd6c6= 1789777606

•AXSM_SCT.CARD.2.V1: Checksum is = 0x78ccfb22= 2026699554

•AXSM_SCT.CARD.3.V1: Checksum is = 0x987919a7= 2558073255

•AXSM_SCT.CARD.4.V1: Checksum is = 0x775bfaa2= 2002516642

•AXSM_SCT.CARD.5.V1: Checksum is = 0xe84c696a= 3897321834

To confirm that the checksum of the SCT file and the file on the node match, enter dspsctchksum <filename>.

AXSM-E SCT Files

The AXSM-E SCTs have the following characteristics:

•CARD and PORT SCT 5—Policing enabled for PNNI, disabled for MPLS

•PORT SCT 6—Policing disabled, used for PNNI ports.

•CARD and PORT SCT 52—Policing enabled on PNNI, disabled on MPLS

•PORT SCT 53—Policing disabled on PNNI and MPLS

•PORT SCT 54— Policing enabled on PNNI, disabled on MPLS

•PORT SCT 55—Policing disabled on PNNI and MPLS

The following are checksums for the new AXSM-E SCT file:

•AXSME_SCT.PORT.5.V1: Checksum is = 0x793c56d0= 2033997520

•AXSME_SCT.PORT.6.V1: Checksum is = 0xe92db9a5= 3912087973

•AXSME_SCT.PORT.52.V1: Checksum is = 0x51241b7a= 1361320826

•AXSME_SCT.PORT.53.V1: Checksum is = 0x34bdf8b9= 884865209

•AXSME_SCT.PORT.54.V1: Checksum is = 0xb5df2c5c= 3051301980

•AXSME_SCT.PORT.55.V1: Checksum is = 0xc5d355c8= 3318961608

•AXSME_SCT.CARD.5.V1: Checksum is = 0x793c56d0= 2033997520

•AXSME_SCT.CARD.52.V1: Checksum is = 0x972810ac= 2535985324

AXSM-XG SCT Files

The AXSM-XG SCTs have the following characteristics:

•CARD SCT 2—Policing disabled on PNNI and MPLS. Applied in ingress direction based on backplane bandwidth.

New WP identifier field for the MPSM-16-T1E1 (CSCin97715). See dspmpbundles

•dspmpbundlecnt and dspppplnkcnt

New statistics for the average bundle or link data rate in Kbps, called kbpsAIR (CSCin97715). See dspmpbundlecnt, and dspppplnkcnt.

•addport, dspport, and dspports

New ds0beg and ds0num parameters for adding for fractional T1/E1 ATM ports (CSCeg68904). See addport, dspport, and dspports.

•dsppathalmcnt

Display elapsed time for current statistics (CSCej89464). See dsppathalmcnt.

•dspmpbundleload, dspwinpathload, and dspwpbundles

Added these MPSM-T3E3-155 commands to the MPSM-16-T1E1 card for consistency.

addport

Add Port

Service Context—ATM and Frame Relay

Modules—MPSM-T3E3-155, MPSM-16-T1E1

Enter the addport command to create and configure a logical port on an active physical line or logical path.

On a BNC-3-T3 or BNC-3-E3 back card, you can add a port on a physical line, or on a path. On an SFP-2-155 and the SMB-2-155-EL OC-3 back card, you can add a port on a path only.

For the MPSM-16-T1E1, you can configure full T1/E1 ports or NxDS0 ports. With PNNI signaling enabled on NxDS0 ports, you must configure the minimum bandwidth that PNNI requires. Otherwise, PNNI trunks may not come up. Use the dsppnctlvc command to display the required PNNI bandwidth.

Before you can add a port to a line or path, you must configure and activate the line or path. You use the upln command to activate a line, or the uppath command to activate a path.

Note The MPSM-T3E3-155 card supports up to 128 ATM ports and 1000 Frame Relay ports. The maximum number of logical ports for the entire MPSM-T3E3-155 is 1000. For example, you can configure 872 Frame Relay ports and 128 ATM ports on one MPSM-T3E3-155 card.

Note If you are going to use card statistics, you must use cnfcdstat before you add logical ports with the addport command. You cannot configure card statistics after adding ports.

The ID of a service class template (SCT) for the port. The range is 0-255. The SCT file must exist on the PXM disk. See cnfcdsct.

Note Currently, the system does not support certain parameters in the service class templates (SCTs). These parameters are (when applicable) PCR, SCR, and ICR. You can specify them through addcon, cnfcon, or Cisco WAN Manager.

ifType

Specifies the port as one of the following types of interfaces:

•1 = UNI (User-to-Network Interface)

•2 = NNI (Network-to-Network Interface)

•3 = VNNI (Virtual Network-to-Network Interface)

•4 = VUNI (Virtual User-to-Network Interface)

•5 = EVUNI (Enhanced Virtual User-to-Network Interface)

•6 = EVNNI (Enhanced Virtual Network-to-Network Interface)

EVNNI and EVUNI permit a range of VPIs for a single interface, and this range of VPIs represents the virtual NNI or virtual UNI trunk. VNNI and VUNI allow only one VPI for a single interface, and that VPI represents the virtual NNI or virtual UNI trunk. Multiple VNNIs and EVNNIs can coexist on the same line.

-vpi

Virtual Path Identifier for a VNNI or VUNI interface:

•VNNI range: 1-4095

•VUNI range: 1-255

-minvpi

The minimum VPI for an EVUNI or EVNNI interface:

•EVUNI range: 0-255

•EVNNI range: 0-4095

-maxvpi

The maximum VPI for an EVUNI or EVNNI interface:

•EVUNI range: 0-255

•EVNNI range: 0-4095

-ds0beg

Specifies the beginning DS0 number:

•T1 paths: 1-24

•E1MF and E1CRCMF paths: 2-16, 18-32 (17 is reserved)

•other E1 paths = 2-32

Note MPSM-16-T1E1 only.

-ds0num

Specifies the number DS0 time slots that will follow the beginning DS0:

•T1 paths: 1-24

•E1MF and E1CRCMF paths: 1-30

•other E1 paths: 1-31

Note MPSM-16-T1E1 only.

Related Commands

cnfport, delport, dspport, dspports, dspportsct

Attributes

Log: yes

State: active

Privilege: GROUP1

Example—ATM Service Context

In the following example, the user creates logical port 3 on line 3 of bay 1. The minimum and maximum cells per second is 96000 cps. The port SCT file ID is 4. The interface type is NNI (specified by the 2 at the end of the command input).

MGX8850.6.MPSM155[ATM].a > addport 3 1.3 96000 96000 4 2

In the following example, the user creates a fractional T1 port on line 5 of bay 1. The logical port number is 205, the minimum and maximum cells per second is 603 cps, the port SCT file ID is 0, and the interface type is NNI. This port has four DS0s, starting with the first DS0 of the T1 line.

Note Enter the dsplns or dsppaths -all command to display all available lines or paths on the card.

bundleNumber

The MLPPP bundle number to which you are adding a PPP link.

•MPSM-16-T1E1 range: 1-16

•MPSM-T3E3-155 range: 1-84

Note Enter the dspmpbundles command to display all MLPPP bundles on the card.

-mru

Maximum Receive Unit, in the range 64-1524.

Default:1500

-lcpTimeout

Note The length of time to wait for an echo reply before bringing down LCP. The value is specified in msec, but is rounded down to the nearest 100 msec.

Range: 1000-4294967 msec

Default: 10000 msec

-restartTimer

The link restart timer value.

Range: 1000-60000 msec

Default: 3000 msec

-cnfReqRetry

The maximum number of configuration request retries.

Range: 1-255

Default: 10

-termReqRetry

The maximum number of termination request retries.

Range: 1-255

Default: 2

-echo

The maximum number of echo retries.

Range: 1-255

Default: 5

-maxFailure

The maximum number of failures.

Range: 1-255

Default: 5

-startDS0

Specifies a starting DS0 for a fractional T1/E1 link, in the following ranges:

•T1 line or path: 1-24

•E1 line or path:

–E1 and CRC types: 2-32 (timeslot 0 reserved)

–MF or CRCMF types: 2-16, 18-32 (timeslots 0 and 16 reserved)

Note Thisparameter is required for a fractional T1/E1 link.

-numDS0

Specifies the number of DS0s for a fractional T1/E1 link, in the following ranges:

•T1 line or path: 1-24

•E1 line or path:

–E1 and CRC types: 1-31 (timeslot 0 reserved)

–MF or CRCMF types: 1-30 (timeslots 0 and 16 reserved)

Default: Maximum number of DS0s

Note A fractional T1/E1 link has a contiguous set of DS0s.

-ds0speed

Specifies the speed of DS0 channels.

•1 = 56K

•2 = 64K (default)

-pfcTx

Controls the compression of PF in PPP packets transmitted from this end.

•1 = enable, PFC is performed if the far end is capable of receiving compressed PF.

•2 = disable, PFC is not performed, even if the far end is capable of receiving compressed PF.

Default: 2

-acfcTX

Controls the compression of address/control fields in PPP packets transmitted from this end.

•1 = enable, ACFC is performed if the far end is capable of receiving compressed address/control fields.

•2 = disable, ACFC is not performed, even if far end is capable of receiving compressed address/control fields.

Default: 2

-loopCheck

Enables or disables loopback check. If loopback check is enabled, when the magic number in the incoming echo reply is the same as of this PPP link, then this PPP link assumes that the far end is in loopback and brings down the LCP session.

•1 = enabled (default)

•2 = disabled

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

cnfppplink, delppplink, dspppplink

Example

In the following example, the user adds a PPP link 5 and line 1.5 and bundle 5.

M8850_SF.27.MPSM16T1E1PPP[FR].a > addppplink 5 1.5 5

cnfppplink

Configure a PPP Link

Service Context—PPP

Modules—MPSM-16-T1E1, MPSM-T3E3-155

Enter the cnfppplink command to change the configuration of a PPP link.

Syntax Description

The length of time to wait for a Echo Reply before bringing down LCP. The value is in msec, rounded down to the nearest 100 msec. Range 1000-4294967.

-restartTimer

The link restart timer value.

Range: 1000-60000 msec

Default: 3000 msec

-cnfReqRetry

The maximum number of configuration request retries.

Range: 1-255

Default: 10

-termReqRetry

The maximum number of termination request retries.

Range: 1-255

Default: 2

-echo

The maximum number of echo retries.

Range: 1-255

Default: 5

-maxFailure

The maximum number of failures.

Range: 1-255

Default: 5

-pfcTx

Controls the compression of PF in PPP packets transmitted from this end.

•1 = enable, PFC is performed if the far end is capable of receiving compressed PF.

•2= disable, PFC is not performed, even if far end is capable of receiving compressed PF.

-acfcTX

Controls the compression of address/control fields in PPP packets transmitted from this end.

•1 = enable, ACFC is performed if the far end is capable of receiving compressed address/control fields.

•2 = disable, ACFC is not performed, even if far end is capable of receiving compressed address/control fields.

-loopCheck

Controls loopback check. If loopback check is enabled, when the Magic Number in the incoming Echo Reply is the same as of this PPP link, then this PPP link assumes that the far end is in loopback and brings down its own LCP session.

•1 = enable

•2 = disable

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

addppplink, delppplink, dspppplink

Example

In the following example, the user configures PPP link 1 with an MRU of 1234 and enables acfcTx and pfcTx compression.

dsppathalmcnt

Display Path Alarm Counters

Service Context—ATM and Frame Relay

Modules—MPSM-T3E3-155

Enter the dsppathalmcnt command to display the path alarm counters for the specified path for the current 15-minute interval and the current 24-hour interval. Optionally, you can display path alarm counters for a specific 15-minute interval only.

Syntax

dsppathalmcnt [path_filter] <path_num> [<intvl>]

Syntax Description

-path_filter

Identifies the path type for which you want to display alarm counters.

Note STS/STM paths and DS3 paths can have the same path number. If you enter the dsppathalmcnt command without the -path_filter option, and only STS/STM paths are configured on the card, the display shows the path alarm counters for the STS/STM path with the specified path number. If there are DS3 paths configured on the card as well as STS/STM paths, and you do not include the -path_filter option with the dsppathalmcnt command, the display shows the path alarm counters for the lowest-level path (the DS3 path). To avoid confusion, Cisco recommends that you specify a -path_filter when you display a path.

path_num

The number of the path to display.

Note Use the dsppaths<path_filter> command to display the path numbers for available paths.

intvl

The time interval to display (0-96). Interval 0 is the current 15-minute and 24-hour interval. Interval 1 is the most recent 15-minute interval. Interval 2 is the next most recent 15-minute interval, and so on. Interval 96 is the oldest 15-minute interval.

Related Commands

clrpathalmcnf

Attributes

Log: no

State: active, standby, init

Privilege: ANYUSER

Example

In the following example, the user displays the path alarm counters for the STS path 1.1.1, which displays the current interval statistics and the elapsed time of the current interval.

M8850_SF.9.MPSM155PPP[FR].a > dsppathalmcnt-sts 1.1.1

Path Number : 1.1.1

Path Type : sts

Path PM:

Elapsed Time(in sec): 309

Num of AISs: 0

Num of RDIs: 0

Near End Far End

CurrentESs : 0 CurrentESs : 0

CurrentSESs : 0 CurrentSESs : 0

CurrentCVs : 0 CurrentCVs : 0

CurrentUASs : 0 CurrentUASs : 0

Current24HrESs : 0 Current24HrESs : 0

Current24HrSESs: 0 Current24HrSESs: 0

Current24HrCVs : 0 Current24HrCVs : 0

Current24HrUASs: 0 Current24HrUASs: 0

In the following example, the user displays interval statistics for the same path.

M8850_SF.9.MPSM155PPP[FR].a > dsppathalmcnt -sts 1.1.1 2

Path Type : sts

Path Number : 1.1.1

Interval Number : 2

Path PM:

--------

Near End Far End

ESs : 0 ESs : 0

SESs : 0 SESs : 0

CVs : 0 CVs : 0

UASs : 0 UASs : 0

dspmpbundles

Display MLPPP Bundles

Service Context—PPP

Modules—MPSM-16-T1E1, MPSM-T3E3-155

Enter the dspmpbundles command to display summary information about all MLPPP bundles.

Syntax

dspmpbundles

Syntax Description

None

Attributes

Log: no

State: active

Privilege: any

Related Commands

addmpbundle, cnfmpbundle, delmpbundle, dspmpbundle, dspwpbundles

Example

In the following example, the user displays all MLPPP bundles on an MPSM-16-T1E1 card:

•The operational state for standby cards is reported as N/A because the operational state of the standby card may not be the same as the active card.

•The total number of connections in the display includes control VCs. The types of control VCs are SSCOP, PNNI-RCC, and ILMI (if integrated local management interface is enabled on MPSM cards). To see the connection counts that do not include control VCs, use dsppnport.

•When a MPSM rebuilds, it provisions the card from the stored database on the PXM disk. If the SCT file associated with a specific port is missing or corrupted, the default SCT file is applied to that port. This is indicated in the dspport output by the string:

"0/0 =Def"

•The SCT ID in the display pertains to the port. For the card-level SCT ID, use dspcd on the current card.

Syntax

dspport <ifNum>

Syntax Description

ifNum

Identifies the logical interface (port number) to display.

Note Use the dspports command in the to display the port numbers for all active ports in the current CLI context.

Related Commands

addport, dnport, dspports

Attributes

Log: no

State: active, standby

Privilege: ANYUSER

Sample ATM Service Context

In the following MPSM-T3E3-155 example, the user displays the port configuration for ATM port 12.

mpsm_node.4.MPSM155[ATM].a > dspport 12

Interface Number : 12

Line/Path Number : 1.1.2 IMA Group Number : N/A

Admin State : Up Operational State : Up

Guaranteed bandwidth(cells/sec): 50 Number of partitions : 1

Maximum bandwidth(cells/sec) : 50 Number of SPVC : 1

ifType : UNI Number of SPVP : 0

VPI number (VNNI, VUNI) : 0 Number of SVC : 0

Number of Sig VC : 0

MIN VPI (EVNNI, EVUNI) : 0 MAX VPI (EVNNI, EVUNI): 0

SCT Id : 0 =Def

F4 to F5 Conversion : Disabled

In the following MPSM-16-T1E1 example, the user displays the port configuration for a fractional T1 ATM port with four DS0s.

M8850_SF.27.MPSM16T1E1[ATM].a > dspport 205

Interface Number : 205

Line/Path Number : 1.5 IMA Group Number : N/A

Admin State : Up Operational State : Up

Guaranteed bandwidth(cells/sec): 603 Number of partitions : 1

Maximum bandwidth(cells/sec) : 603 Number of SPVC : 0

ifType : UNI Number of SPVP : 0

VPI number (VNNI, VUNI) : 0 Number of SVC : 0

Number of Sig VC : 0

MIN VPI (EVNNI, EVUNI) : 0 MAX VPI (EVNNI, EVUNI): 0

SCT Id : 0 =Def

F4 to F5 Conversion : Disabled

Time Slot : 1(4)

In the following MPSM-T3E3-155 example, the user displays the port configuration for IMA port 127.

M8850_SF.9.MPSM155[ATM].a > dspport 127

Interface Number : 127

Line/Path Number : N/A IMA Group Number : 1

Admin State : Up Operational State : Up

Guaranteed bandwidth(cells/sec): 3000 Number of partitions : 1

Maximum bandwidth(cells/sec) : 3000 Number of SPVC : 0

ifType : UNI Number of SPVP : 0

VPI number (VNNI, VUNI) : 0 Number of SVC : 0

Number of Sig VC : 0

MIN VPI (EVNNI, EVUNI) : 0 MAX VPI (EVNNI, EVUNI): 0

SCT Id : 0 =Def

F4 to F5 Conversion : Disabled

Sample Frame Relay Service Context

In the following example, the user displays the port configuration for Frame Relay port 2.

mpsm_node.5.MPSM155[FR].a > dspport 2

Interface Number : 2

Line Number : 1.1.1

DS0 Speed : unused

DS0 Configuration Bit Map : N/A

Admin State : Down

Operational State : Down

Port State : Inactive

Port Signaling State : No Signaling Failure

Interface Type : Frame Relay

SCT Id : 0/0 =Def

Frame Header Length : Two Bytes

Flags Between Frames : 1

Equeue Service Ratio : 1

Port Speed : 44209 kbps

Checksum type : crc16

Over-subscription : Disabled

Over-subscribed : False

Signaling Protocol Type : No Signaling

Enhanced LMI : Disabled

FRF 1.2 Support : Disabled

Asynchronous Updates : Disabled

T391 Link Integrity Timer : 10 secs

Type <CR> to continue, Q<CR> to stop:

T392 Polling Verification Timer : 15 secs

N391 Full Status Polling Counter : 6

N392 Error Threshold : 3

N393 Monitored Event Count : 4

FRF.12 Fragmentation : Disabled

FRF.12 Fragment Size : 64 Bytes

Port HDLC Frame Inversion : Disabled

Number of Partitions : 1

Number of SPVC : 0

In the following example, the user displays the port configuration for Multilink Frame Relay port 4.

M8850_SF.9.MPSM155[FR].a > dspport 4

Interface Number : 4

Line Number : N/A

MFR bundle Number : 1

DS0 Speed : unused

DS0 Configuration Bit Map : N/A

Admin State : Up

Operational State : Up

Port State : Active

Port Signaling State : No Signaling Failure

Interface Type : Frame Relay

SCT Id : 0/0 =Def

Frame Header Length : Two Bytes

Flags Between Frames : 1

Equeue Service Ratio : 1

Port Speed : 1532 kbps

Checksum type : crc16

Over-subscription : Disabled

Signaling Protocol Type : None

Enhanced LMI : Disabled

FRF 1.2 Support : Disabled

Asynchronous Updates : Disabled

T391 Link Integrity Timer : 10 secs

Type <CR> to continue, Q<CR> to stop:

T392 Polling Verification Timer : 15 secs

N391 Full Status Polling Counter : 6

N392 Error Threshold : 3

N393 Monitored Event Count : 4

FRF.12 Fragmentation : Disabled

FRF.12 Fragment Size : 64 Bytes

Port HDLC Frame Inversion : Disabled

Number of Partitions : 1

Number of SPVC : 0

Sample PPP Service Context

In the following example, the user displays the port configuration for Multilink PPP port 5.

M8850_SF.25.MPSM16T1E1PPP[FR].a > dspport 5

Interface Number : 5

Line Number : N/A

DS0 Speed : unused

DS0 Configuration Bit Map : N/A

Admin State : Up

Operational State : Up

Port State : Active

Port Signaling State : No Signaling Failure

Interface Type : Frame Forward

SCT Id : 0/0 =Def

Frame Header Length : Two Bytes

Flags Between Frames : 1

Equeue Service Ratio : 1

Port Speed : 1536 kbps

Checksum type : crc16

Over-subscription : Disabled

Signaling Protocol Type : None

Enhanced LMI : Disabled

FRF 1.2 Support : Disabled

Asynchronous Updates : Disabled

T391 Link Integrity Timer : 10 secs

T392 Polling Verification Timer : 15 secs

Type <CR> to continue, Q<CR> to stop:

N391 Full Status Polling Counter : 6

N392 Error Threshold : 3

N393 Monitored Event Count : 4

FRF.12 Fragmentation : N/A

FRF.12 Fragment Size : 64 Bytes

Port HDLC Frame Inversion : Disabled

Number of Partitions : 1

Number of SPVC : 0

dspports

Display Ports

Service Context—ATM, Frame Relay, PPP

Modules—MPSM-T3E3-155, MPSM-16-T1E1

Enter the dspports command to display general information about all logical ports on the card.

Enter the dspports command in the ATM CLI context to display the following information for all ATM ports on the current card:

ifNum

Identifies the logical interface (port).

Line/Path

Identifies the path number associated with the port.

Admin State

Indicates whether the administrative status of the port is up or down.

Oper State

Indicates whether the port is up or down.

Guarntd Rate

Indicates the minimum guaranteed rate for the port in cells per second.

Max Rate

Indicates the maximum allowed rate for the port in cells per second.

SCT InUse

Indicates the ID of the port-level SCT (see the addport command).

if Type

Indicates the type of interface configured on the port.

VPI (VNNI, VUNI)

The VPI number of the port (applies only where virtual NNIs are available).

VPI (EVUNI, EVNNI)

The minimum and maximum VPI configured for the port (applies only where virtual NNIs are available).

IMA GRP

Identifies the port's IMA group, if IMA groups are configured.

Note If the specified port is not configured for an IMA group, the IMA GRP field reports N/A.

DS0Start (Num)

The first DS0 channel in an NxDS0 port, and the number of DS0s it contains.

Enter the dspports command in the Frame Relay CLI context to display the following information for all Frame Relay ports:

ifNum

The logical interface (port).

Line/Path

The line or path number associated with the port.

Admin State

Indicates whether the administrative status of the port is up or down.

Oper State

Indicates whether the port is up or down.

ifType

The type of interface configured on the port.

sctID Conf/InUse

The ID of the port-level SCT (see the addport command).

DS0 Start (Num)

The first DS0 channel in an NxDS0 port, and the number of DS0s it contains.

Port Speed

Indicates the data rate of the port, in Kbps.

ESR

Indicates the enqueue service ratio

Signaling Type

Indicates the port signaling type, if any.

ELMI Status

Indicates whether enhanced LMI state is enabled or disabled on the port.

FRF 12 Fragmentation

Indicates whether FRF 12 Fragmentation is enabled or disabled on the port.

MLPPP Bundle

Indicates the bundle with which the port is associated for MLPPP services.

Note Displayed only on cards that support MLPPP.

MFR Bundle

Indicates the bundle with which the port is associated for MFR services.

Note Displayed only on cards that support MFR.

Note The operational state for standby cards is reported as N/A because the operational state of the standby card may not be the same as the active card.

Syntax

dspports

Related Commands

addport, cnfport, delport, dspport

Attributes

Log: no

State: active, standby

Privilege: ANYUSER

Sample ATM Service Context

In the following MPSM-T3E3-155 example, the user displays the ATM ports, two of which are IMA groups.

dspmpbundlecnt

Syntax

Syntax Description

bundleNumber

Specifies the MLPPP bundle number for which t o display statistics.

Note Enter the dspmpbundles command to display all MLPPP bundles on the card.

intvl

The time interval to display (0-96). Interval 0 is the current 15-minute and 24-hour interval. Interval 1 is the most recent 15-minute interval. Interval 2 is the next most recent 15-minute interval, and so on. Interval 96 is the oldest 15-minute interval.

Attributes

Log: no

State: active

Privilege: any

Related Commands

dspmpbundle

Example

In the following example, the user displays statistics for interval 0 of MLPPP bundle 1 on an MPSM-16-T1E1:

M8850_SF.27.MPSM16T1E1PPP[FR].a > dspmpbundlecnt 1 0

MLPPP Bundle Number : 1

Interval Number : 0

Receive Packets : 2101305

Receive Bytes : 60955779

Receive Discard Bytes : 0

Receive MRRU Error Packets : 0

Receive Discard Packets : 0

Receive FCS Error Packets : 0

Receive kbpsAIR : 1509

Send Packets : 397

Send Bytes : 29390

Send kbpsAIR : 0

In the following example, the user displays statistics for interval 0 of MLPPP bundle 1 on an MPSM-T3E3-155:

M8850_SF.10.MPSM155PPP[FR].a > dspmpbundlecnt 1 0

MLPPP Bundle Number : 1

Interval Number : 0

Receive Packets : 2101305

Receive Bytes : 60955779

Receive Discard Bytes : 0

Receive MRRU Error Packets : 0

Receive Discard Packets : 0

Receive FCS Error Packets : 0

Receive kbpsAIR : 1509

Send Packets : 397

Send Bytes : 29390

Send kbpsAIR : 0

dspppplnkcnt

Display Statistics on a PPP Link

Service Context—PPP

Modules—MPSM-16-T1E1, MPSM-T3E3-155

Enter the dspppplnkcnt command to display statistics on a PPP link.

Syntax

dspppplnkcnt<link> <intvl>]

Syntax Description

link

Specifies the PPP link number for which to display statistics.

Note Enter the dspppplinks command to display all MLPPP links on the card.

intvl

The time interval to display (0-96). Interval 0 is the current 15-minute and 24-hour interval. Interval 1 is the most recent 15-minute interval. Interval 2 is the next most recent 15-minute interval, and so on. Interval 96 is the oldest 15-minute interval.

Attributes

Log: no

State: active

Privilege: any

Related Commands

clrppplnkcnt

Example

In the following example, the user displays statistics for interval 0 on PPP link 10 on an MPSM-16-T1E1:

M8850_SF.27.MPSM16T1E1PPP[FR].a > dspppplnkcnt 10 0

MLPPP Link Number : 10

Interval Number : 0

Receive Packets : 2291753

Receive Bytes : 66480391

Receive Discard Bytes : 0

Receive MRU Errors : 0

Receive Miscellaneous Errors : 0

Receive FCS Error Packets : 0

Receive kbpsAIR : 1498

Send Packets : 433

Send Bytes : 32054

Send kbpsAIR : 0

In the following example, the user displays statistics for interval 0 on PPP link 10 on an MPSM-T3E3-155:

M8850_SF.10.MPSM155PPP[FR].a > dspppplnkcnt 10 0

MLPPP Link Number : 10

Interval Number : 0

Receive Packets : 2291753

Receive Bytes : 66480391

Receive Discard Bytes : 0

Receive MRU Errors : 0

Receive Miscellaneous Errors : 0

Receive FCS Error Packets : 0

Receive kbpsAIR : 1498

Send Packets : 433

Send Bytes : 32054

Send kbpsAIR : 0

Changed PXM Commands

This release adds a node configuration option that controls secure (SFTP and SSH) access to the PXM. This affects the following commands:

•cnfndparm

•dspndparms

cnfndparms—PXM45

Configure Node Parameters—PXM45

The cnfndparms command lets you configure a diverse set of node-level parameters.

Note Variations exist in the available parameters according to controller card and chassis. For the parameters on a PXM1E, see the next description of the cnfndparms command.

The parameters consist of an option number and a value or a yes/no choice. The configuration resides in nonvolatile RAM and thus survives a system reset or power cycle. Due to the wide range of options and the possible values assigned to these options, the sections that follow describe each option and later describe the values you can assign (a hexadecimal number, a yes or no entry, and so on).

To see the current configuration for these parameters, use the dspndparms command. For information on the alarms that might relate to the parameters, see the dspndalms and dspenvalms descriptions.

Maximum Card Resets

The first two options work together to prevent an endless loop of card resets. The first option specifies the number of seconds for counting resets. The second option is the number of resets.

•Option 1 lets you select the sliding window of time for counting the resets of the shelf management cards. The characteristics of the time period option are:

–The unit of measure is seconds.

–The number is a 16-bit decimal number with a range of 0-65535.

–A 0 means an infinite time period. The impact of an infinite time period is that only a specified count of resets can stop the resets.

–The default is 3600 seconds (1 hour).

•Option 2 lets you select the maximum number of resets of the shelf management card group for the configured time period. Its characteristics are:

–The number is an 8-bit decimal number with a range of 0-255. The meaning of a 0 for this parameter is an infinite number of resets—the resets can continue indefinitely.

–The default is three resets per time period.

Shutting Off Alarms for Absent Core Cards

This option lets you specify whether a redundant core card that is removed from the backplane causes an alarm. (The core cards are the PXMs and SRMs.) The option lets you turn off alarms until you reinstall the card.

Enable Expanded Memory for 250K Connections

This option lets you enable expanded memory on the PXM45 to support 250K connections. For you to enable expanded memory, a pair of PXM45/Bs or PXM45/Cs must reside in the system.

Caution This option cannot be disabled after it is enabled, even if you use the
clrallcnf command.

Required Power Supply Module Bitmap

Through a bitmap mechanism, this option lets you specify the locations of required power supplies in an AC-powered system. If any one of the required supplies is removed, an alarm results. (For related information on alarms, see the dspndalms and dspenvalms descriptions.) Additional supplies can also exist in the power supply tray, but removing one of the additional supplies does not cause an alarm.

An AC power supply tray can hold up to six power supplies. A supply belongs to one of two groups of slots in the power supply tray: A1-A3 or B1-B3. Within the bitmap, an 8-bit hexadecimal number identifies a required supply. The A side of the tray is represented by the least significant hex value. The B side of the tray is represented by the most significant hex value. The map is the sum of the hexadecimal numbers. For example, the bitmap for requiring A1 and B1 is:

0x01 + 0x10 = 0x11

Required Fan Trays

This option lets you specify the required fan trays. The application of this setting is for alarm generation only and does not specify cooling requirements. For example, if you specify that the chassis must have two fan trays but one tray is missing, an alarm is generated. You can turn off fan tray alarms by specifying that no fan trays are required (even though at least one is required for cooling). The value is an 8-bit hexadecimal number.

Note An Cisco MGX 8850 or Cisco MGX 8950 chassis requires two fan trays for cooling regardless of the number you specify for alarm purposes with the cnfndparms command.

•0x0 means no fan tray requirement. (The chassis must still have at least one fan tray for cooling.)

•0x01 refers to the bottom fan tray.

•0x02 refers to the top fan tray.

To require top and bottom fan trays, for example, enter a hexadecimal 3 for the option value:

0x01+0x02=0x03

Trap Manager Aging Timeout

This option lets you specify the number of hours that a trap manager can age before the switch deletes that trap manager's registration. This setting is node-level and thus applies to all trap managers registered on the switch. The default of 0 means that the trap managers on the switch do not age. The only applicable trap managers for this parameter are Cisco WAN Manager (CWM) workstations.

The application of aging is a situation where:

•The IP address of the network management stations are likely to change.

•The workstations themselves are likely to be moved.

Non-CWM users or managers of a stable network manager environment should leave the setting at zero.

Primary IP Interface for Network Management

This option lets you specify a primary IP interface type for discovery by CWM. The primary IP interface is the first choice for CWM to use for network management. The main purpose of this option is to let you change from the default of an ATM interface to a LAN interface for use by CWM. The choice of LAN as the primary lets you use LAN interfaces to build an IP connectivity infrastructure for CWM. CWM discovers this interface type while it performs an ILMI MIB-walk or during a topology table retrieval.

The topology table contains the primary and secondary management interface information for all nodes in the network. CWM obtains this table from one of the nodes so that it does not have to perform an ILMI MIB walk to each node in the network.

Secondary IP Interface for Network Management

This option enables CWM to learn the secondary IP interface by doing a MIB-walk and reading the PNNI topology state element table. If the primary IP interface becomes unreachable, CWM uses the secondary IP interface. If you do not enable the secondary IP interface, the PNNI topology state elements (PTSEs) do not flood the secondary IP address.

The topology table contains the primary and secondary management interface information for all nodes in the network. CWM obtains this table from one of the nodes so that it does not have to perform an ILMI MIB-walk to each node in the network.

Automatic Setting of Cell Bus Clock Speed for RPM

This option lets you enable the automatic setting of cell bus clock speeds for the Route Processor Module-Premium (RPM-PR). If you enable this feature, the switch automatically adjusts the cell bus clock as needed when you insert or remove an RPM-PR at a particular cell bus. If this feature is enabled, for example, and two RPM-PRs are plugged into a cell bus, the clock speed is 42 MHz. If you remove one RPM-PR, the clock drops to 21 MHz.

The cell bus clock rates must be correct for the RPM-PR to do traffic shaping. If clock setting is not automatic, you must adjust the clock speeds by using the cnfcbclk command when needed. To see whether automatic or manual clock setting is enabled, use the dspcbclk command.

If you turn on this feature and one or more service modules are running at 42 MHz, the clock for all such cards immediately becomes 21 MHz, regardless of the number of cards in the switch.

Caution Enable this feature before using two MPSM-8-155s, two RPM-PRs, or one of each of these cards on the same cell bus. For example, slots 3 and 4 are on the same cell bus, and slots 5 and 6 are on the same cell bus.

Inband Node-to-Node IP Connectivity

This option lets you enable or disable inband, node-to-node IP connectivity, so that you can Telnet from the CLI of one switch to the CLI of another switch.

After you Telnet, an SVC is set up between the local node and the remote node. (The SVC is the transmission medium for all IP traffic between two nodes, yet the SVC and Telnet are independent of each other; the Telnet is just one kind of traffic.) If you disable this feature after the SVC is created and then proceed to transfer more IP data between nodes, the transfer of IP data is successful. In fact, it works without disruption until the SVC is torn down. The SVC is torn down when no IP traffic traverses the SVC for 15 minutes.

To exit the CLI of the remote switch—to break the connection and terminate the Telnet session—enter the exit or bye command (see the "Example" section).

This parameter is enabled by default after you run the clrallcnf command. On the other hand, if you upgrade from a software release that does not have this parameter, the default state is disabled.

PXM Switchover on Back Card Mismatch

When enabled, this option causes a switchover of redundant PXMs if the incorrect, field-replaceable back card (FRU) is inserted. The existence of various models of the PXM45, variations in the PXM1Es, and two models of the user interface (UI) back card have led to the creation of an option that lets you specify that if the incorrect combination is detected, the redundant pair switches over. Table 13 lists supported and disallowed combinations. Yes indicates a supported combination; No indicates a mismatch.

Disabling the High-Priority LCN for Interprocess Communication

This option lets you disable the high-priority LCN so that the applications exchanges all messages on the low-priority LCN.

The switch reserves two logical connection numbers (LCNs) for interprocess communication (IPC)—in this instance, the communication between applications on different cards:

•One LCN carries low-priority messages

•The other LCN carries high-priority (urgent) messages.

By default, both priorities of LCN are available, and the cards select the priority for messages as needed.

Disabling Telnet Access

To disable Telnet access to this switch, type yes when prompted. This option lets you disable Telnet access to the switch so that only the Secure Shell (SSH) utility can be used to access the switch from either a workstation or another Cisco MGX 88xx or Cisco MGX 8950 switch. Telnet is an unsecured access method because its communication uses clear text. SSH ensures secure communication by providing unique encryption for each session.

Disabling Unsecured Access

By default, the switch permits unsecured access from Telnet and FTP clients, and secure access from SSH and SFTP clients. To disable unsecured access from Telnet and FTP clients, set the Unsecured Access to Node Disabled option to yes.

•yes to no has no affect on the Telnet Access To Node Disabled option.

Option Values

This command requires various number formats for the support of its parameters:

•Boolean yes/no

•An 8-bit decimal has the range 0-255.

•A 16-bit decimal number has the range 0-65535.

•A 32-bit decimal number has the range 0-4294962795.

•An 8-bit hexadecimal number has the range 0-0xff.

•A 16-bit hexadecimal number has the range 0-0xffff.

•A 32-bit hexadecimal number has the range 0-0xffffffff.

Each option description states the type of number involved and the actual range for that option. Alternatively, the description states whether the choice is yes to enable or no to disable.

Syntax

cnfndparms <option_number> <option_value>

Syntax Description for PXM45

option number

This number selects the option.

Range: 1-15

Option 1

Option 1 is the number of seconds that the controller counts resets of the shelf management cards. A 0 means an infinite time period. The impact of an infinite time period is that only a specified count of resets can stop the resets.

•Range: 0-65535 seconds

•Default is 3600 seconds (1 hour)

Option 2

Option 2 is the maximum number of resets of the shelf management card group. See Option 1 for the period in which resets are counted. The meaning of a 0 for this parameter is an infinite number of resets—the resets can continue regardless of how many resets occur.

•Range 0-255 resets

•Default: 3 resets

Option 3

This option lets you enable or disable core card redundancy. Enter yes to enable or no to disable alarms on a missing, redundant core card. The default is enable, which means an alarm appears in the absence of a redundant core card.

Option 4

This option lets you enable or disable expanded memory on the PXM45/B or PXM45/C to support 250K connections. Enter yes to enable or no to disable. The default is no.

Note You cannot disable this option after it is enabled, even if you use the clrallcnf command.

Option 5

This option lets you specify the locations of required power supplies in an AC-powered system. The number is 8-bit hexadecimal:

•0x0 (the default) means no specified power supply requirement related to this particular form of alarm generation (although the configuration must still meet the power requirements of the switch).

•0x01: PSU A1 is required.

•0x02: PSU A2 is required.

•0x04: PSU A3 is required.

•0x10: PSU B1 is required.

•0x20: PSU B2 is required.

•0x40: PSU B3 is required.

Option 6

This option lets you specify the location of one or more required fan trays. The number is 8-bit hexadecimal:

•0 for no specific fan try requirement

•0x01 for bottom fan tray required

•0x02 for top fan tray required

Option 7

This option lets you specify the number of hours that a trap manager can age before the switch deletes that trap manager's registration. This node-level setting applies to all registered trap managers. For details, see the "Trap Manager Aging Timeout" section.

Option 8

This option enables CWM to learn the primary IP interface by doing a MIB-walk and reading the PNNI topology state element table. Enter a number in the range 0-2:

•0: The ATM0 interface is the primary.

•1: No interface is used. This choice prevents ILMI node discovery.

•2: The lnPci0 interface is the primary.

Default: ATM

Option 9

This option enables CWM to learn the secondary IP interface by doing a MIB-walk and reading the PNNI topology state element table. Enter a number in the range 0-2:

•0: The ATM0 interface is the secondary.

•1: No interface is used as the secondary.

•2: The lnPci0 interface is the secondary.

•Default: lnPci0 (LAN)

Option 10

This option lets you enable the automatic setting of cell bus clock speed. In the current release, it applies to RPM-PR only. The choices are yes and no.

Default: yes

Option 11

This option lets you enable inband, node-to-node IP connectivity so you can Telnet between this CLI and other switches where this feature is enabled. Type yes to enable or no to disable.

Default: yes (enabled)

Option 12

Obsolete. Use dsprcons for Gang Card Status.

Option 13

This option enables automatic switch-over when a FRU back card mismatch occurs. Type a 1 to enable or a 0 to disable this feature. This option applies to the combinations of controller card models and the user interface (UI) back card. Refer to the section, "PXM Switchover on Back Card Mismatch," for information on the combinations.

Default: 0 (disabled).

Option 14

This option lets you disable the high-priority LCN for inter-process communication (IPC) between cards. Type yes or no:

•yes: the card-to-card, high-priority LCN is not used. This choice forces all IPC traffic between cards to share the same, low-priority LCN and prevents applications from sending urgent messages or critical data over a high-priority connection to applications on other cards.

•no: the card-to-card, high-priority LCN is used. This choice allows applications to choose the appropriate priority for carrying IPC traffic between cards. An application with a purpose for sending urgent or critical data selects the high priority LCN (if both cards support the high-priority LCN). Other messages take the low priority LCN as needed.

Default: No

Option 15

Type yes to disable Telnet access to this switch. Type no to enable Telnet access.

Default: no (Telnet access is enabled)

Option 16

Type yes to disable unsecured access to this switch, either Telnet or FTP. Changing this option from no to yes automatically changes Option 15 to yes. Changing from yes to no has no affect on Option 15.

Default: no (Unsecured access is enabled)

option value

The option value can be a decimal or hexadecimal number or a yes or no entry. The following shows the possible ranges or values for each type of numeric option.

•8-bit decimal: 0-255

•16-bit decimal: 0-65535

•32-bit decimal: 0-4294962795

•8-bit hexadecimal: 0-0xff

•16-bit hexadecimal: 0-0xffff

•32-bit hexadecimal: 0-0xffffffff

Related Commands

dspndparms, dspndalms, dspenvalms, cnfcbclk, dspcbclk

Attributes

Log: no

State: active

Privilege: SUPER_GP

Example

Specify 30 minutes (1800 seconds) for Card Reset Sliding Window. You can enter the option number and option value without prompting. The system subsequently uses the parameters and shows the result.

MGX8850.7.PXM.a > cnfndparms 1 1800

NODE CONFIGURATION OPTIONS

Opt# Value Type Description

---- ----- ---- -----------

1 1800 16bit Decimal SHM Card Reset Sliding Window (secs)

Enable automatic setting of cell bus clock speed. Type the cnfndparms command without parameters to see all of the options, and then enter 10 and y at the subsequent prompt. This card is a PXM45. Afterwards, see if it is enabled by using the dspcbclk command.

dspndparms

Display Node Parameters—PXM45, PXM1E

The dspndparms command displays the node parameters that were configured by use of the cnfndparms command. The node parameters in this case are a general set of diverse parameters. Refer to cnfndparms for a description of the parameters and their possible values.

Note The PXM45 has more node parameters than the PXM1E. For example, the PXM45 has expanded memory for 250K connections.

Syntax

dspndparms

Syntax Description

This command takes no parameters.

Related Commands

cnfndparms

Attributes

Log: no

State: active, standby

Privilege: ANYUSER

Example

Display the current node parameters on this Cisco MGX 8850 switch with a PXM1E card.

PXM1E_NY.7.PXM.a > dspndparms

PXM1E_NY System Rev: 05.03 Feb. 13, 2007 14:37:03 PST

MGX8850 Node Alarm: MAJOR

NODE CONFIGURATION OPTIONS

Opt# Value Type Description

---- ----- ---- -----------

1 3600 16bit Decimal SHM Card Reset Sliding Window (secs)

2 3 8bit Decimal SHM Max Card Resets Per Window (0 = infinite)

3 No Boolean Core Redundancy Enabled

4 0x0 8bit Hex Required Power Supply Module Bitmap

5 0x0 8bit Hex Required Fan Tray Unit Bitmap

6 0 8bit Decimal Trap Manager Aging timeout value(Hour(s))

7 atm0 8bit Decimal Primary IP interface for Netmgmt

8 lnPci0 8bit Decimal Secondary IP interface for Netmgmt

9 Yes Boolean Auto Setting of Cellbus Clock Rate Enabled

10 Yes Boolean Inband Node-to-Node IP Connectivity Enabled

11 0 8bit Decimal Obsolete. Use dsprcons for Gang Card Status

12 0 8bit Decimal Card Switchover on Backcard FRU mismatch

13 No Boolean Card-to-Card High Priority LCN Disabled

14 No Boolean Telnet Access To Node Disabled

15 No Boolean Insecure Access(Telnet / Ftp) To Node Disabl

Display the current node parameters on this Cisco MGX 8850 switch with a PXM45.

Changed AXSM-XG Commands

MGX Release 5.5.10 Limitations, Restrictions, and Notes

This section includes information about limitations, restrictions, and notes pertaining to MGX Release 5.5.10.

Upgrade Limitation

None.

BERT Limitation

If you configure the BERT with an excess information rate (EIR) value of 2 (for 1 in 10), any configuration changes or BERT failure that could cause BERT to go out of sync will cause the BERT state to remain out of sync until you stop and restart BERT.

MGX Chassis Bandwidth Limitations

The total bandwidth of all cards and configured ports in your MGX switch must not exceed the total switch capacity. If you install more cards or configure more ports than your switch can support, your switch may drop traffic. This section describes the bandwidth limits, card placement, and oversubscription options for narrowband cards. It also provides the solution for caveat CSCei02096.

Bandwidth Limits

A Cisco MGX 8850 (PXM45) chassis supports up to OC-12 aggregate bandwidth for narrowband cards, within the following limitations:

•Each pair of slots in the upper bay supports a total of OC-6 aggregate cell bus throughput.

•Each pair of slots in the lower bay supports a total of OC-6 aggregate cell bus throughput.

•Each half of the lower bay can support total OC-6 aggregate cell bus bandwidth.

•The left half of the switch can support a total of OC-9 aggregate cell bus throughput. This includes both the top and bottom bays, combined.

•The right half of the switch can support a total of OC-9 aggregate cell bus throughput. This includes both the top and bottom bays, combined.

Note These limits do not apply to broadband cards such as the AXSM, AXSME, AXSM-XG, RPM-XF, and VXSM. Broadband cards use a serial bus, rather than the cell bus.

Card Placement Guidelines

Placement of the MPSM-T3E3-155 is important because of the total card capacity. Other narrow band cards also use cell bus capacity, but they have smaller bandwidth requirements and place less load on the backplane.

To fully use the bandwidth of MPSM-T3E3-155 cards, install cards according to the following guidelines:

•Install MPSM-T3E3-155 cards so that they are balanced on the left side and right side of your switch (8 slots apart). For example, if you plan to install 2 active MPSM-T3E3-155 cards in your switch, and you place 1 MPSM-T3E3-155 card in slot 6, then place the second MPSM-T3E3-155 in slot 14.

•Install no more than 4 active MPSM-T3E3-155 cards in one Cisco MGX switch.

•Install broadband cards, such as RPM-XF and AXSM cards, between MPSM-T3E3-155 cards. These cards use a different backplane bus and do not affect the narrowband bandwidth.

Bandwidth Oversubscription

You can install more than the recommended number of cards under the following circumstances:

•Do not configure the full port rate available to each card installed in your switch.

•Use statistical multiplexing of traffic to support overbooking of cell bus traffic. Statistical multiplexing works better for a T3 port that is channelized down to DS1s than it does for a T3 port that uses its full T3 capacity.

If you do not have this information available when installing your switch, you must follow the general recommendations to provide adequate bandwidth margins.

PXM1E Switch Limitations

The following notes apply to PXM1E based switches—Cisco MGX 8850 (PXM1E) and Cisco MGX 8830:

•Y-red is not supported on the MCC electrical back card.

•For inter-card APS to work on the PXM1E-8-155, and one front card is missing or not available, both back cards must be present. A front card cannot drive the alternate trunk back card when its own local trunk back card is absent.

•MPLS controller is not supported on PXM1E.

•PXM1E clock source is supported by VISM-PR, CESM, and AUSM cell bus service module cards. CESM and AUSM can provide one clock source, either primary or secondary.

•Only SPVCs and SPVPs are supported on cell bus service modules. SVCs are not supported on CBSMs.

•No bandwidth CAC support exists on the cell bus service modules, except for the RPM card, which is checked against the OC-3 card rate. For example, for a given RPM, the bandwidth allocated to all connections might not exceed the OC-3 rate. Bandwidth CAC is supported on the PXM1E uplink port.

•The maximum bandwidth to be distributed among cell bus service modules is approximately an OC-10 rate while traffic on the network interfaces on PXM1E can achieve true OC-12 line rate.

•Traffic must be balanced between the cell bus controllers (CBC) to achieve the OC-10 rate. The traffic must be distributed equally at a rate of about OC-5 on the two CBCs.

The CBCs cannot load share to achieve OC-10 with one cell bus set at an OC-6 rate, and another cell bus set at an OC-4 rate. Traffic above the OC-6 rate is dropped. However, if only one CBC is used and the other CBC is not used, then the CBC can achieve an OC-10 rate.

On a Cisco MGX 8850, the CBCs are split between the left and right side of the chassis: CBC0 supports slots 1-6 and 17-22 and CBC1 supports slots 9-14 and 25-30. On a Cisco MGX 8830, CBC0 supports slots 3, 5, 10, and 12 and CBC1 supports slots 4, 6, 11, and 13. Balance traffic by evenly distributing cell-based cards on the left and right sides of the chassis.

PXM1E Hardware Limitations

PXM1E hardware limitations are as follows:

•For inter-card APS to work on the PXM1E-8-155 with one front card missing or unavailable, both back cards must be present. A front card cannot drive the alternate trunk back card when its own local trunk back card is absent.

•During hardware upgrade from PXM1E-4-155 to PXM1E-8-155, at the time when the inserted card types are different (one PXM1E-4-155 card set and one PXM1E- 8-155 card set), the standby trunk back card functionality is not available. Therefore, LED functionality is not available, and APS lines do not work on that back card. Modular optical transceiver (SFP-8-155) mismatches are not reported for that back card, and SFP-8-155 mismatches are not reported during hardware upgrades.

•Because the PXM1E-4-155 and PXM1E-8-155 back cards support LC and SC interfaces respectively, the following restriction applies when upgrading from PXM1E-4-155 to PXM1E-8-155 hardware:

After replacing the first PXM1E-4-155 card with the PXM1E-8-155 card set, update cabling for the PXM1E-8-155 interfaces with an LC-SC converter.

Similarly, after the second card set is replaced, perform the same update for the interfaces on the new card set. Otherwise, the upgrade is not graceful and becomes service affecting, until appropriate cables are installed.

•When MGX-8850-APS-CON is used, and one trunk back card is removed, screw the remaining back card in completely to ensure that the contacts are fully engaged.

•When MGX-8850-APS-CON is used, the Combo card and the PXM1E-4-155 card do not require a mini-backplane, but the PXM1E-8-155 does. Therefore, to support graceful upgrade to the PXM1E-8-155 card in the future, insert a mini-backplane with the PXM1E-4-155.

PXM1E Reserved Virtual Channel Identifiers

You cannot provision the following reserved VCIs:

•On a feeder trunk, VPI.VCI 3.8 is reserved for inband communication with the feeder shelf, and 3.31 is used for the feeder trunk Annex.G ILMI.

•VPI = 0 and VCI = 5 are used for SSCOP for UNI signaling ports. If the port is configured for non-signaling (univer = none), no VPI/VCI is reserved.

•VUNI uses configured VPI and VCI = 5 for SSCOP.

•EVUNI uses minimum VPI and VCI = 5 for SSCOP.

•NNI uses VPI = 0, VCI = 18 for PNNI RCC.

•VNNI uses configured VPI for the port and the VCI = 18 for PNNI RCC.

•EVNNI uses minimum VPI and the VCI = 18 for PNNI RCC.

•VPI = 0 and VCI = 16 are used for ILMI if ILMI is enabled. VUNI and VNNI uses configured VPI for the port and VCI = 16 for ILMI. Similarly, ILMI for EVNNI or EVUNI uses a minimum VPI and VCI = 16.

Multipoint enhances network efficiency because multiple streams of data can be replaced by a single transmission up to the multicast distribution point, typically an MGX with PXM45. Point-to-multipoint differs from broadcast because it replicates packets only to specific destination endpoints in the multicast distribution tree.

The Cisco MGX 8830 (PXM1E) and Cisco MGX 8850 (PXM1E) can be used in conjunction with an MGX (PXM45) in a network to support point-to-multipoint connections. The PXM45 hardware performs cell replication to multiple destination endpoints. The MGX with PXM1E functions as the originating node or as an intermediate node of a point-to-multipoint connection. If necessary, MGX with PXM1E can perform limited branching or cell replication to support multiple parties, or leaves, of a point-to-multipoint connection.

Enabling cell replication or branching of more than two leaves per root in the PXM1E node is not recommended for mission-critical point-to-multiple connections because of potential ATM cell drops. Cisco plans to enhance the PXM1E embedded hardware in the future to support cell replication for higher root/leaves ratio with minimal cell drops.

PXM1E Parity Errors

The PXM1E handles parity errors as follows:

•If the PXM1E card has a CBC CBH RAM parity error and all connections do not have traffic, then the PXM1E card fails to detect this parity error and does not switch over to the standby card. Also, all service module cards reset.

•The PXM1E standby card comes up even after a QE TS RAM parity error.

PXM1E Policing Accuracy

The PXM1E card has a policing accuracy limitation. The policing rate is defined as 50000000/PCR, so if the PCR is comparable to the OC-12 line rate (1412830), the policing rate parameter is a relative small number (50000000/1412830 = ~35.38996).

Because the PXM1E performs integer division, the decimal results are truncated and the policing parameter is not calculated accurately. Moreover, the policing rate parameter is stored as an exponent (5 bits) and mantissa (9 bits), which cannot represent a small number accurately. Therefore, a 100 percent accurate policing parameter cannot be configured for large PCR values.

To ensure that you obtain the rate that you have specified, the software configures policing at the next larger rate that the hardware supports. For example, if you program a connection with PCR = 1400000, the software programs the policing rate to be 1428571. For a worst-case scenario, if you configure a VBR2 connection with a PCR of 1400010 and the ingress user traffic is 1428570, there is no policing because the ATM policing rate is actually 1428571.

PXM45 and PXM1E System Limitations

The following limitations apply to PXM45 and PXM1E systems:

•Because of granularity limitations in the AXSM-E hardware, cell traffic does not reach the configured PCR rate when WFQ is enabled. For connections that have WFQ enabled, configure a PCR of 101 percent of the required rate. ABR has the same Qbin priority as UBR in the SCT tables. In this case ABR and UBR share excess bandwidth if WFQ is enabled.

•The percentage trunk utilization with overbooking is calculated using the following formula:

–(overbooked MaxCR - overbooked ACR)/overbooked MaxCR. This occurs if you are interoperating with SES from Release 3.0.x and later.

–ACR = MaxCR - (trunk utilization/overbooking factor).

–overbooked ACR = ACR/overbooking factor.

–overbooked MaxCR = MaxCR/overbooking factor.

•The overbooked ACR is calculated differently for MGX and SES.

–On MGX, the bandwidth for all current connections on the port are considered overbooked when calculating the trunk use.

–On the SES, the bandwidth for all current connections on the port are not considered overbooked when calculating the trunk use.

Therefore, the trunk utilization calculation is lower on the MGX than on the SES when there are existing connections on the port with an overbooking factor configured. This in turn yields a lower percentage trunk utilization on the MGX compared to the SES.

•The PXM45/A card is not supported in Release 5.0.00 and later.

•Disable complex node for physical nodes (the lowest level node) to decreases memory usage without decreasing functionality. Complex node should only be turned on for logical nodes.

•Simple Network Timing Protocol CWM MIB is not supported.

Maximum Threshold Accuracy

The PXM45 and PXM1E have a limitation with the accuracy of the maximum threshold. The Qbin threshold and VI rate are stored in the form of exponent and mantissa, and some accuracy is lost in expressing the real rate. In testing the thresholds, the lack of accuracy is compounded with both of the Qbin and VI rate (draining rate). Therefore, you cannot calculate an exact 100 percent correct discard rate.

To ensure that you obtain the rate that you have specified, the software configures Qbin depth at the next larger rate that the hardware supports. As a result, Int. Cell Gap (ICG) and Relative Service Delay (RSD) are truncated.

Clearing the Configuration on Redundant PXM45 and PXM1E Cards

These notes apply to redundant cards.

•Because of checks to prevent an inserted card from affecting the system, an additional step might be required when inserting two non native PXM45 (or PXM1E) cards in a shelf. Insert the first PXM45, use the clrallcnf command, and allow this to become active before inserting the second PXM45 (or PXM1E).

SPVC Interoperability Limitations

•Terminating single-ended SPVCs on MGX switch with legacy service modules is not supported.

•Origination of single-ended SPVCs, with slavepers flag, from legacy service modules (FRSM, CESM, and RPM) is not supported.

•CC (Continuity Check) is not available at the slave end of a single-ended SPVC.

•Reporting AIS detection to CWM is not available at the slave end of a single-ended SPVC.

•The tstdelay command is not available at the slave end of a single-ended SPVC for Cisco MGX 8850. For SES-PNNI, the command is available from the PXM even for the slave endpoint.

•The slave end of a single-ended SPVC is not visible to CWM.

•If single-ended SPVCs originate from MGX switches, they can only be configured from the CLI and not from CWM.

•Single-end provisioning is not supported for DAX connections as no value addition is seen for interoperability.

•SPVC statistics are not available for the slave endpoint of a single-ended SPVC because this endpoint is nonpersistent.

•When the persistent slave endpoint of an existing SPVC connection is deleted and the master endpoint remains, the connection might get established as a single-ended SPVC connection. In this case, CWM shows the connection as Incomplete.

•Override of SVC connections on a VPI because of an incoming SPVP request for that VPI is not supported. Only the following override options are supported:

–spvcoverridesvc

–spvcoverridesvp

–spvpoverridesvp

Service Card Limitations

This section describes service card limitations.

AXSM-16-155-XG with MCC Back Card Limitations

You might experience the following scenario when card to card APS is configured on one card but not the other:

The Protection Line Status in dspapslns or dspapsln shows OK if the other side has added the card redundancy and activated the line but not the APS. If the back cards are SFP back cards, the Protection Line Status is in SF in the same setup.

From the CLI window on the side of APS added, the only way to find out if the remote APS has been added is through the Receive chanfield and modefield in dspapsln. The following display shows the APS status during configuration:

For GR253:

Receive k2 chanfield—Null Channel

Receive k2 modefield—Undefined

After adding remote APS (with MCC):

Receive k2 chanfield—Null Channel

Receive k2 modefield—UNI1+1 or Bi depending on mode

For ITU (or AnnexA):

Receive k2 chanfield—Null Channel

Receive k2 modefield—Undefined

After adding remote APS:

Receive k2 chanfield—Null Channel

Receive k2 modefield—Undefined

For AnnexB:

Receive k2 chanfield—Null Channel

Receive k2 modefield—Undefined

After adding remote APS:

Receive k2 chanfield—Working Section 1 or 2

Receive k2 modefield—Undefined

AXSM-32-T1E1-E and PXM1E-16-T1E1 Card Limitations

The following notes apply to the AXSM-32-T1E1-E and PXM1E-16-T1E1 cards:

•IMA version fall back is part of IMA group operation. If a group is configured with Version 1.1 and it is connected to a far end group which is configured with Version 1.0, this group falls back to Version 1.0.

•The IMA link Loss of IMA Frame (LIF) and Link Out of Delay Synchronization (LODS) defect integration times are configurable.

•ATM layer configuration for line and IMA ports takes an additional parameter, AIS enable. It is enabled by default.

•In T1 mode, payload scrambling is disabled by default and in E1 mode it is enabled by default on all lines and IMA groups.

•Only 10 SVC calls per second is guaranteed.

•FDL support for Loopback code detection is not supported.

•Far End Line Performance counters are supported only for E1. They are not supported for the T1 interface.

•HMM support is not available for the IMA and the Framer devices. When a switchover occurs, it can take up to 3.5 seconds for the IMA groups to recover. Data is lost until the groups recover.

•IMA Autorestart (persistent RX IMA ID) feature is supported.

•IMA groups cannot have links from upper and lower bays together.

•ITC clocking mode on IMA is not supported.

•One-way transmission delay of more than 500 ms on the T1/E1 IMA links is not supported.

•There is 5 ms fluctuation on IMA delay tolerance.

•While the IMA group accumulated delay is being removed with clrimadelay, the following applies:

–Any changes to this IMA group configuration are temporarily blocked.

–Any changes in the FE IMA links in this group can cause the NE IMA group to restart.

•The VC and COSB thresholds are updated when the links are added/deleted from the IMA groups.

•The thresholds for the connections added when there are N links in the group can differ from connections added when there are (N+1) links in the IMA group.

•BERT is only supported on the T1 interfaces. BERT is not supported on E1 interfaces.

•The port number in the pnport (shelf.slot:subslot.port:subport) could be a random number. Do not interpret this number as line or IMA group number. Refer to caveat CSCdy08500.

•PNNI requires SCR = 453 cells per second and PCR = 969 cells per second for the control connection.

•SSCOP requires of SCR = 126 cells per second and PCR = 2000 cells per second.

AXSM-E Card OAM Limitations

The following notes apply to AXSM-E OAM cells:

•Any connection can receive E2E/OAM loopback cells up to the line rate, as long as the policing policy permits it.

•The AXSM-E card can receive up to 1,500 segment OAM loopback cells per second for all connections operating in the normal mode (not loopback), assuming an even flow rate. Any excessive segment OAM loopback cells are dropped.

For example, if only one connection exists, that connection can receive 1,500 segment OAM loopback cells per second. If 2,000 connections exist on an AXSM-E card, and each connection passes one segment OAM loopback cell per second, then only 1,500 of the connections can receive loopback cells at any given second. The additional 500 loop back cells are not received for that second.

General AXSM Card Limitations

If ER stamping is used, the rate interval does not provide sufficient accuracy to be completely effective. As a result, when an AXSM card has a PNNI link that is congested with mixed CBR/ABR traffic, cells are dropped. This condition only occurs when ER stamping is enabled and CI is disabled on an AXSM PNNI link where CBR/ABR traffic causes congestion on the link.

Use the CI/EFCI mechanism for rate feedback rather than the ER stamping mechanism, especially if CBR/ABR traffic is expected.

AXSM-XG Signal Level Limitation

The IR/LR/XLR SFP modules need a 10 db attenuator when connected with short cables. Otherwise, the signal overloads the receiver.

ATM Multicast Limitation

Configure an Cisco MGX 8950 with ATM multicast as follows:

•Cisco MGX 8950 system loaded with AXSM/Bs without AXSM-XG cards in the system.

•Cisco MGX 8950 system loaded with all AXSM-XG based cards without AXSM/Bs in the system.

A Cisco MGX 8950 system with a mix of AXSM-XG and AXSM/B cards is not recommended for the ATM multicast application because of limitations in the backplane serial buses. The workaround for Cisco MGX 8950 systems that must have a mix of AXSM-XG and AXSM/B cards is to configure the PNNI node as branching restricted.

cnfpnni -node 1 -branchingRestricted on.

Priority Bumping Limitation

When you enable priority bumping on the node, you cannot change the booking factor for AXSM signaling ports. You can still change the booking factor for non-signaling ports.

AXSM Card APS Limitations

Thee APS feature has the following limitations:

•For AXSM APS, the back card of the active card must be present for correct APS operation.

•AXSM front cards need the corresponding back card for correct APS operation. The AXSM cards do not support cross back card removal—the upper back card of one AXSM and lower back card of another AXSM.

•If you remove the upper back card of the active front AXSM, it triggers an active card switch. At this point the APS is still operational. However, if the lower back card of the current active AXSM is removed, it does not trigger switching because the standby card is missing the back card.

•Port LED lights on AXSM-E, AXSM-XG and PXM1E front cards indicate the receive status of physical line connected to it only when the card is in the active state. For a standby AXSM-E, AXSM-XG, and PXM1E card, the LEDs always remains green when the lines are in LOS irrespective of which lines are active.

MPSM Card Limitations

The MPSM cards have the following limitations:

•The MPSM-T3E3-155 card does not support the LMI Autosense feature.

•The MPSM-8T1-FRM and MPSM-8E1-FRM cards do not support the LMI Autosense feature.

•If a combination of RPM-PR and MPSM-T3E3-155 cards are being installed in slots served by the same cell bus, then enable Option 10 of cnfndparms (auto clock rate setting) before installing the MPSM-T3E3-155 and RPM-PR cards. This note applies when two RPM-PR cards or two MPSM-T3E3-155 cards (or one RPM-PR and one MPSM-T3E3-155 card) are inserted into slots under the same cell bus master, for example, slots 5 and 6 or 3 and 4.

•The MPSM cards are cell bus based cards, and they have limitations that suggest only a few of these cards could be used in a chassis when running at full port rate.

In reality, the full port rate available is rarely used. Statistical multiplexing of traffic across many ports can allow overbooking of the cell bus capacity just as it allows overbooking of trunk capacity. Estimates on how much overbooking is practical without dropping cells relies on the network's characteristics, such as the mix of service types, port speeds, and offered traffic loads as a percentage of port speed or as generated cell rates. Work with your Cisco Customer Engineering representative to help you characterize the quantity of MPSM cards suitable for your network.

•If you order MPSM cards with systems, the MPSM licenses can be shipped on the PXM card. For more information about MPSM licensing, see the Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.5.10.

MPSM-16-T1E1 Card PPP Limitation

On the RPM-XF, Rated Priority Queue is not supported; SAR based QoS is enabled instead. The traffic on priority queue can exceed the limit even if the class-based weighted fair (CBWF) queues are relatively free. RPM-XF supports absolute priority only, where the upper limit on the traffic is layered using the policing command.

CBSM Card Limitations

Cell Bus Service Modules (CBSM), formerly known as narrowband service modules, have the following limitations:

•When you enter the switchredcd command at the same time as a PXM switchover occurs, either through the switchcc/resetcd command at the PXM or because of a failure, the switchover can fail.

Conditions: switchredcd is entered at the PXM command line to perform CBSM Switchover, but the PXM switches over (manual or automatic) before the service module switchover is complete.

Symptom: Service module did not switch over after switchredcd.

If the PXM switches over before the CBSM switchover completes, the following can occur:

–The switchover might not be complete and the standby card is in an indeterminate state. The dspcd command from PXM still shows it as 'standby' and later switchover (because of active service module removal or reset) fails, causing loss of traffic. The switchredcd command also fails.

–The switchredcd from PXM again causes the failure because the standby service module is not able to allocate memory.

Workaround: Reset the standby service module card.

•Each CBSM has the following maximum number of connections:

–FRSM-8 = 1,000

–FRSM-2CT3 = 4,000

–FRSM-2T3 = 2,000

–FRSM-2E3 = 2,000

–CESM-8 = 248

IGX Feeder Limitation

After adding an IGX as a feeder to a SES/BPX or MGX node, the IGX has a default node number that might not be unique within the network. If the number is not unique, modify it to a unique node number by entering rnmnd <x>, where x is unique with respect to all other AutoRoute nodes. To find the other node numbers, enter dspnds +n. Failure to assign a unique number could cause the CWM Databroker to incorrectly form a hybrid connection database. The CWM interface might show the connection as incomplete.

Clock Source Limitations

•The FRSM card does not support clock source configuration. Attempts to configure the clock source are not recorded in the database.

•When resetcd is invoked, the primary and secondary (if configured) clock sources are recommitted. Recommitted means that the primary and secondary get requalified. The node temporarily uses the internal oscillator until the clock is requalified, and then locks onto the primary clock source again.

Clearing Card Configuration Notes

The clear service module configuration feature has the following behavior:

•Do not execute clrsmcnf on more than one card at a time.

•If a controller card switchover occurs before the clear service module configuration operation is complete, the clrsmcnf command must be re-entered to ensure that the configuration is completely cleared and to avoid incomplete cleanup.

•The clrsmcnf command might result in a discrepancy in the PNNI configuration. For example, some connections might be in the mismatch state.

•If the clrsmcnf command is entered with the <all> option to clear the software version for the slot as well, then cell bus service modules enter the boot/empty state and broadband service modules (for example, AXSM or MPSM-155-T3E3) enter the fail/active state.

•After entering the clrsmcnf command, the card in the specified slot is not usable until the operation has successfully completed.

PNNI Limitations

This section describes limitations to PNNI links and routing.

Logical Link Limits

The number of logical links in the higher levels of the PNNI hierarchy is limited to 30 per level when the complex node configuration is enabled. The limit is essential to reduce the processing time for finding the bypasses between the logical links. A significant change in bandwidth in one of the links within the peer group triggers the bypass calculation. The bypasses are usually found from one logical link to another.

If there are n logical links, the calculation involves the finding n*n bypasses. If the number of logical links n is large, calculating the bypasses requires significant processing resources. The number of logical links can be controlled by configuring the appropriate number of aggregation tokens for the outside links for that peer group.

Preferred Route Limitations

Preferred routes have the following limitations:

•Preferred routes are not supported for connections with endpoints on the RPM-PR.

•Upgrading from any Release 3.0.x is nongraceful. During the upgrade, the preferred route identifier information for each connection is lost, and the preferred route identifier must be reprovisioned on the service module cards.

Also, the preferred route table at the PXM controller is lost. Connections that have already been routed with preferred routing remain, and no alarms for these connections occur. If a node in the PNNI network is removed by physical decommissioning and if any nodes in the network had preferred routes that contained the removed node as one of the hops, you must manually delete and modify the preferred routes.

•When a connection is routed on a route other than its preferred route and if the preferred route becomes available, the connection is not automatically routed back to its preferred route. You must deroute and reroute using configuration commands (optrte, rrtcon, dncon/upcon, and so on). QoS precedence over the preferred route does not apply to multipeer group networks (CSCdz40310).

•A preferred route configured with a higher node ID cannot be blocked (CSCdz41145, CSCdz49001). Because of differences in physical port numbering, non-MGX nodes can only be the terminating nodes in a preferred route.

•Preferred route status is supported in Release 5.0.00 and later. After an upgrade, manually reconfigure using commands like cnfcon. This step is necessary one time after the upgrade, and does not need to be repeated on subsequent upgrades.

Priority Route Limitations

Priority routing has the following limitations:

•Prioritized reroute of SPVCs is not guaranteed if the SPVCs originate on a signaling port. SPVCs might get routed out of order. In-order routing of SPVCs is guaranteed on non-signaling ports only.

•The RPM does not support configuration of routing priority. The PXM assigns a priority of 8 to all RPM-mastered SPVCs.

•The addcon command on SES does not support routing priority; all added SPVCs are assigned a routing priority of 8. Use the cnfcon command to change the routing priority of the SPVCs.

•Changing the routing priority for DAX connections does not change the priority of the associated SVCs. The SPVCs are not derouted and rerouted if only the endpoint parameters are changed, and routing priority is an end-point parameter. Also, because DAX connections are never derouted even when the UNI port stops responding and the rrtcon command does not support DAX connections, the routing priority change never gets reflected. The only way to reflect this change is to enter a dncon and then upcon. Because DAX connections are never derouted, the effect of this limitation is void.

•Priority routing operates in a best effort manner for the following reasons:

–Two in-order releases can still arrive out of order at the master node if they travel along two different paths.

–Under congestion, releases can be transmitted out-of-order. This is because releases of other calls must not be held up if you are not able to send releases on one of the congested interfaces. The calls that were not released could be higher priority calls.

•Lower priority SPVCs can be routed ahead of higher priority SPVCs. This can occur after several failed attempts to route higher priority SPVCs. To prevent starvation of lower priority SPVCs after these failures, the software starts to route lower priority SPVCs and postpones higher priority SPVCs routing.

Persistent Topology Limitations

The persistent topology feature has the following limitations:

•In a mixed network of pre-Release 4.0.00 and 4.0.00 or later nodes, only the node name and the node ID are shown for a pre-Release 4.0.00 node in the topology database. This is because the feature is not present in pre-Release 4.0.00 nodes.

•If a peer group is made up of physical nodes with pre-Release 4.0.00 logical nodes, the information for the logical node is stored in the topology database. This is because there is no way to distinguish between physical nodes and pre-Release 4.0.00 logical nodes. Logical nodes with Release 4.0.00 or later software release are not stored in the topology database.

•To delete a node information entry from the topology database:

a. Remove the node from the network, either by disconnecting the cables or by downing all the links between that node and the network. Wait for 1 hour.

b. Delete that node from the topology database. Perform this step because even if a node is removed from the topology database of all nodes in the peer group, its PTSEs remain stored in the other nodes until they are flushed from those nodes. This happens within 1 hour, but it is configurable as a PNNI timer value. If the node is deleted from the topology database within 1 hour, and the node performs a switchcc/reboot, then it is possible that the node information for the deleted node is added back into the topology database.

•When the node ID of a node is changed, the old node ID is added back into the topology database as a new node entry. In addition, the old node ID still is stored in the topology database of all the other nodes in the peer group. To delete this entry, wait for an hour so that the PTSEs with the old node ID is flushed from the database of all the nodes in the peer group. Then, delete the information of the old node ID from the topology database.

•Some gateway nodes are not in sync in a peer group. This could occur in many situations. For example, a gateway node is added in a peer group, then a node is deleted from the PG, and another gateway node is configured, then the information for the deleted node does not appear in the second gateway node. Another example is that a node is deleted from one gateway node, but not in another gateway node.

When deleting a node from the peer group, you must delete the node information from all of the nodes in that peer group including the non-gateway-node nodes. Otherwise, the node information for the deleted node remains in the non-gateway-node nodes. This could cause inconsistencies later if this node is configured to be a gateway node.

Fault Isolation and Trace Limitations

This section describes fault isolation and trace limitations.

Serial Bus Path Fault Isolation Limitation

The Serial Bus Path Fault Isolation feature isolates errors on local cards only. However, when a common error occurs on the switching fabric card, this feature does not resolve the error. As a result, a problem on the PXM card or the XM-60 is reported by all cards that detect the symptoms of this problem.

Cell Bus Path Fault Isolation and Recovery Limitations

Cell bus path fault isolation has the following limitations:

•The isolation procedures can isolate the cell bus path in the serial bus service modules (for example, AXSM, AXSM/B, AXSM-E) and all communication with the standby controller card and the cell bus service modules (for example, FRSM, CESM). These procedures cannot isolate cell bus path failures involving the ATMizer SAR, which is used for all intercard communication except polling, between the active controller card and the serial bus based service modules.

•The isolation procedures can isolate the cell bus path failures to the active controller card only. This isolates the active controller card faults for the intercard communication over the cell bus from the active controller card to the service modules and the standby controller card. It does not isolate the fault if the active controller card fails to communicate with some cards and successfully communicates with the rest on the cell bus.

•At least two cards (two service modules or one service module and one standby PXM) must exist to isolate cell bus path failures to the active controller card.

•Only failures that are detected by periodic polling trigger the isolation procedures. Failures reported from other sources in the system about a service module or the standby controller card, due to the cell bus path failures, do not initiate the isolation procedures. Such failures reset the card for which the failure is reported, even while the active controller card is in the process of isolating the cell bus path failures triggered by the polling failures.

•No separate trap or alarm is generated for the active controller card cell bus path when the fault is isolated to the active controller card. Use the event logs to investigate events triggered by the card reset and switchover traps.

CLI Access Level Notes

Configuration of CLI access levels has the following limitations:

•Not all CLI command access levels can be changed and a command cannot be changed to CISCO_GP group access level.

•Only the switch software can generate the access level binary file. This file has an authentication signature which must be validated before the file can be used. Any manual changes to the file make the file void.

•If the binary file becomes corrupted, then the command access levels revert back to the default values during the card bring-up. To recover, repeat the installation process or retain a copy of the binary file and do cnfcli accesslevel install on that service module.

•Command names are verified, but an invalid command name might be parsed and be added to the binary file. However, this invalid name is ignored later.

•If replication to standby failed, the installation process failed.

•The cnfcli accesslevel defaultcommandrestores all command access levels to default for the service module on which the command is executed. This command does not remove the binary file, so this change is not persistent. If the command is executed on the active card of a redundancy pair, the standby card is not affected. When a card is reset and the binary file exists, the card is configured from the binary file when it is brought up.

Disk Space Maintenance Notes

The firmware does not audit the disk space usage and remove unused files, so you must manually manage the disk space in C: and E: drives.

Manually delete unused saved configuration files, core files, and firmware files and the configuration files of the MGX-RPM-PR-256/512 and MGX-RPM-XF-512 cards. This avoids a shortage of disk space for storing event logs.

To remove files from the active controller card:

Step 1 Change to the directory that needs grooming.

CLI: cd <directory_name>

Step 2 List the directory to identify old files that can be removed and available disk space.

CLI: ll

Step 3 Remove any old files (you may also use wild cards in the filename).

CLI: rm <complete_filename>

Step 4 List the directory to see if the file has been removed and disk space is available.

CLI: ll

Non-native Controller Front Card and PXM-HD Card Notes

The following notes pertain to non-native front card controllers and the PXM-HD card:

•When the front controller cards or the PXM-HD back cards are swapped within the same system, the system performs a non-native card check. As a result, the controller card that attempts to come up as Active/Active might get reset two times.

•When a non-native PXM1E front card or a PXM-HD card is inserted into the standby controller slot, after the standby controller front card becomes Active/Standby, the active controller front card copies its hard disk content over to the standby controller card. The active controller front card does not automatically remove hard disk content from the active or standby controller card.

•The system keeps only the two most recent copies of the saved system configuration in the C:/CNF directory. You can use FTP to transfer all of the saved configuration files in C:/CNF to a local server for future reference. All files under C:/CNF are not replicated to the standby controller card under any circumstances.

Other Limitations and Restrictions

Other limitations and restrictions are as follows:

•When configuring virtual interfaces (for example, VUNI, VNNI, EVUNI, EVNNI), the physical interface must all be the same ATM header type, either UNI or NNI. The signaling that is applied to a virtual port is independent of the actual virtual port ATM header. The only limit is that the VPI value must be within the UNI ATM header range (see CSCdz33652).

•If you clear the channel counters using the clrchancnt command while you are monitoring the channel counts using the dspchancnt command, the counters return incorrect values. To display correct data, enter the dspchancnt command again.

•The clrsmcnf command does not work for redundant service modules.

•The clrsmcnf does not work while an upgrade is in progress.

•If RPM-PR or RPM-XF are configured as Label Switch Controllers (LSC), execution of the clrsmcnf command on those LSC slots is rejected.

•Configuration information is not synchronized between PXMs during upgrades. You must reboot the standby PXM after it enters a stable state to synchronize changes made during the upgrade.

•Release 3.0.00 or later with PXM45/B supports up to 250,000 connections.

•The BPX does not support NCDP.

Installation and Upgrade Procedures

This section defines the supported upgrade paths and the associated installation and upgrade procedures.

For information on the following installation and upgrade procedures, refer to the Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.5.10.

Upgrade Information

The upgrade appendix in the Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.5.10 contains the following procedures:

•Graceful PXM1E and PXM45 Boot Upgrades

•Nongraceful PXM1E and PXM45 Boot Upgrades

•Graceful PXM1E and PXM45 Runtime Software Upgrades

•Nongraceful PXM1E and PXM45 Runtime Software Upgrades

•Graceful Service Module Boot Upgrades

•Nongraceful Service Module Boot Upgrades

•Graceful Service Module Runtime Software Upgrades

•Nongraceful Service Module Runtime Software Upgrades

•Graceful RPM-PR and RPM-XF Boot Software Upgrades

•Graceful RPM-PR and RPM-XF Runtime Software Upgrades

•Nongraceful RPM-PR and RPM-XF Boot Software Upgrades

•Nongraceful RPM-PR and RPM-XF Runtime Software Upgrades

•Upgrading an AXSM/A, AXSM/B, or AXSM-E to an AXSM-XG

Upgrading AXSM-XG Cards

The following notes apply to AXSM-XG card upgrades:

•Before you install AXSM-XG cards, use Table 15 to verify that the node is running a compatible software release.

Table 15 AXSM Card Compatible Software Releases

Card

Software Release When First Supported

AXSM-1-9953-XG

Release 4.0.00

AXSM-4-2488-XG

Release 4.0.00

AXSM-16-155-XG

Release 5.0.00

AXSM-8-622-XG

Release 5.2.00

Note Do not attempt to downgrade the AXSM-XG cards to releases earlier than supported.

•When configuring virtual interfaces (for example, VUNI, VNNI, EVUNI, or EVNNI), the physical interface must be of all one ATM header type, either UNI or NNI. The signaling that is applied to a virtual port is independent of the virtual port ATM header. The only limit is that the VPI value must be within the UNI ATM header limitations.

For information about graceful upgrade of AXSM-XG cards, see the Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.5.10.

Upgrading the VISM-PR Image

If you upgrade the VISM-PR image to Release 3.2.1x or later, and upgrade the PXM1E or PXM45 image from Release 4.x or earlier to Release 5.x, do so in this order:

1. Upgrade the VISM-PR cards.

2. Upgrade the PXM1E or PXM45 cards in the same node.

Do not configure the new VISM features until you have fully upgraded the network. After you upgrade your network to PXM1E or PXM45 Release 5.x or later and VISM-PR to Release 3.2.1x or later, apply the standard upgrade process.

Maintenance Information

The upgrade appendix in the Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.5.10 contains the following procedures:

•Replacing PXM1E-4-155 cards and with PXM1E-8-155 Cards

•Replacing PXM45/A or PXM45/B Cards with PXM45/C Cards.

Online Insertion or Removal of the MGX-RPM-1FE-CP Back Card

Online insertion or removal (OIR) of the MGX-RPM-1FE-CP back card for the RPM-PR card requires the following RPM-PR commands:

Open Caveats

Headline: IMA group goes down when vfb/restart/switching is done on an MPSM16T1E1 card.

Symptom: IMA group goes down when version fallback is disabled on MPSM16T1E1.

Workaround: Always keep the version fallback enabled on the card. Even if you do not require a version fall back to happen, still keep the version fall back parameter enabled. By default, this parameter is enabled at group level.