 Feedback
|
Table Of Contents
1.1.35 Version Software Release Notes Cisco WAN MGX 8850, 8230, and 8250 Software
Features Introduced in Release 1.1.35
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.35 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.35
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.35 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.35, 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.35 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.35
None. This is a maintenance release including all features supported up to release 1.1.34.
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.
MGX 8230
The MGX 8230 functions as a feeder to the IGX, BPX, or MGX 8850 switches, or can be used for bringing in service. It has a seven slot (double-height) chassis, and the slots are oriented in the following manner:
•
•
•
Figure 1 shows the MGX 8230 with its door attached. Note that there are light pipes in the door that display the status of the processor models (PXMs). Figure 2 is a conceptual drawing of an MGX 8230 showing the dimensions and the slot numbering. The slot numbering is as it appears from the front of the MGX 8230; slots 8 and 9 refer to back card slots only.
Note that the following features are not supported in 1.2xx baseline:
•
•
•
•
Note
Figure 1 MGX 8230 with Door Attached
Figure 2 MGX 8230 Dimensions
Note
Main Features
Release 1.0 of MGX 8230 includes:
•
–
–
–
–
–
•
•
–
–
–
–
–
–
–
•
•
•
•
The MGX 8230 backplane supports a minimum of 1.2 Gbps of non-blocking switching and has a high-end limit of 21 Gbps with the PXM1. Individual line rates can range from DS0 through OC-3.
The MGX 8230 can also support a wide range of services over narrowband and mid-band user interfaces. It maps all the service traffic to and from ATM circuits based on standardized interworking methods.
The MGX 8230 supports up to 64 channelized or non-channelized T1 and E1 interfaces on a single IP + TM multiservice gateway. These interfaces support:
•
•
•
•
•
Frame-based services on T3 and E3 high-speed lines are also supported.
The MGX 8230 also supports Inverse Multiplexing for ATM (IMA) to provide ATM connectivity below T3 or E3 rates via the AUSM-8T1/E1 (AUSM/B).
The modular, software-based system architecture enables it to support new features through downloadable software upgrades or new hardware modules.
The Service Resource Module-3T3 (MGX-SRM-3T3/B), when supported in a future release, will be able to support up to 64 T1 interfaces over its three T2 lines and provide 1:N redundancy for the T1 and E1 cards. This feature is described in the MGX 8230 switch documentation, but is currently not supported by the hardware.
Standards-Based Conversion to ATM
The MGX 8230 converts all user-information into 53-byte ATM cells by using the appropriate ATM Adaptation Layer (AAL) for transport over the ATM backbone network. The individual service modules segment and reassemble (SAR) cells to eliminate system bottlenecks. The following list shows the applicable AAL for each service:
•
•
•
•
Refer to the Cisco MGX 8230 Installation and Configuration Guide for further installation and physical descriptions for the MGX 8230 switch.
MGX 8230 Cards
MGX 8230 Processor Switch Module (PXM1)
The MGX 8230 Processor Switch Module (PXM1) performs shelf control and shared-memory switching functions. It also serves as a data processing and ATM interface card. The PXM1 processor module for the MGX 8230 is identical to the PXM1 for the MGX 8250.
Primarily, the MGX 8230 PXM1 controls the switch and provides 1.2 Gbps of non-blocking, shared memory ATM switching and ATM trunking up to OC-12 speed. In addition, the PXM features:
•
•
•
The PXM1 and its two types of back cards make up the required control card set. The following are model numbers of cards supported by the MGX 8230 for this release:
The following are model numbers of cards supported by the MGX 8230 for this release:
•
•
•
•
•
•
•
•
•
PXM1 User Interface Back Card
The PXM1 User Interface card (PXM-UI) provides the MGX 8230 with the several user- interface ports. It mates with an PXM1 through the backplane and is installed in a back card slot (slot 8 or 9). As seen from the back of the MGX 8230, the PXM-UI will plug into the slot that is on the right side of its corresponding PXM1. The user-interface ports provide the following functions:
•
•
•
The PXM UI has the following physical connectors and interfaces:
•
•
•
•
•
•
MGX 8230 OC-3 Uplink Back Card
The MGX 8230 Uplink back card, which mates with a corresponding PXM1 through the backplane, provides the feeder trunk to the MGX switch. This uplink back card can provide either a multi-mode or single-mode fiber OC-3 interface:
•
•
•
FRSM Cards
The primary function of the FRSM is to convert between the Frame Relay-formatted data and ATM/AAL5 cell-formatted data. It converts the header format and translates the address for Frame Relay port/DLCIs, ATM-Frame UNI (FUNI) port/frame address, or frame forwarding port, and the ATM virtual connection identifiers (VPI/VCIs).
The MGX 8230 supports the following FRSM models:
•
The FRSM-8T1 card provides interfaces for up to eight T1 lines, each of which can support one
56 Kbps or one Nx64 Kbps FR-UNI, FR-NNI port, ATM-FUNI, or a frame forwarding port.
Note that this unchannelized card cannot be configured to support sub-T rates.•
The FRSM-8T1-C card provides interfaces for up to eight T1 lines, each of which can support up to twenty-four 56 Kbps or Nx64 Kbps FR-UNI, FR-NNI, ATM-FUNI, or frame forwarding ports.•
The FRSM-8E1 card provides interfaces for up to eight E1 lines, each of which can support one
56 Kbps or one Nx64 Kbps FR-UNI, FR-NNI, ATM-FUNI, or frame forwarding port.•
The FRSM-8E1-C card provides interfaces for up to eight E1 channelized Frame Relay lines, each of which can support multiple (up to thirty-one) 56 Kbps or Nx64 Kbps FR-UNI, FR-NNI, ATM-FUNI, or frame forwarding ports.•
The FRSM-2E3/T3 card provides interfaces for up to two T3 or E3 Frame Relay lines, each of which can support either two T3 lines (each at 44.736 Mbps) or two E3 lines (each at 34.368 Mbps) FR-UNI, FR-NNI, ATM-FUNI, or frame forwarding ports.•
The FRSM-2CT3 card supports interfaces for up to two T3 channelized Fame Relay lines, each of which supports 56 Kbps, 64 Kbps, Nx56 Kbps, Nx64 Kbps, T1 ports for a total of 256 ports that can be freely distributed across the two T3 lines.•
The FRSM-HS2 provides unchannelized Frame Relay service for up to 1000 user-connections over two HSSI lines on the SCSI2-2HSSI back card. The maximum rate for the card is 104 Mbps. Each port can operate in either DTE or DCE mode with incremental rates of N x T1 or N x E1 up to
52 Mbps.OC-12 Uplink Back Card
For Automatic Protection Switching (APS) requires the "B" model—an SMFLR-1-622/B.
SMFIR-1-622 Back Card
For Automatic Protection Switching (APS) requires the "B" model—an SMFIR-1-622/B.
BNC-2T3 Back Card
BNC-2E3 Back Card
Two versions of the BNC-2E3 card are available. The BNC-2E3A applies to Australia only, and the BNC-2E3 applies to all other sites that require E3 lines on the PXM uplink card.
ATM Universal Service Module
AUSM/B Front Card
AUSM/B Back Cards
The MGX-AUSM/B-8T1 and MGX-AUSM/B-8E1 use the generic 8-port T1 or E1 line modules that operate with the 8-port service modules. The standard T1 version of the back card has eight RJ-48 connectors. The standard versions of the E1 back card have either eight RJ-48 connectors or eight pairs of SMB connectors. The following back cards are compatible with the AUSM/B:
•
•
•
Circuit Emulation Service Module 8T1E1
CESM Models
The MGX 8230 supports the following CESM models:
•
The CESM-8T1 card provides interfaces for up to eight T1 lines, each of which is a 1.544 Mbps structured or unstructured synchronous data stream.•
The CESM-8E1 card provides interfaces for up to eight E1 lines, each of which is a 2.048 Mbps structured or unstructured synchronous data stream.•
The CESM-8T1E1 card set consists of the CESM-8T1E1 front card and one of the following back cards:
•
•
•
Redundancy Architecture
Since the MGX 8230 chassis is a smaller form factor MGX 8850, most of the redundancy features available in MGX 8850 are available in MGX 8230 chassis. The following is a list of available redundancy features on the MGX 8230 chassis.
•
•
•
•
•
•
•
MGX 8230 Management
To give you access for control purposes, the MGX 8230 switch supports high- and low-level user interfaces. You can use the Cisco WAN Manager application (formerly StrataView Plus) for connection management, the CiscoView application for hardware configuration, and a command line interface for low-level control of hardware functionality and connection control. An assortment of ports and protocols supports these user-interfaces. For communicating with the MGX 8230 switch, the control port (SLIP protocol only), the LAN (Ethernet) port, and the in-band ATM connection (feeder application only) all support access by the command line interface (CLI) via Telnet, TFTP, and SNMP protocols.
The downloadable firmware on each card determines the functionality, and you can upgrade functionality by downloading new firmware through a TFTP application on a workstation or a PC.
The current status and configuration parameters of the MGX 8230 modules reside in a Management Information Base (MIB). The firmware on each card updates the MIB as changes in status and configuration occur.
MGX 8250
The Cisco MGX 8250 wide-area edge switch supports:
•
•
•
•
•
It does not support PNNI, despite the fact that some CLI commands may show options for PNNI.
This chapter contains a brief outline of the features of the Cisco MGX 8250 switch. An illustration of the AC-powered version of the switch appears in Figure 3.
Figure 3 MGX 8250 Switch
The Applications of the MGX 8250 Switch
The MGX 8250 switch operates in two operational applications:
•
•
For a description of how to configure the switches for a particular application, see the MGX 8250 Switch Installation and Configuration Guide.
The switch is also capable of supporting Cisco Multiprotocol Label Switching (MPLS).
Universal Edge Architecture
The MGX 8250 switch can support a wide range of services over narrowband and mid-band user interfaces. It maps all the service traffic to and from ATM by using standardized interworking methods.
The supported interfaces for user-traffic are:
•
•
•
•
The optional Service Resource Module-3T3 (MGX-SRM-3T3/B) can support up to 80 T1 interfaces over its three T3 lines and provide 1:N redundancy for the T1 and E1 cards.
The modular, software-based system architecture enables the switch to support new features through downloadable software upgrades or new hardware modules.
The MGX 8250 backplane supports a minimum of 1.2 Gbps of non-blocking switching. Individual line rates range from DS0 through OC-12.
Standards-Based Conversion to ATM
The MGX 8250 switch converts all user information into 53-byte ATM cells by using the appropriate ATM Adaptation Layer (AAL) for transport over the ATM backbone network. The individual service modules segment and reassemble (SAR) cells to eliminate system bottlenecks. The following list shows the applicable AAL for each service:
•
•
•
•
MGX 8250 Cards
The MGX 8250 switch supports core cards and service modules. The Processor Switching Module (PXM) and optional Service Resource Module (SRM) are core cards. In addition to the PXM being a core card, it is also part of a a card set. A card set consists of a front card, a back card, and a daughter card. Service modules are not combined in this manner and are never part of a card set. Instead, service modules provide the interface to the transport technologies of the CPE—Frame Relay, ATM, and so on. The MGX 8250 enclosure contains up to 24 service modules (I/O cards) and 4 optional Service Redundancy Modules (SRMs) provide redundancy. A card set consists of a front card with its attached daughter card and a back card (or line module). The front card contains the processing intelligence and, on the daughter card, the firmware that distinguishes the interface (OC-3, T3, E3, and so on). The back card is a simple card that provides the electrical interface for one or more lines of a particular type. The MGX 8250 front and back cards are the:
•
This front card controls the switch and supports external interfaces for user-access and trunking or UNI ports. The back cards consist of a user interface card (PXM-UI) and a broadband network module (see subsequent list items).•
The PXM1-UI is the user interface card that has various types of ports to let you access and control the switch.•
The SMFIR-1-622 is a broadband network module for the PXM and provides a SONET OC12/STM4 ATM interface at 622 Mbps.•
The MMF-4-155 is a broadband network module for the PXM and provides four SONET OC3/STM1 ATM interfaces at 155 Mbps.•
The MGX-BNC-2T3 is a broadband network module for the PXM and provides two T3 ATM interfaces.•
The MGX-BNC-2E3 is a broadband network module for the PXM and provides two E3 ATM interfaces. A version for Australia, New Zealand, and elsewhere is available (MGX-BNC-2E3A).•
The MGX-FRSM-2E3/T3 provides interfaces for up to two T3 or E3 Frame Relay lines, each of which can support either two T3 lines (each at 44.736 Mbps) or two E3 lines (each at 34.368Mbps) FR-UNI, ATM-FUNI, or frame forwarding port.•
The MGX-FRSM-2CT3 supports interfaces for up to two T3 channelized Frame Relay lines, each of which supports 56 Kbps, 64 Kbps, Nx56 Kbps, Nx64 Kbps, T1 ports for a total of 256 ports that can be freely distributed across the two T3 lines.•
The MGX-HS2/B supports interfaces for 2 unchannelized HSSI lines, each of which supports approximately 51 Mbps. With both lines operating, maximum throughput is 70 Mbps.•
The AX-FRSM-8T1 provides interfaces for up to eight T1 lines, each of which can support one
56 Kbps or one Nx64 Kbps FR-UNI, ATM-FUNI, or a frame forwarding port. Note that this unchannelized card cannot be configured to support sub-T rates.•
The AX-FRSM-8T1c provides interfaces for up to eight T1 lines, each of which can support up to 24 56 Kbps or N x 64 Kbps FR-UNI, ATM-FUNI, or frame forwarding port.•
The AX-FRSM-8E1 provides interfaces for up to eight E1 lines, each of which can support one
56 Kbps or one N x 64 Kbps FR-UNI, ATM-FUNI, or frame forwarding port.•
The AX-FRSM-8E1c provides interfaces for up to 8 E1 channelized Frame Relay lines Each line can support N x 64-Kbps or (up to 31) 56-Kbps FR-UNI, ATM-FUNI, or frame forwarding ports.•
The MGX-AUSM/B-8T1 provides interfaces for up to eight T1 lines. You can group N x T1 lines to form a single, logical interface (IMA).•
The MGX-AUSM/B-8E1 provides interfaces for up to eight E1 lines. You can group N x E1 lines to form a single, logical interface (IMA).•
The AX-CESM-8T1 provides interfaces for up to eight T1 lines, each of which is a 1.544 Mbps structured or unstructured synchronous data stream.•
The AX-CESM-8E1 provides interfaces for up to eight E1 lines, each of which is a 2.048 Mbps structured or unstructured synchronous data stream.•
The RPM is a Cisco 7200 series router redesigned as a double-height card. Each RPM uses two single-height back cards. The back-card types are single-port Fast Ethernet, four-port Ethernet, and single-port (FDDI).•
The optional MGX-SRM-3T3/B provides bit error rate testing (BERT), 1:N redundancy for T1 and E1 service modules, and a demultiplexing function for T1 service called bulk mode.•
A multipersonality back card that supports either X.21 or V.35 interface.MGX 8250 Management
To give you access for control purposes, the MGX 8250 switch supports high- and low-level user interfaces. You can use the Cisco WAN Manager application (formerly StrataView Plus) for connection management, the CiscoView application for hardware configuration, and a command line interface for low-level control of hardware functionality and connection control. An assortment of ports and protocols supports these user-interfaces. For communicating with the MGX 8250 switch, the control port (SLIP protocol only), the LAN (Ethernet) port, and the in-band ATM connection (feeder application only) all support access by the command line interface (CLI) via Telnet, TFTP, and SNMP protocols.
The downloadable firmware on each card determines the functionality, and you can upgrade functionality by downloading new firmware through a TFTP application on a workstation or a PC.
The current status and configuration parameters of the MGX 8250 modules reside in a Management Information Base (MIB). The firmware on each card updates the MIB as changes in status and configuration occur.
Continued Support for the MGX 8850
The Cisco MGX 8850 wide area edge switch supports:
•
•
•
•
•
It does not support PNNI, despite the fact that some CLI commands may show options for PNNI.
An illustration of the AC-powered version of the switch appears in Figure 4.
Figure 4 MGX 8850 Switch
The Applications of the MGX 8850 Switch
The MGX 8850 switch operates in two operational applications:
•
•
For a description of how to configure the switches for a particular application, see the MGX 8250 Switch Installation and Configuration Guide.
The switch is also capable of supporting Cisco Multiprotocol Label Switching (MPLS).
Universal Edge Architecture
The MGX 8850 switch can support a wide range of services over narrowband and mid-band user interfaces. It maps all the service traffic to and from ATM by using standardized interworking methods. When the MGX 8850 switch operates as a feeder, it uses a single port to communicate the aggregated traffic over an ATM interface with an MGX 8850 or BPX 8600 series switch.
The supported interfaces for user-traffic are:
•
•
•
•
The optional Service Resource Module-3T3 (MGX-SRM-3T3/B) can support up to 80 T1 interfaces over its 3 T3 lines and provide 1:N redundancy for the T1 and E1 cards.
The modular, software-based system architecture enables the switch to support new features through downloadable software upgrades or new hardware modules.
The MGX 8850 backplane supports a minimum of 1.2 Gbps of non-blocking switching up to
45 Gbps. Individual line rates range from DS0 through OC-12.Standards-Based Conversion to ATM
The MGX 8850 switch converts all user-information into 53-byte ATM cells by using the appropriate ATM Adaptation Layer (AAL) for transport over the ATM backbone network. The individual service modules segment and reassemble (SAR) cells to eliminate system bottlenecks. The following list shows the applicable AAL for each service:
•
•
•
•
MGX 8850 Cards
The MGX 8850 switch supports two types of card sets: the core cards (or core modules) and service modules. The Processor Switching Module (PXM) and optional Service Resource Module (SRM) are core cards. The service modules provide the interface to the transport technologies of the CPE—Frame Relay, ATM, and so on. The MGX 8850 enclosure contains up to 24 service modules (I/O cards) and 4 optional Service Redundancy Modules (SRMs) provide redundancy. A card set consists of a front card with its attached daughter card and a back card (or line module). The front card contains the processing intelligence and, on the daughter card, the firmware that distinguishes the interface (OC-3, T3, E3, and so on). The back card is a simple card that provides the electrical interface for one or more lines of a particular type. The MGX 8850 front and back cards are the:
•
This front card controls the switch and supports external interfaces for user-access and trunking or UNI ports. The back cards consist of a user interface card (PXM-UI) and a broadband network module (see subsequent list items).•
The PXM1-UI is the user interface card that has various types of ports to let you access and control the switch.•
The SMFIR-1-622 is a broadband network module for the PXM and provides a SONET OC12/STM4 ATM interface at 622 Mbps.•
The MMF-4-155 is a broadband network module for the PXM and provides four SONET OC3/STM1 ATM interfaces at 155 Mbps.•
The MGX-BNC-2T3 is a broadband network module for the PXM and provides two T3 ATM interfaces.•
The MGX-BNC-2E3 is a broadband network module for the PXM and provides two E3 ATM interfaces. A version for Australia, New Zealand, and elsewhere is available (MGX-BNC-2E3A).•
The MGX-FRSM-2E3/T3 provides interfaces for up to two T3 or E3 Frame Relay lines, each of which can support either two T3 lines (each at 44.736 Mbps) or two E3 lines (each at 34.368Mbps) FR-UNI, ATM-FUNI, or frame forwarding port.•
The MGX-FRSM-2CT3 supports interfaces for up to two T3 channelized Frame Relay lines, each of which supports 56 Kbps, 64 Kbps, Nx56 Kbps, Nx64 Kbps, T1 ports for a total of 256 ports that can be freely distributed across the two T3 lines.•
The MGX-HS2/B supports interfaces for two unchannelized HSSI lines, each of which supports approximately 51 Mbps. With both lines operating, maximum throughput is 70 Mbps.•
The AX-FRSM-8T1 provides interfaces for up to eight T1 lines, each of which can support one
56 Kbps or one Nx64 Kbps FR-UNI, ATM-FUNI, or a frame forwarding port.•
The AX-FRSM-8T1c provides interfaces for up to eight T1 lines, each of which can support up to 24 56 Kbps or N x 64 Kbps FR-UNI, ATM-FUNI, or frame forwarding port.•
The AX-FRSM-8E1 provides interfaces for up to eight E1 lines, each of which can support one
56 Kbps or one N x 64 Kbps FR-UNI, ATM-FUNI, or frame forwarding port.•
The AX-FRSM-8E1c provides interfaces for up to eight E1 channelized Frame Relay lines Each line can support N x 64-Kbps or (up to 31) 56-Kbps FR-UNI, ATM-FUNI, or frame forwarding ports.•
The MGX-AUSM/B-8T1 provides interfaces for up to eight T1 lines. You can group N x T1 lines to form a single, logical interface (IMA).•
The MGX-AUSM/B-8E1 provides interfaces for up to eight E1 lines. You can group N x E1 lines to form a single, logical interface (IMA).•
The AX-CESM-8T1 provides interfaces for up to eight T1 lines, each of which is a 1.544 Mbps structured or unstructured synchronous data stream.•
The AX-CESM-8E1 provides interfaces for up to eight E1 lines, each of which is a 2.048 Mbps structured or unstructured synchronous data stream.•
The RPM is a Cisco 7200 series router redesigned as a double-height card. Each RPM uses two single-height back cards. The back-card types are: single port Fast Ethernet, four port Ethernet, and single-port (FDDI).•
The optional MGX-SRM-3T3/B provides bit error rate testing (BERT), 1:N redundancy for T1 and E1 service modules, and a demultiplexing function for T1 service called bulk mode.•
A multi-personality back card that supports either X.21 or V.35 interface.MGX 8850 Management
To give you access for control purposes, the MGX 8850 switch supports high- and low-level user interfaces. You can use the Cisco WAN Manager application (formerly StrataView Plus) for connection management, the CiscoView application for hardware configuration, and a command line interface for low-level control of hardware functionality and connection control. An assortment of ports and protocols supports these user-interfaces. For communicating with the MGX 8850 switch, the control port (SLIP protocol only), the LAN (Ethernet) port, and the in-band ATM connection (feeder application only) all support access by the command line interface (CLI) via Telnet, TFTP, and SNMP protocols.
The downloadable firmware on each card determines the functionality, and you can upgrade functionality by downloading new firmware through a TFTP application on a workstation or a PC.
The current status and configuration parameters of the MGX 8850 modules reside in a Management Information Base (MIB). The firmware on each card updates the MIB as changes in status and configuration occur.
Features Introduced in Release 1.1.23
MGX 8850 Release 1.1.23 is a maintenance release of Release 1.1.22. In addition, it introduces the following new features:
•
•
•
•
•
Release 1.1.32 MGX 8850, MGX 8230, and MGX 8250 Hardware
MGX 8850 is a 45 Gbps backplane with 1.2 Gbps switching fabric for Release 1.1.32. The same backplane is used with different switching fabric cards (1.2, 45 Gbps) to achieve scalability. MGX 8850 Release 1.1.21 hardware components and their revisions that are supported are as follows:
Support for embedded Cisco IOS router (Router Processor Module - [RPM])
•
–
–
–
MGX 8220 Hardware Not Supported on Release 1.1.32 of the MGX 8850
The following cards are not supported in Release 1.1.32:
•
•
•
•
•
MGX 8220 Hardware That Has Been Superseded on the MGX 8850 by MGX 8850-Specific Hardware
•
The MGX-SRM-3T3-C front card replaces the original AX-SRM-3T3-A front card and the MGX-BNC-3T3 back card replaces the original AX-BNC-3T3 back card. This change allows the use of slots 9, 10, 25, and 26 for 1:N redundancy and BERT in the MGX 8850 chassis. Both the AX-SRM-3T3-A/AX-BNC-3T3 card set and the MGX-SRM-3T3-C/MGX-BNC-3T3 card set are supported on the MGX 8220.
New card should have enabled use of bulk distribution in slots 9 and 10. 1:N redundancy should have been supported in those slots with the model A card.
•
Superseded by the MGX-SCSCI2-2HSSI/B, which works with the MGX-FRSM-HS2 front card. A V.35 interface is supported on the MGX-FRSM-HS1/B in this release.
•
Superseded by MGX-AUSM-8T1/B and MGX-AUSM-8E1/B.
•
Superseded by MGX-AUSM-8T1/B and MGX-AUSM-8E1/B.
MGX 8220 Hardware Not Supported on the MGX 8850
•
•
•
•
Software Platform Features
MGX 8850 provides high-speed native ATM interfaces, which can be configured as ATM UNI ports or trunks. Table 2 contains redundancy support information for service modules.
Support for Bulk Distribution using SRM-3T3-C card.
Service module and PXM upgrades.
Features Not Supported in This Release
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Note
Major Network Management Features
•
•
•
•
•
•
•
For more details refer to the CWM Release 9.2.07 release notes part number 78-6659-07.
Connection Limits
•
•
•
•
SNMP MIB
The SNMP MGX Release 1 MIB are provided with the delivery of Release 1.1.35. The MIB is in standard ASN.1 format and is located in the same directory within the 1.1.35 bundle on CCO. These files may be compiled with most standards-based MIB compilers. For changes in this MIB from the previous release, please refer to the MIB release notes.
Their are two formats contained in the bundle:
•
•
The old_mibFormat is released and maintained for Legacy and backward compatibility. These files can be used by NMS, only if the NMS is not using any standard MIBs for DS1, DS3 and SONET.
The NMS should not be managing MGX Release 2 as that product uses the standard DS3, SONET and DS1 MIBs. This rule applies to any other Cisco or third-party product that supports these MIBs.
For those who are using both MGX Release 1 and MGX Release 2 in the same network and managing the two products by the same NMS, use the new_mibFormat.
Notes and Cautions
The following notes and cautions should be reviewed before using Release 1.1.35.
Stratum-3 Clocking
The PXM-UI-S3 back card used in previous releases to support Stratum-3 level clocking, is not supported in Release 1.1.35.
UPC Connection Parameters
In Release 1.1.35, the default UPC connection parameters on the PXM have changed. The default PCR is 50 cps, and the default for policing is "enabled." These settings are insufficient for running RPM ISIS protocol over the connection, and with such settings, the ISIS protocol will fail. The PCR value needs to be increased, depending upon the number of interfaces configured for ISIS on the RPM. CLI modification and changes in this release.
Depending upon your connection type, you can use the following CLIs to modify the PCR parameter.
•
•
•
•
ForeSight and Standard ABR Coexistence Guidelines
ForeSight is similar to the rate-based ABR control system in TM 4.0 in that they both use Rate up and Rate down messages sent to the source of the connection to control the rate a connection runs at, based on congestion within the switches along that connections path. Both systems use Resource Management (RM) cells to pass these messages. There are differences between the two systems that need to be considered.
RM Cell Generation
ForeSight is a destination-driven congestion notification mechanism. The destination switch is responsible for generating the RM cells, which defaults to every 100 ms. This means that any rate modifications at the source end happen approximately every 100 ms, and the time delay between the actual congestion at the destination and the source getting to know about it could be 100 ms.
In standard ABR a source generates FRM cells every (nRM) cell intervals, where n is configurable. These are used to pass congestion information along to the destination switch, which then uses this information to generate BRM (Backward RM cells) back to the source A further consideration is that the actual user data flow will be lower for an equivalent rate due to the additional RM cells. Therefore, the more traffic being generated on a connection at any one time, the faster the feedback will be to the source.
There is also a TRM parameter which states that if no RM cells have been generated after this time has passed then one will automatically be sent. Depending upon the speed it is running at, an ABR connection may therefore react faster or slower to congestion than the equivalent ForeSight connection. (for example, if an ABR connection runs at 100 cells per second, and nRM is 32, then approximately three RM cells will be generated per second, or once every 300 msecs. If it runs at 1000 cps then an RM cell would be generated approximately every 30 msecs. In both cases, the equivalent ForeSight connection would generate an RM cell every 100 msec.)
Reaction to Feedback Messages - Rate Up
In ForeSight, in response to a Rate Up cell from the destination, the source increases its rate by a percentage of the MIR for that connection. If we call this percentage the rate increase percentage (RIP), then RIP is configurable at the card level (the default is 10 percent). In the case where MIR is low, the ForeSight rate increase will be slow as it has to increase as a percentage of MIR (rather than CIR).
On a standard ABR connection, in the event of available bandwidth (no congestion) the source increases its rate by a factor of (RIF*PCR). This means the rate increase step sizes are much bigger than for ForeSight for larger values of RIF (RIF has a range of 1/2, 1/4,....,1/32768). If RIF is not configured properly then standard ABR will ramp up its rate much faster and to a higher value. This is aided by the fact that the step sizes are bigger and the step frequency is higher in comparison with ForeSight.
Reaction to feedback messages - Rate Down
In ForeSight on receiving a Rate Down cell from the remote end, the source reduces its current rate (actual cell rate) by 13 percent. The rate decrease percentage (RDP). RDP is configurable at the card level.
In standard ABR, rate decrease is by an amount (RDF*ACR). Currently, the default value of RDF is 1/16 (6.25 percent). This means when this connection co-exists with ForeSight connections, in the event of congestion ForeSight connection reduces its rate by 13 percent whereas standard ABR connection reduces its rate by only 6.25 percent. Therefore, in the case of co-existence, if we need to approximate the same behavior across the two connection types, then RDF should be changed to 1/8, so that both connections ramp down by the same amount (13 percent).
Fast-Down
In ForeSight if the destination egress port drops any data due to congestion then the destination sends a Fast Rate Down cell. Also, if a frame cannot be reassembled at the egress due to a lost cell somewhere in the network, a Fast-down will be generated. On reception of Fast Rate Down the source reduces its current rate by 50 percent (this is again a card-level configurable parameter).
Standard ABR does not distinguish between drops and the ECN/EFCI threshold being exceeded. This means that, in case of drops in the egress port queue, a standard ABR connection rate reduces by only (RDF*ACR) but the ForeSight connection rate reduces by (ACR*0.5). Therefore, in the case of co-existence, if we need to approximate the same behavior across the two connection types then Fast Down could be effectively disabled by configuring the reaction to be 13 percent rate down instead of 50 percent.
Guidelines
The two systems will work together within the network, but as the above description suggests, if the differences between the two systems are not taken into consideration, then a ForeSight connection and an ABR connection with the same configuration parameters will not behave the same way within the network.
ABR and ForeSight provide a mechanism for distributing excess bandwidth between connections over and above the minimum rate, therefore if these guidelines are not taken into consideration then the allocation of this excess bandwidth may be biased toward connections running one of these algorithms over connections running the other.
If this is a requirement, the following guidelines may be useful, assuming ForeSight is set to defaults except for Fast Rate Down which is set for 13 percent.
1.
100 milliseconds, to match that of ForeSight. This calculation is based on the expected average, or sustained, cell rate of the connection. However, if the (potential) fast-down messages from ForeSight are left to equate to 50 percent rate down, then an estimate of how often this may occur needs to be made and factored into the equation. If the connection receives Fast-down messages, then this would make the ForeSight connection react faster than the equivalent ABR connection to congestion. To compensate for this, Nrm needs to be set at a value of less than 100 msecs, a suggested value to aim for is between 60-70 msecs (this would be approximate as n is configurable in steps of 2**n). This would mean that, in the event of congestion, the ABR connection would start to react faster.2.
3.
The following worked examples may help explain this further
Assume a network is currently running ForeSight with default parameters, and supports the following four connection type, where CIR = MIR, PIR = port speed, and QIR = PIR:
T1 Port Speed 64K CIR
Example:
CIR = MIR = 64K
PIR = QIR = port speed = 1544
Fastdown = 13%(The calculation used to convert between frame based parameters (CIR, PIR, and so on.) and their equivalent cell-based parameters is FR_param *3/800. This allows for cell overheads, and so on. based on frame sizes of 100 octets.)
CIR = MIR = (64000*3/800) = 240 cps
PIR = QIR = (1544 *3/800) = 5790 cpsForeSight ABR
Rate-up equals (240*.1) = 24 cps RIF equals x where (1590/x) = 24 cps
X needs to be approx 200
RIF equals 256 (nearest factor of 2)RDF equals 13% RDF = 1/8
Nrm equals 100 msecs Nrm equals 32RM cells will be generated somewhere between 6 (5790 cps approx equal to 32 cells per 6 msecs) and 133 msecs (240 cps approx equal to 32 cells every 133 msecs) depending on ACR.
CLI Modifications in 1.1.35 and Prior Releases
dspfail <slotno>
shows all failed connections per slot basis
dspfabit <slotno>
shows all A-bit failed connections per slot basis
dsplmiloop
shows if LMI loop is present
chkslotcon <slotno>
checks database consistency per slot basis
chkportcon <slotno> <portno>
checks database consistency per slot basis
Chkcon <slot.port.vpi.vci>
checks database consistency per connection basis
dspbecnt
displays bit error count
CLI modification and changes in previous releases:
•
–
–
–
–
–
–
–
–
–
–
–
–
–
Syntax:
cnfifip "Interface IPaddr [NetMask [BroadcastAddr]]"
or cnfifip "Interface Flag"
Interface -- 26/28/37 (26:Ethernet 28:SLIP 37:ATM)
or Ethernet/SLIP/ATM
IP_Addr -- <n>.<n>.<n>.<n> (<n>: integer 0..255)
Net_Mask -- <n>.<n>.<n>.<n> (<n>: integer 0..255)
BroadcastAddr -- <n>.<n>.<n>.<n>
(<n>: integer 0..255)
Flag -- a string "UP" or "DOWN"
Example:
> cnfifip atm 192.9.200.1 255.255.255.128
This configures the ATM interface and brings it UP.
> cnfifip atm up
This will bring up the ATM interface with current information in the database.
> cnfifip atm down
This will bring down the ATM interface and preserve the information in the database.
–
Syntax:
delifip Interface
Interface -- 26/28/37 (26:Ethernet 28:SLIP 37:ATM) or Ethernet/SLIP/ATM
Example:
> delifip 37
This will bring down the ATM interface and delete the information in the database.
–
Example:
> dspifipInterface Flag IP Address Subnetmask Broadcast Addr--------------- ---- --------------- --------------- ---------------Ethernet/lnPci0 UP 172.29.37.77 255.255.255.0 172.29.37.255SLIP/sl0 DOWN 172.29.36.253 255.255.255.252 (N/A)ATM/atm0 UP 192.9.200.1 255.255.255.128 0.0.0.0
This command shows the current condition of all three interfaces. The data shown for the SLIP interface will apply when it is turned UP with, for example, cnfifip slip on.
–
Syntax:
cnfenetgw IPAddr
Example:
> cnfenetgw 172.29.37.1This command will set the default gateway and add the appropriate routes necessary to it.
–
Example:
> dspenetgwEnet Gateway: 172.29.37.1–
Several lines are essential for the network to function:
- boot device : lnPci
(The only Ethernet interface)
- inet on ethernet (e) : 172.29.37.40:ffffff00
(IP address and subnetmask)
- gateway inet (g) : 172.29.37.1
(Default Ethernet gateway)
The PXM will try to correct bad entries when it boots up. This information will be copied to the standby card and if different than the shelf IP address it will up the interface on the standby with the bootChange IP address. The shellconn version of this command only updates the local bootline values and is not copied to the other card.
–
Used to bring up the Ethernet interface when CLI prompt is not there or in backup boot if it's not enabled.
The following commands are related to FRSM-2CT3 line-level loopbacks.
•
This loopback can be configured in FRSM-2CT3 using the following commands:
addds3rmtloop <lineno>
xcnfln -ds3 <lineno> -e 3 -lpb 2
•
This loopback can be configured in FRSM-2CT3 using the following commands:
addds3loop <lineno>
xcnfln -ds3 <lineno> -e 3 -lpb 3
DS3 Loopback status will be displayed with following commands:
dspds3ln <lineno>
dspalm -ds3 <lineno>
dspalms -ds3
FEAC codes monitoring and Inband loopbacks for DS3 are not supported in FRSM-2CT3
•
This loopback can be configured in FRSM-2CT3 using the following commands:
cnfbert (from PXM)
addrmtloop <lineno>
xcnfln -ds1 <lineno> -e 3 -lpb 2
•
This loopback can be configured in FRSM-2CT3 using the following commands:
cnfbert (from PXM)
addlnloop <lineno>
xcnfln -ds1 <lineno> -e 3 -lpb 3
DS1 Loopback status will be displayed with following commands:
dspln <lineno>
dspalm -ds1 <lineno>
dspalms -ds1
•
xcnfln -ds1 <lineno> -e 3 -detect 2
•
•
•
–
–
–
Node Related
A maximum of one BERT test can be performed per shelf at any point in time. BERT can be activated only through the CLI.
Do not execute the restoreallcnf command in the middle of the installation process. If you follow the steps below, the dsplns command will display a line as disabled, but you cannot run an addln command. Do not execute the restoreallcnf command until the install and newrev commands have completed
The correct order for the restore procedure is:
Step 1
Step 2
Step 3
Step 4
Note
Addln should be issued before issuing addapsln.
The following line and alarm-related commands have been modified to allow slots 8, 16, and 32 as valid arguments if PXM at slot 8 is active:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Full SRM redundancy requires redundant SRMs. There must be SRMs in BOTH slot 15 and 16 to ensure service module redundancy for the upper shelf and SRMs in BOTH slot 31 and 32 to ensure service module redundancy for the lower shelf. Lack of the second SRM in either shelf may result in mismatch conditions.
For service module redundancy support, if the active service module is physically removed from the slot then a switchcc would cause the now active service module to be inaccessible. The workaround is to make sure that both the active and standby cards are physically present in their slots. If the active card does need to be removed, then at shellconn type: pmmStartScmPolling(slotnumber) after the switchcc.
If you are moving service modules from an existing MGX 8220 platform to the MGX 8850, the MGX 8220 service modules (AX-FRSM-8T1/E1, and AX-CESM-8T1/E1) need to have the boot flash upgraded to MGX 8220 Release 5.0.00 common boot code (1.0.01 version) before they can be plugged in to the MGX 8850 chassis. All MGX 8220 service module versions that use Release 4.0.xx of boot code and earlier are not supported in the MGX 8850.
If loading of the correct common boot code image is required then it will have to be performed on an MGX 8220 chassis, and cannot be performed on an MGX 8850 chassis. Please refer to the procedure below, which is also outlined in the Cisco MGX 8850 Installation and Configuration publication on the documentation CD.
Step 1
Step 2
Step 3
tftp <ip address of the MGX 8220 shelf >binput <boot filename> AXIS_SM_1_<slot#>.BOOTInsure that TFTP downloaded the appropriate boot code by verifying the flash checksums.
Step 1
cc <slot #>'Step 2
chkflash'If not, repeat the process until they are the same. If they are the same, then you can safely remove the card. At this point the service module can be used in the MGX 8850 shelf.
Caution
Whenever an MGX 8850 is added as a feeder to a BPX 8600, SWSW automatically programs a channel with a VPI.VCI of 3.8 for use as the IP Relay channel. IP Relay is used to send IP data between nodes via the network handler, allowing every node in the domain to be directly addressable via IP addressing and CWM workstations to communicate with every node (especially feeders) using TELNET, SNMP and CWM protocols. If the user tries to add a channel with a VPI.VCI of 3.8, the BPX 8600 does not prevent the user channel from being added, but the MGX 8850 rejects it. To delete the added channel on the BPX 8600, and to get IP relay working you need to reset the BXM card.
In addition to clearing the entire configuration, clrallcnf clears the network IP addresses. IP addresses and netmasks stay the same (dspifip). However, it's recommended by engineering to reconfigure them using the cnfifip command. Network IP is gone (dspnwip), and must be reconfigured using the cnfifip command. Refer to the entry on cnfifip in the Cisco MGX 8850 Command Reference publication on the documentation CD for syntax.
•
A minimum of two and up to four IP addresses are needed to be configured for MGX 8850 (one or more of the following: Ethernet, ATM, SLIP) and the boot IP address. The user should use bootChange to set up IP gateway when the PXM card is just installed. The IP default gateway should be on the same subnet as the PXM board. Use the bootChange command to set correct IP address, netmask, and default gateway.
Do not install a Y-cable on the UIA CP port for PXMs. If you do, both serial ports will be enabled and you will not be able to communicate with the shelf through the console ports. If after switchcc the standby PXM loses the down-level port, it is most likely due to a downlevel Beta version of UIA back card that was shipped during field-trial only. Upgrading the UIA back card to the latest version should fix this problem.
To configure the external clock source, use the interface label 7.35. Do not use 0.33 or 7.33.
There are also routeShow/routeAdd/routeDelete commands for modifying routing tables.
You must reboot your PXM after each modification with "bootChange" for it to take effect. Also make sure the subnet mask is 255.255.0.2
. bootChange- Only enter the ethernet IP address, netmask and default gateway.- Type "." to erase incorrect entries.tigers.1.7.PXM.a > bootChange'.' = clear field; '-' = go to previous field; ^D = quitboot device :lnPciprocessor number :0host name :C <-- Please put "C".file name :inet on ethernet (e) :172.29.37.40:ffff00 <-- Ethernet IP Addr/Netmaskinet on backplane (b):host inet (h) :gateway inet (g) :172.29.37.1 <-- Default Gatewayuser (u) :ftp password (pw) (blank = use rsh):flags (f) :0x0target name (tn) :startup script (s) :other (o) :- Type in reboot, after this the command "" will work:tigers.1.7.PXM.a > 171.71.54.53 1171.71.54.53 is aliveConfiguration save-and-restore is supported only through the CLI (CWM does not support configuration save-and-restore). Service module upgrades error handling is not provided. If the user skips any of the steps during upgrade or if a power failure happens in the middle of the upgrade, results will be unpredictable. See the Special Installation and Upgrade requirements section for service module upgrades. To recover from procedural errors contact your TAC support personnel.
The MGX 8850 supports 15 simultaneous Telnet sessions and 10 TFTP sessions.
You must use the following Y-cables for FRSM-HS2 and FRSM-CT3 redundancy as specified in the Product Orderability Matrix (Straight Cable: 72-0710-01, Crossover Cable: 72-1265-01, Straight Y-cable: FRSM-HS2: CAB-SCSI2-Y, FRSM-CT3: CAB-T3E3-Y). Other cables are not supported.
Y-cable redundancy for FRSM-HS2, FRSM-2CT3, FRSM-2T3, FRSM-2E3 is supported only for adjacent slots.
Statistics are not supported for the RPM.
There is no need to issue the syncdisk and shutdisk commands before removing the PXMs. The system quiesces the disk by detecting the removal of the PXM board and flushes the write buffers to the disk and puts the PXM in sleep mode. This disables any further hard disk access since it locks the actuator. When the card is reinserted the PXM automatically comes out of sleep mode.
Syntax of addlink command has changed as follows:
New Syntax:
Syntax: addlink <T3LineNum> <T1Slot> <NumberOfT1s> <TargetSlotNum>
<TargetSlotLineNum>
<T3LineNum> where = Slot.Line
Slot = 15,31
Line = 1 - 3
<T1Slot> where T1Slot = 1 - 28
<NumberOfT1s> where NumberOfT1s = 1-8
<TargetSlotNum> where TargetSlotNum = 1-6|11-14|17-22|27-30
<TargetSlotLineNum> where TargetSlotLineNum = 1-8
PAR command cnfnwip has been disabled in this release, please use cnfifip instead.
If you lose power, or remove the online PXM you lose the broadcast address. Use the "cnfifip" command to configure the broadcast address. To redefine your ATM address and IP address that are in the same subnet, you have to change the ATM address to a temporary address not in the same subnet, then add back your IP address with the original Broadcast address, then go back and correct your ATM address.
Cooling and Power limitations: Customer should be aware of the need for extra power supplies and fans beyond certain limitations. A single fan tray will support all configurations that draw between 1200 and 1400 watts. For power requirements, the MGX 8850 requires a minimum of one power supply per line cord to support the power requirement for five cards.
This is based on an estimated worst-case power requirement of 190W plus margin per card slot.
Connection Management Related
The name of the node cannot be changed if there are PVCs. The node name must be changed from the default value before adding connections, since it cannot be changed later. Use the cnfname command to change the node name.
Only one feeder trunk can be configured. No BNI trunk to MGX 8850 as a feeder is supported.
The slave end of a connection must be added first.
The slave end cannot be deleted and re-added back by itself. If you delete the slave end, the entire connection must be completely torn down and re-added back. If the slave end of the connection is deleted and re-added back by itself, then unpredictable results will happen.
For user connections, VCI 3 and VCI 4 on every VPI are reserved for VPC OAMs.
The actual number of feeder connections you can provision on the PXM is always two less than you have configured. The dsprscprtns command shows max connections as 32767, but you can only use 32767 - 2 = 32765. One connection is used for LMI and another one for IP relay.
There is no error handling detection while provisioning through the CLI. Invalid endpoints and unsupported connection types (such as connections between FRSM-CESM ports or connections between structured and unstructured connections) are permitted using the CLI. The user should not configure these connections.
The sum of CIR of all channels of a port can be greater than port speed as long as CAC is disabled. However, it is not acceptable for one channel's CIR to be greater then port speed even if CAC is disabled. Two channels added up can exceed port speed. This means you cannot oversubscribe a port if only one channel is configured.
When trying to add a port on DS0 slot 32 of a CESM-8E1 line using an SNMP set or the CiscoView Equipment Manager, the SNMP agent in CESM will time out, without adding the port. The SNMP libraries treat the 32 bit DS0 slotmap (cesPortDs0ConfigBitMap) as an integer. The value for the last DS0 is treated as the sign value. This causes a corruption in the packet coming to the agent. As the agent does not receive a complete SNMP packet, it does not respond and times out. Use the command line interface to add a port on DS0 slot 32 of a CESM-8E1 line.
The cnfport command does not allow VPI ranges to be reduced. The cnfport command only allows the VPI range to expand. The correct sequence is to delete all connections on the partitions, delete the partitions, delete the port, and add the port with new VPI range.
On an FRSM-2CT3, one can add 128 ports on a group of 14 T1 lines as indicated below.
•
•
•
•
So, to add 256 ports on one T3: add 128 ports on the first 14 T1 lines and the remaining 128 on the next 14 T1 lines.
Note that (A) and (D) are connected to first FREEDM and (B) and (C) are connected to the second FREEDM. Each FREEDM supports only 128 ports. If 128 ports are added on one T3 as in (A), then there cannot be any more ports as in (D). The 129th port should be on lines 15 to 42 (as in B or C).
If the user adds a connection between an RPM and a PXM and then deletes the connection, the RPM shows no connection but the PXM still has the connection. The MGX was designed and implemented in such a way that only the connections that have the master end show up on PXM (by dspcons command). Consider these three connections:
•
•
•
When using the dspcons command, c2 and c3 will be displayed, not c1. The connection will not show up once the master end (PXM) is deleted. Recommendation: When adding a connection, if one end of the connection is PXM, always configure the PXM side to be the slave. Thus when deleting the RPM side, which is the master, the connection will not show up on the PXM. However, keep in mind that the slave end (PXM) still exists. This also provides a side benefit. When a connection exists with only the slave side, no bandwidth is occupied. The bandwidth is reserved only if the master end exists (with or without the slave).
The MGX-FRSM-HS1/B is capable of supporting a total throughput (card-level) of 16 Mbps. However, it is possible to configure four lines each supporting up to 8 Mbps, thus oversubscribing the card. This has been raised in bug #CSCdm71476 and a restriction/warning will be added in a future release.
Addlnloop on an FRSM-HS1/B line works only when there is a (valid) cable plugged in to the back card on that line. This is a hardware limitation on the back card and has been mentioned in the Release Notes in bug# CSCdm44993.
RPM Related
The RPM/PR and RPM/B operate under the following IOS and Release 1 software.
With MGX Release 1.1.32, two Route Processor Modules (RPMs) are supported; the RPM/B and the RPM-PR.
The RPM/B is a NPE-150 based router card capable of sustaining 150,000 pps. The RPM-PR is an NPE-400 based router capable of sustaining over 350,000 pps. The RPM-PR will only operate with IOS 12.1(5.3)T_XT or later. For the following section "RPM" will refer to both the RPM/B and the RPM-PR, (unless specifically called out) even though some software versions and limitations are not applicable to the RPM-PR because it doesn't support IOS versions before 12.1(5.3)T_XT.
With RPM/B versions earlier than 12.O.7T1, some limitations in Inter-Process Communication when the RPM/B is at high loads can cause the PXM to declare that the RPM/B has Failed. To avoid this with RPM/B, software releases earlier than 12.0.7T1, throughput is limited to 62,000 pps, and it is recommended that MPLS configurations are limited to 100 interfaces. With RPM software releases from 12.0.7T1, those limitations are removed. In a separate limitation, the number of directly connected OSPF networks supported by an RPM is currently limited to 27. This means that any or all of the subinterfaces supported by the RPM can run OSPF, but the number of distinct OSPF networks supported is limited to 27. (A work around is available and is discussed below.) The limit of 27 arises because of the overheads of supporting separate link-state databases for separate networks.
In an application where the RPM is a Provider Edge Router in an MPLS Virtual Private Network service, a much better solution in any case is to use a distance-vector routing protocol between the customer routers and the RPM. A distance-vector routing protocol provides exactly the information required for this application: reachability information, and not link-state information. The distance-vector routing protocols supported by the RPM are BGP, RIP v1 and RIP v2, as well as static routing. With RPM software releases from 12.0.7T1, distance-vector routing protocols can be used with as many different networks as subinterfaces.
Note that if the RPM is acting as a Provider Edge Router in an MPLS Virtual Private Network service, and even if OSPF is running in a customer network, it is not necessary to run OSPF between the customer router and the RPM. If the customer edge devices run Cisco IOS, they can redistribute OSPF routing information into RIP using the IOS commands, redistribute RIP in the OSPF configuration, and redistribute OSPF in the RIP configuration. Similar configurations are possible for BGP. (For more information on readvertisement, see the "Configuring IP Routing Protocol-Independent Features" chapter in the Cisco IOS Release 12.0 Network Protocols Configuration Guide, Part 1). Redistribution is not unique to Cisco CPE, and other vendors' equipment also supports redistribution.
RPM Front Card Resets on an MGX 8250 Switch
The RPM front card resets on an MGX 8250 switch when the ethernet back card is removed. While this problem is observed on the MGX 8250 switch, it does not occur on an MGX 8230 switch.
This reset problem can be easily avoided if "shut" interface is executed before the removal of the back card.
RPM-PR Back Ethernet Card Support
For Ethernet connectivity with the RPM-PR, the model "/B" four-port Ethernet back card is required (order number: MGX-RJ45-4E/B).
RPM/B Ethernet Back Card Support
The model "/B" four-port Ethernet back card can be used with the RPM/B module only in combination with IOS 12.2(2)T2 or higher. The model "/B" back card will not work on the RPM/B with earlier versions of the IOS.
The order number is order number: MGX-RJ45-4E/B.
Older back cards can be used with any version of the IOS.
model "/B" back card
12.2(2)T2
earlier back card models
Min. IOS for RPM/B on MGX 8250 is 12.0(7)T
Refer to Route Processor Module (RPM) Addendum for more specific information about the RPM.
Limitations
CWM Recognition of RPM/PR and RPM/B Back Cards
CWM does not distinguish between the Ethernet back card versions installed with the RPM/B or RPM-PR. There is no functionality difference. The ability for CWM to distinguish between the Ethernet back card revisions is planned, but there is no targeted release at this time.
restoreallcnf
Do not execute the restoreallcnf command in the middle of the installation process. If you do, the dsplns command will display a line as disabled, but you cannot run an addln command. Do not execute the restoreallcnf command until the install and newrev commands have completed.
The correct order for the restore procedure is:
Step 1
Step 2
Step 3
Step 4
Note
Please also note the following:
•
•
•
•
clrsmcnf
As a speedy way to wipe out all configuration on an SM, you can use clrsmcnf. This command works in the following scenarios:
•
•
•
To be able to use an SM of a different type from the current one in a slot you can also use clrsmcnf for example, if there is a FRSM8T1/E1 in the slot with some configuration and the customer wants to use this slot for an AUSM8T1/E1 card.
The clrsmcnf cannot delete a port or channel due to corruption or error locally on the SM. It is able to delete the port/channel from within the PXM, but it cannot delete a port or channel due to corruption/error on the PXM itself. You can save an SM configuration and restore it back to the same slot on the same node. If the SM configuration is corrupted on disk, but the run-time image is okay and the file contented is corrupted, this is supported.
The following are NOT supported on the MGX 8850:
•
•
•
If you have more than 500 connections on a service module, before issuing clrsmcnf you need to change the session timeout default value.
Use CLI command timeout 0 (no timeout)
clrsmcnf
After it is done, use the CLI command timeout 600 (to set the timeout value back to the default).
Note
Problems Fixed in Release 1.1.35
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
Compatibility Notes
MGX 8230/8250/8850 Software Interoperability with Other Products
Boot File Names and Sizes
The following table displays the boot file names and sizes for the Release 1.1.34.
MGX 8250/8850 Firmware Compatibility
The following firmware compatibility matrix is for System Release 1.1.34.
MGX 8230 Firmware Compatibility
The following firmware compatibility matrix is for System Release 1.1.34.
Compatibility Matrix
This multiservice gateway comparison matrix is designed to identify capabilities supported in the MGX 8220, 8230, 8250, and 8850 platforms.
Special Installation and Upgrade Requirements
Existing customers should use the upgrade procedure Service Module Upgrades to upgrade. A graceful upgrade from any release previous to 1.1.34 is supported. For new customers, the image will be pre-installed as 1.1.34 and should use the PXM installation procedure to upgrade to future maintenance releases.
A graceful upgrade from any release previous to 1.1.34 is supported, but a graceful downgrade is not supported. Abort or fallback to the previous release is supported at any stage during the upgrade. For abort instructions, refer to Instructions to Abort Upgrade.
Special Instructions for Networks Containing FRSM 2 CT3
Under certain conditions with the FRSM 2 CT3, a script must be ran in order to properly upgrade from previous releases to Release 1.1.34. The script resolves the FREEDM buffer issue described inanomally CSCds66176; namely, that ports are lost sometimes after softswitch or resetcd. The algorithm to allocate FREEDM buffers was changed in order to fix this anomally. Because of the algorithm change, ports might be lost when upgrading from a release (FRSM version < 10.0.22) with the older algorithm. The script identifies cards which will lose ports if the card is upgraded to Release 1.1.32 or greater.
A README file contained in the Release 1.1.34 TAR file located on CCO describes how to run the script and shows an example of the script output.
Executing the Script
Execute the script:
•
•
Script Functionality
The script applies the new algorithm for buffer allocation to existing ports to determine if all the ports will remain intact during the upgrade process. After application of the new algorithm, a log file is created for each FREEDM chip on all the FRSM 2CT3 cards on the shelf. The log file contains confirmation that the buffer allocations are OK or NOTOK. If the log file contains NOTOK for a card, then upgrading the card to the new release will cause the card to lose ports. Therefore, ports must be moved to another card before upgrading this card.
Single PXM Installation Procedure
Step 1
saveallcnfStep 2
node-prompt> ll "C:/CNF"size date time name-------- ------ ------ --------512 APR-08-1999 08:16:18 . <DIR>512 APR-08-1999 08:16:18 .. <DIR>512 APR-09-1999 05:26:42 TMP <DIR>45433 APR-09-1999 05:28:42 NODENAME_0409990528.zip45433 APR-09-1999 05:28:42 NODENAME.zipIn the file system :total space : 819200 K bytesfree space : 787787 K bytesStep 3
unix-prompt> tftp shelf.ip.addresstftp> bintftp> get CNF/NODENAME_0409990528.zipReceived 45433 bytes in 0.4 secondsStep 4
tftp <node_name or IP address>binput pxm_bkup_1.1.34.fw @PXM.BTquitStep 5
tftp <node_name or IP address>binput pxm_1.1.34fw @PXM.FWquitStep 6
tftp <node_name or IP address>binput ComMat.datquitStep 7
copy ComMat.dat /FW/ComMat.datStep 8
Step 9
Step 10
PXM.a> install 1.1.34redundancy is not availablethe other card is not availableyou are not in redundant mode,do you want to try an ungraceful upgrade(yes or no)?yes
Installation Procedure for Redundant PXMs
This section applies to upgrades from 1.1.23, 1.1.25, or 1.1.32.
Caution
During the graceful upgrade procedure, if after the newrev command the non-active card enters the "MISMATCH" state, do the normal commit command. You will get a warning message:
other card not found,
do you still want to complete the commit operation
Answer yes and then reset the non-active card.
If you get the MISMATCH during the upgrade process, after you finish, you will also get the MISMATCH. To correct the mismatch, you must check your back cards; they must be identical.
Note
To set the PXM address, use the bootChange command:
node-prompt> bootChange'.' = clear field; '-' = go to previous field; ^D = quitboot device : lnPciprocessor number : 0host name :file name :inet on ethernet (e) : 172.29.37.220:ffff00inet on backplane (b):host inet (h) :gateway inet (g) : 172.29.37.1user (u) :ftp password (pw) (blank = use rsh):flags (f) : 0x0target name (tn) :startup script (s) :other (o) :Set the "inet on ethernet (e) :" field with the first part of the entry (before the :) as the IP address, and the second part as the subnet mask.
Set the "gateway inet (g) :" with the gateway address.
This must be done on both PXMs. This can also be done in backup boot from the VxWorks prompt "->".
To set the shelf IP address:
node-prompt> cnfifip 26 shelf.ip.address subnet.mask broadcast.address•
•
•
Step 1
saveallcnfStep 2
node-prompt> ll "C:/CNF"size date time name-------- ------ ------ --------512 APR-08-1999 08:16:18 . <DIR>512 APR-08-1999 08:16:18 .. <DIR>512 APR-09-1999 05:26:42 TMP <DIR>45433 APR-09-1999 05:28:42 NODENAME_0409990528.zip45433 APR-09-1999 05:28:42 NODENAME.zipIn the file system :total space : 819200 K bytesfree space : 787787 K bytesStep 3
unix-prompt> tftp shelf.ip.addresstftp> bintftp> get CNF/NODENAME_0409990528.zipReceived 45433 bytes in 0.4 secondsStep 4
Step 5
unix-prompt> tftp pxm.ip.addresstftp> bintftp> put pxm_bkup_1.1.34.fw POPEYE@PXM.BTtftp> quitStep 6
unix-prompt> tftp pxm.ip.addresstftp> bintftp> put pxm_1.1.34.fw @PXM.FWSent 1982672 bytes in 18.3 secondsMake sure that the transfer is successful by looking at the message displayed on the PXM console after the transfer:
Program length = 1982672Calculated checksum = 0xd9779bc6 stored checksum = 0xd9779bc6Fw checksum passedStep 7
tftp <node_name or IP address>bincd fwput ComMat.datcopy ComMat.dat to FW directory on the PXM.quitStep 8
copy ComMat.dat /FW/ComMat.datStep 9
Step 10
Step 11
The Active card will be reset and go to hold state.
After the newrev the firmware should now show the new revision on dspcd.
Caution
Step 12
Instructions to Abort Upgrade
A graceful downgrade is not supported. However, abort or fallback to the previous release is supported at any stage during the upgrade. The following procedure should be used to abort to a previous release.
Upgrade to 1.1.34 from 1.1.3x
If the upgrade needs to be aborted for any reason during the upgrade process, follow these instructions.
Step 1
PXM.a> abort 1.1.32
Upgrade to 1.1.34 from 1.1.2x
If the upgrade needs to be aborted for any reason during the upgrade process, follow these instructions
Step 1
a.
b.
c.
d.
e.
f.
g.
PXM.a > shellConn-> smCardMibVer=21-> saveDBToArchive 7, 7-> uploadBram 7, 7Step 2
Service Module Firmware Download Procedure
Step 1
tftp <node_name or IP address>binput <backup boot> POPEYE@SM_1_0.BTquittftp <node_name or IP address>put <FW file> POPEYE@SM_1_0.FWquitYou cannot do two puts in the same TFTP session.
Step 2
Step 3
Step 4
Note
Note
Manual Configuration of Chassis Identification
MGX as a Standalone Node
If any MGX box is to be used as a standalone node for testing, the intended model number from the PXM firmware configuration should be matched MANUALLY by running the "runConfigurator" utility.
Example: ipfrnj40 was running 1.1.24 as a 8850 node:
If the node's model number is set to 8250 by default after a 1.1.32 firmware upgrade, but the ipfrnj40 is still configured as a 8850 standalone node on the CWM side, then CWM will reject the node on discovery, and the node will remain undiscovered.
Solution: On every standalone node, manually verify that the runConfigurator settings match the switch.
Chassis Identification During a Firmware Upgrade
On the CWM side, the emd.conf must be modified to a one second wait time so it can help clean up the emc process's internal cache and CWM database (regarding any slot that has sent the functional removal trap). This ensures that CWM will sync up whatever is current with the switch after the upgrade.
Before a firmware upgrade is begun, complete the following steps:
Step 1
"Hold for 300 secs before deleting the card after a func module trap is received".
to
"Hold for 1 secs before deleting the card after a func module trap is received".
Note
Step 2
Step 3
Step 4
Service Module Installation/Upgrade and Flash Download Requirements.
Caution
If you are moving service modules from an existing MGX 8220 platform to the MGX 8850, the MGX 8220 service modules (AX-FRSM-8T1/E1, and AX-CESM-8T1/E1) need to have the boot flash upgraded to MGX 8220 Release 5.0.00 common boot code (1.0.01 version) before they can be plugged in the MGX 8850 chassis. All MGX 8220 service module versions that use Release 4.0.xx of boot code and earlier are not supported in the MGX 8850.
SPARE DEPOT: Customers receiving a replacement service module via the TAC (through the RMA process) will have the common boot code image that works for MGX 8220 Release 4.x, 5,x, and MGX 8850 installed on legacy service modules. (Spare service modules received directly from manufacturing through the normal ordering process will have the correct boot code image already loaded.)
If loading of the correct common boot code image is required then it will have to be performed on an MGX 8220 chassis, and cannot be performed on an MGX 8850 chassis. Please refer to the procedure below, which is also outlined in the Cisco MGX 8850 Installation and Configuration Guide on the documentation CD.
Use ftp to port the Axis 5 common boot image for the service module to a workstation.
Plug in the card into the MGX 8220 shelf.
Download the proper MGX 8220 shelf Release 5.0 boot image using the following commands from the workstation:
tftp <ip address of the MGX 8220 shelf >binput <boot filename> AXIS_SM_1_<slot#>.BOOTNow you must insure that TFTP downloaded the appropriate boot code by verifying the flash checksums.
Login to the shelf.
cc <slot #>'chkflash'Verify that the two checksums are the same.
If NOT, repeat the process until they are the same. If they are the same, then you can safely remove the card. At this point the service module can be used in the MGX 8850 shelf.
Service Module Upgrades
The following steps need to be followed for service module upgrades. Service module firmware images cannot be downloaded as specific versions in MGX 8850 Release 1.1.32 because only one image can be present on the disk at one instance. Hence the user cannot revert back during the installation process.
Step 1
unix-prompt> tftp shelf.ip.addresstftp> bintptp>put frsm_8t1e1_10.0.01.fw POPEYE@SM_1_0.FWSent 1982672 bytes in 18.3 secondsMake sure that the transfer is successful by looking at the message displayed on the PXM console after the transfer:
Program length = 1982672Calculated checksum = 0xd9779bc6 stored checksum = 0xd9779bc6Fw checksum passedRepeat for each service module type and for each slot-independent firmware.
For a slot-specific image (in this example the service module is tied to slot 1),
tftp <ip address of the MGX 8850 shelf >binput frsm_<version>.fw POPEYE@SM_1_1.fwfor a slot-dependent image,
Note
•
•
Step 2
Step 3
install sm <slot> <version>where <slot> is the service module that is being upgraded
and <version> is the service module image on the disk.
Note
newrev sm <slot> <version>where <slot> is the service module that is being upgraded
and <version> is the service module image on the disk.
commit sm <slot> <version>where <slot> is the service module that is being upgraded
and <version> is the service module image on the disk.
Note
Known Anomalies for Platform Software Release 1.1.34 and Service Module Firmware
The following is the list of known anomalies in the service module firmware and the Release 1.1.34 software. Included with each is a brief discussion of the problem. A more in-depth discussion is available in the Release Note enclosure of the problem record in Bug Navigator.
Known Anomalies for Platform Software Release 1.1.32 and Service Module Firmware
The following is the list of known anomalies in the service module firmware and the Release 1.1.32 software. Refer to Bug Navigator for a current description of these problems, or to the 1.1.32 Version Software Release Notes Cisco WAN MGX 8850, 8230, and 8250 Software.
CSCdk54268
When sending cells of VPI=0, VCI=0, and CLP=1 from a UNI port, dspportcnt reports the cells as being discarded due to VpiVciErr and the cell rate also gets updated.
CSCdk71643
End-to-end connectivity with full recovery in cases of error does not fully function with current design.
CSCdk86638
When using CWM to add connections, if the connection addition request times out, subsequent addition of the same connection may fail as well, complaining that the connection already exists (even though it timed out).
CSCdm05358
When modifying a particular protected memory address on CESM8p, which causes CESM HW watchdog reset, PXM got reset or lost SAR functionality.
CSCdm10722
SM upgrade should be done with the following commands in this order: install, newrev and commit .
CSCdm11410
When listing a directory, some file names contain either illegal characters or a timestamp for the name instead of a standard DOS file name.
CSCdm22510
Connection traps are not sent out when receiving A-bit update from CPE. Related to CSCdm22510.
CSCdm31437
SV+ needs a trap when a line is added or deleted.
CSCdm33351
An Endpoint Added Trap message and an Endpoint is Active message are sent to the manager from VISM.
CSCdm33605
When a switchover to a redundant VISM card takes place due to a reset/failure of the active VISM card, the display on CWM is not correct.
CSCdm33638
When a switchover to a redundant VISM card takes place, the display of active lines is not consistent between the shelf and CiscoView.
CSCdm42849
An execution of the dlmi command to display LMI messages results in a system reboot.
CSCdm43053
Connection addition fails.
CSCdm48639
Better error checking needs to be provided for SM boot and firmware download. It's possible to download the boot image as firmware and vice versa.
CSCdm53758
Channel alarms do not get propagated to the middle segment if NNI signaling is enabled.
CSCdm56094
The far-end device cannot be put into a loopback using the "Far End Inband Loopback" or the "Far End ESF Loopback" options under the "DEVICE TO LOOP" menu in the cnfbert command.
CSCdm85931
There are display errors for FRSM-HS1 card for dspchancnt 17.
CSCdm91930
LED status in CWM is different for lines in same status in Active card/hot standby.
CSCdm92345
The VHS SM have either DAX or FEEDER connections on the logical port, which is simulated with some kind of signaling.
CSCdp00912
Core redundancy should be allowed in mismatch state
CSCdp11859
The ABCD bits that are produced on the egress of a CCS-to-CAS connection seem to have a random/unpredictable pattern.
CSCdp32043
SV+ node sync always failed because of timeout, due to TFTP very low.
CSCdp34543
Install backup boot fails when it tries to program the flash on the standby card.
CSCdp35772
This should not affect the normal running of the system as the background memory check checks for memory corruption and leaks.
CSCdp36477
The switchcc on 8850 causes a Sig_F APS line switch on BPX.
CSCdp39894
The software error is logged as a result of an attempt to refer to a transaction that is already complete.
CSCdp39900
The software error is logged when trying to allocate a msg buffer to send VSI commit for a connection.
CSCdp42349
A PXM1-155 alarm is issued.
CSCdp44837
When deleting a large number of connections using a script, it was found that for some connections, the resources were not properly freed.
CSCdp46927
VISM card in alarm after addcid.
CSCdp48790
This problem has not been reproducible.
CSCdp50045
During boot time, VC-create failed message will be displayed.
CSCdp50317
Information displayed using the dsphotstandby command is not consistent.
CSCdp51707
Removing a Service Module, then inserting an RPM in the same slot causes the RPM to go to Active State instead of Mismatch.
CSCdp52549
This software error has been a one-time occurrence when deleting a connection.
CSCdp52776
New CLI command to delportrscprtn for the AUSM and the FRSM.
CSCdp53342
Information on this anomaly is unavailable at this time.
CSCdp53347
If two different HS1 SM have too many master and slave connections, delete about 15 slaves first.
CSCdp59851
Per the log messages, PAR failed, followed by PVC deletion.
CSCdp60443
A data outage occurs on the FRSM-2CT3, up to 15 seconds in length.
CSCdp63530
FRSM-2T3 fails after upgrading causing switchover to secondary.
CSCdp63922
Connections could not be added successfully from a SM, with a particular port/DLCI combo that did not seem to be used.
CSCdp63924
SYSTEM ERROR 20102 (PV_DB_RMV_ERR) is reported when we try to refer a completed transaction. Duplicate of the bug CSCdp39894.
CSCdp65639
Existence of any such problem that can lead to time-out scenario described in the bug report would be the one to be addressed as the root cause.
CSCdp65652
The ImaGroupRxImaId is not updating properly on the AUSM when the TxImaGroupId parameter is manually changed via the Kentrox CPE.
CSCdp71408
No information is available about this anomaly at this time.
CSCdp75846
In the AAL1 cells generated by CESM for a Structured T1 CAS connection, the AAL1 pointer may not be pointing to the first 125 us frame of the multiframe.
CSCdp77451
Inserting standby PXM can cause the Telnet to be lost on the active PXM.
CSCdp81287
The clrsmcnf says unsupported SM for CESM-8E1.
CSCdp84145
When adding a connection from CWM using local and remote nodename, which is different from the one configured on the node (because CWM is not synced), the addcon request erroneously passes and the connection gets added.
CSCdp84773
It has been found that the Resource Partitioning of an AUSM card on the PXM is registered as zero instead of a value of three.
CSCdp86479
PVCs shown as UP on RPM even when they are deleted remotely.
CSCdp89717
In some cases, when RPM fails, it is not declared as failed on PXM, and any attempt to cc to this FAILED card fails, even though it is showing ACTIVE on PXM.
CSCdp92736
The line, port, channel counters are reset to zero, and start counting from 0 after a switchcc.
CSCdp93004
When a connection fails, the A-bit status displayed on the connection manager for the particular connection always stays as "ok".
CSCdp94060
Receiving user connection modification traps 25015 for no reason.
CSCdp96632
The table rpm_port parameter will have -1 value, even if the port is in the active state.
CSCdp99496
When FRSM-VHS2T3? is ran, the return display shows that dspportstats is a command. However, no such command exists.
CSCdr00016
This problem was encountered sometimes when deleting more than 500 connections using a single delchans command.
CSCdr01410
PXM resets if holding down the return key while cc'ed to a service module.
CSCdr01426
Error logs overwritten and no core dump. Information is not retained on reset.
CSCdr02667
When IMA ports are configured on AUSM via SRM (BULK distribution), execution of switchcc causes IMA port failure.
CSCdr04154
Customer has come upon a failed PXM in their shelf and would like to have EFA done on it to determine the root cause of the failure.
CSCdr05471
Softswitch caused FRSM-CT3 cards to go to failed state, and ed map in the PXM had the same slot number for both the entries.
CSCdr06052
The dspcd in PXM would show the FAB number as 800-XXX, which is actually the PCB number.
CSCdr10332
Upon switchcc, AUSM in bulk mode receives wrong VPI-VCI cells.
CSCdr11454
PVC alarm status was not reported correctly after a Softswitch was executed on FRSM-2CT3.
CSCdr14672
Standby FRSM shows not available under redundancy and hot standby table.
CSCdr15892
The addlnloop on the PXM causes SONET line alarms, which sometimes do not clear when the loop is removed.
CSCdr16499
RPM sends Trap 50600 after resetcd.
CSCdr16720
Softswitch caused the standby FRSM-VHS to Failed state. (Though Softswitch succeeded according to the CLI it really didn't occur.)
CSCdr17959
AUSM card hangs if 2 to 3 ILMI requests are sent on a port. It reboots if 5 ILMI requests are sent.
CSCdr19456
Sending five ILMI requests to an AUSM card makes the directly connected AUSM card reboot.
CSCdr20239
When the command tstcon is issued, it clears the alarm status of connection when connection is failed due to remote A-bit failure.
CSCdr21393
The AUSM-AUSM loopback connections go into alarm.
CSCdr22375
The added between SMs fails to report a feature mismatch but dspsmcnf shows identical feature bitmaps for the two SMs.
CSCdr23964
The 50012 trap is sent twice.
CSCdr25038
There are times when we are not able to send the cc frame to the RPM card and as such not able to do a cc.
CSCdr25083
Mod Conn fails with error "Wrong OID or problem with Varbind" for FRSM-VHS endpoint connections. Both DAX/NONDAX.
CSCdr25163
Details on this anomaly are not available at this time.
CSCdr26529
Able to restoresmcnf on a different slot.
CSCdr28177
During a switchcc, VISM lines go into yellow alarm for a very short interval.
CSCdr36469
CLI commands are required to display the NOVRAM contents of all the MGX 8850 cards.
CSCdr41616
Unable to Telnet to the active FRSM card even when there only one cc session initiated to that SM.
CSCdr43216
The stand-by PXM and all service modules go into a failed stated after 64-byte packet transmitted from RPM.
CSCdr44024
The MGX and BPX defaults are consistent. The solution is to explicitly configure the framing. AXSM needs to be changed.
CSCdr44337
The aveallcnf creates 2 identical files.
CSCdr44487
System error is printed onscreen.
CSCdr49478
One-time occurrence. After a sequence combination of adding and deleting SM redundancy and clrsmcnf, and connection deletion/addition, tstcon is not passing on certain connections
CSCdr53807
The LED on a card is green even though the card failed.
CSCdr57422
Channel Active or Channel Added trap was not received by CWM.
CSCdr58123
The card gets reset.
CSCdr58189
Alarm status is inconsistent for standby PXM card.
CSCdr60198
The Arbiter PLD on the existing 4E back cards is not compatible with the PCI rev2.1 Port Adapter bridges that are used on the RPM-PR.
CSCdr61309
MGX log fills up when the Frame Relay port is in alarm.
CSCdr61335
The card gets reset.
CSCdr61360
When the AUSM card is receiving AIS from the network side as well the A-bit alarm from PXM, duplicate AIS on the port side orrurs.
CSCdr61544
No information is available about this anomaly at this time.
CSCdr62285
When running BERT tests on CESM lines or ports, the PXM might report a general error.
CSCdr62322
Some of the BERT test patterns, for example, QRSS, fail to synchronize with the new CESM-8T1 card.
CSCdr62361
Able to configure line parameters on an FRSM when BERT port tests are running.
CSCdr62370
BERT pattern tests on the SRM-3T3-C are intermittently not synchronized with the FRSM-8E1 module.
CSCdr66666
Some of the lines in IMA group become unavailable. Duplicate of CSCdr58168.
CSCdr68155
Sometimes the disk update messages for the simulated delete connection/delete port done when the clrsmcnf command is issued occurs after the database is removed.
CSCdr71479
Lines on AUSM/B in slot 9 of MGX 8850 are failed upon switchover to redundant AUSM/B.
CSCdr71982
CESM addred displays incorrect error message when the card is in Reserved State.
CSCdr73483
Information on this anomaly is unavailable at this time.
CSCdr82396
The srvovrd option is not functioning in cnfchansrvrate command.
CSCdr90512
Not able to collect statistics from the MGX 8850 Release 1 shelf.
CSCdr90658
Even though xaddcon/xcnfcon displays 38328 cps as the maximum value if calculated, do not configure it to a maximum of 38328 cps.
CSCdr90871
Customer is requesting additional information be provided in the log file when a PVC is deleted.
CSCdr90987
The cnfclklevel command succeeds for level 3 even if the old PXM UI back card is used.
CSCdr91331
Configurations, like bulk mode SRM configurations, seen in unused slots of the shelf.
CSCdr91665
The displayShelfBanner on Standby PXM does not display the right banner.
CSCdr92373
PUBLIC community string should be "READ-ONLY", on MGX "PUBLIC" can be used to write by SNMP.
CSCdr93342
Details on this anomaly are not available at this time.
CSCdr93376
Details on this anomaly are not available at this time.
CSCdr93664
Unused slots on 8250 show up as "reserved" even after a clrallcnf.
CSCdr96138
Configure the transmit FEAC code to be dsx3SendPayloadCode on DS1s, which should be rejected since DS3 application on PXM is unchannelized.
CSCdr98578
Parameter fields for command dspalms is not preceded with an -example: dspalms ds3 | e3 | SONET instead of dspalms -ds3 | -e3 | -SONET
CSCds03072
The soft reset path on the RPM-PR rommon is not re-initializing the TLB correctly.
CSCds04372
Initial Burst Size behavior (IBS) is not functioning correctly for the ABR connections.
CSCds05040
The major alarm LED on the active and the standby PXM on MGX 8850 are on, while the CLI commands do not show any indication of alarm.
CSCds05580
On doing a dspcon on a PXM connection, the remote end LCN is displayed as 0.
CSCds05593
Issue a clralm on the SRM and the AlarmState clears. Issue a clralm on any SM (AUSM, FRSM, CESM) and the AlarmState does not clear.
CSCds05978
On trying to use option "*" for VCI in the cnfilmi command as specified in the CLI help, the command returns an error.
CSCds07944
The clralmcnt -ds3 does not clear the counters.
CSCds08528
The ports do not go into signaling failure even after the two ports have a signaling mismatch.
CSCds09036
The version displays StrataCom instead of displaying Cisco.
CSCds09448
At present CWM is setting %util values(lper_util, rper_util) to -1. CWM will get these values from * TFTP config UpLoad File * SNMP UpLoad file.
CSCds10270
When a OC-12 feeder trunk is configured as 1+1 unidirectional mode, the PXM-622 OC-12 line had no option to specify "working" or "protection" line would be applied upon an external request .
CSCds10279
Request for user-friendly APS status information.
CSCds10286
The PXM displays the incorrect error message when trying to switch APS line using switchapsln CLI.
CSCds10287
An APS protection switch has occurred because of line alarm. When the status of dsptrks and dspalms are checked, they indicate that the lines are clear.
CSCds10377
When one of the OC-12/OC-3 lines are in alarm, the CLI dspapsln shows the line status as "ALM" instead of specifically indicating LOS/LOF.
CSCds10765
Software error 20304 was observed during resetsys/switchcc.
CSCds11679
No known workaround. To be fixed in later releases.
CSCds12647
From Cisco WAN Manager, v9.2.07, Connection Manager, customer tries to create a new NRTVBR3 connection on MGX 8850. There are three passwords: login, password, and RPM enable password.
CSCds13629
Issue clrallcnf on PXM, RPM-PR failed to erase the connection setup in NVRAM.
CSCds14812
During a switchcc, the AUSM Secondary active card LEDS show LOS for a while.
CSCds15610
PXM takes long time (10+ mins) to reprogram the connections after power recycle.
CSCds15835
When a user configures a CESM-T3 or E3 line in a local loopback, the dspalm display does not indicate that the loopback is configured on the line.
CSCds16990
When issuing clrsmcnf, an "auto:upLoadBram, Read file failure" can be seen on screen.
CSCds17001
Log file cannot be found for a particular slot.
CSCds18374
Reset of an FRSM-HS2 card corrupted the PXM card type matrix and it started displaying improper card types.
CSCds18459
The help string shows an incorrect value for the line rate.
CSCds18513
Error message while configuring the line rate gave a misleading reason for failure.
CSCds18524
Addcon help for CIR shows a range greater than the possible line rate.
CSCds18760
Local Connection ID returns wrong VPI on the slave side of addcon.
CSCds19141
The card goes into mismatched after the CLI cnfbctype.
CSCds19155
The tstcon passes for a deleted side of connection.
CSCds19333
The port loopbacks trap are not generated when the loopback is initiated using BERT.
CSCds19363
Details on this anomaly is not available at this time.
CSCds19477
Details on this anomaly is not available at this time.
CSCds19934
Port is generating a large number of async updates when the connection is made up/down.
CSCds20497
An alarm is not raised by the slave end when the corresponding master end is deleted.
CSCds25261
SNMP trap to indicate ILMI failure on AUSM card causes HP OpenView to crash.
CSCds25992
The command cnfplpp configures a line even when the line has not been added/enabled.
CSCds28525
The alarm status for the connection shown at CESM and PXM do not match. The CLIs tstcon and tstdelay fails for these connections.
CSCds38687
FRSM-8T1/E1 takes Invalid (lesser) no. of parameters in the addcon CLI and does not display any error message.
CSCds47676
When the clock level is configured to be STRATUM-3, the PXM trunk card does not receive the STRATUM-3 clock signal. The trunk card still gets the STRATUM-4 clock.
CSCds47699
The cnfupcvbr setting incorrect default ingress %util when parm=0.
CSCds47719
The xdspconstdabr and xdspcon displayed the contents of the first channel, when the channel number was given without the "-chn" prefix.
CSCds48610
Neither the VBR connections are getting higher bandwidth even when it has higher Maxbwinc values than CBR and ABR VCC's.
CSCds48615
The VBR connections are not getting a higher bandwidth even though their CLP-high and CLP-Low values are changed to Q-Max.
CSCds51198
RPM-PR crashes in boot mode when in dir c:
CSCds52875
The value of Maxbwinc is reset to 0 after this action and hence traffic is stopped.
CSCds52894
Maxbwinc in all queues can total up to more than 512; however, if the rtVBR queue set to Algorithm 3, the Minbwinc in nrtVBR, ABR, and UBR were set to 0; the rtVBR Minbwinc= 447.
CSCds53841
There are six type options available to set the CoS. No ConnServiceType option for rtVBR.
CSCds56829
After switchcc the Standby PXM back card still displays on.
CSCds59688
CESM/T3 & CESM/E3 failed to upgrade to 10.0.20 version.
CSCds60827
The FRSM 2CT3 VCCs were configured with CBR and CIR=4240.
CSCds63641
FRSM/T1 in an MGX1 Feeder node, added 470 CBR VCCs on port 1 with script.
CSCds64800
The FRSM/2T3 card was in Active, with 200 VCCs.
CSCds65754
Both PXM modules stuck in boot mode.
CSCds78615
Redundant PXM goes into failed state when restoring SM configuration.
CSCds81277
Adding a slave connection on FRSM-HS1/B returns a wrong Local Connection ID.
CSCds81743
A system error 21205 is sometimes seen after invoking a switchcc.
CSCds82088
The clrsmcnf gives wrong error message when the card is not present.
CSCds82667
Ports are Alarms Free when line and channels are on Alarms.
CSCds82670
delchans causes Telnet session to freeze.
CSCds83090
The clrsmcnf times out when deleting a non-existent port on FRSM-8E1.
CSCds83131
The clrsmcnf fails after a Service Module is replaced with an RPM.
CSCds83554
When doing a graceful upgrade, a system error is sometimes seen.
CSCds83584
The savesmcnf/restoresmcnf are not blocked for RPM cards even though the commands are not supported.
CSCds84695
Display for slot 14 disappears in MGX 8230.
CSCds85934
Restoring the SMs configuration takes a long time (8 to 20 mins) using CLI restoresmcnf <slot #>.
CSCds86720
One end of Frame Forwarding connection is permanently on Alarm.
CSCds86780
The dspcd, dspln, dsplns, dspport, dspports, dspcon, dspcons commands never prompt after adding multiple 3 segment connections.
CSCds87189
The RcvLOS count toggles between 0 and 252.
CSCds89200
SYSTEM ERROR 20301 logged after deleting a frame forwarding port.
CSCds89508
Able to configure the port N393 timer values less than N392.
CSCds89838
The delchans command causes SYSTEM ERROR 20404.
CSCds90056
DAX connections on FRSM-HS1/B are free of alarms after removing one of the two cards used to establish those connections.
CSCds91080
The addport command with wrong port type causes Data Bus Error.
CSCds92204
System Error 20617 caused by delchans command.
CSCdt00596
The dspcons command display is not aligned on FRSM-HS2
CSCdt00613
The dlecon or delchans commands when deleting connections cause System Error 20300.
CSCdt03252
The tstcon and tstdelay fail for the CESM-T3 to CESM-T3 three-segment connection.
CSCdt03580
Ungraceful upgrades of AUSM-8E1 sometimes fail when the configuration for the SM is lost. This problem occurred once.
CSCdt05474
A bit alarm on a three-segment connection is not propagated from PXM to FRSM-2T3
CSCdt05984
The xcnfchan command does not display the setup options correctly.
CSCdt07206
On a PXM to PXM feeder connection, when doing a dspchancnt on the ATM port side of the connection, "Discard Cells to Port" shows that cells have been discarded.
.
CSCdm22510
The NNI part of the connection is working correctly. A=0 is being sent from the tester to the local port of the FRSM and the remote port of the FRSM is sending A=0 to the remote port of the tester. However, Test Suite 16 of Bellcore's Frame Relay Protocol Conformance Certification Test Suites states "Since the active/inactive indication is independent of direction, the IUT(FRSM) Local port (DLCI 16) should transmit STATUS messages with ACTIVE status to the local test equipment." In other words port 1(Local port) of the FRSM should also transmit A=1 back to port 1(Local port) of the tester. This is stated in Frame Relay Forum Document No. FRF 2.1 Frame Relay Network-to-Network Interface Implementation Agreement. This was verified by Bellcore Engineers.
The last sentence of the expected results statement: "Since the active/inactive indication is independent of direction, the IUT Local port (DLCI 16) should transmit STATUS messages with ACTIVE status to the local test equipment." is correct as stated. This statement actually reflects a requirement from FRF 2.1 Section 4.2:
"PVC status information from full status reports and optionally from single PVC asynchronous status reports shall be propagated toward the user-to-network interface (UNI) of the multi-network PVC. The PVC status information element active bit state signaled at the NNI is independent of the PVC status information element active bit state signaled in the other direction at the same NNI."
Bidirectional status signaling requires that a user-side process and a network-side process execute concurrently. Nowhere in the requirements, Annex A, Annex D, FRF 2.1 does it state that these processes share information. They are totally independent. PVC status is signaled to the local user based on the service affecting conditions or PVC status signaled from the remote user side.
Polling Requirements of Network-to-network Interfaces
Two sets of sequence numbers and local in-channel signaling parameters are administered for the network-to-network interface as shown below; see the table for parameter ranges and default values.
•
•
The table below summarizes the acceptable values when using bidirectional procedures at the NNI. The default values should be used as the actual system parameter values. Parameter values other than the default values are a subscription time option. Procedures for starting and stop T391 and T392 are described in Q.933 Annex A.
Both networks are required to initiate status enquiry messages based on T391. A full status report is requested each N391 (default 6) polling cycles. Both networks shall have the same values for T391, T392, N392, and N393 for both user side procedures and network side procedures; N391 is not required to have the same value in both networks.
PVC status information from full status reports and optionally from single PVC asynchronous status reports shall be propagated towards the user-to-network interface (UNI) of the multi-network PVC. The PVC status information element active bit state signaled at the NNI is independent of the PVC status information element active bit state signaled in the other direction at the same NNI.
Note
Known Anomalies for RPM release 12.1(1)T
1.
The user will still be able to add the connections. The only side effect is that there will be a syslog entry (and a message on the console, if not under Telnet) every five minutes.
2.
Known Anomalies for RPM Release 12.0(5)T1
These RPM anomalies are tied to its function with the MGX 8850. For generic IOS issues, refer to the 12.0.5T1 release notes.
•
•
•
Note
•
•
•
This problem will not occur when either enough time is given to the protocols to converge or the newly added connections are just added without enabling these protocols, and later these protocols are enabled on them.
To avoid this condition, you may limit the tag PVP connections to 75 or fewer. Above this, the TDP updates may create a CPUHOG condition (with CPU utilization very high). This in turn will break the IPC channel between PXM and RPM, and PXM will declare the RPM as Failed.
•
•
If not, the saved config needs to be copied to running config by "copy" command.
•
•
%error opening c: filename (bad file number)
message then delete:
(rm <filename>)
the existing file and then copy the new file.
•
If the PVC leg of the connections is added using the pvc command, then the "VCD" is chosen automatically for those PVCs. If the RPM is reloaded, then these VCD values might change. If they do change, then those connections will appear in the mismatched state.
This condition does not affect traffic. The problem can be avoided by using the atm pvc command which requires the user to specify the VCD value explicitly in the command. The "show switch connections nextvcd" command can be used to determine a VCD value that can be used with the atm pvc command.
In the event that the pvc commands were used and the connections go into the mismatched state, they can be cleaned up by re-adding the affected connections or if all the connections are affected and all of them are in the mismatched state, they can all be re-added using the "copy startup-config running-config" command.
This problem is fixed in the 120-5.T1 release.
RPM Configuration Examples for MPLS-based Virtual Private Networks
The following are MPLS VPN examples with MGX/RPM. These examples will be included in the online version of the Cisco RPM Installation and Configuration publication.
One PE - Two CE Configuration
The following is a one PE and two CE VPN configuration.
Note
e10/1/2+---------+e0/1 +---------+ PVC +----------+ e14/1/2| CE1 |--------------| PE1 |--------------| PE2 |------+| sys-2-1 | +-------| |sw1.1 sw1.1| | |+---------+ | +---------+ +----------+ || e0/3 | e10/1/3 || | || e0/2 | |+---------+ | +----------+ e0/1 || CE3 |------+ | CE2 |------+| sys-2-2 |e0/1 PE1 ==> RPM-18-110 | sys-2-4 |+---------+ PE2 ==> RPM-18-114 +----------+One PE - Two CE Configuration - OSPF & IBPG Between PEs & EBGP between PE-CE
CE1 Configuration:
sys-2-1#sho runBuilding configuration...Current configuration:!version 12.0service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname sys-2-1!boot system tftp mpls/12.0/c3620-js-mz.120-5.0.2.T2 3.3.0.1logging buffered 4096 debuggingno logging console!!!!!ip subnet-zerono ip domain-lookupip host ios-lab-fw 3.3.0.1!ip cefcns event-service server!!!process-max-time 200!interface Loopback0ip address 12.12.12.12 255.255.255.255no ip directed-broadcast!interface Ethernet0/0ip address 3.3.30.1 255.255.0.0no ip directed-broadcastshutdown!interface Ethernet0/1ip address 50.0.0.1 255.0.0.0no ip directed-broadcast!interface Ethernet0/2no ip addressno ip directed-broadcastshutdown!interface Ethernet0/3ip address 52.0.0.1 255.0.0.0no ip directed-broadcast!interface Serial1/0no ip addressno ip directed-broadcastshutdownno fair-queue!interface Serial1/1no ip addressno ip directed-broadcastshutdown!interface Serial1/2no ip addressno ip directed-broadcastshutdown!interface Serial1/3no ip addressno ip directed-broadcastshutdown!router ospf 100redistribute bgp 101passive-interface Ethernet0/1network 12.0.0.0 0.255.255.255 area 100network 52.0.0.0 0.255.255.255 area 100!router bgp 101no synchronizationnetwork 12.0.0.0network 13.0.0.0network 50.0.0.0network 51.0.0.0network 52.0.0.0neighbor 50.0.0.2 remote-as 100!ip default-gateway 3.3.0.1no ip classlessno ip http server!!!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4password lablogin!!endsys-2-1#sys-2-1#CE2 Configuration
sys-2-4#sho runBuilding configuration...Current configuration:!version 12.0service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname sys-2-4!boot system tftp mpls/12.0/c3640-js-mz.120-5.0.2.T2 3.3.0.1logging buffered 4096 debuggingno logging console!!!!!ip subnet-zerono ip domain-lookupip host ios-lab-fw 3.3.0.1!ip cefcns event-service server!!!process-max-time 200!interface Loopback0ip address 14.14.14.14 255.255.255.255no ip directed-broadcast!interface Ethernet0/0ip address 3.3.30.4 255.255.0.0no ip directed-broadcastshutdown!interface Ethernet0/1ip address 53.0.0.2 255.0.0.0no ip directed-broadcast!interface Ethernet0/2no ip addressno ip directed-broadcastshutdown!interface Ethernet0/3no ip addressno ip directed-broadcastshutdown!router ospf 100redistribute bgp 102passive-interface Ethernet0/1network 14.0.0.0 0.255.255.255 area 100!router bgp 102no synchronizationnetwork 14.0.0.0network 53.0.0.0neighbor 53.0.0.1 remote-as 100!ip default-gateway 3.3.0.1no ip classlessno ip http server!!!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4password lablogin!!endsys-2-4#sys-2-4#CE3 Configuration:
sys-2-2#sho runBuilding configuration...Current configuration:!version 12.0service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname sys-2-2!boot system tftp mpls/12.0/c3640-js-mz.120-5.0.2.T2 3.3.0.1logging buffered 4096 debuggingno logging console!!!!!ip subnet-zerono ip domain-lookupip host ios-lab-fw 3.3.0.1!ip cefcns event-service server!!!process-max-time 200!interface Loopback0ip address 13.13.13.13 255.255.255.255no ip directed-broadcast!interface Ethernet0/0ip address 3.3.30.2 255.255.0.0no ip directed-broadcastshutdown!interface Ethernet0/1ip address 51.0.0.2 255.0.0.0no ip directed-broadcast!interface Ethernet0/2ip address 52.0.0.2 255.0.0.0no ip directed-broadcast!interface Ethernet0/3no ip addressno ip directed-broadcastshutdown!interface Serial1/0no ip addressno ip directed-broadcastshutdownno fair-queue!interface Serial1/1no ip addressno ip directed-broadcastshutdown!interface Serial1/2no ip addressno ip directed-broadcastshutdown!interface Serial1/3no ip addressno ip directed-broadcastshutdown!router ospf 100redistribute bgp 101passive-interface Ethernet0/1network 13.0.0.0 0.255.255.255 area 100network 52.0.0.0 0.255.255.255 area 100!router bgp 101no synchronizationnetwork 12.0.0.0network 13.0.0.0network 50.0.0.0network 51.0.0.0network 52.0.0.0neighbor 51.0.0.1 remote-as 100!ip default-gateway 3.3.0.1no ip classlessno ip http server!!!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4password lablogin!!endsys-2-2#sys-2-2#PE1 Configuration:
rpm-18-110#sho runBuilding configuration...Current configuration:!version 12.0no service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname rpm-18-110!boot system tftp mpls/12.0/rpm-js-mz.120-5.T.bin 3.3.0.1no logging console!!!!!clock timezone EST -5clock summer-time EDT recurringip subnet-zerono ip domain-lookupip host ios-lab-fw 3.3.0.1!!ip vrf vpn1rd 100:1route-target export 100:1route-target import 100:1ip cefcns event-service server!!process-max-time 200!interface Loopback0ip address 11.11.11.11 255.255.255.255no ip directed-broadcast!interface Loopback1no ip addressno ip directed-broadcast!interface Ethernet1/1ip address 3.3.18.110 255.255.0.0no ip directed-broadcastno ip mroute-cacheno keepalive!interface Ethernet1/2ip vrf forwarding vpn1ip address 50.0.0.2 255.0.0.0no ip directed-broadcastno ip mroute-cacheno keepalivetag-switching ip!interface Ethernet1/3bandwidth 100ip vrf forwarding vpn1ip address 51.0.0.1 255.0.0.0no ip directed-broadcastno ip mroute-cachetag-switching ipno fair-queue!interface Ethernet1/4no ip addressno ip directed-broadcastno ip mroute-cacheno keepalive!interface FastEthernet2/1no ip addressno ip directed-broadcastno ip mroute-cache!interface Switch1no ip addressno ip directed-broadcastno atm ilmi-keepalive!interface Switch1.1 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 50 50 0 aal5snaptag-switching atm vp-tunnel 50tag-switching ip!interface Switch1.2 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 30 30 0 aal5snaptag-switching atm vp-tunnel 30tag-switching ip!interface Switch1.3 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 60 60 0 aal5snaptag-switching atm vp-tunnel 60tag-switching ip!router ospf 100passive-interface Ethernet1/2passive-interface Ethernet1/3network 11.0.0.0 0.255.255.255 area 100!router bgp 100no synchronizationno bgp default ipv4-unicastneighbor 10.10.10.10 remote-as 100neighbor 10.10.10.10 update-source Loopback0!address-family ipv4 vrf vpn1neighbor 50.0.0.1 remote-as 101neighbor 50.0.0.1 activateneighbor 51.0.0.2 remote-as 101neighbor 51.0.0.2 activateno auto-summaryno synchronizationexit-address-family!address-family vpnv4neighbor 10.10.10.10 activateneighbor 10.10.10.10 send-community extendedexit-address-family!ip default-gateway 3.3.0.1no ip classlessno ip http server!dialer-list 1 protocol ip permitdialer-list 1 protocol ipx permit!x25 host shorun!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4password lablogin!exception core-file mpls/mgx/dumps/rpm-18-110.corerpmrscprtn PAR 100 100 0 255 0 3840 4047addcon vpc switch 1.2 30 rslot 0 3 30 master localaddcon vpc switch 1.1 50 rslot 14 1 50addcon vpc switch 1.3 60 rslot 0 4 60 master localendrpm-18-110#rpm-18-110#rpm-18-110#PE2 Configuration:
rpm-18-114#sho runBuilding configuration...Current configuration:!version 12.0no service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname rpm-18-114!boot system tftp mpls/12.0/rpm-js-mz.120-5.T.bin 3.3.0.1no logging console!!!!!clock timezone EST -5clock summer-time EDT recurringip subnet-zerono ip domain-lookupip host ios-lab-fw 3.3.0.1!!ip vrf vpn1rd 100:1route-target export 100:1route-target import 100:1ip cefcns event-service server!!process-max-time 200!interface Loopback0ip address 10.10.10.10 255.255.255.255no ip directed-broadcast!interface Loopback1no ip addressno ip directed-broadcast!interface Ethernet1/1ip address 3.3.18.114 255.255.0.0no ip directed-broadcastno ip mroute-cacheno keepalive!interface Ethernet1/2bandwidth 100ip vrf forwarding vpn1ip address 53.0.0.1 255.0.0.0no ip directed-broadcastno ip mroute-cachetag-switching ipno fair-queue!interface Ethernet1/3no ip addressno ip directed-broadcastno ip mroute-cache!interface Ethernet1/4bandwidth 100no ip addressno ip directed-broadcastno ip mroute-cacheno fair-queue!interface Switch1no ip addressno ip directed-broadcastno atm ilmi-keepalive!interface Switch1.1 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 50 50 0 aal5snaptag-switching atm vp-tunnel 50tag-switching ip!interface Switch1.2 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 40 40 0 aal5snaptag-switching atm vp-tunnel 40tag-switching ip!interface Switch1.3 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 20 20 0 aal5snaptag-switching atm vp-tunnel 20tag-switching ip!router ospf 100passive-interface Ethernet1/2network 10.0.0.0 0.255.255.255 area 100!router bgp 100no synchronizationno bgp default ipv4-unicastneighbor 11.11.11.11 remote-as 100neighbor 11.11.11.11 update-source Loopback0!address-family ipv4 vrf vpn1neighbor 53.0.0.2 remote-as 102neighbor 53.0.0.2 activateno auto-summaryno synchronizationexit-address-family!address-family vpnv4neighbor 11.11.11.11 activateneighbor 11.11.11.11 send-community extendedexit-address-family!ip default-gateway 3.3.0.1no ip classlessno ip http server!dialer-list 1 protocol ip permitdialer-list 1 protocol ipx permit!!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4password lablogin!exception core-file mpls/mgx/dumps/rpm-18-114.corerpmrscprtn PAR 100 100 0 255 0 3840 4047addcon vpc switch 1.3 20 rslot 0 2 20 master localaddcon vpc switch 1.2 40 rslot 0 1 40addcon vpc switch 1.1 50 rslot 10 1 50 master localendrpm-18-114#One PE - Two CE Configuration - OSPF & IBPG Between PEs & RIP between PE-CE
CE1 Configuration
sys-2-1#sho runBuilding configuration...Current configuration:!version 12.0service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname sys-2-1!boot system tftp mpls/12.0/c3620-js-mz.120-5.0.2.T2 3.3.0.1logging buffered 4096 debuggingno logging console!!!!!ip subnet-zerono ip domain-lookupip host ios-lab-fw 3.3.0.1!ip cefcns event-service server!!!process-max-time 200!interface Loopback0ip address 12.12.12.12 255.255.255.255no ip directed-broadcast!interface Ethernet0/0ip address 3.3.30.1 255.255.0.0no ip directed-broadcastshutdown!interface Ethernet0/1ip address 50.0.0.1 255.0.0.0no ip directed-broadcast!interface Ethernet0/2no ip addressno ip directed-broadcastshutdown!interface Ethernet0/3ip address 52.0.0.1 255.0.0.0no ip directed-broadcast!interface Serial1/0no ip addressno ip directed-broadcastshutdownno fair-queue!interface Serial1/1no ip addressno ip directed-broadcastshutdown!interface Serial1/2no ip addressno ip directed-broadcastshutdown!interface Serial1/3no ip addressno ip directed-broadcastshutdown!router ripversion 2network 12.0.0.0network 50.0.0.0network 52.0.0.0no auto-summary!ip default-gateway 3.3.0.1no ip classlessno ip http server!!!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4password lablogin!!endsys-2-1#sys-2-1#CE2 Configuration
sys-2-4#sho runBuilding configuration...Current configuration:!version 12.0service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname sys-2-4!boot system tftp mpls/12.0/c3640-js-mz.120-5.0.2.T2 3.3.0.1logging buffered 4096 debuggingno logging console!!!!!ip subnet-zerono ip domain-lookupip host ios-lab-fw 3.3.0.1!ip cefcns event-service server!!!process-max-time 200!interface Loopback0ip address 14.14.14.14 255.255.255.255no ip directed-broadcast!interface Ethernet0/0ip address 3.3.30.4 255.255.0.0no ip directed-broadcastshutdown!interface Ethernet0/1ip address 53.0.0.2 255.0.0.0no ip directed-broadcast!interface Ethernet0/2no ip addressno ip directed-broadcastshutdown!interface Ethernet0/3no ip addressno ip directed-broadcastshutdown!router ripversion 2network 14.0.0.0network 53.0.0.0no auto-summary!ip default-gateway 3.3.0.1no ip classlessno ip http server!!!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4password lablogin!!endsys-2-4#sys-2-4#sys-2-4#CE3 Configuration
sys-2-2#sho runBuilding configuration...Current configuration:!version 12.0service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname sys-2-2!boot system tftp mpls/12.0/c3640-js-mz.120-5.0.2.T2 3.3.0.1logging buffered 4096 debuggingno logging console!!!!!ip subnet-zerono ip domain-lookupip host ios-lab-fw 3.3.0.1!ip cefcns event-service server!!!process-max-time 200!interface Loopback0ip address 13.13.13.13 255.255.255.255no ip directed-broadcast!interface Ethernet0/0ip address 3.3.30.2 255.255.0.0no ip directed-broadcastshutdown!interface Ethernet0/1ip address 51.0.0.2 255.0.0.0no ip directed-broadcast!interface Ethernet0/2ip address 52.0.0.2 255.0.0.0no ip directed-broadcast!interface Ethernet0/3no ip addressno ip directed-broadcastshutdown!interface Serial1/0no ip addressno ip directed-broadcastshutdownno fair-queue!interface Serial1/1no ip addressno ip directed-broadcastshutdown!interface Serial1/2no ip addressno ip directed-broadcastshutdown!interface Serial1/3no ip addressno ip directed-broadcastshutdown!router ripversion 2network 13.0.0.0network 51.0.0.0network 52.0.0.0no auto-summary!ip default-gateway 3.3.0.1no ip classlessno ip http server!!x25 host shorun!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4password lablogin!!endsys-2-2#sys-2-2#PE1 Configuration
rpm-18-110#sho runBuilding configuration...Current configuration:!version 12.0no service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname rpm-18-110!boot system tftp mpls/12.0/rpm-js-mz.120-5.T.bin 3.3.0.1no logging console!!!!!clock timezone EST -5clock summer-time EDT recurringip subnet-zerono ip domain-lookupip host ios-lab-fw 3.3.0.1!!ip vrf vpn1rd 100:1route-target export 100:1route-target import 100:1ip cefcns event-service server!!process-max-time 200!interface Loopback0ip address 11.11.11.11 255.255.255.255no ip directed-broadcast!interface Loopback1no ip addressno ip directed-broadcast!interface Ethernet1/1ip address 3.3.18.110 255.255.0.0no ip directed-broadcastno ip mroute-cacheno keepalive!interface Ethernet1/2ip vrf forwarding vpn1ip address 50.0.0.2 255.0.0.0no ip directed-broadcastno ip mroute-cacheno keepalivetag-switching ip!interface Ethernet1/3bandwidth 100ip vrf forwarding vpn1ip address 51.0.0.1 255.0.0.0no ip directed-broadcastno ip mroute-cachetag-switching ipno fair-queue!interface Ethernet1/4no ip addressno ip directed-broadcastno ip mroute-cacheno keepalive!interface FastEthernet2/1no ip addressno ip directed-broadcastno ip mroute-cache!interface Switch1no ip addressno ip directed-broadcastno atm ilmi-keepalive!interface Switch1.1 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 50 50 0 aal5snaptag-switching atm vp-tunnel 50tag-switching ip!interface Switch1.2 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 30 30 0 aal5snaptag-switching atm vp-tunnel 30tag-switching ip!interface Switch1.3 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 60 60 0 aal5snaptag-switching atm vp-tunnel 60tag-switching ip!router ospf 100passive-interface Ethernet1/2passive-interface Ethernet1/3network 11.0.0.0 0.255.255.255 area 100network 50.0.0.0 0.255.255.255 area 100network 51.0.0.0 0.255.255.255 area 100!router ripversion 2!address-family ipv4 vrf vpn1version 2redistribute bgp 100 metric 2network 50.0.0.0network 51.0.0.0no auto-summaryexit-address-family!router bgp 100no synchronizationno bgp default ipv4-unicastneighbor 10.10.10.10 remote-as 100neighbor 10.10.10.10 update-source Loopback0!address-family ipv4 vrf vpn1redistribute ripno auto-summaryno synchronizationexit-address-family!address-family vpnv4neighbor 10.10.10.10 activateneighbor 10.10.10.10 send-community extendedexit-address-family!ip default-gateway 3.3.0.1no ip classlessno ip http server!dialer-list 1 protocol ip permitdialer-list 1 protocol ipx permit!!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4password lablogin!exception core-file mpls/mgx/dumps/rpm-18-110.corerpmrscprtn PAR 100 100 0 255 0 3840 4047addcon vpc switch 1.2 30 rslot 0 3 30 master localaddcon vpc switch 1.1 50 rslot 14 1 50addcon vpc switch 1.3 60 rslot 0 4 60 master localendrpm-18-110#rpm-18-110#PE2 Configuration
rpm-18-114#sho runBuilding configuration...Current configuration:!version 12.0no service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname rpm-18-114!boot system tftp mpls/12.0/rpm-js-mz.120-5.T.bin 3.3.0.1no logging console!!!!!clock timezone EST -5clock summer-time EDT recurringip subnet-zerono ip domain-lookupip host ios-lab-fw 3.3.0.1!!ip vrf vpn1rd 100:1route-target export 100:1route-target import 100:1ip cefcns event-service server!!process-max-time 200!interface Loopback0ip address 10.10.10.10 255.255.255.255no ip directed-broadcast!interface Loopback1no ip addressno ip directed-broadcast!interface Ethernet1/1ip address 3.3.18.114 255.255.0.0no ip directed-broadcastno ip mroute-cacheno keepalive!interface Ethernet1/2bandwidth 100ip vrf forwarding vpn1ip address 53.0.0.1 255.0.0.0no ip directed-broadcastno ip mroute-cachetag-switching ipno fair-queue!interface Ethernet1/3no ip addressno ip directed-broadcastno ip mroute-cache!interface Ethernet1/4bandwidth 100no ip addressno ip directed-broadcastno ip mroute-cacheno fair-queue!interface Switch1no ip addressno ip directed-broadcastno atm ilmi-keepalive!interface Switch1.1 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 50 50 0 aal5snaptag-switching atm vp-tunnel 50tag-switching ip!interface Switch1.2 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 40 40 0 aal5snaptag-switching atm vp-tunnel 40tag-switching ip!interface Switch1.3 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 20 20 0 aal5snaptag-switching atm vp-tunnel 20tag-switching ip!router ospf 100passive-interface Ethernet1/2network 10.0.0.0 0.255.255.255 area 100network 53.0.0.0 0.255.255.255 area 100!router ripversion 2!address-family ipv4 vrf vpn1version 2redistribute bgp 100 metric 2network 53.0.0.0no auto-summaryexit-address-family!router bgp 100no synchronizationno bgp default ipv4-unicastneighbor 11.11.11.11 remote-as 100neighbor 11.11.11.11 update-source Loopback0!address-family ipv4 vrf vpn1redistribute ripno auto-summaryno synchronizationexit-address-family!address-family vpnv4neighbor 11.11.11.11 activateneighbor 11.11.11.11 send-community extendedexit-address-family!ip default-gateway 3.3.0.1no ip classlessno ip http server!dialer-list 1 protocol ip permitdialer-list 1 protocol ipx permit!!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4password lablogin!exception core-file mpls/mgx/dumps/rpm-18-114.corerpmrscprtn PAR 100 100 0 255 0 3840 4047addcon vpc switch 1.3 20 rslot 0 2 20 master localaddcon vpc switch 1.2 40 rslot 0 1 40addcon vpc switch 1.1 50 rslot 10 1 50 master localendrpm-18-114#rpm-18-114#rpm-18-114#One PE - Two CE Configuration - OSPF & IBPG Between PEs & STATIC ROUTES between PE-CE
CE1 Configuration
sys-2-1#sho runBuilding configuration...Current configuration:!version 12.0service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname sys-2-1!boot system tftp mpls/12.0/c3620-js-mz.120-5.0.2.T2 3.3.0.1logging buffered 4096 debuggingno logging console!!!!!ip subnet-zerono ip domain-lookupip host ios-lab-fw 3.3.0.1!ip cefcns event-service server!!!process-max-time 200!interface Loopback0ip address 12.12.12.12 255.255.255.255no ip directed-broadcast!interface Ethernet0/0ip address 3.3.30.1 255.255.0.0no ip directed-broadcastshutdown!interface Ethernet0/1ip address 50.0.0.1 255.0.0.0no ip directed-broadcast!interface Ethernet0/2no ip addressno ip directed-broadcastshutdown!interface Ethernet0/3ip address 52.0.0.1 255.0.0.0no ip directed-broadcast!interface Serial1/0no ip addressno ip directed-broadcastshutdownno fair-queue!interface Serial1/1no ip addressno ip directed-broadcastshutdown!interface Serial1/2no ip addressno ip directed-broadcastshutdown!interface Serial1/3no ip addressno ip directed-broadcastshutdown!router ospf 100passive-interface Ethernet0/1network 12.0.0.0 0.255.255.255 area 100network 50.0.0.0 0.255.255.255 area 100network 52.0.0.0 0.255.255.255 area 100!ip default-gateway 3.3.0.1no ip classlessip route 0.0.0.0 0.0.0.0 Ethernet0/1 50.0.0.2no ip http server!!!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4password lablogin!!endsys-2-1#sys-2-1#CE2 Configuration
sys-2-4#sho runBuilding configuration...Current configuration:!version 12.0service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname sys-2-4!boot system tftp mpls/12.0/c3640-js-mz.120-5.0.2.T2 3.3.0.1logging buffered 4096 debuggingno logging console!!!!!ip subnet-zerono ip domain-lookupip host ios-lab-fw 3.3.0.1!ip cefcns event-service server!!!process-max-time 200!interface Loopback0ip address 14.14.14.14 255.255.255.255no ip directed-broadcast!interface Ethernet0/0ip address 3.3.30.4 255.255.0.0no ip directed-broadcastshutdown!interface Ethernet0/1ip address 53.0.0.2 255.0.0.0no ip directed-broadcast!interface Ethernet0/2no ip addressno ip directed-broadcastshutdown!interface Ethernet0/3no ip addressno ip directed-broadcastshutdown!router ospf 100passive-interface Ethernet0/1network 14.0.0.0 0.255.255.255 area 100network 53.0.0.0 0.255.255.255 area 100!ip default-gateway 3.3.0.1no ip classlessip route 0.0.0.0 0.0.0.0 Ethernet0/1 53.0.0.1no ip http server!!!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4password lablogin!!endsys-2-4#CE3 Configuration
sys-2-2#sho runBuilding configuration...Current configuration:!version 12.0service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname sys-2-2!boot system tftp mpls/12.0/c3640-js-mz.120-5.0.2.T2 3.3.0.1logging buffered 4096 debuggingno logging console!!!!!ip subnet-zerono ip domain-lookupip host ios-lab-fw 3.3.0.1!ip cefcns event-service server!!!process-max-time 200!interface Loopback0ip address 13.13.13.13 255.255.255.255no ip directed-broadcast!interface Ethernet0/0ip address 3.3.30.2 255.255.0.0no ip directed-broadcastshutdown!interface Ethernet0/1ip address 51.0.0.2 255.0.0.0no ip directed-broadcast!interface Ethernet0/2ip address 52.0.0.2 255.0.0.0no ip directed-broadcast!interface Ethernet0/3no ip addressno ip directed-broadcastshutdown!interface Serial1/0no ip addressno ip directed-broadcastshutdownno fair-queue!interface Serial1/1no ip addressno ip directed-broadcastshutdown!interface Serial1/2no ip addressno ip directed-broadcastshutdown!interface Serial1/3no ip addressno ip directed-broadcastshutdown!router ospf 100passive-interface Ethernet0/1network 13.0.0.0 0.255.255.255 area 100network 51.0.0.0 0.255.255.255 area 100network 52.0.0.0 0.255.255.255 area 100!ip default-gateway 3.3.0.1no ip classlessip route 0.0.0.0 0.0.0.0 Ethernet0/1 51.0.0.1no ip http server!!!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4password lablogin!!endsys-2-2#sys-2-2#sys-2-2#PE1 Configuration
rpm-18-110#sho runBuilding configuration...Current configuration:!version 12.0no service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname rpm-18-110!boot system tftp mpls/12.0/rpm-js-mz.120-5.T.bin 3.3.0.1no logging console!!!!!clock timezone EST -5clock summer-time EDT recurringip subnet-zerono ip domain-lookupip host ios-lab-fw 3.3.0.1!!ip vrf vpn1rd 100:1route-target export 100:1route-target import 100:1ip cefcns event-service server!!process-max-time 200!interface Loopback0ip address 11.11.11.11 255.255.255.255no ip directed-broadcast!interface Loopback1no ip addressno ip directed-broadcast!interface Ethernet1/1ip address 3.3.18.110 255.255.0.0no ip directed-broadcastno ip mroute-cacheno keepalive!interface Ethernet1/2ip vrf forwarding vpn1ip address 50.0.0.2 255.0.0.0no ip directed-broadcastno ip mroute-cacheno keepalivetag-switching ip!interface Ethernet1/3bandwidth 100ip vrf forwarding vpn1ip address 51.0.0.1 255.0.0.0no ip directed-broadcastno ip mroute-cacheshutdowntag-switching ipno fair-queue!interface Ethernet1/4no ip addressno ip directed-broadcastno ip mroute-cacheno keepalive!interface FastEthernet2/1no ip addressno ip directed-broadcastno ip mroute-cache!interface Switch1no ip addressno ip directed-broadcastno atm ilmi-keepalive!interface Switch1.1 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 50 50 0 aal5snaptag-switching atm vp-tunnel 50tag-switching ip!interface Switch1.2 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 30 30 0 aal5snaptag-switching atm vp-tunnel 30tag-switching ip!interface Switch1.3 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 60 60 0 aal5snaptag-switching atm vp-tunnel 60tag-switching ip!router ospf 100passive-interface Ethernet1/2passive-interface Ethernet1/3network 11.0.0.0 0.255.255.255 area 100network 50.0.0.0 0.255.255.255 area 100network 51.0.0.0 0.255.255.255 area 100!router bgp 100no synchronizationno bgp default ipv4-unicastneighbor 10.10.10.10 remote-as 100neighbor 10.10.10.10 update-source Loopback0!address-family ipv4 vrf vpn1redistribute connectedredistribute staticno auto-summaryno synchronizationexit-address-family!address-family vpnv4neighbor 10.10.10.10 activateneighbor 10.10.10.10 send-community extendedexit-address-family!ip default-gateway 3.3.0.1no ip classlessip route vrf vpn1 12.0.0.0 255.0.0.0 Ethernet1/2 50.0.0.1ip route vrf vpn1 13.0.0.0 255.0.0.0 Ethernet1/3 51.0.0.2ip route vrf vpn1 50.0.0.0 255.0.0.0 Ethernet1/2 50.0.0.1ip route vrf vpn1 51.0.0.0 255.0.0.0 Ethernet1/3 51.0.0.2ip route vrf vpn1 52.0.0.0 255.0.0.0 Ethernet1/2 50.0.0.1ip route vrf vpn1 52.0.0.0 255.0.0.0 Ethernet1/3 51.0.0.2no ip http server!dialer-list 1 protocol ip permitdialer-list 1 protocol ipx permit!!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4password lablogin!exception core-file mpls/mgx/dumps/rpm-18-110.corerpmrscprtn PAR 100 100 0 255 0 3840 4047addcon vpc switch 1.2 30 rslot 0 3 30 master localaddcon vpc switch 1.1 50 rslot 14 1 50addcon vpc switch 1.3 60 rslot 0 4 60 master localendrpm-18-110#rpm-18-110#rpm-18-110#PE2 Configuration
rpm-18-114#sho runBuilding configuration...Current configuration:!version 12.0no service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname rpm-18-114!boot system tftp mpls/12.0/rpm-js-mz.120-5.T.bin 3.3.0.1no logging console!!!!!clock timezone EST -5clock summer-time EDT recurringip subnet-zerono ip domain-lookupip host ios-lab-fw 3.3.0.1!!ip vrf vpn1rd 100:1route-target export 100:1route-target import 100:1ip cefcns event-service server!!process-max-time 200!interface Loopback0ip address 10.10.10.10 255.255.255.255no ip directed-broadcast!interface Loopback1no ip addressno ip directed-broadcast!interface Ethernet1/1ip address 3.3.18.114 255.255.0.0no ip directed-broadcastno ip mroute-cacheno keepalive!interface Ethernet1/2bandwidth 100ip vrf forwarding vpn1ip address 53.0.0.1 255.0.0.0no ip directed-broadcastno ip mroute-cachetag-switching ipno fair-queue!interface Ethernet1/3no ip addressno ip directed-broadcastno ip mroute-cache!interface Ethernet1/4bandwidth 100no ip addressno ip directed-broadcastno ip mroute-cacheno fair-queue!interface Switch1no ip addressno ip directed-broadcastno atm ilmi-keepalive!interface Switch1.1 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 50 50 0 aal5snaptag-switching atm vp-tunnel 50tag-switching ip!interface Switch1.2 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 40 40 0 aal5snaptag-switching atm vp-tunnel 40tag-switching ip!interface Switch1.3 tag-switchingip unnumbered Loopback0no ip directed-broadcastatm pvc 20 20 0 aal5snaptag-switching atm vp-tunnel 20tag-switching ip!router ospf 100passive-interface Ethernet1/2network 10.0.0.0 0.255.255.255 area 100network 53.0.0.0 0.255.255.255 area 100!router bgp 100no synchronizationno bgp default ipv4-unicastneighbor 11.11.11.11 remote-as 100neighbor 11.11.11.11 update-source Loopback0!address-family ipv4 vrf vpn1redistribute connectedredistribute staticno auto-summaryno synchronizationexit-address-family!address-family vpnv4neighbor 11.11.11.11 activateneighbor 11.11.11.11 send-community extendedexit-address-family!ip default-gateway 3.3.0.1no ip classlessip route vrf vpn1 14.0.0.0 255.0.0.0 Ethernet1/2 53.0.0.2ip route vrf vpn1 53.0.0.0 255.0.0.0 Ethernet1/2 53.0.0.2no ip http server!dialer-list 1 protocol ip permitdialer-list 1 protocol ipx permit!!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4password lablogin!exception core-file mpls/mgx/dumps/rpm-18-114.corerpmrscprtn PAR 100 100 0 255 0 3840 4047addcon vpc switch 1.3 20 rslot 0 2 20 master localaddcon vpc switch 1.2 40 rslot 0 1 40addcon vpc switch 1.1 50 rslot 10 1 50 master localendrpm-18-114#Route Processor Module (RPM) Addendum
This section describes the installation requirements and guidelines for RPM modules installed with Release 1.1.34.
About the Cisco IOS 12.1(5.3)T_XT Release
The Cisco IOS 12.1(5.3)T_XT or higher is used with MGX Release 1.1.32 and provides support for:
•
(Note: RPM-PR is FCS with Release 1.1.32; and General Availability with Release 1.1.34.)•
•
•
Note
About the Cisco IOS 12.2(2)T2 Release
The Cisco IOS 12.2(2)T2 or higher is used with MGX Release 1.1.34. This IOS release does not support new RPM features, but has been tested with 1.1.34 and continues to support existing features on the RPM/PR and RPM/B cards.
RPM Compatibility Matrix
Special Upgrade Requirements for RPM
This section describes procedures for graceful firmware/hardware upgrades and downgrades in nodes.
Recommendations for Booting
You can boot the RPM/B or RPM/PR from any of the following sources:
•
•
•
Recommendations for saving RPM configuration
The current implementation provides the following options:
•
•
•
•
It is recommended to save the configuration on flash and on the PXM Disk, as well as on the network server. This ensures that the configuration can be restored, even in the case of multiple failures.
For example, if an RPM card has problems, you can copy the configuration from either the PXM disk or from the network to new RPM card. In case of multiple hardware failures (both RPM and PXM cards have problems) you can copy the configuration from the network server.
Replacing the existing RPM with a new card or a card with old configuration in flash
The existing configuration (of the old card) can be restored on the newly inserted card by following the instructions given below:
Step 1
Step 2
Step 3
Step 4
Step 5
Please note that in RPM context the "config save/restore" feature of the PXM restores only the PXM part of the RPM configuration/connections. The RPM part of the configuration should also be saved from RPM CLI through copy command. For example, copy run c: <config-filename> for saving to PXM Disk for future restoration.
RPM Connection Resynchronization
The RPM Connection Resync process is supported in the 12.04T and higher releases. This feature checks for consistency between the RPM and PXM connection databases.
General Upgrade/Downgrade Guidelines
•
•
•
The following upgrade instructions are included in this section:
•
•
•
Upgrade the RPM Firmware
Step 1
•
Step 2
Step 3
Step 4
a.
b.
c.
d.
Note
Step 5
Step 6
Step 7
Upgrade a RPM/B Module to RPM-PR
RPM-PR requires IOS Release 12.2(2)T2 or higher.
Caution
Step 1
Step 2
Step 3
a.
b.
c.
Step 4
•
•
Install an RPM-PR Module in a Fresh Slot
This section contains instructions to insert an RPM-PR card in a fresh slot. RPM-PR requires IOS Release 12.2(2)T2 or higher.
Step 1
Step 2
Step 3
Step 4
Operate an RPM/B or RPM-PR in an MGX 8230 Chassis
Step 1
Step 2
Note
http://www.cisco.com/public/sw-center/
The filename is: rpm-js-mz.122-2.T2
A laptop or workstation with an IP stack will be required to access this FTP location.Step 3
Step 4
New CLI Commands for RPM
The new CLI commands for the Route Processor Module are:
•
•
•
•
•
Note
ATM ping command for the RPM
This command provides a single point of reference from which troubleshooting can be performed along with the round-trip transit time information. The command syntax is:
atm <switch interface> <vpi> <vci> {seg-loopback | end-loopback} [<repeat>] [<timeout>]
For example, issuing the command "atm sw1.200 0 300 end-loopback" would give 53 byte OAM echoes to the connection end-point over VPI 0, VCI 300 and provide a reliability and round-trip time measurement. The command can be extended so that the default repeat and timeout values can be modified. The command can be issued even when the OAM management is configured to run periodic background test on the same VC. The user can abort the command by the escape sequence before the command finishes.
Due to the inclusion of the new ATM ping command, the command privilege exec level 0 ping provides only standard pings. To have extended ping capability, the following, use the command privilege exec level 0 ping ip.
ATM pvp <vpi> command for configuring a VPC connection on RPM
This command is not new, but is necessary in order to configure an OAM-managed PVC for a VPC connection. When configuring a VPC connection on RPM, you must configure PVP parameters under the main interface, SW1. If these configurations are not performed first, the OAM-managed PVCs, which are part of this VPI will not function.
Before configuring the PVC, configure the PVP under the SW1 interface by entering the following interface configuration command:
atm pvp <vpi> <pcr>
or
pvp <vpi> <pcr>
<vpi>
The VPI number to be used.
<pcr>
The bandwidth to be allocated (default OC3).
debug rpm ecc
This new CLI command displays the number of ECC errors since the system was booted.
debug rpm ecc [number]
This new CLI command allows an administrator to determine the number of ECC errors (since the system was booted) that will result in a switch over.
Problems Fixed with IOS 12.1(5.3)T_XT
Please refer to the IOS 12.1 Release Notes at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt/index.htm
Obtaining Documentation
The following sections provide sources for obtaining documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following sites:
•
•
•
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
•
http://www.cisco.com/cgi-bin/order/order_root.pl
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
http://www.cisco.com
Technical Assistance Center
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
Contacting TAC by Using the Cisco TAC Website
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
http://www.cisco.com/tac
P3 and P4 level problems are defined as follows:
•
•
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
Contacting TAC by Telephone
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
•
•
