Table Of Contents
1.1.34 Version Software Release Notes Cisco WAN MGX 8850, 8230, and 8250 Software
Features Introduced in Release 1.1.34
Power On Self Test (POST) on PXM
VISM 2.1(0) on MGX 8250/8850/8230
Features Introduced in Release 1.1.32
Support for Multiple RPM Card Types
Support for RPM-PR Module with MGX-PXM1
Feature Descriptions in Releaes 1.1.31
ForeSight and Standard ABR Coexistence Guidelines
Independent Service Rate on FRSM-HS1/B
Standard ABR on FRSM-8 and FRSM8-C Modules
VISM 2.0.0 on MGX 8230/8250/8850
Features Introduced in Release 1.1.25
Features Introduced in Release 1.1.24
Continued Support for the MGX 8850
Features Introduced in Release 1.1.23
Release 1.1.32 MGX 8850, MGX 8230, and MGX 8250 Hardware
MGX 8220 Hardware Not Supported on Release 1.1.32 of the MGX 8850
MGX 8220 Hardware That Has Been Superseded on the MGX 8850 by MGX 8850-Specific Hardware
MGX 8220 Hardware Not Supported on the MGX 8850
Features Not Supported in This Release
Major Network Management Features
ForeSight and Standard ABR Coexistence Guidelines
CLI Modifications in 1.1.34 and Prior Releases
RPM Front Card Resets on an MGX 8250 Switch
RPM-PR Back Ethernet Card Support
RPM/B Ethernet Back Card Support
CWM Recognition of RPM/PR and RPM/B Back Cards
Problems Fixed in Release 1.1.34
Problems Fixed in Release 1.1.32
Problems Fixed in Release 1.1.31
Problems Fixed in Release 1.1.25
Problems Fixed in Release 1.1.24
Problems Fixed in Release 1.1.23
MGX 8230/8250/8850 Software Interoperability with Other Products
MGX 8250/8850 Firmware Compatibility
MGX 8230 Firmware Compatibility
Special Installation and Upgrade Requirements
Special Instructions for Networks Containing FRSM 2 CT3
Single PXM Installation Procedure
Installation Procedure for Redundant PXMs
Service Module Firmware Download Procedure
Manual Configuration of Chassis Identification
Chassis Identification During a Firmware Upgrade
Service Module Installation/Upgrade and Flash Download Requirements.
Known Anomalies for Platform Software Release 1.1.34 and Service Module Firmware
Known Anomalies for Platform Software Release 1.1.32 and Service Module Firmware
Known Anomalies for RPM release 12.1(1)T
Known Anomalies for RPM Release 12.0(5)T1
RPM Configuration Examples for MPLS-based Virtual Private Networks
One PE - Two CE Configuration - OSPF & IBPG Between PEs & EBGP between PE-CE
One PE - Two CE Configuration - OSPF & IBPG Between PEs & RIP between PE-CE
One PE - Two CE Configuration - OSPF & IBPG Between PEs & STATIC ROUTES between PE-CE
Route Processor Module (RPM) Addendum
About the Cisco IOS 12.1(5.3)T_XT Release
About the Cisco IOS 12.2(2)T2 Release
Special Upgrade Requirements for RPM
General Upgrade/Downgrade Guidelines
Upgrade a RPM/B Module to RPM-PR
Install an RPM-PR Module in a Fresh Slot
Operate an RPM/B or RPM-PR in an MGX 8230 Chassis
Problems Fixed with IOS 12.1(5.3)T_XT
Obtaining Technical Assistance
Contacting TAC by Using the Cisco TAC Website
1.1.34 Version Software Release Notes Cisco WAN MGX 8850, 8230, and 8250 Software
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. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Note that for Release 1.1.34, the product documents (Command Reference, Overview, and Installation and Configuration Guides) were not updated. Use the Release 1.1.3 documents in addition to the 1.1.34 Version Software Release Notes Cisco WAN MGX 8850, 8230, and 8250 Software.
Product documentation for MGX 8850 is at:
http://cisco.com/univercd/cc/td/doc/product/wanbu/mgx8850/1_1_31/index.htm
Product documentation for MGX 8230 is at: http://cisco.com/univercd/cc/td/doc/product/wanbu/mgx8230/1_1_31/index.htm
Product documentation for MGX 8250 is at:
http://cisco.com/univercd/cc/td/doc/product/wanbu/mgx8250/1_1_31/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.1.34
Release 1.1.34 is a feature release. The following Reliability, Availability, and Serviceability (RAS) features are available for the MGX 8850, MGX 8250, and MGX 8230 with Release 1.1.34.
Online Diagnostics
The online diagnostics feature provides you with the tools to proactively monitor the hardware and software components on the PXM. While diagnostics usually focuses solely on hardware, equally critical software resources can impact network availability. The online diagnostics feature provides support in critical software areas and allows you to:
•
Run non-destructive tests on some of the hardware and software components on the PXM.
•
•
•
•
Table 1 lists the commands used to configure, run, and display the online diagnostics. More information about each command, along with examples of the command, are found in the sections that follow the table.
adddiagtest
Description
Adds a test as part of the online diagnostics on ASC.
Syntax
adddiagtest <testNumber> <testState>
Example
PXM.a > adddiagtest 1 3Test Number 1 ? "BRAM Checksum" added to Online DiagnosticsUse Unique Test ID 16 to refer to this testcnfdiagtest
Description
Modifies the parameters of a diagnostic test that is configured as part of online diagnostics.
Syntax
cnfdiagtest <Unique Test ID> <startTime> <period> <iterations>
Example
PXM.a > cnfdiagtest 10 NOW 15 -1PXM.a >Test added to start executing immediately, every 15 minutes, forever.cnfdiagtest (Contd..)Sample Output 2PXM.a > cnfdiagtest 5 12:00 1440 -1PXM.a >cnfdiagparams
Description
Modifies test input parameters of a test added as part of online diagnostics
Syntax
cnfdiagparams <Unique Test ID> <param1> <param2>
Example
PXM.a > cnfdiagparams 10 10 0PXM.a >dspdiagtests
Description
Displays the configured tests and their parameters.
Syntax
dspdiagtests
Example
PXM.a > dspdiagtestsID Test Name State Start Time Period Iteratns Param1 Param2-- ------------------------------- ------- --------------- --------- ---------- ----------- -----------1 BRAM Checksum Act/Stb FOREVER 1 FOREVER N/A N/A2 Trap Frequency Monitor Active FOREVER 1 FOREVER 50 N/A3 Hard Disk Access Standby FOREVER 1 FOREVER N/A N/A4 Framer Access Act/Stb FOREVER 1 FOREVER N/A N/AOnline Diagnostics : RUNNINGPXM.a >dspdiagresults
Description
Display the results of the configured tests.
Syntax
dspdiagresults
Example
PXM.a > dspdiagresultsID Test Name Result Pass Count Fail Count-- ------------------------------- --------- --------------- --------------1 BRAM Checksum PASS 5603 02 Trap Frequency Monitor FAIL 5602 13 Hard Disk Access PASS 5603 04 Framer Access PASS 5603 0PXM.a >clrdiagresults
Description
Clears the results of all the configured tests. To confirm that the results have been cleared, you can run the command dspdiagresults.
Syntax
clrdiagresults
Example
PXM.a > dspdiagresultsID Test Name Result Pass Count Fail Count-- ------------------------------- --------- --------------- --------------1 BRAM Checksum PASS 5603 02 Trap Frequency Monitor FAIL 5602 13 Hard Disk Access PASS 5603 04 Framer Access PASS 5603 0PXM.a >clrdiagresultsPXM.a > dspdiagresultsID Test Name Result Pass Count Fail Count-- ------------------------------- --------- --------------- --------------1 BRAM Checksum N/A 0 02 Trap Frequency Monitor N/A 0 03 Hard Disk Access N/A 0 04 Framer Access N/A 0 0PXM.a >showdiagtests
Description
Displays the list of available tests when executed without the optional parameter. When the optional parameter Test Number is used, displays the meaning of the test, as well as test parameter options.
Syntax
showdiagtests [<Test Number>]
Example 1
PXM.a > showdiagtestsTest Number Test Name------------------ ---------1 BRAM Checksum2 Hard Disk Access3 Framer Access4 CBC Access5 QE Access6 RCMP Access7 Ethernet Test8 SRM M13 Access9 DRAM Memory Availability10 SAR Buffer Availability11 CPU Performance Monitor12 Trap Frequency Monitor13 QE ASIC Error Counter Monitor14 CBC ASIC Monitor15 CBC Path TestXM.a >Example 2
PXM.a > showdiagtests 12Function : Monitors the Trap FrequencyAn Alarm is reported if Trap Frequency cross the threshold.Input Parameter : Threshold : (0 > = 0) Th4reshold for permissibletrap numbers to be sent per second.Example 3
PXM.a > showdiagtests 1Function : Performs BRAM Checksum TestInput Parameter : None.PXM.a >deldiagtest
Description
Removes a test from being executed in the background.
Syntax
deldiagtest <Unique Test ID>
Example
PXM.a > deldiagtest 1PXM.a >rundiagtest
Description
Executes an individual diagnostics test.
Syntax
rundiagtest <Test Number> <param1> <param2>
Example
PXM.a > rundiagtest 10 10 0SAR Buffer Availability PASSEDPXM.a >pausediag/resumediag
Description
The pausediag command temporarily pauses diagnostic test execution. After running this command, you can execute the dspdiagtests command; "online diagnostics" at the bottom of the display will indicate PAUSED.
Run the resumediag command to remove the pause and resume the diagnostics test.
Syntax
pausediag
Example
PXM.a > pausediagOnline Diagnostic Tests are PausedPXM.a > dspdiagtestsID Test Name State Start Time Period Iteratns Param1 Param2-- ------------------------------- ------- --------------- --------- ---------- ----------- -----------1 BRAM Checksum Act/Stb FOREVER 1 FOREVER N/A N/A2 Trap Frequency Monitor Active FOREVER 1 FOREVER 50 N/A3 Hard Disk Access Standby FOREVER 1 FOREVER N/A N/A4 Framer Access Act/Stb FOREVER 1 FOREVER N/A N/AOnline Diagnostics : PAUSEDPXM.a > resumediagclralldiagtests
Description
Deletes all tests from online diagnostics that are currently configured. Confirmation of this command can be seen by running the dspdiagtests command, which will show "No tests configured to run online."
Syntax
clralldiagtests
Example
PXM.a > clralldiagtestsCleared all Online Diagnostic testsPXM.a > dspdiagtestsOnline Diagnostics : No tests configured to run onlinePXM.a >Diagnostics Failure Reporting
The following examples show the log and card output. Both examples show the alarms generated by failed diagnostics test.
Example 1 log output
PXM.a > dsplog05/29/2001-16:19:56 08 tOnlnDiag ONLI-7-ONLNDIAG_CARDINCard in alarm: Online Diag Test SAR Buffer Availability Unique ID: 1 Failed05/29/2001-16:19:56 08 tOnlnDiag ONLI-7-ONLNDIAG_TEST_FOnline Diag Test SAR Buffer Availability Unique ID: 1 Failed05/29/2001-16:19:56 08 tOnlnDiag ONLI-7-ONLNDIAG_TEST_F Online Diag test Failed.SAR Buffer Availability Unique ID: 1 Pool: 0. PctAvlSarBuf = 99, Threshold = 100Example 2 card output
PXM.a > dspcdModuleSlotNumber: 8FunctionModuleState: ActiveFunctionModuleType: PXM1-T3E3FunctionModuleSerialNum: SBK042500A3FunctionModuleHWRev: A0FunctionModuleFWRev: 1.1.34lFunctionModuleResetReason: Upgrade ResetLineModuleType: PXM-UILineModuleState: PresentSecondaryLineModuleType: LM-BNC-2T3SecondaryLineModuleState: PresentmibVersionNumber: 0.0.22configChangeTypeBitMap: No changescardIntegratedAlarm: MinorcardMajorAlarmBitMap: ClearcardMinorAlarmBitMap: Online Diags Failure on slot 8BkCardSerialNum: SBK043601D1TrunkBkCardSerialNum: SBK0310007TFrontCardPCBNumber: 800-05760-02TrunkBkCardPCBNumber: 800-04057-02Power On Self Test (POST) on PXM
The Power On Self Tests (POST) on the PXM are destructive tests executed on key components, and are used to detect component failure. The PXM Boot code executes the POST tests, and therefore, are executed on every reset.
Because some components cannot be turned on during the bootup, POST is limited to testing the components that are on during the bootup phase.
POST Failure is reported through the CLI, log messages, card alarms, and traps.
POST Tests on PXM include:
•
•
•
•
•
•
•
•
Example 1 PXM boot capture
z16c30DevInit.DonePOST: BRAM checksum...PASSEDPOST: QE ram...PASSEDPOST: CBC ram...PASSEDPOST: Ethernet reg...PASSEPOST: PCI-IDE reg...PASSEDsysHwInit2z16c30DevInit2POST: Clock mux...PASSEDPOST: Framer access...PASSEDPOST: RCMP ram...PASSEDCopied POST results to 0x80001000, 704 bytesInitializing the disk driver .........................................
Example 2 dsppostresults and dspcd commands
Use the command dsppostresults on Active and Standby PXM to determine the POST results for the respective PXM cards.
8.PXM.s > dsppostresultsTest Description Result Detail Description---------------- ------ ------------------BRAM checksum PASSQE ram PASSCBC ram PASSEthernet reg PASSPCI-IDE reg PASSClock mux PASSFramer access PASSRCMP ram PASSUse the command dspcd to display the card alarms. Notice the alarm Post Failure on slot 8.
PXM.a > dspcdModuleSlotNumber: 8FunctionModuleState: ActiveFunctionModuleType: PXM1-T3E3FunctionModuleSerialNum: SBK042500A3FunctionModuleHWRev: A0FunctionModuleFWRev: 1.1.34lFunctionModuleResetReason: Upgrade ResetLineModuleType: PXM-UILineModuleState: PresentSecondaryLineModuleType: LM-BNC-2T3SecondaryLineModuleState: PresentmibVersionNumber: 0.0.22configChangeTypeBitMap: No changescardIntegratedAlarm: MinorcardMajorAlarmBitMap: ClearcardMinorAlarmBitMap: POST Failure on slot 8BkCardSerialNum: SBK043601D1TrunkBkCardSerialNum: SBK0310007TFrontCardPCBNumber: 800-05760-02TrunkBkCardPCBNumber: 800-04057-02Enhanced ATM-LMI
Enhanced ATM-LMI is designed to protect data traffic in the case of a ATM-LMI failure. ATM-LMI is an important protocol used between a feeder and a switch; for example, the MGX 8230 used as a feeder and connected to a BPX 8600. Motivation. Any failure of this protocol fails all the PVCs on the node; therefore, this protocol should be highly reliable and fail only for genuine reasons.
When a ATM-LMI protocol failure occurs, and enhanced ATM-LMI is enabled, the data continuity will be checked before conditioning the PVC's into alarm.
In order for the feature to provide full coverage, the similar feature must exist in the version of software running on the BPX 8600 or other ATM switch. Also, it depends on the presence of data traffic.
Use the commands cnfenhlmi and dspenhlmi to configure and display Enhanced ATM-LMI.
Syntax
cnfenhlmi <slot.port> <EnhLmiEnable> <dataContRetry>
Example
PXM.a > cnfenhlmi 7 1 Yes 5PXM.a > dspenhlmiTRK ENHANCED LMI ENABLED CNF RETRY-----------------------------------------7.1 No 0PXM.a >Buffer Allocation Priority
SAR buffers are shared by all applications on the PXM. If a low priority application operates inefficiently and overutilizes SAR buffers, it impacts higher priority and more critical applications by forcing them to operate without adequate buffers. Such conditions impact it impact network availability.
The buffer allocation priority feature distinguishes SAR buffer allocation between high priority and low priority applications. This directly supports ATM-LMI and SCM polling, both of which are considered high priority applications.
The feature is available once a successful upgrade to Release 1.1.34 is completed, and cannot be enabled or disabled.
VISM 2.1(0) on MGX 8250/8850/8230
VISM 2.1(0) is supported on MGX 8250, MGX 8230, and MGX 8850 switches for Release 1.1.34. For VISM upgrade instructions see the Release Notes for Cisco Voice Interworking Service Module Release 2.1(0).
This section describes the VoIP, ATM Adaptation Layer 2 (AAL2), and general features introduced for the VISM 2.1(0) release.
VoIP Features
The following VoIP features are included in VISM Release 2.1(0):
•
•
–
–
–
–
•
–
–
•
–
–
–
•
•
–
–
•
•
•
•
•
•
AAL2 Features
The following AAL2 features are included in VISM Release 2.1(0):
•
–
–
•
•
–
–
–
•
–
–
–
•
–
–
–
•
•
•
•
–
–
•
•
–
–
•
•
•
•
•
General Features
The following general features are included in VISM Release 2.1(0):
•
Graceful upgrade VISM 2.0 and 2.0(1) to VISM 2.1(0).
About the 1.1.32 Release
This is a maintenance release including all features supported up to release 1.1.25.
Features Introduced in Release 1.1.32
Feature Descriptions
Note
Support for Multiple RPM Card Types
When multiple RPM card types are present in the network, the PXM1 will recognize and display the correct RPM card type. The current RPM card types are RPM/B and RPM-PR. The MGX 1.1.32 Release contains PXM code base changes that recognize the multiple RPM card types.
Support for RPM-PR Module with MGX-PXM1
The RPM-PR provides the following features:
•
•
•
•
The higher-performance RPM requires Software Release 1.1.32, IOS version12.1(5.3)T_XT, and a minimum CWM version of 10.4.01.
Support for RPM/B in MGX 8230
Installation of the RPM/B in the MGX 8230 requires Release 1.1.32 and IOS version 12.1(5.3)T_XT
.
Note
Features Introduced in Release 1.1.31The following features are available for the MGX 8850, MGX 8250, and MGX 8230 with Release 1.1.31 and IOS 12.1(3)T:
Feature Descriptions in Releaes 1.1.31
For descriptions of the features introduced in Release 1.1.31, see the following sections:
•
•
•
•
•
CoS Map for FRSM-8
This feature implements the ATM Class of Service (CoS) on the FRSM-8 Module. This feature maps the connection with ATM Class of Service parameters to the appropriate queue in the ingress side of the FRSM-8 and PXM.
Previous versions do not support any CoS type of connections; only ForeSight and non-ForeSight type connections are supported. By mapping the CoS parameters, the connections can then be scheduled in the appropriate queue on the PXM.
The following service types are added to the existing service types: UBR, VBR, VBR-RT, VBR-nRT, and STD-ABR. The current limit on connection count is to be retained as far as possible. This feature is supported by CWM 10.3 (which is not targeted for General Availability).
DS3 Loopback on PXM-T3
This feature enables the active PXM to initiate the DS3 loopback code (program the T3 framers to generate the sequence of 16 bit FEAC codes, or Far End Alarm and Control codes). The main functions are:
•
•
The active PXM will initiate this code, which will also run on the standby PXM. This feature has CLI support and is supported by CWM 10.3 (which is not targeted for General Availability).
Stratum-3 Clocking
Standard clocking in the MGX is supported with a built-in Stratum-4 clock source. For network applications that require a higher clock accuracy, the PXM-UI back card used with the Stratum-4 can be replaced with an optional PXM-UI-S3 back card that carries a Stratum-3 clock. This clock reference conforms to AT&T T1.5 and ITU G.824 specifications. A provision is also made for a Service Provider to connect an external clock source, if necessary.
Both holdover and fail-over modes are supported by the PXM-UI-S3. That is, if all clock sources fail, the Stratum-3 clock will hold the last best-known clocking frequency.
The default clock is the internal Stratum-4. Pertinent CLI and MIB support are provided for Stratum-3 configuration. The PXM-UI-S3 back card is also recognized by the Cisco WAN Manager.
Hardware Changes
A new PXM-UI-S3 back card replaces existing PXM-UI-B cards.
The new PXM-UI-S3 supports both T1 and E1 interfaces through an RJ-45/48 connector.
CLI
A new CLI cnfclklevel permits the user to set the STRATUM level desired.
Default Settings
The default clock source is set to be the Internal Oscillator. Subsequently, an External/Inband/SM clock can be configured to be the primary/secondary clock driving the node.
Limitations
There are two physical ports on the PXM-UI-S3 back card for providing External clock. However, only "Ext Clk 1" is currently supported. There are 2 physical LAN ports on the PXM-UI-S3 back card. However, only "LAN port 1" is currently supported.
Warning
* cnfclklevel 3
* cnfextclk (with T1/E1 option)
ForeSight and Standard ABR Coexistence Guidelines
With Release 1.1.31, both ABR TM4.0 and ForeSight congestion control are supported on the FRSM and AUSM modules. This document contains the following:
•
•
•
Independent Service Rate on FRSM-HS1/B
This feature provides the capability to configure a connection service rate in the ingress direction. Users can also specify EIR if connection is "0" of CIR. This feature is already implemented in FRSM-8 and FRSM-VHS.
This functionality is the same as that provided in FRSM-8 and FRSM-VHS. This feature is not supported by CWM 10.3 (which is not targeted for General Availability).
Online Diagnostics for PXM
This feature provides hardware tests to check the health of the SRM and PXM modules (both active and standby). This test is non-intrusive and operates with minimum overhead while the shelf is running. Connections, states and tasks are not affected.
The Online Diagnostics are optional tests operated through CLI and SNMP interfaces. The test is invoked from the active PXM. If a standby PXM exists and is in standby state, it also will be tested. When the test is executed, each component is checked and the results are presented on the screen. The results of the diagnostics are written to a log file so they can be viewed and analyzed offline.
Initially, intelligence is not provided, but built-in intelligence may be considered as a future enhancement. The hardware and software components selected for running the diagnostics will be selected from field experience. The targets are hard disk and memory components. Although the intent is to check the health of the hardware, a switchover should not occur except under severe circumstances.
SRM in MGX 8230
This feature provides SRM support in the MGX 8230. Only the newest version of the SRM, MGX-SRM-3T3/C, is supported in the 8230 chassis. This feature is not supported by CWM 10.3 (which is not targeted for General Availability), but is planned for a future release.
Standard ABR on AUSM
This feature involves implementing the standards-based TM 4.0 ABR congestion control loop. The current AUSM-8 card only supports ForeSight, which is pre-standards-based. Standard ABR is required on AUSM cards in order for them to interoperate with third-party devices that support standard ABR and AXSM cards.
Support for standard ABR calls for implementing the RM cells to perform the flow control. All three modes are considered: EFCI, ER, and RR. Only modes that can be supported on the existing hardware are implemented. In addition, all appropriate behaviors are implemented. These behaviors include Source, Destination, and Switch. Connections with the standard ABR parameter are mapped to the appropriate queue. This feature includes new CLI and MIB support. Also expected for the CWM support is the appropriate formula. Due to current hardware limitation, VS/VD is not considered. This feature is supported by CWM 10.3 (which is not targeted for General Availability).
Standard ABR on FRSM-8 and FRSM8-C Modules
The feature implements TM 4.0 ABR service on the FRSM card. The current FRSM supports ForeSight, a pre-standard version of congestion control. This feature provides standards-compliant ABR congestion mechanism in addition to ForeSight. The module will generate RM cells to dynamically increase or decrease bandwidth rate. This includes all applicable modes of behavior: Source, Destination, and Switch. Only relevant modes need be considered. Connections with the standard ABR parameter will be mapped to the appropriate queues and will co-exist with ForeSight connection types.
This feature is implemented via appropriate MIBS and CLI. This feature is supported by CWM 10.3 (which is not targeted for General Availability). ABR license (similar to ForeSight license) is created and is a billable feature. One common license is available for either ForeSight or standard ABR on FRSM. Standard ABR fulfils the standards-compliance part of TM 4.0.
VBR-rt on AUSM
This feature involves implementing the standard Class of Service on the AUSM-8 Module. VBR-rT CoS is required for video and real time voice applications. In terms of conformance definition it is same as VBR-nRT, which is already supported. The connection parameters will be bounded by Peak Cell rate (PCR), Sustainable Cell Rate (SCR) and Maximum Burst Size (MBS). Cell Delay Variation Tolerance (CDVT) will be parameter to characterize the PCR.
This new CoS requires scheduling the appropriate queue in both the ingress and egress direction. It has lower priority than CBR but higher than VBR-nRT.
Appropriate CLI commands to configure the parameters are implemented. This feature is supported by CWM 10.3 (which is not targeted for General Availability).
VISM 2.0.0 on MGX 8230/8250/8850
VISM 2.0.0 supports all of the VISM 1.5.05 features listed above. VISM 2.0.0 is supported on MGX 8230/8250/8850. CWM 10.3 (which is not targeted for General Availability) supports VISM 2.0.0. VISM is not targeted for General Availability.
PRI Backhaul to the Softswitch Using RUDP
The PRI backhaul capability provides PRI termination on the VISM with the Softswitch providing call control. ISDN Layer 2 is terminated on the VISM and the layer 3 messages are transported to the Softswitch using RUDP.
Latency Reduction (<60 ms round-trip)
Significant improvements have been made to bring the round-trip delay to less than 60 ms.
Codecs Preference
VISM provides the capability to have the codecs negotiated between the two end-points of the call. The VISM can be configured, for a given end-point, to have a prioritized list of codecs. Codec negotiation could be directly between the end-points or could be controlled by a Softswitch
31 DS0 for E1 with 240 Channels Only
While all 31 DS0s on a E1 port can be used, there is a limitation of 240 channels per card.
VISM 1.5.05 on MGX 8250/8850
VISM 1.5.05 is supported on MGX 8250/8850. For VISM on MGX 8230, please use VISM 2.0.0 listed below. CWM 10.3 (which is not targeted for General Availability) supports VISM 1.5.05. VISM is not targeted for General Availability.
VoIP using RTP (RFC 1889)
VISMR1.5 supports standards-based VoIP using RTP (RFC1889) and RTCP protocols. This allows VISM to interwork with other VoIP Gateways.
VoAAL2 (With sub-cell multiplexing) PVC
The VISM supports standards-compliant AAL2 adaptation for the transport of voice over an ATM infrastructure. AAL2 trunking mode is supported.
Codec Support
G.711 PCM (A-law, Mu-law), G.726, G.729a/b
8 T1/E1 Interfaces
The VISM supports 8 T1 or 8 E1 interfaces when G.711 PCM coding is used. For higher complexity coders such as G.726-32K and G.729a-8K, the density drops to 6 T1 or 5 E1 interfaces (max 145 channels).
1:N redundancy using SRM.
T3 Interfaces (via SRM Bulk Distribution)
T3 interfaces are supported using the SRM's bulk distribution capability. In this case, the T3 interfaces are physically terminated at the SRM module. The SRM module breaks out the individual T1s and distributes the T1s via the TDM backplane bus to the individual VISM cards for processing.
Echo Cancellation
The VISM provides on-board echo cancellation on a per-connection basis. Up to 128 msec. user-configurable near-end delay can be canceled. The echo cancellation is compliant with ITU G.165 and G.168 specifications.
Voice Activity Detection (VAD)
VISM uses VAD to distinguish between silence and voice on an active connection. VAD reduces the bandwidth requirements of a voice connection by not generating traffic during periods of silence in an active voice connection. At the far-end, comfort noise is generated.
Fax/Modem Detection for ECAN and VAD Control
The VISM continually monitors and detects fax and modem carrier tones. When carrier tone from a fax or modem is detected, the connection is upgraded to full PCM to ensure transparent connectivity. Fax and modem tone detection ensures compatibility with all voice-grade data connections.
CAS Tunneling via AAL2 (For AAL2 Trunking Mode)
The VISM in AAL2 mode facilitates transport of CAS signaling information. CAS signaling information is carried transparently across the AAL2 connection using type 3 packets. In this mode, VISM does not interpret any of the signaling information.
PRI Tunneling via AAL5 (For AAL2 Trunking Mode)
VISM supports transport of D-ch signaling information over an AAL5 VC. The signaling channel is transparently carried over the AAL5 VC and delivered to the far-end. In this mode, VISM does not interpret any of the signaling messages.
Voice CAC
VISM can be configured to administer Connection Admission Control (CAC) so that the bandwidth distribution between voice and data can be controlled in AAL2 mode.
Type 3 Packet for DTMF
The VISM in AAL2 mode facilitates transport of DTMF signaling information. DTMF information is carried transparently across the AAL2 connection using type 3 packets.
Dual (Redundant) PVCs for Bearer/Control
The VISM provides the capability to configure two PVCs for bearer/signaling traffic terminating on two external routers (dual-homing). VISM continually monitors the status of the active PVC by using OAM loopback cells. Upon detection of failure, the traffic is automatically switched over to the backup PVC.
64 K Clear Channel Transport
The VISM supports 64 Kbps clear channel support. In this mode, all codecs are disabled and the data is transparently transported through the VISM.
DTMF Relay for G.729
In VoIP mode, DTMF signaling information is transported across the connection using RTP NSE (Named Signaling Event) packets
MGCP 0.1 for VoIP with Softswitch Control
VISM supports Media Gateway Control Protocol (MGCP) Version 0.1. This open protocol allows any Softswitch to interwork with the VISM module.
Resource Coordination via SRCP
Simple Resource Control Protocol (SRCP) provides a heartbeat mechanism between the VISM and the Softswitch. In addition, SRCP also provides the Softswitch with gateway auditing capabilities.
Full COT Functions
VISM provides the capability to initiate continuity test as well as provide loopbacks to facilitate continuity tests when originated from the far-end.
Courtesy Down
This feature provides a mechanism for graceful upgrades. By enabling this feature, no new calls are allowed on the VISM while not disrupting the existing calls. Eventually, when there are no more active calls, the card is ready for a upgrade and/or service interruption.
Features Introduced in Release 1.1.25
None.
Features Introduced in Release 1.1.24
While no new features are incorporated into Software Release 1.1.24, this software release does provide support to two new wide area switches, the MGX 8230 and the MGX 8250, as well as continued support for the MGX 8850 switch.
Guest
