Table Of Contents
Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830, Software Version 5.0.20
Contents
About Release 5.0.20
Changes to Release 5.0.20
Type of Release
Locating Software Updates
Features and Enhancements in Release 5.0.20
Multilink Frame Relay on MPSM-T3E3-155
Features
Restrictions
Multilink Frame Relay Quick Start Provisioning Procedures
Multilink Frame Relay General Provisioning Procedures
Adding a Port to the MFR Bundle
Deleting an MFR Bundle, Link, or Port
Port Oversubscription on MPSM-T3/E3-155
Channel Loopback on MPSM-T3E3-155
Restrictions
Enhancement to Statistics Counters on MPSM-T3E3-155
Features and Enhancements in Previous Release 5.0.10
CES Line Conditioning
Platforms
MPSM Service Modules
MPSM Licenses
Platforms
PXM45 RAS
Platforms
Standard Available Bit Rate (ABR) Mapping Changes (PER 4148)
Platforms
License Management
Platforms
AXSM-16-155-XG Feeder Support
Limitation
Platforms
Unique Device Identifier (UDI)
Limitations
Platforms
Features and Enhancements in Previous Release 5.0.00
SRME/B
Platforms
AXSM-16-155-XG
Platforms
AIS Delay, Deroute Delay, Absolute Grooming
Platforms
Soft Reroute
Platforms
Point to Multipoint Support on PXM1E
Limitation
Platforms
Enhancements to Route Optimization
Platforms
Priority Bumping
Platforms
Enhancements
Service Class Template (SCT) File Information
MPSM-155
PXM1E
AXSM and AXSM/B
AXSM-E
AXSM-XG
System Requirements
Software/Firmware Compatibility Matrix
MGX and RPM Software Version Compatibility Matrix
Additional Notes
SNMP MIB Release
Hardware Supported
New Hardware in Release 5.0.20
New Hardware in Release 5.0.10
Product IDs, Card Types, and APS Connectors
New and Changed Commands
New and Changed MPSM-T3E3-155 Commands
New Multilink Frame Relay Commands
addmfrbundle
addmfrlnk
addmfrport
clrmfrbundlecnt
clrmfrbundlecnts
clrmfrlnkcnt
clrmfrlnkcnts
cnfmfrbundle
cnfmfrlnk
delmfrbundle
delmfrlnk
dnmfrbundle
dspmfrbundle
dspmfrbundlealm
dspmfrbundlealms
dspmfrbundlebucketcnt
dspmfrbundlecnt
dspmfrbundles
dspmfrlnk
dspmfrlnkalm
dspmfrlnkalms
dspmfrlnkbucketcnt
dspmfrlnkcnt
dspmfrlnks
upmfrbundle
New Channel Loopback Commands
addchanloop
delchanloop
dspchanloop
Changed Commands
Removed Commands
Commands Changed in Release 5.0.10
PXM45 Commands
PXM1E Commands
AXSM and AXSM-E Commands
Limitations, Restrictions, and Notes for 5.0.20
AXSM-16-155-XG with MCC Back Cards
Upgrading AXSM-XG Cards
Upgrading the VISM-PR Image
MPSM Notes
PXM1E Parity Errors
Upgrading to 5.0
Higher Level Logical Link Limits
CLI Upgrade
Preferred Route
AXSM-32-T1E1-E and PXM1E-16-T1E1
Cell Bus Service Modules (Formerly Known as Narrow Band Service Modules) and RPM-PR
IGX Feeder
Policing Accuracy for PXM1E
Maximum Threshold Accuracy for PXM45 and PXM1E
PXM1E-Based Switches
PXM1E Hardware Limitations
Reserved VCIs
AXSM-E OAM
CLI Configurable Access
Controller Card Mastership Sanity Verification
Serial Bus Path Fault Isolation
Cell Bus Path Fault Isolation and Recovery
Disk Space Maintenance
Non-native Controller Front Card and PXM-HD Card
clrsmcnf Command
APS
Path and Connection Trace
Simple Network Timing Protocol (SNTP)
Priority Routing
SPVC Interop
Persistent Topology
Manual Clocking
AXSM Cards
AXSM-XG Hardware Limitation
ATM Multicast
Priority Bumping
Other Limitations and Restrictions
Clearing the Configuration on Redundant PXM45 and PXM1E Cards
Troubleshooting APS Lines
Installation and Upgrade Procedures
Upgrade Information
Maintenance Information
Anomalies
MGX 8850, MGX 8830, and MGX 8950 5.0.20 Anomalies
Known Anomalies in Release 5.0.20
Resolved Anomalies in Release 5.0.20
Anomalies Status Change in Release 5.0.20
Resolved Anomalies in Previous Releases
Resolved Anomalies in Release 5.0.10
Resolved Anomalies in Release 5.0.00
Known Route Processor Module or MPLS Anomalies
MGX-RPM-XF-512 and MGX-RPM-PR-256/512 Anomalies
Documentation
Obtaining Documentation
Cisco.com
Documentation DVD
Ordering Documentation
Documentation Feedback
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support Website
Submitting a Service Request
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Acronyms
Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830, Software Version 5.0.20
These release notes are Part Number OL-6856-01 Rev. G0, March 2007.
Contents
About Release 5.0.20
Version .205 of Release 5.0.20 is a patch release that does not introduce new features. The resolved anomalies for Version .205 are listed in Table 24.
These release notes describe the system requirements, new features, and limitations that apply to Release 5.0.20 of the MGX 8850, MGX 8950, and MGX 8830 Multiservice Switches. These notes also contain Cisco support information.
For a list of the open and resolved anomalies in this release, see the "MGX 8850, MGX 8830, and MGX 8950 5.0.20 Anomalies" section.
Changes to Release 5.0.20
Table 1 summarizes the software changes in Release 5.0.20.
Table 1 Changes to Release 5.0.20 Software
Revision Date on Cisco.com
|
Software
|
Version Change
|
Resolved Anomalies
|
Reference
|
11/14/05
|
MPSM-T3E3-155
|
.201 to .202
|
CSCei35633
CSCej32681
CSCej15496
|
Table 25 in Resolved Anomalies in Release 5.0.20
|
AXSM-XG
|
.203 to .204
|
09/09/05
|
PXM45
|
.202 to .203
|
CSCei67407
CSCei82475
|
Table 26 in Resolved Anomalies in Release 5.0.20
|
PXM1E
|
.202 to .203
|
AXSM-XG
|
.202 to .203
|
MPSM-T3E3-155
|
.200 to .201
|
CSCei59862
CSCei65805
|
AXSM/B
|
.200 to .201
|
05/12/05
|
PXM45
|
.201 to .202
|
CSCec04754
CSCec48191
CSCeg25173
CSCeg62909
CSCeg68790
CSCeg76224
CSCeg88649
CSCeh14484
CSCeh15349
CSCeh15410
CSCeh16336
CSCeh19705
CSCeh21259
CSCeh21549
CSCeh23987
|
Table 27 in Resolved Anomalies in Release 5.0.20
|
PXM1E
|
.201 to .202
|
AXSM-XG
|
.201 to .202
|
MPSM-8-T1E1
|
.201 to .202
|
Type of Release
Release 5.0.20 is a software and hardware release for the following MGX switches:
•
MGX 8830 PNNI routing switch
•MGX 8850 (PXM1E)
•MGX 8850 (PXM45)
•MGX 8950
Locating Software Updates
This is the location for the MGX 8850 (PXM45/PXM1E), MGX 8830, and MGX 8950 5.0.20 software:
http://www.cisco.com/public/sw-center/wan/wan-planner.shtml
Features and Enhancements in Release 5.0.20
This section contains the following new features and enhancements in Release 5.0.20:
•Multilink Frame Relay on MPSM-T3E3-155
•Port Oversubscription on MPSM-T3/E3-155
•Channel Loopback on MPSM-T3E3-155
•Enhancement to Statistics Counters on MPSM-T3E3-155
Multilink Frame Relay on MPSM-T3E3-155
Multilink Frame Relay (MFR) combines multiple individual links into one logical interface, called an MFR bundle. Multilink bundles help bridge the gap between DS1 and DS3 bandwidths, and can increase resiliency because the failure of a link usually does not bring down the whole bundle. In the MPSM-T3E3-155, each link is a T1 path on a channelized DS3 line or path.
The bundle interface serves as the Frame Relay data link, and performs the same functions as a physical Frame Relay interface. The bundle interface is visible to peers, so you configure Frame Relay functionality on the bundle interface. This section describes how to provision Mulitlink Frame Relay (MFR) services on the MPSM-T3E3-155 card.
Note Before you perform the procedures in this section, you must first configure the MPSM-T3E3-155 card and lines.
Features
The MPSM-T3E3-155 provides the following features:
•MFR supported on the 3-port channelized T3 back card and the 2-port channelized OC-3 back cards.
•Maximum of 42 bundles with up to 12 links per bundle.
•Support for Class A, Class B, and Class C bandwidth classes.
•Bundling of links that belong to different channelized T3 (up to 3 T3s) or STS-1s (up to 3 STS-1s).
•Aggregation of only full T1/E1 links. MFR bundles with NxDS0 links are not supported.
•12 bit sequence number format.
•Two-byte Frame Relay header supported.
•Support only for Extended Super Frame (ESF).
•Both UNI and NNI mode as per FRF.16.1 are supported.
•MPSM is transparent to end-to-end MFR and cannot be the initiating or terminating end for end-to-end MFR.
•FRF.2.1 Annex 1 is supported on NNI-type bundle interfaces.
Restrictions
The MPSM-T3E3-155 has the following restrictions:
•Aggregation of full T1 links only; MFR bundles with n x DS0 links are not supported
•Blending T1 and E1 is not supported
•Two-byte Frame Relay header (for example, 10 bit DLCI) is supported
•Four-byte Frame Relay header for extended addressing is not supported. Frame Relay extended addressing uses a 23-bit DLCI field that enables support for thousands of DLCIs in NNI networks.
•Frame Relay fragmentation is not supported.
•Super Frame (SF) mode is not supported. Only ESF (Extended Super Frame) mode is supported for MFR services.
•A maximum of 200 DLCIs per bundle is supported.
Multilink Frame Relay Quick Start Provisioning Procedures
This section provides quick start procedures for provisioning MFR on the MPSM-T3E3-155.
.
| |
Command
|
Comments
|
Step 1
|
addmfrbundle
related commands:
dspmfrbundle
cnfmfrbundle
delmfrbundle
|
Add a MFR bundle using default parameters. Refer to Creating an MFR Bundle for detailed instructions on adding an MFR bundle.
|
Step 2
|
cnfmfrbundle
related commands:
addmfrbundle
cnfmfrbundle
delmfrbundle
|
Configure MFR bundle parameters. Refer to Configuring an MFR Bundle for detailed instructions on configuring an MFR bundle.
|
Step 3
|
addmfrlnk
related commands:
cnfmfrlnk
dspmfrlnk
delmfrlnk
|
Add links to the MFR bundle. Refer to Adding Links to an MFR Bundle for detailed instructions on adding an MFR link.
|
Step 4
|
addmfrport
related commands:
dspport
cnfport
delport
|
Add an MFR port. Refer to Adding a Port to the MFR Bundle for detailed instructions on adding an MFR port.
|
Step 5
|
addcon
related commands:
cnfcon
dspcon
delcon
|
Add SPVCs for the MFR service.
|
Multilink Frame Relay General Provisioning Procedures
This section contains procedures for provisioning MFR on the MPSM-T3E3-155. You create SPVCs for MFR the same way that you create Frame Relay SPVCs.
Note To support MFR, both ends of a physical link must be MFR capable, and the MFR configuration must match on both ends.
Creating an MFR Bundle
The MPSM-T3E3-155 implements MFR service using MFR bundles, which contain one or more serial links. When you add a bundle, the MPSM-T3E3-155 creates the corresponding Frame Relay data link layer interface for the service. After adding a bundle, you can then add MFR links to the bundle.
When you add a bundle using the addmfrbundle command, you specify the bundle number and activation class only; all other bundle parameters assume default values. You subsequently configure other bundle parameters using the cnfmfrbundle command. For example, after adding a Class C bundle you also need to configure the minimum number of links that must be operational before the bundle is operational.
To create an MFR bundle, perform the following steps:
Step 1 Establish a configuration session with the MPSM-T3E3-155 using a user name with GROUP1 privileges or higher.
Step 2 Create an MFR bundle using the addmfrbundle command.
M8850_SF.10.MPSM155[FR].a > addmfrbundle <bundleNum> <activationClass>
Table 2 describes the parameters for the addmfrbundle command.
Table 2 addmfrbundle Command Parameters
bundleNum
|
Bundle Number, range 1-42
|
activationClass
|
Bundle activation class:
•1=Class A—At least one bundle links must be operational for the MFR Bundle to be operational
•2=Class B—All the bundle links must be operational for the MFR Bundle to be operational
•3=Class C—Configured number of bundle links must be operational for the MFR Bundle to be operational.
|
This command creates a MFR bundle with the default configuration shown in Table 3.
Table 3 MFR Bundle Default Configuration
Parameter
|
Description
|
minimumLinks
|
Specifies the minimum number of active links required for a Class-C MFR bundle to be operational. The default value is 1 link
|
helloTimer
|
Specifies the interval in seconds at which to send hello messages. The default is 10 seconds.
|
ackTimer
|
Specifies the maximum time period to wait for an acknowledgement message from the far end. The default is 4 seconds.
|
maxRetry
|
Specifies maximum number of times to re-try sending a hello message to the far end if an acknowledgement message is not returned. The default is 2 retries.
|
bundleName
|
Identifies the near-end bundle. The default bundle name is of the form node.slot.bundle, for example M8850_SF.Slot10.Bundle03
|
The following example creates MFR bundle 3 with Class A service type using default bundle parameters:
M8850_SF.10.MPSM155[FR].a > addmfrbundle 4 3
Step 3 To verify that the MFR bundle has been created, enter the dspmfrbundle <bundleNum> command, specifying the number of the bundle.
M8850_SF.10.MPSM155[FR].a > dspmfrbundle 4
Hello Timer (seconds) : 10
Maximum Bundle Links : 12
Configured Number of Links : 0
Active Number of Links : 0
Near End Bundle Name : M8850_SF.Slot10.Bundle04
Far End Bundle Name : <not defined>
Configuring an MFR Bundle
When you add an MFR bundle, most of the configuration options are defaults (See Table 3). For example, if you want to add a bundle with a minimum number of links that is greater than one, you have to configure the minimum number of links is this procedure.
To configure an MFR bundle, perform the following steps:
Step 1 Establish a configuration session with the MPSM-T3E3-155 using a user name with GROUP1 privileges or higher.
Step 2 If the MFR bundle is administratively up, bring it down by entering the dnmfrbundle <bundleNum> command.
Step 3 Configure MFR bundle parameters using the cnfmfrbundle command.
M8850_SF.9.MPSM155[FR].a > cnfmfrbundle -bundle <bundleNum>
[-class <activationclass>] [-minlinks <minimumlinks>]
[-hellotimer <hellotimer>] [-acktimer <acktime>]
[-maxretry <maxretry>] [-bname <bundleName>]
Table 4 describes the parameters for the cnfmfrbundle command.
Table 4 cnfmfrbundle Command Parameters
Parameter
|
Description
|
-bundle
|
Identifies the MFR bundle number.
Enter the dspmfrbundles command to display all MFR bundles on the card.
|
-class
|
Bundle activation class:
•1=Class A—At least one bundle links must be operational for the MFR Bundle to be operational
•2=Class B—All the bundle links must be operational for the MFR Bundle to be operational
•3=Class C—Configured number of bundle links must be operational for the MFR Bundle to be operational.
|
-minlinks
|
Minimum number of Links for Class-C activation class, range 1-12.
|
-hellotimer
|
Interval for sending hello messages, range 1-180 seconds.
|
-acktimer
|
Maximum time period to wait for an acknowledgement from the far end, range 1-10 seconds
|
-maxretry
|
Maximum number of Retries (Maximum retries), range 1-5 retries.
|
-bname
|
Near-end bundle name:
A null-terminated string consisting of ASCII characters A-Z, a-z, 0-9 and any printable characters, with a maximum of 49 characters.
|
In the following example, the user increases the minimum number of links for a Class C MFR bundle to 4 and sets the maximum number of retries to 4.
M8850_SF.9.MPSM155[FR].a > dnmfrbundle 4
M8850_SF.9.MPSM155[FR].a > cnfmfrbundle -bundle 4 -minlinks 4 -maxretry 4
Step 4 Restore the bundle to the administrative up state by entering the upmfrbundle <bundleNum> command.
Step 5 To verify MFR bundle configuration, enter the dspmfrbundle <bundleNum> command, specifying the number of the bundle you want to display.
M8850_SF.10.MPSM155[FR].a > dspmfrbundle 4
Hello Timer (seconds) : 10
Maximum Bundle Links : 12
Configured Number of Links : 0
Active Number of Links : 0
Near End Bundle Name : M8850_SF.Slot10.Bundle04
Far End Bundle Name : <not defined>
Adding Links to an MFR Bundle
After you have established and configured an MFR bundle, you can add links to the bundle. Adding a link sends an Add-Link request message to the far-end of the bundle. A link is actively operating in a bundle only after the following conditions are met:
•An Add-Link acknowledgement is received from the Far end for the transmitted Add-Link message.
•An Add-Link request is received from the Far-end.
After both messages are received from the far-end, the MFR link is ready to transmit and receive data. Depending on the Activation Class of the bundle, the Bundle Up Indication is sent by the MFR Bundle layer to the Frame Relay Data Link layer under the following conditions.
•Class A bundles—After receiving link activation confirmation for one link.
•Class B bundles—After receiving link activation confirmation for all links in the bundle.
•Class C bundles—After a predefined number of links in the bundle confirm activation.
To add a link to an MFR bundle, perform the following steps:
Step 1 Establish a configuration session with the MPSM-T3E3-155 using a user name with GROUP1 privileges or higher.
Step 2 Bring up the links (paths) that you want to add to the MFR bundle by entering the uppath [-path_filter] <path_num> command. To display all available paths, enter the dsppaths -all command.
Step 3 Add links to the MFR bundle by entering the addmfrlnk command. The new link has a default name with the format node.card.link.
M8850_SF.10.MPSM155[FR].a > addmfrlnk <link> <bundleNum>
Table 5 describes the parameters for the addmfrlnk command.
Table 5 addmfrlnk Command Parameters
Parameter
|
Description
|
link
|
Specifies a DS1 or E1 path:
•DS3 payload: bay.line.sts:ds1
•VT payload: bay.line.sts:vtg.vt
•VT structured: bay.line.sts:tug3.vtg.vt
where: bay=1, line=1-3, sts=0-3, ds1=1-28,
tug3=1-3, vtg=1-7, vt=1-4 (VT15) or 1-3 (VT2)
Note Enter the dsppaths -all command to display all available paths on the card.
|
bundleNum
|
Bundle number, in the range 1-42
Note Enter the dspmfrbundles command to display all bundles on the card.
|
The following example adds link 1.1:11 (bay 1, DS3 1, DS1 11) to bundle 4.
M8850_SF.10.MPSM155[FR].a > addmfrlnk 1.1:11 4
Step 4 To verify that the link was added to the MFR bundle, enter the dspmfrlnk <linkNum> command, specifying the number of the bundle.
M8850_SF.10.MPSM155[FR].a > dspmfrlnk 1.1:11
Link Delay (Rtt in msec) : 0
Link Near End Name : M8850_SF.Slot10.Link11
Link Far End Name : <not defined>
Link Far End Bundle Name : <not defined>
Link PHY Operational Status : Down
Configuring MFR Links
Optionally, reconfigure the near-end name of the MFR link. Links have a default near-end name in the format node.slot.link, for example M8850_SF.Slot10.Link11.
To rename a link, perform the following steps.
Step 1 Establish a configuration session with the MPSM-T3E3-155 using a user name with GROUP1 privileges or higher.
Step 2 Reconfigure the link by entering the cnfmfrlnk command.
M8850_SF.10.MPSM155[FR].a > cnfmfrlnk -link <lnkNum> -lname <linkname>
Table 6 describes the parameters for the cnfmfrlnk command.
Table 6 cnfmfrlnk Command Parameters
Parameter
|
Description
|
-link
|
Specifies the MFR link number:
Note Enter the dspmfrlnks command to display all MFR links on the card.
|
-lname
|
Near-end link name:
A null -terminated string consisting of ASCII characters A-Z, a-z, 0-9 and any printable characters with a maximum of 49 characters.
|
In the following example, the user changes the MFR link name to M8850_SF.Slot09.Bundle04.Link11.
M8850_SF.9.MPSM155[FR].a > cnfmfrlnk -link 1.1.1:1 -lname M8850_SF.Slot09.Bundle04.Link11
Step 3 To verify MFR link configuration, enter the dspmfrlnk <lnkNum> command.
M8850_SF.10.MPSM155[FR].a > dspmfrlnk 1.1:11
Link Delay (Rtt in msec) : 0
Link Near End Name : M8850_SF.Slot09.Bundle04.Link11
Link Far End Name : <not defined>
Link Far End Bundle Name : <not defined>
Link PHY Operational Status : Down
Adding a Port to the MFR Bundle
You need to add a port to an MFR bundle to connect it to other endpoints.
To add a port to an MFR bundle, perform the following steps:
Step 1 Establish a configuration session with the MPSM-T3E3-155 using a user name with GROUP1 privileges or higher.
Step 2 Prepare to add a port to the MFR bundle:
a. Determine the bundle number on which you will add the port. To display a list of the MFR bundle numbers, enter the dspmfrbundles command.
b. Verify that the bundle and port number you want to use are not already configured. To display a list of the Frame Relay ports already configured on the MPSM-T3E3-155 card, enter the dspports command in the Frame Relay service context.
When you add a port, you must specify a port number that is unique on the MPSM-T3E3-155 card. For example, if port number (If Num) 5 is assigned, you cannot use port 5 on any other line or bundle on that MPSM-T3E3-155 card.
Step 3 Add and configure an MFR port for the MFR bundle by entering the addmfrport command:
M8850_SF.10.MPSM155[FR].a >addmfrport <ifNum> <bundle> <portType> <sct>
[-rat <rat>] [-oversub <oversub>]
[-lmiSig <lmiSigType> ] [-asynUpdt <updateType>]
[-elmi <elmiState>][-segLmi <segLmiStatus>]
[-t391 <t391Value>] [-t392 <t392Value>]
[-n391 <n391Value>] [-n392 <n392Value>][-n393 <n393Value>]
Table 7 lists the parameter descriptions for adding MFR ports.
Table 7 addmfrport Command Parameters
ifNum
|
A number for the port, in the range 1-1003.
|
bundleNum
|
The MFR bundle number, in the range 1-42.
Note Enter the dspmfrbundles command to display all MFR bundles on the card.
|
portType
|
Type of logical interface (port):
•1 = Frame Relay Service
•3 = Frame Forward (Not applicable for MFR bundles)
|
sct
|
The Service class template (SCT) for the port, range 0-255.
Default: 0
Note The port SCT file must exist and be registered on the PXM disk before it is available for use. Enter the PXM dspscts command to view all registered SCT files on the PXM card.
|
-rat
|
The egress service ratio of the high priority and the low priority queues, range 0-15.
•Enter 0 to indicate that no service ratio is configured. In this case, bandwidth is allocated to both the high priority and the low priority queues on demand, which means that traffic is dynamically allocated on a first-come, first-serve basis.
•The default setting is 1. In this case, the traffic of the CBR and rt-VBR service categories is allocated to the high priority queue, while the traffic of the nrt-VBR, ABR, and UBR service categories is allocated to the low priority queue.
|
-oversub
|
Oversubscription control:
•1 = enable
•2 = disable (default)
|
-lmiSig
|
LMI signaling protocol type:
•2 = No Signaling (default)
•3 = StrataLMI
•4 = AnnexAUNI
•5= AnnexDUNI
•6 = AnnexANNI
•7 = AnnexDNNI
Note When LMI is configured, the maximum number of connections per port for Strata LMI port is 560 and for Annex A/D UNI/NNI port is 898.
|
-asynUpdt
|
Enables or disables asynchronous updates. Asynchronous updates are an extension to the LMI protocol that notify the user immediately of changes in PVC and Multicast status. Before enabling this feature, make sure that any DTE equipment you are connected to supports asynchronous updates from the network.
Asynchronous update control:
•1 = Disable both Asynchronous Status Updates and Unsolicited Full Status (default)
•2 = Enable Asynchronous Status Updates
•3 = Enable Unsolicited Full Status
•4 = Enable Asynchronous Status Updates and Unsolicited Full Status
|
-elmi
|
Enable or disable enhanced LMI. Enhanced LMI enables the automatic exchange of Frame Relay QoS parameter information between the DTE and DCE. When enabled on both the DTE and the MPSM port, this allows the DTE device to learn QoS parameters from the frame relay port and use them for traffic shaping, configuration, or management purposes.
•1 = enable
•2 = disable (default)
|
-segLmi
|
Segmented LMI control:
•1 = enable
•2 = disable (default)
|
-t391
|
T391 timer. This is the Link Integrity Verification polling timer. The user (DTE) sends Status Enquiry messages to the network (DCE) every T391 seconds. An error is recorded if a Status message is not received within T391 seconds. The T391 counter always applies to the user equipment. It applies to the user and network if NNI bi-directional polling is present. Range 5-30. Default: 10
|
-t392
|
T392 timer. This is the Polling Verification timer. The network (DCE) expects Status Enquiry messages from the user (DTE) every T392 seconds. If the network does not receive a Status Enquiry message from the user within T392 seconds and the timer expires, then the network records a missing Status Enquiry message by incrementing the N392 counter. This timer value must be set greater than the T391 timer. The T392 timer always applies to the network. It applies to the network and user if NNI bi-directional polling is present. Range 5-30. Default: 15
|
-n391
|
N391 counter. This setting establishes the Full Status (status of all PVCs) polling cycle. The user (DTE) sends a Full Report Status Enquiry to the network (DCE) every N391 polls. The N391 counter always applies to the user equipment. It applies to the user and network if NNI bi-directional polling is present. Range 1-255. Default: 6
|
-n392
|
N392 counter. This setting specifies the UNI/NNI error threshold. This is the number of errors during N393 events that will cause an error condition. This counter should be less than or equal to the N393 counter. This counter can apply to both the user (DTE) and the network (DCE). Range 1-10. Default: 3
|
-n393
|
N393 counter. This setting is the monitored UNI/NNI events count, which must be greater than the N392 counter. N392 errors during N393 events will cause an error condition. If the N393 counter is set to a value much less than the N391 counter, the port could go in and out of an error condition without notification to either the user equipment or the network. This counter can apply to both the user (DTE) and the network (DCE). The value of this parameter should be greater than that for the -n392 parameter. Range: 1-10. Default: 4
|
Step 4 To display a list of all Frame Relay ports configured on the MPSM-T3E3-155 card, enter the dspports command in the Frame Relay service context. Port numbers are listed in the ifNum (interface number) column. If you want to view information on a particular port, note the number of that port.
In the following example, the user adds MFR port 4 to bundle number 4 with service class template 0.
M8850_SF.10.MPSM155[FR].a > addmfrport 4 4 1 0
Step 5 To verify the port, enter the dspports command:
M8850_SF.10.MPSM155[FR].a > dspports
ESR: Egress queue Service Ratio
If Line/Path Admn Oper if In Start Speed Signaling LMI 12 MFR
Num Num Stat Stat Type Use (Num) kbps ESR Type St Frg Bundle
---- ----------- ---- ---- ---- --- ------ ------ --- --------- --- --- ------
4 N/A Up LLDn FR 0 N/A 1532 1 None Off Off 4
11 1.1:1 Up Up FR 0 1(24) 1536 1 None Off Off N/A
12 1.1:2 Up Up FR 0 1(4) 256 1 None Off Off N/A
13 N/A Up Up FR 0 N/A 6131 1 None Off Off 1
21 1.2:1 Up Up FR 0 1(24) 1536 1 None Off Off N/A
22 1.2:2 Up Up FR 0 1(4) 256 1 None Off Off N/A
23 N/A Up Up FR 0 N/A 6131 1 None Off Off 2
Deleting an MFR Bundle, Link, or Port
Use the following procedure to delete an MFR bundle, link, or port.
Step 1 Establish a configuration session with the MPSM-T3E3-155 using a user name with GROUP1 privileges or higher.
Step 2 To delete an MFR port, enter the delport <ifNum> command. You must delete connections to the port before deleting the port.
Step 3 To delete an MFR link, enter the delmfrlnk <link> command. You must delete the port before deleting the last link.
Deleting a link sends a Remove-Link request message to the far-end of the link. The bundle stops transmitting data on the link after the Remove-Link request has been sent. However, data received on the link is processed until the acknowledgement for the Remove-Link request is received.
Step 4 To delete an MFR bundle, enter the delmfrbundle <bundleNum> command. You must delete all links from the bundle before deleting the bundle.
Step 5 To verify the deletion of ports, links, or bundles, enter the dspports, dspmfrlnks, or dspmfrbundles commands respectively.
Port Oversubscription on MPSM-T3/E3-155
This release adds Frame Relay port oversubscription to the MPSM-T3/E3-155 card. When enabled, the total committed information rate of all connections on the port can exceed the physical port rate. However, traffic is always limited to the physical port rate.
This feature affects the following commands:
•addport—new -oversub option to enable or disable oversubscription for a new port
•cnfport—new -oversub option to enable or disable oversubscription for an existing port
•dspport— also displays activation and oversubscription status for a port
The following table describes the oversubscription option.
-oversub <value>
|
Oversubscription control. Enter a number to enable or disable the oversubscription indicator, as follows:
•1 = enable
•2 = disable
|
Channel Loopback on MPSM-T3E3-155
Channel loopback is a feature that loops all channel traffic (data and OAM) back to the source. There are two types of loopback:
•Ingress—loops incoming line (CPE) traffic back to the line
•Egress—loops outgoing (network) traffic back to the switch
You specify the type of loopback when you activate a channel loopback. You activate, deactivate, and display channel loopbacks using the commands shown in Table 8. Channel loopback configurations are persistent, so they survive a card reset.
Table 8 MPSM-T3E3-155 Channel Loop Commands
Command
|
Description
|
addchanloop
|
Activates a channel loopback
|
delchanloop
|
Deactivates a channel loopback
|
dspchanloop
|
Displays channels in loopback
|
Restrictions
The following restrictions apply to channel loopbacks:
•A connection cannot be modified when a loopback is activated.
•A maximum of 8 connection loopbacks can be configured on MPSM-T3/E3-155 card
•Frame Relay connections support Egress loopback only.
Enhancement to Statistics Counters on MPSM-T3E3-155
The dspchancnt command now displays additional Frame Relay statistics. Frame Relay traffic is transmitted and received in AAL5 frames. Table 9 describes the AAL5 statistics for Frame Relay.
Table 9 AAL5 Statistics
Counter
|
Description
|
Rcv AAL5 frames
|
The number of ingress (line) AAL5 frames received.
|
Rcv CLP0 cells
|
The number of ingress CLP0 cells received.
|
Rcv CLP1 cells
|
The number of ingress CLP1 cells received.
|
Xmt AAL5 frames
|
The number of egress (backplane) AAL5 frames transmitted.
|
Xmt CLP0 cells
|
The number of egress CLP0 cells transmitted.
|
Xmt CLP1 cells
|
The number of egress CLP1 cells transmitted.
|
Table 10 describes the OAM statistics counters for Frame Relay.
Table 10 OAM Statistics
Counter
|
Description
|
Rcv OAM Seg Lpbk Cells
|
The number of ingress OAM segment loopback cells received.
|
Rcv OAM E2E Lpbk Cells
|
The number of ingress end-to-end OAM segment loopback cells received.
|
Xmt OAM Seg Lpbk Cells
|
The number of egress OAM segment loopback cells transmitted.
|
Xmt OAM E2E Lpbk Cells
|
The number of egress end-to-end OAM segment loopback cells transmitted.
|
Table 11 describes the ABR statistics for Frame Relay connections.
Table 11 ABR Statistics
Counter
|
Description
|
Xmt FRM cells to network
|
The number of egress Forward RM cells transmitted.
|
Xmt BRM cells to network
|
The number of egress Backward RM cells transmitted.
|
Rcv FRM cells from network
|
The number of ingress Forward RM cells received.
|
Rcv BRM cells from network
|
The number of egress Backward RM cells received.
|
Features and Enhancements in Previous Release 5.0.10
This section contains the following new features and enhancements in Release 5.0.10:
•CES Line Conditioning
•MPSM Service Modules
•PXM45 RAS
•Standard Available Bit Rate (ABR) Mapping Changes (PER 4148)
•License Management
•AXSM-16-155-XG Feeder Support
•Unique Device Identifier (UDI)
CES Line Conditioning
Previously, on a CESM card with structured ports, the line is not conditioned when an OAM AIS is received on a VC. For unstructured ports, the line is conditioned (AIS is sent on the line). Non line conditioning is a problem for applications that convert T1 to E1. For this application, a structured port of 24 time slots is created on both ends. Therefore, when the T1 line goes into alarm, the far end E1 line stays up.
This feature enables CESM-8-T1E1 and MPSM-8-T1E1 cards in CES mode to send AIS on the line if OAM AIS is received on any channel irrespective of other channels on the line. When line conditioning (lineCondition) is enabled on a connection and OAM AIS is received on the connection from the network, AIS is generated on the line. AIS generation is irrespective of other active connections on the line. Similarly, when the VC stops receiving OAM AIS from the network, AIS generation on the line is stopped. This parameter is only applicable to connections on a structured port.
The following limitations apply to CES conditioning:
1. This channel parameter is not available for configuration upload.
2. Two ends of the CES channels have enabled the line condition, and two ends of the lines have physical loop back. After removing one loop back and inserting back, two ends of the lines are stuck in alarm. The channel is also stuck in alarm.
3. Two ends of the CES channels have enabled the line condition, and two ends of the lines are connected to CPE. Two CPEs that keep having alarms and alarm recovering might cause the line to be stuck in alarm. However, this occurrence is of a very low probability.
Workaround for limitations 2 and 3 is to add a soft loop back (addnloop) to one line, or, disable the line condition from one end of the channel.
Platforms
The feature is supported on the following MGX switches:
•MGX 8850 (PXM45)
•MGX 8850 (PXM1E)
MPSM Service Modules
The MPSM is the next-generation Multi-Protocol Service Module that is intended to support Any-Service-Any-Port (ASAP) or Any-Service-Any-Card (ASAC) functionality. MPSM-8-T1E1 provides the same services currently provided by the FRSM, AUSM, and CESM Cell Bus Service Modules (CBSMs).
The following MPSM cards are supported:
•MPSM-8-T1E1
– ATM
–Frame Relay
–Circuit Emulation
–IMA
–Inline BERT testing
–ASAC
–Same 8-port backcard support as the current CBSMs (AX-RJ48-8E1, AX-RJ48-8E1, AX-SMB-8E1, AX-R-RJ48-8T1, AX-R-RJ48-8E1, AX-R-SMB-8E1)
•MPSM-T3E3-155
–ATM
–Frame Relay
–ASAP
–Inline BERT testing
–OC-3/STM-1 back card with APS support - (SFP-2-155 requires SMFIR-1-155-SFP Optics)
–T3E3 back card (BNC-3-T3E3)
MPSM Licenses
You can purchase MGX systems, spares, and MPSM licenses from www.cisco.com, specifically, http://www.cisco.com/order/apollo/configureHome.html.
Table 12 lists the MPSM licensed services that are available.
Table 12 Available Licensed Services for MPSM-8-T1E1 and MPSM-T3E3-155 Cards
Name of Licensed Service
|
Product ID of Licensed Service for MPSM-8-T1E1 Card
|
Product ID of Licensed Service for MPSM-T3E3-155 Card
|
Description
|
Multiservice
|
—
|
MPSM-MS-HS-LIC(=)
|
The Multiservice License allows simultaneous provisioning of both ATM and Frame Relay connections on the MPSM-T3E3-155 module.
One license of this type is required by a licensable service module.
|
RateControl
|
MPSM-RC-8-LIC (=)
|
MPSM-RC-HS-LIC(=)
|
MPSM-8-T1E1: The Rate Control license provides either Standard ABR or Foresight features to Frame Relay connections on the MPSM-8-T1E1 card.
MPSM-T3E3-155: The Rate Control License allows the use of a Standard ABR feature for Frame Relay connections.
One Rate Control license is required by a licensable service module.
|
Channelization
|
—
|
MPSM-CH-HS-LIC(=)
|
The Channelization License allows the physical port to support multiple DS0s for Frame Relay service and/or DS1s for ATM service.
One license of this type is required by a licensable service module.
|
Multilink
|
—
|
MPSM-ML-HS-LIC(=)
|
This license covers multilink features, which include IMA (Inverse Multiplexing for ATM) and MFR.
One license of this type is required by a licensable service module.
|
Note Redundant cards require the same licenses as the primary cards they protect. For 1:N redundancy, a redundant card needs one of each type of license used by the primary cards it protects.
MPSM licenses enable the optional MPSM features listed in Table 13. These features are enabled whenever a feature license is available in the license pool.
Table 13 Feature Options for MPSM Services
Licensed Feature
|
MPSM-8T1E1
|
MPSM-T3E3-155
|
ATM
|
Circuit Emulation
|
Frame Relay
|
ATM
|
Frame Relay
|
Rate Control
|
—
|
—
|
X
|
—
|
X
|
Channelization
|
—
|
—
|
—
|
X
|
X
|
Multiservice1
|
—
|
—
|
—
|
X
|
X
|
Multilink2
|
—
|
—
|
—
|
X
|
MFR
|
Additional information about MPSM licensing is available as follows:
•For MPSM card specifications, refer to the data sheets at http://www.cisco.com/en/US/products/hw/modules/ps2706/products_data_sheets_list.html.
•For detailed procedures about managing MPSM licenses (for example, with movelic, cnflic, and other commands), refer to Appendix F of the Cisco MGX 8850 (PXM1E/PXM45), MGX 8950, MGX 8830, and MGX 8880 Configuration Guide, Release 5 at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px45/rel5/scg/mgx5scg.pdf. For example, this appendix explains how to transfer license between nodes, and how to relieve a license alarm state.
•For additional information about MPSM cards, refer to the MGX product documentation listings at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/index.htm, starting with Release 5.
Platforms
The feature is supported on:
•
