1.2.22 Release Notes for MGX 8230, MGX 8250, and MGX 8850 (PXM1) [Cisco MGX 8800 Series Switches]

Table Of Contents

Release Notes for Cisco MGX 8230, MGX 8250, and MGX 8850 (PXM1), Software Version 1.2.22

Contents

About These Release Notes

Features Introduced in Release 1.2.22

Features Introduced in Release 1.2.21

LMI AutoSense

addport

xcnfport

cnfport

dspport

MIB Changes

Features Not Supported in This Release

MGX 8220 Hardware That Has Been Superseded by MGX 8850-Specific Hardware

Service Module Redundancy Support

Network Management Features

Port/Connection Limits

SNMP MIB

Notes and Cautions

New Boot Image for FRSM-HS2, FRSM-2CT3 and FRSM-2T3E3 Cards

Using the restoresmcnf command

Loopback Plug on a HSSI:DTE Interface

UPC Connection Parameters

ForeSight and Standard ABR Coexistence Guidelines

RM Cell Generation

Reaction to Feedback Messages - Rate Up

Reaction to feedback messages - Rate Down

Fast-Down

Guidelines

Node Related

Connection Management Related

Documentation Corrections

New and Changed Commands in the 1.2.x Baseline

Limitations

CWM Recognition of RPM-PR and MGX-RPM-128M/B Back Cards

clrsmcnf

Problems after Power Cycle

Anomalies Fixed in Release 1.2.22

Anomalies Fixed in Release 1.2.21

Known Anomalies for Platform Software Release 1.2.22 and Service Module Firmware

Compatibility Notes

MGX 8230, MGX 8250, and MGX 8850 (PXM1) Software Certification with Other Products

Boot File Names and Sizes

MGX 8250 and MGX 8850 (PXM1) Firmware Compatibility

MGX 8230 Firmware Compatibility

Comparison Matrix

RPM Compatibility Matrix

MGX 8850 (PXM1), MGX 8250, and MGX 8230 Release 1.2.22 Hardware

Special Installation and Upgrade Requirements

Special Instructions for Networks Containing FRSM-2-CT3

Executing the Script

Script Functionality

Upgrade Procedure for Non-Redundant PXM

Upgrade Procedure for Redundant PXMs

Instructions to Abort PXM Upgrade

Aborting an Upgrade from Release 1.1.3x and Above

Aborting an Upgrade from Release 1.1.2x

Service Module Boot/Firmware Download Procedure

Manual Configuration of Chassis Identification

MGX as a Standalone Node

Chassis Identification During a Firmware Upgrade

Interoperability of Service Module on MGX 8220 and MGX 8250 Switches

Service Module Upgrades

Historical Information from the 1.2.x Baseline

Features Introduced in Release 1.2.20

AUSM CAC Based on SCR in VBR

Features Introduced in Release 1.2.13

Additional PXM1 Stats and NBSM Stats for AUSM and FRSM

Command to Terminate a Telnet Session

Features Introduced in Release 1.2.11

RPM Automatic Cellbus Double Clocking

Enhanced Alarm Filtering

Features Introduced in Release 1.2.10

AUSM-8T1E1 Egress Channel Counters

PXM-UI-S3 Secondary BITS Clocking

VISM-PR Front Cards

Features Introduced in Release 1.2.02

Configuring the Cellbus Clock (CBC) Rate

Features Introduced in Release 1.2.01

Standard ABR on FRSM-VHS Modules

APS Support on SRM-E

Features Introduced in Release 1.2.00

FRSM-HS2/B

SRM-E

ITU APS Annex-A, All Configurations Supported on PXM1

CESM 8T1 Model B

PXM-UI-S3

Problems Fixed in Release 1.2.20

Problems Fixed in Release 1.2.13

Problems Fixed in Release 1.2.11

Problems Fixed in Release 1.2.10

Problems Fixed in Release 1.2.02

Problems Fixed in Release 1.2.01

Problems Fixed in Release 1.2.00

Related Documentation

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Web Site

Cisco TAC Escalation Center

Release Notes for Cisco MGX 8230, MGX 8250, and MGX 8850 (PXM1), Software Version 1.2.22

Contents

About These Release Notes

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription.

Note that for Release 1.2.22, the user documentation (command reference, overview, and installation and configuration guides) were not updated. Use the existing documents in addition to this release note.

Product documentation for MGX 8850 (PXM1) is available at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8850/index.htm

Product documentation for MGX 8250 is available at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8250/index.htm

Product documentation for MGX 8230 is available at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8230/index.htm

Product documentation for VISM is available at the following URLs:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8850/

Product documentation for RPM is available at the following URLs:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8850/rpm/index.htm
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8250/rpm/index.htm
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8230/rpm/index.htm

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.

Features Introduced in Release 1.2.22

This is a maintenance release that includes bug fixes only. There are no new features introduced with this release

Release 1.2.22 supports all features introduced in prior releases. (See the "Features Not Supported in This Release" section and the "Historical Information from the 1.2.x Baseline" section.)

Features Introduced in Release 1.2.21

Release 1.2.21 supports all features introduced in prior releases. (See "Historical Information from the 1.2.x Baseline" section.)

LMI AutoSense

The LMI AutoSense feature on the Frame Relay Cards on MGX switches enables a frame relay port to detect the LMI type supported by the frame relay CPE (customer premise equipment). This autosensing feature avoids the need to configure the LMI type on each frame relay port.on the FRSM-8T1/E1 and FRSM-VHS(2CT3, 2T3, 2E3, 2HS2, 2HS2B) cards on the PXM platform.

The LMI AutoSense feature is supported for Frame Relay and FUNI port types. It is not applicable for Frame Forwarding port types. The detected LMI types will be of the following UNI types:

•AnnexD-UNI

•AnnexA-UNI

•StrataLMI

The LMI AutoSense feature is not supported on NNI interfaces.

The LMI AutoSense feature is configurable at a per port level.

A new MIB variable portLmiSigConfMethod has been added to the existing frPortCnfSigLMIGrpTable MIB table.

The addport, cnfport, xcnfport and dspport CLI commands have been modified to configure/display the new portLmiSigConfMethod MIB variable.

addport

One more parameter lmi_autosense will be added to the addport CLI, which can be optionally specified by the user while adding the port. By default the value will be set to Manual(1).

If the user wants to configure the port for LMI AutoSense, the user needs to set the lmi_autosense parameter value to AutoSense(2) while adding the port using addport.

The addport command syntax for the cards will thus be modified to as shown below

FRSM-8P and FRSM-2CT3.

Syntax:

addport "port_num line_num ds0_speed begin_slot num_slot port_type [lmi_autosense]"

where lmi_autosense can be configured for either mode Manual(1) or AutoSense(2)

FRSM-2T3, FRSM-2E3, FRSM-HS2, FRSM-HS2B.

Syntax:

addport "port_num line_num port_type [lmi_autosense]"

xcnfport

One more parameter "-lmias" has been added to the xcnfport CLI, which can be specified while either adding the port or modifying the port using xcnfport. By default the value is set to Manual(1).

To configure the port for LMI AutoSense set the "-lmias" parameter value to AutoSense(2) while addding/modifying the port using xcnfport. At the same time, set the port signalling protocol type to noSignalling using the "-sig" option.

The xcnfport command syntax for the cards has been modified as shown below.

Syntax:

xcnfport "-pt <PortNum> -ln <PortLineNum> -en <PortEnable> -rat <PortEqueueServiceRatio> -flag <PortFlagsBetweenFrames> -asy <AsynchMsg> -t391 <T391Timer> -t392 <T392Timer> -n391 <N391Counter> -n392 <N392Counter> -n393 <N393Counter> -enhancedLmi <enhancedLmi> -pta <portAdmin> -svcen <portSvcStatus> -svcuse <portSvcInUse> -pbe <portBertEnable> -m32eqth <EgressQueueThreshold> -lmias <lmi autosense>"

where -lmias <lmi_autosense> can be set to either 1 for Manual or 2 for AutoSense.

cnfport

One more parameter lmi_autosense has been added to the cnfport CLI, which can be specified while modifying the port. By default the value is set to Manual(1).

To configure the port for LMI AutoSense set the lmi_autosense parameter value to AutoSense(2) and lmiSig to noSignalling while using cnfport.

The cnfport command syntax for the cards has been modified to as shown below:

Syntax:

cnfport "portNum lmiSig asyn ELMI T391 T392 N391 N392 N393 [lmi_autosense]"

where [lmi_autosense] can be set to either 1 for Manual or 2 for AutoSense.

dspport

The existing CLI dspport will be enhanced to display the value of the new MIB variable. The display of this new variable portLmiSigConfMethod will be added between the display of PortSpeed and SignallingProtocolType.

Example:
node.1.4.VHSHS2.a > dspport 1
    SlotNum:                      		4
    PortLineNum:                  		1
    PortNum:                      		1
    PortRowStatus:                		Add
    PortDs0Speed:                 		notUsed
    PortDs0ConfigBitMap(1stDS0):  		0xffffff(1)
    PortEqueueServiceRatio:       		n/a
    PortFlagsBetweenFrames:       		0
    PortSpeed:                    		51840 kbps
    portLmiSigConfMethod:             Manual
    SignallingProtocolType:       		NoSignalling
    AsynchronousMsgs:             		UPD_UFS disabled
    T391LineIntegrityTimer:       		10 sec
    T392PollingVerificationTimer: 		15 sec
    N391FullStatusPollingCounter: 		6
    N392ErrorThreshold:           		3
    N393MonitoredEventCount:      		4
    EnhancedLmi:                  		Off
    PortState:                    		FailedDuetoLineFailure
    PortSignallingState:          		No Signalling Failure
    CLLMEnableStatus:             		Disable
    CLLMxmtStatusTimer:          		 40 ms
    portType:                     		frameRelay
    portEnhancedSIW:              		Disable
    PortIngrPercentUtil:          		0
    PortEgrPercentUtil:           		0
    PortOversubscribed:           		False
    PortSvcStatus:                		Disable
    PortSvcInUse:                 		Not In-Use
    PortSvcShareLcn:              		Card-based
    PortSvcLcnLow:                		0
    PortSvcLcnHigh:               		0
    PortSvcDlciLow:               		0
    PortSvcDlciHigh:              		0
    PortNumNextAvailable:         		2
MIB Changes

frPortCnfSigLMIGrpTable MIB Table

In support of LMI AutoSense, the new MIB object portLmiSigConfMethod has been added to the end of the frPortCnfSigLMIGrpTable MIB table.This MIB can hold either of the two values 1) Manual, 2) AutoSense. By default the value of the MIB will be set to "Manual". While enabling the port, the MIB can be used to configure the port to AutoSense LMI. After reset or softswitch the MIB retains its values to what was configured before reset.
portLmiSigConfMethod OBJECT-TYPE
    SYNTAX  INTEGER {
            manual    (1),
            autosense (2)
            }
    ACCESS  read-write
    STATUS mandatory
    DESCRIPTION
        " This object enables/disables the port LMI signalling autosense.
Setting this object to autosense(2) enables the port to autodetect and configure port LMI 
signalling type.
When this object is set to manual(1), user needs to manually configure the port LMI 
signalling type using the SignallingProtocolType mib.
        "
    DEFVAL { manual }
    ::= { frPortCnfSigLMIGrpEntry 11}
trapConfigChange MIB Table

The new MIB PortLmiCnfType is configurable using snmpset and the value of the mib can be accessed using snmpget. Once the MIB is set for LMI autosense, autodetection happens and the detected LMI type will be set and also the config change trap (trap no 50600 for PXM1-based MGX platforms) will be sent indicating the detected LMI type.
trapConfigChange  TRAP-TYPE
        ENTERPRISE      basis
        VARIABLES       {
                         lastSequenceNumber,
                         shelfNodeName,
                         shelfNum,
                         moduleSlotNumber,
                         moduleTrapAlarmSeverity,
                         functionModuleType,
                         configChangeTypeBitMap,
                         configChangeObjectIndex,
                         configChangeStatus
                        }
        DESCRIPTION
                "Sent when the config has changed.
                 The bit map tells if the change on
                 line/port/channel and the object
                 index shows the line#/port#/channel#,
                 the status shows if it's an add or
                 mod or del.
                "
        ::= 50600
Configuration Upload

A new MIB object has been added to the Configuration File for upload. The new MIB object is included at the end of the existing Signalling port table configuration information.

Features Not Supported in This Release

•Layer 2 support as an AutoRoute routing node

•Interworking with Cisco 3810

MGX 8220 Hardware That Has Been Superseded by MGX 8850-Specific Hardware

The following MGX 8220 hardware has been superseded by MGX 8850 hardware.

•The MGX-SRM-3T3/C front card replaces the original AX-SRM-3T3 front card and the MGX-BNC-3T3 back card replaces the original AX-BNC-3T3-M back card. Both the AX-SRM-3T3/AX-BNC-3T3-M card set and the MGX-SRM-3T3/C/MGX-BNC-3T3 card set are supported on the MGX 8220.

•The AX-SCSI2-2HSSI is superseded by the MGX-SCSI2-2HSSI/B, which works with the MGX-FRSM-HS2 and MGX-FRSM-HS2/B front card.

•The AX-CESM-8T1 is superseded by the MGX-CESM-8T1/B.

•The AX-AUSM-8T1 and AX-AUSM-8E1 is superseded by the MGX-AUSM-8T1/B and MGX-AUSM-8E1/B, respectively.

Service Module Redundancy Support

MGX 8850 (PXM1) provides high-speed native ATM interfaces, which can be configured as ATM UNI ports or trunks. The following table contains redundancy support information for service modules.

Table 1 Service Module Redundancy Support

Front Card Model #

Redundancy Supported

MGX-AUSM-8E1/B

1:N redundancy

MGX-AUSM-8T1/B

1:N redundancy

AX-CESM-8E1

1:N redundancy

AX-CESM-8T1

1:N redundancy

MGX-CESM-8T1/B

1:N redundancy

MGX-CESM-2T3E3

1:1 redundancy

AX-FRSM-8E1

1:N redundancy

AX-FRSM-8E1-C

1:N redundancy

AX-FRSM-8T1

1:N redundancy

AX-FRSM-8T1-C

1:N redundancy

MGX-FRSM-HS2

1:1 redundancy

MGX-FRSM-HS2/B

with HSSI back card, 1:1 redundancy
with 12IN1-8S back card, no redundancy

MGX-FRSM-2CT3

1:1 redundancy

MGX-FRSM-2T3E3

1:1 redundancy

MGX-FRSM-HS1/B

No redundancy

MGX-RPM-128M/B

1:N redundancy

MGX-RPM-PR-256

1:N redundancy

MGX-RPM-PR-512

1:N redundancy

MGX-VISM-8T1

1:N redundancy

MGX-VISM-8E1

1:N redundancy

MGX-VISM-PR-8T1

1:N redundancy

MGX-VISM-PR-8E1

1:N redundancy

Note Support for 1:N redundancy is provided in conjunction with an MGX-SRM-3T3¹ card or an MGX-SRM-E² card.

¹SRM-3T3 cards only support bulk Distribution for T1 lines.

²Bulk Distribution is supported for T1 and E1 lines using the SRM-E card.

Network Management Features

Network management features are detailed in the CWM Release 12 Release Notes at: http://cisco.com/univercd/cc/td/doc/product/wanbu/svplus/index.htm

Port/Connection Limits

Connection limits can vary. The table below shows total connections per card, but also shows the number of connections per port with LMI enabled. For example, the new FRSM-HS2/B card using a HSSI back card can support a total of 2000 connections on the card. However, if LMI is enabled on both ports, the total number of connections goes down. If StrataLMI is enabled for one ports, that port supports 560 connections. The other port not configured for LMI can support 1000 connections, for a total of 1560 connections.

Overall, there is a limit of 16,000 connections per shelf.

Refer to Table 2 for detailed connection information.

Table 2 Port/Connection Limits

Card Type

Back Card(s)

Conns./Card

Physical Ports

Logical Ports

Per port with StrataLMI

Per port with Annex A/D NNI/UNI

MGX-FRSM-HS2/B

HSSI

2000

2

2

560

898

12IN1-8S

4000

8

8

560

898

MGX-FRSM-HS2

HSSI

2000

2

2

560

898

MGX-FRSM-2CT3

BNC-2T3

4000

2

256

560

898

MGX-FRSM-2T3E3

BNC-2T3

2000

2

2

560

898

BNC-2E3

2000

2

2

560

898

BNC-2E3A

2000

2

2

560

898

MGX-FRSM-HS1/B

12IN1-4S

192

4

4

192

192

MGX-AUSM-8E1/B

RJ48-8E1

1000

8

8

N/A

N/A

SMB E1

1000

8

8

N/A

N/A

MGX-AUSM-8T1/B

RJ48-8T1

1000

8

8

N/A

N/A

AX-CESM-8E1

RJ48-8E1

248

8

248

N/A

N/A

SMB-8E1

248

8

248

N/A

N/A

AX-CESM-8T1

RJ48-T1

192

8

192

N/A

N/A

MGX-CESM-8T1/B

RJ48-T1

192

8

192

N/A

N/A

MGX-CESM-2T3E3

BNC-2T3

1

1

1

N/A

N/A

BNC-2E3

1

1

1

N/A

N/A

AX-FRSM-8E1

RJ48-8E1

1000

8

8

560

898

SMB-8E1

1000

8

8

560

898

AX-FRSM-8E1-C

RJ48-8E1

1000

8

248

560

898

SMB-8E1

1000

8

248

560

898

AX-FRSM-8T1

RJ48-8T1

1000

8

8

560

898

AX-FRSM-8T1-C

RJ48-8T1

1000

8

192

560

898

For the MGX 8230 and MGX 8250 Edge Concentrators, 16,000 connections (PVC) on the PXM1 based PAR Controller. If the MGX is a feeder to a BPX, only 15,729 feeder connections are available—271 connections are reserved for communication between the BPX and MGX. Maximum number of PXM UNI connections supported is still 4000 (as in prior releases).

SNMP MIB

The MGX 1 MIB naming convention has been changed as of the 1.2.10 release. The MIBS provided with Release 1.2.22 are named mgx1rel1222mib.tar.

The MIBs are bundled in the firmware bundle posted to CCO.

Note The old_mib_Format has been discontinued as of the 1.2.10 release As of the 1.2.10 release the new_mibFormat will be named mgx1rel<releasenumber>mib.tar

Notes and Cautions

The following notes and cautions should be reviewed before using this release.

New Boot Image for FRSM-HS2, FRSM-2CT3 and FRSM-2T3E3 Cards

There is a new FRSM Boot image for the FRSM-HS2, FRSM-2CT3 and FRSM-2T3E3 cards. The image is only required for the fix for CSCdz18745 (See "Anomalies Fixed in Release 1.2.21" on page 25 for additional information).

To upgrade the boot image, please follow the procedure in Service Module Upgrades.

Using the restoresmcnf command

Before using the restoresmcnf command, you must issue a clrsmcnf to make sure that there are no dangling connections after the restoresmcnf command.

Loopback Plug on a HSSI:DTE Interface

Using a loopback plug on a HSSI:DTE interface is not supported and can bring the node down.

UPC Connection Parameters

In Release 1.1.40 and higher, the default PCR is 50 cps, and the default for policing is "enabled." These settings are insufficient for running RPM ISIS protocol over the connection, and with such settings, the ISIS protocol will fail. The PCR value needs to be increased, depending upon the number of interfaces configured for ISIS on the RPM. CLI modification and changes in this release.

Depending upon your connection type, you can use the following CLIs to modify the PCR parameter.

•cnfupccbr

•cnfupcvbr

•cnfupcabr

•cnfupcubr

ForeSight and Standard ABR Coexistence Guidelines

ForeSight is similar to the rate-based ABR control system in TM 4.0 in that they both use Rate up and Rate down messages sent to the source of the connection to control the rate a connection runs at, based on congestion within the switches along that connections path. Both systems use Resource Management (RM) cells to pass these messages. There are differences between the two systems that need to be considered.

RM Cell Generation

ForeSight is a destination-driven congestion notification mechanism. The destination switch is responsible for generating the RM cells, which defaults to every 100 ms. This means that any rate modifications at the source end happen approximately every 100 ms, and the time delay between the actual congestion at the destination and the source getting to know about it could be 100 ms.

In standard ABR a source generates FRM cells every (nRM) cell intervals, where n is configurable. These are used to pass congestion information along to the destination switch, which then uses this information to generate BRM (Backward RM cells) back to the source A further consideration is that the actual user data flow will be lower for an equivalent rate due to the additional RM cells. Therefore, the more traffic being generated on a connection at any one time, the faster the feedback will be to the source.

There is also a TRM parameter which states that if no RM cells have been generated after this time has passed then one will automatically be sent. Depending upon the speed it is running at, an ABR connection may therefore react faster or slower to congestion than the equivalent ForeSight connection. (for example, if an ABR connection runs at 100 cells per second, and nRM is 32, then approximately three RM cells will be generated per second, or once every 300 msecs. If it runs at 1000 cps then an RM cell would be generated approximately every 30 msecs. In both cases, the equivalent ForeSight connection would generate an RM cell every 100 msec.)

Reaction to Feedback Messages - Rate Up

In ForeSight, in response to a Rate Up cell from the destination, the source increases its rate by a percentage of the MIR for that connection. If we call this percentage the rate increase percentage (RIP), then RIP is configurable at the card level (the default is 10 percent). In the case where MIR is low, the ForeSight rate increase will be slow as it has to increase as a percentage of MIR (rather than CIR).

On a standard ABR connection, in the event of available bandwidth (no congestion) the source increases its rate by a factor of (RIF*PCR). This means the rate increase step sizes are much bigger than for ForeSight for larger values of RIF (RIF has a range of 1/2, 1/4,....,1/32768). If RIF is not configured properly then standard ABR will ramp up its rate much faster and to a higher value. This is aided by the fact that the step sizes are bigger and the step frequency is higher in comparison with ForeSight.

Reaction to feedback messages - Rate Down

In ForeSight on receiving a Rate Down cell from the remote end, the source reduces its current rate (actual cell rate) by 13 percent. The rate decrease percentage (RDP). RDP is configurable at the card level.

In standard ABR, rate decrease is by an amount (RDF*ACR). Currently, the default value of RDF is 1/16 (6.25 percent). This means when this connection co-exists with ForeSight connections, in the event of congestion ForeSight connection reduces its rate by 13 percent whereas standard ABR connection reduces its rate by only 6.25 percent. Therefore, in the case of co-existence, if we need to approximate the same behavior across the two connection types, then RDF should be changed to 1/8, so that both connections ramp down by the same amount (13 percent).

Fast-Down

In ForeSight if the destination egress port drops any data due to congestion then the destination sends a Fast Rate Down cell. Also, if a frame cannot be reassembled at the egress due to a lost cell somewhere in the network, a Fast-down will be generated. On reception of Fast Rate Down the source reduces its current rate by 50 percent (this is again a card-level configurable parameter).

Standard ABR does not distinguish between drops and the ECN/EFCI threshold being exceeded. This means that, in case of drops in the egress port queue, a standard ABR connection rate reduces by only (RDF*ACR) but the ForeSight connection rate reduces by (ACR*0.5). Therefore, in the case of co-existence, if we need to approximate the same behavior across the two connection types then Fast Down could be effectively disabled by configuring the reaction to be 13 percent rate down instead of 50 percent.

Guidelines

The two systems will work together within the network, but as the above description suggests, if the differences between the two systems are not taken into consideration, then a ForeSight connection and an ABR connection with the same configuration parameters will not behave the same way within the network.

ABR and ForeSight provide a mechanism for distributing excess bandwidth between connections over and above the minimum rate, therefore if these guidelines are not taken into consideration then the allocation of this excess bandwidth may be biased toward connections running one of these algorithms over connections running the other.

If this is a requirement, the following guidelines may be useful, assuming ForeSight is set to defaults except for Fast Rate Down which is set for 13 percent.

•Nrm: Nrm needs to be set at a value whereby the approximate RM cell generation is
100 milliseconds, to match that of ForeSight. This calculation is based on the expected average, or sustained, cell rate of the connection. However, if the (potential) fast-down messages from ForeSight are left to equate to 50 percent rate down, then an estimate of how often this may occur needs to be made and factored into the equation. If the connection receives Fast-down messages, then this would make the ForeSight connection react faster than the equivalent ABR connection to congestion. To compensate for this, Nrm needs to be set at a value of less than 100 msecs, a suggested value to aim for is between 60-70 msecs (this would be approximate as n is configurable in steps of 2**n). This would mean that, in the event of congestion, the ABR connection would start to react faster.

•RIF: Rate increase factor is a factor of PCR in ABR and MCR in ForeSight. The default RIF for ForeSight is MCR*.10. Therefore, RIF should be configured so that (PCR*RIF) approximates MCR*0.1. If Fast-Down is still effectively enabled, then PCR*RIF should approximate MCR*0.62 to compensate.

•RDF: (Rate Decrease Factor) RDF should be 1/8. This approximates to 13 percent that ForeSight uses.

The following worked examples may help explain this further

Assume a network is currently running ForeSight with default parameters, and supports the following four connection type, where CIR = MIR, PIR = port speed, and QIR = PIR:

T1 Port Speed 64K CIR

Example:

CIR = MIR = 64K
PIR = QIR = port speed = 1544
Fastdown = 13%

(The calculation used to convert between frame based parameters (CIR, PIR, and so on.) and their equivalent cell-based parameters is FR_param *3/800. This allows for cell overheads, and so on. based on frame sizes of 100 octets.)

CIR = MIR = (64000*3/800) = 240 cps
PIR = QIR = (1544 *3/800) = 5790 cps

ForeSight ABR
Rate-up equals (240*.1) = 24 cps RIF equals x where (1590/x) = 24 cps
X needs to be approx 200
RIF equals 256 (nearest factor of 2)

RDF equals 13% RDF = 1/8
Nrm equals 100 msecs Nrm equals 32

RM cells will be generated somewhere between 6 (5790 cps approx equal to 32 cells per 6 msecs) and 133 msecs (240 cps approx equal to 32 cells every 133 msecs) depending on ACR.

Node Related

•A maximum of one BERT test can be performed per bay at any point in time. The command addln should be issued before executing the addapsln command.

•If you are moving service modules from an existing MGX 8220 platform to the MGX 8850 (PXM1), MGX 8250, or MGX 8230, the MGX 8220 service modules (AX-FRSM-8T1/E1, and AX-CESM-8T1/E1) need to have the boot flash upgraded to MGX 8220 Release 5.0.00 common boot code (1.0.01 version) before they can be plugged in to the MGX 8850 (PXM1), MGX 8250, or MGX 8230 chassis. All MGX 8220 service module versions that use Release 4.0.xx of boot code and earlier are not supported in the MGX 8850 (PXM1), MGX 8250, or MGX 8230.

If loading of the correct common boot code image is required then it will have to be performed on an MGX 8220 chassis, and cannot be performed on an MGX 8850 (PXM1), MGX 8250, or MGX 8230 chassis. Please refer to the procedure below, which is also outlined in the Cisco MGX 8850 (or MGX 8250 /MGX 8230) Installation and Configuration publication on the documentation CD.

Step 1 Use ftp to port the MGX 8220 Release 5 common boot image for the service module to a workstation.

Step 2 Plug in the card into the MGX 8220 shelf.

Step 3 Download the proper MGX 8220 shelf Release 5.0 boot image using the following commands from the workstation:
tftp <ip address of the MGX 8220 shelf > 
bin 
put <boot filename> AXIS_SM_1_<slot#>.BOOT 
To insure that TFTP downloaded the appropriate boot code, perform the following procedure to verify the flash checksums.

Step 1 Log into the shelf.
cc <slot #> 
Step 2 Verify that the two checksums are the same.
chkflash
If not, repeat the process until they are the same. If they are the same, then you can safely remove the card. At this point the service module can be used in the MGX 8850 (PXM1) shelf.

Caution If the checksums are not the same when you remove the service module, then the service module will not boot when it is plugged in and the service module will have to be returned using the Cisco Returned Material Authorization process.

•Whenever an MGX 8850 is added as a feeder to a BPX 8600, SWSW automatically programs a channel with a VPI.VCI of 3.8 for use as the IP Relay channel. IP Relay is used to send IP data between nodes via the network handler, allowing every node in the domain to be directly addressable via IP addressing and CWM workstations to communicate with every node (especially feeders) using TELNET, SNMP and CWM protocols. If the user tries to add a channel with a VPI.VCI of 3.8, the BPX 8600 does not prevent the user channel from being added, but the MGX 8850 rejects it. To delete the added channel on the BPX 8600, and to get IP relay working you need to reset the BXM card.

•In addition to clearing the entire configuration, clrallcnf command clears the network IP addresses. IP addresses and netmasks stay the same (dspifip). However, Cisco recommends entering the cnfifip command to reconfigure the network IP addresses. Network IP is gone (dspnwip), and must be re-configured using the cnfifip command. Refer to the entry on cnfifip in the Cisco MGX 8850 Command Reference for syntax.

•Service module upgrades error handling is not provided. If the user skips any of the steps during upgrade or if a power failure happens in the middle of the upgrade, results will be unpredictable. See the Special Installation and Upgrade requirements section for service module upgrades. To recover from procedural errors contact your TAC support personnel.

•The MGX 8850 (PXM1) supports 15 simultaneous Telnet sessions and up to 10 TFTP sessions per shelf.

•You must use the following Y-cables for FRSM-HS2 and FRSM-CT3 redundancy as specified in the Product Orderability Matrix (Straight Cable: 72-0710-01, Crossover Cable: 72-1265-01, Straight Y-cable: FRSM-HS2: CAB-SCSI2-Y, FRSM-CT3: CAB-T3E3-Y). Other cables are not supported.

Y-cable redundancy for FRSM-HS2, FRSM-2CT3, FRSM-2T3, FRSM-2E3 is supported only for adjacent slots.

•There is no need to issue the syncdisk and shutdisk commands before removing the PXMs. The system quiesces the disk by detecting the removal of the PXM board and flushes the write buffers to the disk and puts the PXM in sleep mode. This disables any further hard disk access by locking the actuator.

Note When the card is reinserted the PXM automatically comes out of sleep mode.

Caution Cooling and Power limitations: Be aware of the need for extra power supplies and fans beyond certain limitations. A single fan tray will support all configurations that draw between 1200 and 1400 watts. For power requirements, the MGX 8850 (PXM1) requires a minimum of one power supply per line cord to support the power requirement for five cards (see Table 3).

Table 3 Number of Power Supplies Per Line Cord Based on Cards Supported

0-5 Cards

6-10 Cards

11 and Above

Single Line Cord (N+1):

2

3

4

Dual Line Cord (2N):

2

4

6

This is based on an estimated worst-case power requirement of 190W plus margin per card slot.

Connection Management Related

•The name of the node cannot be changed if there are PVCs. The node name must be changed from the default value before adding connections, since it cannot be changed later. Use the cnfname command to change the node name.

•Only one feeder trunk can be configured. No BNI trunk to MGX 8850 (PXM1) as a feeder is supported.

•The slave end of a connection must be added first.

The slave end cannot be deleted and re-added back by itself. If you delete the slave end, the entire connection must be completely torn down and re-added back. If the slave end of the connection is deleted and re-added back by itself, then unpredictable results will happen.

•For user connections, VCI 3 and VCI 4 on every VPI are reserved for VPC OAMs.

•The actual number of feeder connections you can provision on the PXM is always two less than you have configured. The dsprscprtns command shows max connections as 32767, but you can only use 32767 - 2 = 32765. One connection is used for LMI and another one for IP relay.

•There is no error handling detection while provisioning through the CLI. Invalid endpoints and unsupported connection types (such as connections between FRSM-CESM ports or connections between structured and unstructured connections) are permitted using the CLI. The user should not configure these connections.

•The sum of CIR of all channels of a port can be greater than port speed as long as CAC is disabled. However, it is not acceptable for one channel's CIR to be greater then port speed even if CAC is disabled. Two channels added up can exceed port speed. This means you cannot oversubscribe a port if only one channel is configured.

•When trying to add a port on DS0 slot 32 of a CESM-8E1 line using an SNMP set or the CiscoView Equipment Manager, the SNMP agent in CESM will time out, without adding the port. The SNMP libraries treat the 32 bit DS0 slotmap (cesPortDs0ConfigBitMap) as an integer. The value for the last DS0 is treated as the sign value. This causes a corruption in the packet coming to the agent. As the agent does not receive a complete SNMP packet, it does not respond and times out. Use the command line interface to add a port on DS0 slot 32 of a CESM-8E1 line.

•The cnfport command does not allow VPI ranges to be reduced. The cnfport command only allows the VPI range to expand. The correct sequence is to delete all connections on the partitions, delete the partitions, delete the port, and add the port with new VPI range.

•On an FRSM-2CT3, one can add 128 ports on a group of 14 T1 lines as indicated below.

– lines 1 to 14: 128 ports (A)

– lines 15 to 28: 128 ports (B)

– lines 29 to 42: 128 ports (C)

– lines 43 to 56: 128 ports (D)

So, to add 256 ports on one T3: add 128 ports on the first 14 T1 lines and the remaining 128 on the next 14 T1 lines.

•Note that (A) and (D) are connected to first FREEDM and (B) and (C) are connected to the second FREEDM. Each FREEDM supports only 128 ports. If 128 ports are added on one T3 as in (A), then there cannot be any more ports as in (D). The 129th port should be on lines 15 to 42 (as in B or C).

•If the user adds a connection between an RPM and a PXM and then deletes the connection, the RPM shows no connection but the PXM still has the connection. The MGX was designed and implemented in such a way that only the connections that have the master end show up on PXM (by dspcons command). Consider these three connections:

•c1: has only slave end

•c2: has only master end

•c3: has both master and slave end

When using the dspcons command, c2 and c3 will be displayed, not c1. The connection will not show up once the master end (PXM) is deleted. Recommendation: When adding a connection, if one end of the connection is PXM, always configure the PXM side to be the slave. Thus when deleting the RPM side, which is the master, the connection will not show up on the PXM. However, keep in mind that the slave end (PXM) still exists. This also provides a side benefit. When a connection exists with only the slave side, no bandwidth is occupied. The bandwidth is reserved only if the master end exists (with or without the slave).

Documentation Corrections

The documentation for the PXM1-based MGX switches incorrectly describes the Cellbus to slot assignments.

For example, the MGX 8250 with a PXM1 has 8 cellbuses. The distribution of these 8 cellbuses to the appropriate slot numbers can be found executing the CLI command dspcbclk.

m8250-4a.1.8.PXM.a > dspcbclk
  CellBus    Rate (MHz)     Slot     AutoClkMode
    --------------------------------------------------
       CB1         21           1, 2       disable
       CB2         21           3, 4       disable
       CB3         21           5, 6       disable
       CB4         21        17 - 22       disable
       CB5         21          9, 10       disable
       CB6         21         11, 12       disable
       CB7         21         13, 14       disable
       CB8         21        25 - 30       disable
New and Changed Commands in the 1.2.x Baseline

Table 4 lists the new and modified commands in Release 1.2.x baseline.
Table 4 New and Modified CLI Commands in the 1.2.x Baseline
CLI

Changes

For Feature

addapsln

The parameter archmode sets the APS architect mode to be used on the working/protection line pairs. The new value "5" is added to specify 5: 1+1 Annex A.

ITU APS Annex-A
SRM-E¹

addcon

Two new values have been introduced for cesCas type to configure a channel with the multiframe option enabled. The values are ds1SfCasMF and ds1EsfCasMF.

The channels on a particular line can be either all MF (SF MF or ESF SF) or all non-mf (SF or ESF). The first connection type added on a particular line (mf/non-mf) decides the sync mode. The second connection must have the same cesCas type, and so on.

CESM²

adddiagtest

Diagnostics.The diagnostic commands are modified for test number 8-SRM M13 Access. This command will perform SRM or SRM-E hardware online diagnostics, depending upon what kind of cards are in the slot. Refer to the Release Notes for Cisco WAN MGX 8850, MGX 8230, and MGX 8250 Software Version 1.1.40 at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8850/14/rnotes/rn1140.htm

SRM-E

addlink

Bulk redundancy/distribution. The existing command addlink is modified to link a certain number of T1/E1 channels from a bulk interface on SRM-E to a service module's T1/E1 lines. This command checks the card type of the service module in the target slot. The service module must be a T1/E1 type, depending upon the tributary type configured for the SRM-E line using the cnfln command. A service module will switch all its lines to bulk mode even if only one line is mapped to a tributary from SRM-E.

Note You must enable the lines on the SRM-E cards (using the upln and cnfln commands) before you can configure them for distribution.

SRM-E

addln

Existing addln command is modified to support per line interface type configuration (used only with the 12IN1-8S). If the user doesn't specify <interface_type>, the default type V.35 is used.

FRSM-HS2/B

SRM-E

addlnloop

Physical interface. Existing command addlnloop is modified to add a logical loopback on a line on the new card. (SRM-E)

SRM-E

addport

One more parameter lmi_autosense has been added to the command where lmi_autosense can be configured for either mode Manual(1) or AutoSense(2).

FRSM-8T1/E1

FRSM-VHS6

addred

Redundancy activities. The existing command addred is modified to configure redundancy on the new card.

SRM-E

clralldiagtests

Command is modified for test number 8-SRM M13 Access. The command will perform SRM or SRM-E hardware online diagnostics, depending upon what kind of cards are in the slot.

SRM-E

clralm

Managing alarms. Existing command clralm is modified to clear alarms on a line on the new card.

SRM-E

clralmcnt

Managing alarms. The existing command clralmcnt is modified to clear alarm counts on a line on the new card.

SRM-E

cnfbert

BERT activities. The existing command cnfbert is modified to configure a line or port for BERT and start the test on the new card.

SRM-E

cnfcacparm

New command introduced in 1.2.20 Release to configure CAC based on SCR in VBR.

CAC Based on SCR in VBR³

cnfclktype

Existing cnfclktype command is added to FRSM-HS2B to configure line clock type for V.35/X.21 interfaces. This command is valid on the FRSM-HS2B-12IN1 card.

FRSM-HS2/B

cnfdiagparams

Command is modified for test number 8-SRM M13 Access. The command will perform SRM or SRM-E hardware online diagnostics, depending upon what kind of cards are in the slot.

SRM-E

clrdiagresults

Command is modified for test number 8-SRM M13 Access. The command will perform SRM or SRM-E hardware online diagnostics, depending upon what kind of cards are in the slot.

SRM-E

cnfclklevel

Permits the user to set the STRATUM level desired. (S-3 Clocking)

PXM-UI-S3

cnfdiagtest

Command is modified for test number 8-SRM M13 Access. The command will perform SRM or SRM-E hardware online diagnostics, depending upon what kind of cards are in the slot.

SRM-E

cnflink

Bulk redundancy/distribution. The existing command cnflink is modified to configure the link for T1 byte-sync mapping on the new card. For byte-sync mapping on sonet interfaces, the T1 framing format should be configured.

The framing format can be specified at line level for all links using the cnfln command. It can be then overridden on a per link basis using the cnflink command.

Note The cnflink command is not applicable to 3T3 back cards. Also, byte-sync mapping is supported only for Sonet --> T1 mapping. Therefore, this command is not applicable if an SRM-E's line are configured for SDH --> E1 mapping.

SRM-E

cnfln

Existing cnfln command is modified on FRSM-HS2/B to support new MIB objects.

Note Do not configure an interface to DTE mode when a physical loopback plug is plugged in. This will cause the line to go in and out of alarm and generate software errors on the PXM. If this situation occurs, use the command cnfln to configure the line as DCE to recover from the situation.

For SRM-E, cnfln command is modified to support new MIB objects and new enumerations for line rate.

For tributary type, option VT2 (carries E1 signals in Sonet) is not supported in this release.

For tributary mapping type, only option, 2 byte-synchronous mapping, is supported for T1.

FRSM-HS2/B

SRM-E

cnfport

One more parameter lmi_autosense has been added to the command which can be specified while modifying the port. The parameter lmi_autosense can be either mode -- Manual(1) or AutoSense(2).

FRSM-8T1/E1

FRSM-VHS6

cnfsrmcklsrc

Managing clock sources. Existing command cnfsrmclksrc is modified to support the new SRM-E card.

SRM-E

clrsrmcnf

Managing configuration. The existing command clrsrmcnf is modified to clear all card configuration including distribution links. The configuration cannot be cleared if redundancy is enabled.

SRM-E

delbert

BERT activities. The existing command delbert is modified to delete/terminate the operation in progress on the new card.

SRM-E

deldiagtest

Command is modified for test number 8-SRM M13 Access. The command will perform SRM or SRM-E hardware online diagnostics, depending upon what kind of cards are in the slot.

SRM-E

dellink, delslotlink

Bulk redundancy/distribution. The existing commands dellink/delslotlink are modified to delete distribution links on the new card. After the last distribution link to a service module is deleted, the service module switches all its lines to non-bulk mode (to its back card).

SRM-E

delln

Physical interface. Existing command delln is modified to disable a line on the new card.

Note A line cannot be deleted if distribution links are configured for that line.

SRM-E

dellnloop

Physical interface. Existing command dellnloop is modified to delete a logical loopback on a line on the new card.

SRM-E

delred

Redundancy activities. The existing command delred is modified to delete the redundancy configuration on the new card.

SRM-E

delsesn

Use this command to terminate a UNIX-based telnet session.

delsesn <sesn no> [sesn no>] [sesn no>] ...

where sesn no is the number of the session in the range 0-15.

PXM⁴

dspalmcnt

Managing alarms.The existing command dspalmcnt is modified to display alarm counts on a line on the new card.

SRM-E

dspalm

Managing alarms. Existing command dspalm is modified to display alarms on a line on the new card.

SRM-E

dspalmcnf

Managing alarms. Display alarm configuration for a line.

SRM-E

dspalms

Managing alarms. Existing command dspalms is modified to display alarms on all lines of a slot on the new card.

SRM-E

dspapsln

ITU APS Annex-A
SRM-E1

dspbert

BERT activities. The existing command dspbert is modified to display the parameters and the results of an ongoing operation on the new card.

SRM-E

dspcacparm

New command introduced in 1.2.20 Release to display CAC parameters

CAC Based on SCR in VBR3

dspcd

The dspcd command on the CESM model B card is modified to display "CESM8T1B" next to the Fab number. This can be used to differentiate between CESM model A and B cards.

CLI changes

The channels on a particular line can be either all MF (SF MF or ESF SF) or all non-mf (SF or ESF). The first connection type added on a particular line (mf/non-mf) decides the sync mode. The second connection must have the same cesCas type and so on.

CESM2
dspclkinfo
Displays some extra information about second external BITS clock, as shown in the following screen example:
NOEXTCLK2 = OFF
extClock2Present = No
Last External Clock2 Present = 1
PXM-UI-S3⁵
dspparifs

Displays the existence of interface 7.36 along with interface 7.35.

PXM-UI-S35

dspdiagresults.

Command is modified for test number 8-SRM M13 Access. The command will perform SRM or SRM-E hardware online diagnostics, depending upon what kind of cards are in the slot

SRM-E

dspdiagtests

Command is modified for test number 8-SRM M13 Access. The command will perform SRM or SRM-E hardware online diagnostics, depending upon what kind of cards are in the slot.

SRM-E

dsplink, dspslotlink

Bulk redundancy/distribution. The existing commands dsplink/dspslotlink are modified to display distribution links.

SRM-E

dspln

Existing dspln command is modified on FRSM-HS2 B and SRM-E to display new objects.

FRSM-HS2/B
SRM-E

dsplns

Existing dsplns command is modified to display interface type.

FRSM-HS2/B
SRM-E

dsplog

The command dsplog will include SRME online diagnostics failure if it happens.

SRM-E

dspport

The existing CLI dspport will be enhanced to display the value of the new MIB variable. The display of this new variable portLmiSigConfMethod will be added between the display of PortSpeed and SignallingProtocolType.

FRSM-8T1/E1

FRSM-VHS6

dspred

Redundancy activities. The existing command dspred is modified to display the redundancy configuration on the new card.

SRM-E

dspsrmclksrc

Managing clock sources. Existing command dspsrmclksrc is modified to display the card types of the current and previous SRM card.

SRM-E

dspsrmcnf

Managing configuration. The existing command dspsrmcnf is modified to display the current card configuration on the new card.

SRM-E

modbert

BERT activities. The existing command modbert is used to modify BERT parameters.

SRM-E

pausediag
resumediag

Command is modified for test number 8-SRM M13 Access. The command will perform SRM or SRM-E hardware online diagnostics, depending upon what kind of cards are in the slot

SRM-E

rundiagtest

Command is modified for test number 8-SRM M13 Access. The command will perform SRM or SRM-E hardware online diagnostics, depending upon what kind of cards are in the slot

SRM-E

showdiagtests

Command is modified for test number 8-SRM M13 Access. The command will perform SRM or SRM-E hardware online diagnostics, depending upon what kind of cards are in the slot

SRM-E

softswitch

Redundancy activities. The existing command softswitch is modified to manually switch to the redundant module for the SRM-E.

SRM-E

switchapsln

The command is modified to include the following options:

3 = forced working-> protection

4 = forced protection->working

5 = manual working->protection

6 = manual protection-> working

ITU APS Annex-A

SRM-E1

switchback

Redundancy activities. The existing command switchback is modified to switch back to the primary module from the redundant module for the SRM-E.

SRM-E

xcnfalm

Managing alarms.The existing command xcnfalm is modified to configure alarms for a line on the new card. The xcnfalm command allows only DS3 and E3 alarm thresholds to be configured.

SRM-E

xcnfcon

Two new values have been introduced for cesCas type to configure a channel with the multiframe option enabled. The values are ds1SfCasMF and ds1EsfCasMF.

The channels on a particular line can be either all MF

Hierarchical Navigation

Cisco MGX 8800 Series Switches

1.2.22 Release Notes for MGX 8230, MGX 8250, and MGX 8850 (PXM1)

Downloads

Table Of Contents

Release Notes for Cisco MGX 8230, MGX 8250, and MGX 8850 (PXM1), Software Version 1.2.22

Contents

About These Release Notes

Features Introduced in Release 1.2.22

Features Introduced in Release 1.2.21

LMI AutoSense

addport

FRSM-8P and FRSM-2CT3.

FRSM-2T3, FRSM-2E3, FRSM-HS2, FRSM-HS2B.

xcnfport

cnfport

dspport

Example:

MIB Changes

frPortCnfSigLMIGrpTable MIB Table

trapConfigChange MIB Table

Configuration Upload

Features Not Supported in This Release

MGX 8220 Hardware That Has Been Superseded by MGX 8850-Specific Hardware

Service Module Redundancy Support

Network Management Features

Port/Connection Limits

SNMP MIB

Notes and Cautions

New Boot Image for FRSM-HS2, FRSM-2CT3 and FRSM-2T3E3 Cards

Using the restoresmcnf command

Loopback Plug on a HSSI:DTE Interface

UPC Connection Parameters

ForeSight and Standard ABR Coexistence Guidelines

RM Cell Generation

Reaction to Feedback Messages - Rate Up

Reaction to feedback messages - Rate Down

Fast-Down

Guidelines

Node Related

Connection Management Related

Documentation Corrections

New and Changed Commands in the 1.2.x Baseline