Table Of Contents
Configuring the J1 Byte TxTrace Option on AXSM-XG Cards
Disabling SSHV1, FTP, and Telnet on MGX
SNMP and STATS Support for Card Uptime
SNMP Support for resetcd, switchcc, and switchredcd
Command for Grouping the Output of Existing Commands
Command for Displaying Configuration Information
Command for Displaying Statistics Information
MultiVC Access to PXM Through Nonredundant RPM-XF
Hardware and Resource Monitoring on MPSM-155 Cards
Commands for Hardware and Resource Monitoring
Traps for Hardware and Resource Monitoring
Detecting Parity Error on a Standby AXSM
Refreshing the AXSM Virtual Connection Table
Support for Back Card Status Message
Support for TACACS Challenge Messages
Support for AXSM-16-T3E3/B Card in 8830/B Chassis with PXM45C
Bidirectional Forwarding Detection Version 1
DSCP Marking on RPM-XF Management Interface
Support for AXSM-1-2488/B Card in 8830/B Chassis with PXM45C
Support for Clear Channel E1 Lines
Support for BERT Tests on Clear Channel T3/E3 Lines
Non-Redundant Upgrade Procedure
Cisco MGX 8800 Series Operating and Storage Environment
Guidance for Operating and Storage Environments
Operating Environment Specifications
Non-operating and Storage Environment Specifications
Multilink Point-to-Point Protocol Enhancements for CDMA2000 and EV-DO
Fractional T1/E1 Links for ATM Services
Fractional T1/E1 Configuration
Fractional T1/E1 Configuration Limitations
Remote IP Management Connection Enhancements
Management Connection Limitations
Configuring an RPM Management Connection
Management Configuration—Example
Routing Enhancement for AXSM-XG Cards
Graceful Upgrades to AXSM-XG Cards
Multilink PPP on the MPSM-T3E3-155 Card
PXM45/C Support in the Cisco MGX 8830/B Chassis
Compression and Multiplexing Support for RPM-PR Cards
Multilink PPP Feature for CDMA2000 and EV-DO
MPSM-155-T3E3 and MPSM-16-T1E1 Online Diagnostics
Private Network Node Interface Current Route Feature
Operational and Redundancy Limitations
Software/Firmware Compatibility Matrix
MGX and RPM Software Version Compatibility Matrix
Product IDs, Card Types, and APS Connectors
Service Class Template File Information
New Commands in Release 5.5.00
Changed Commands in Release 5.5.00
Changed Commands in Release 5.4.00
Changed Commands in Release 5.3.20
Changed Commands in Release 5.3.00
MGX Release 5.5.00 Limitations, Restrictions, and Notes
MGX Chassis Bandwidth Limitations
PXM1E Reserved Virtual Channel Identifiers
PXM1E Point to Multipoint Support
PXM45 and PXM1E System Limitations
Clearing the Configuration on Redundant PXM45 and PXM1E Cards
SPVC Interoperability Limitations
AXSM-16-155-XG with MCC Back Card Limitations
AXSM-32-T1E1-E and PXM1E-16-T1E1 Card Limitations
Clearing Card Configuration Notes
Persistent Topology Limitations
Fault Isolation and Trace Limitations
Serial Bus Path Fault Isolation Limitation
Cell Bus Path Fault Isolation and Recovery Limitations
Path and Connection Trace Notes
Non-native Controller Front Card and PXM-HD Card Notes
Other Limitations and Restrictions
Installation and Upgrade Procedures
Online Insertion or Removal of the MGX-RPM-1FE-CP Back Card
Known Route Processor Module or MPLS Caveats
Cisco PNNI Network Planning Guide for MGX and SES Products Updates
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Software Release 5.5.00
Revised: November 14, 2008, OL-13646-01Contents
The content of this document is arranged into the following major sections:
Configuring the J1 Byte TxTrace Option on AXSM-XG Cards
Disabling SSHV1, FTP, and Telnet on MGX
SNMP and STATS Support for Card Uptime
SNMP Support for resetcd, switchcc, and switchredcd
MultiVC Access to PXM Through Nonredundant RPM-XF
Hardware and Resource Monitoring on MPSM-155 Cards
Detecting Parity Error on a Standby AXSM
Refreshing the AXSM Virtual Connection Table
Support for Back Card Status Message
Support for TACACS Challenge Messages
Support for AXSM-16-T3E3/B Card in 8830/B Chassis with PXM45C
Bidirectional Forwarding Detection Version 1
DSCP Marking on RPM-XF Management Interface
Support for AXSM-1-2488/B Card in 8830/B Chassis with PXM45C
Support for Clear Channel E1 Lines
Support for BERT Tests on Clear Channel T3/E3 Lines
Non-Redundant Upgrade Procedure
Cisco MGX 8800 Series Operating and Storage Environment
Guidance for Operating and Storage Environments
Operating Environment Specifications
Non-operating and Storage Environment Specifications
Multilink Point-to-Point Protocol Enhancements for CDMA2000 and EV-DO
Fractional T1/E1 Links for ATM Services
Fractional T1/E1 Configuration
Fractional T1/E1 Configuration Limitations
Remote IP Management Connection Enhancements
Management Connection Limitations
Configuring an RPM Management Connection
Management Configuration—Example
Routing Enhancement for AXSM-XG Cards
Graceful Upgrades to AXSM-XG Cards
Multilink PPP on the MPSM-T3E3-155 Card
PXM45/C Support in the Cisco MGX 8830/B Chassis
Compression and Multiplexing Support for RPM-PR Cards
Multilink PPP Feature for CDMA2000 and EV-DO
MPSM-155-T3E3 and MPSM-16-T1E1 Online Diagnostics
Private Network Node Interface Current Route Feature
Operational and Redundancy Limitations
Software/Firmware Compatibility Matrix
MGX and RPM Software Version Compatibility Matrix
Product IDs, Card Types, and APS Connectors
Service Class Template File Information
Changed Commands in Release 5.4.00
Changed Commands in Release 5.3.20
Changed Commands in Release 5.3.00
MGX Release 5.5.00 Limitations, Restrictions, and Notes
MGX Chassis Bandwidth Limitations
MGX Chassis Bandwidth Limitations
PXM1E Reserved Virtual Channel Identifiers
PXM1E Point to Multipoint Support
PXM45 and PXM1E System Limitations
Clearing the Configuration on Redundant PXM45 and PXM1E Cards
SPVC Interoperability Limitations
AXSM-16-155-XG with MCC Back Card Limitations
AXSM-32-T1E1-E and PXM1E-16-T1E1 Card Limitations
Clearing Card Configuration Notes
Persistent Topology Limitations
Fault Isolation and Trace Limitations
Serial Bus Path Fault Isolation Limitation
Cell Bus Path Fault Isolation and Recovery Limitations
Path and Connection Trace Notes
Non-native Controller Front Card and PXM-HD Card Notes
Other Limitations and Restrictions
Installation and Upgrade Procedures
Online Insertion or Removal of the MGX-RPM-1FE-CP Back Card
Obtaining Documentation, Obtaining Support, and Security Guidelines
About This Release
These release notes describe the system requirements, new features, and limitations that apply to Release 5.5.00. These notes also contain Cisco support information.
Release 5.5.00 is a software release for the following Cisco multiservice switches (MGXs):
•
Cisco MGX 8830 (Processor Switch Module, or PXM1E)
•
•
•
•
Note
Locating Software Updates
Release 5.5.00 software is located at:
http://www.cisco.com/public/sw-center/wan/wan-planner.shtml
Route Processor Module (RPM) Cisco IOS software images are located at:
http://www.cisco.com/public/sw-center/sw-ios.shtml
New Features
Release 5.5.00 includes the following new features for the Cisco MGX platforms:
•
•
•
•
•
•
•
•
•
•
•
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:
Unknown.12.AXSM-XG[ATM].a > cnftxtraceopt 1For more information about the commands, refer to the section New and Changed Commands
Note
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:
•
•
For more information about the commands, refer to the section New and Changed Commands.
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:
•
•
•
•
Limitations
•
•
–
–
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:
•
•
For more information about the commands, refer to the section New and Changed Commands.
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
•
•
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.
The following example displays the command output:
Saras.8.PXM.a > dspenvalmsSaras System Rev: 05.03 May. 16, 2007 18:02:08 GMTMGX8850 Node Alarm: MAJORENVIRONMENTAL ALARM STATE INFO ^Notification Disabled *Alarm DetectedAlarm Type Unit Threshold DataType Value State---------------- ---- -------------- -------- ---------- -------------Temperature <= 50 Celsius 32 NormalPower Supply A1 none None none MissingPower Supply A2 none None none MissingPower Supply A3 none None none NormalDC Voltage A 42 to 58 VoltsDC 0 IndeterminatePower Supply B1 none None none MissingPower Supply B2 none None none NormalPower Supply B3 none None none MissingDC Voltage B 42 to 58 VoltsDC 0 IndeterminateSNMP 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:
•
•
•
•
•
•
•
•
•
The following cards support STATS:
•
•
•
•
•
•
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:
•
•
•
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 in the CISCO-ENTITY-REDUNDANCY-MIB.my are:
•
•
•
•
Limitations
•
•
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:
dspcd
dspchancnt <connection> <interval> (for every connection)
dspcons
dsplns
dspmpbundles
dspmpbundle <bundle> (for every bundle)
dsppaths -all
dspppplinks
dspppplink <link> (for every link)
dsprmalms
dsptotals
logConsoleShow
For more information about the command, refer to the section New and Changed 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:
•
•
Command for Displaying Configuration Information
The command dspbundleconfiginfo displays the configuration information related to the following:
•
•
•
•
The following commands are used for displaying the output:
•
•
•
•
Command for Displaying Statistics Information
The command dspbundlestatsinfo displays the statistics information related to the following:
•
•
•
•
The following commands are used for displaying the output:
•
•
•
•
Note
For more information about the commands, refer to the section New and Changed Commands.
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.
For configuration information, refer to Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.5.00.
Limitations
The following limitations apply:
•
•
•
•
•
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:
•
•
The following hardware devices are monitored on an MPSM-155 card:
•
•
•
•
Note
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:
•
•
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:
•
•
•
For more information about the commands, refer to the section New and Changed Commands.
Traps for Hardware and Resource Monitoring
The Hardware Error Report trap is raised by HMM under the following conditions:
•
•
•
•
No new traps are added. The existing trap, cwHardwareErrorReport, is used for sending traps.
The RM raises the Resource Update Report trap when a change of state is detected for a resource. The existing trap, cwModuleOsRsrcUpdate, is used for reporting the state of change.
Detecting Parity Error on a Standby AXSM
On an AXSM card, the queuing engine QE48 maintains the virtual connection table (VCT). In rare instances, parity errors occur in VCT memory. This leads to failure of the active AXSM card and, subsequently, the standby card.
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
Note
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
Limitations
The following limitations apply:
•
•
•
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
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.00.
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:
•
•
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:
•
•
•
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:
•
•
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
Release 5.3.20 has the following new and changed features:
•
•
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.
Note
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:
•
–
–
–
–
–
–
•
–
–
–
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 9M8850_SF.27.MPSM16T1E1[FR].a > addport 11 1.10 1 0M8850_SF.27.MPSM16T1E1[FR].a > addcon 11 400 1 1 2 2048000For 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:
•
•
•
•
•
•
•
•
•
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
<
Guest
