|
Table Of Contents
1.1.22 Version Software Release Notes
Cisco WAN MGX 8850 SoftwareFeatures Introduced in Release 1.1.22
Features Introduced in Release 1.1.21
Features Introduced in Release 1.1.12
Features Introduced in Release 1.1.11
Features Introduced in Release 1.1.10
Release 1.1.22 MGX 8850 Hardware
MGX 8220 Hardware not supported on Release 1.1.22 of the MGX 8850
MGX 8220 Hardware that has been superseded on the MGX 8850 by MGX 8850-specific Hardware
MGX 8220 Hardware that will not be supported on the MGX 8850
Features not Supported in this Release:
Major Network Management Features
Problems Fixed in Release 1.1.22
Problems Fixed in Release 1.1.21
Problems Fixed in Release 1.1.20
Problems Fixed in Release 1.1.12
Problems Fixed in Release 1.1.11
Problems Fixed in Release 1.1.10
Problems Fixed in Release 1.1.01
Problems Fixed in Release 1.1.00
Problems Fixed for RPM in 12.0.5T1
Problems Fixed for RPM in 12.0.4T
Problems Fixed for VISM in 1.1.20 release of PXM
Special Installation and Upgrade Requirements
Single PXM Installation Procedure
Installation Procedure For Redundant PXMs:
Service Module Firmware Download Procedure
Service Module Installation/Upgrade and Flashdownload Requirements.
Known Anomalies for Platform Software and Service Module Firmware
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
1.1.22 Version Software Release Notes
Cisco WAN MGX 8850 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.
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.
About the 1.1.22 Release
Release 1.1.22 of the MGX 8850 supports the same network scenarios as Release 1.1.12 and 1.1.21.
1. Feeder concentration to the BPX 8600 and all other endpoints (no BPX 8600 BNI trunk connections). IGX endpoints are supported in this release using Switch Software 9.2.
The MGX 8850 provides multiservice, high density ATM, Circuit Emulation and Frame Relay feeder concentration to the BPX 8600. The MGX 8850 connects to the BPX 8600 using the feeder trunk protocol over a PXM port. On the BPX 8600 side the feeder connection trunk to the MGX 8850 is supported on the BXM card only. Interoperability support is limited to (a) MGX 8850 to MGX 8850, (b) MGX 8850 to MGX 8220, c) MGX 8850 to BPX 8600 (FR to ATM service interworking) and (d) MGX 8850 to IGX.
2. MGX 8850 in a Stand-alone Concentrator configuration and full PXM UNI support on all ports.
Stand-alone capability allows the MGX 8850 to act as an edge concentrator to any vendor ATM network which implies service interoperability with other vendor's equipment. All connections for stand-alone are local switching connections.
Features
This section lists the features supported in each of the maintenance releases that comprise MGX 8850 Release 1.1.22. Except where noted, all features are generally available.
Features Introduced in Release 1.1.22
MGX 8850 Release 1.1.22 is a maintenance release of Release 1.1.21. In addition, it introduces the following new features:
•core dump facility.
•FRSM2T3 subrate to Kentrox box is now supported. Previously we only supported Digital Link.
•Clrsmcnf/savesmcnf/restoresmcnf feature support.
Features Introduced in Release 1.1.21
MGX 8850 Release 1.1.21 includes all the features in Release 1.1.12 and earlier. In addition, it introduces the following new features:
•Support for the IGX-SES.
•FRSM-HS1B 12inOne (X.21/V.35 programmable feature)
Support for the FRSM-HS1B dual-personality back-card that can be configured for either V.35 interfaces or X.21 interfaces.
•Support of (real time) rt-VBR as a new class of ATM connection service type for the following service modules:
–FRSM-2CT3
–FRSM-2T3/E3
–FRSM-HS2
•Support for the "fixed ratio queuing" algorithm for egress queue management on the following service modules:
–FRSM-2CT3
–FRSM-2T3/E3
–FRSM-HS2
•Support for hot-standby on the following service modules:
–FRSM-2CT3
–FRSM-2T3/E3
–FRSM-HS2
This feature reduces switchover time for the above service modules.
•Support for Zero CIR on the following service modules:
–FRSM-2CT3
–FRSM-2T3/E3
–FRSM-HS2
–FRSM-8T1/E1
•FRSM-2T3/E3 subrate support
This feature supports running the T3 or E3 lines on the FRSM at sub rates. The interfaced DSU/CSU supported are the Digital Link DL3100 for T3 and the Digital Link DL3100E for E3.
Features Introduced in Release 1.1.12
MGX 8850 Release 1.1.12 was a maintenance release of Release 1.1.11. In addition, it introduced the following new features:
•Introduction of MGX-CESM-T3E3 - Circuit Emulation Module Card, including the following features:
–Provides 1 standard T3 or E3 interfaces
–1:1 redundancy using Y-cable
Note The MGX-CESM-T3E3 is an FCS product.
•PLCP payload scrambling
•Support for IP Address discovery of the MC3810 using ILMI
Features Introduced in Release 1.1.11
MGX 8850 Release 1.1.11 was a maintenance release of Release 1.1.10. In addition, it introduced the following new features:
•Introduction of MGX-VISM-8T1E1 - Voice Service Module Card, including the following features:
–Provides 8 standard T1 or E1 interfaces with B8ZS, AMI & HDB3 line coding.
–Support for voice over IP (VoIP) to RFC 1889.
–Support for both PCM a-law and u-law.
–Programmable 16, 32,64,128 ms near end echo cancellation.
–Voice activity detection (VAD) and comfort noise generation using variable threshold energy (Cisco proprietary).
–Support for signalling using Simple Gateway Control Protocol (SGCP) version 1.0.
–ATM AAL5 connections for Management and voice IP packets.
–Support for loop timing, payload and line loopbacks.
–1:N redundancy using SRM-3T3 capabilities (bulk mode support for T1 lines only).
Note The MGX-VISM-8T1E1 is an FCS product.
•RPM/B card and double clock OC6 support with IOS 12.0.5T1.
The RPM has a custom ASIC on it called the ATMizer. This chip is being replaced by the ATMizer II+, AKA "G10" version of the chip. The RPM-B contains this new chip, along with a 16Mbyte Flash SIMM instead of 4Mbyte. The RPM-B can operate at 21Mhz and 42Mhz Cellbus clock rate with 1.1.11 and 12.0.5T1, while the RPM-A can only operate at 21 Mhz.
•Support for CellBus speed configuration. The CellBus can be configured for double clock speed for all VHS service modules.
•MPLS (tag edge router only) support for RPM.
Note MPLS support for RPM is currently an FCS feature.
•Support of MGX-FRSM-HS/1-B (V.35 support)
•Major Redundancy Enhancements (SRM failures cause switchover, removal of FRSM-2CT3 backcard causes switchover)
•APS fixes (removing back card from active PXM causes APS line to not fail, APS memory leak, APS switch on SDBER threshold exceed)
•Saveallcnf includes RPM configuration
•PXM core dump subsystem feature
•MGX 8220 Release 4.1.00 circuit emulation endpoints
Features Introduced in Release 1.1.10
MGX 8850 Release 1.1.10 provided the following features in addition to the ones provided in Release 1.1.01 and earlier:
•APS redundancy on PXM-OC3 and OC12 interfaces. Only 1+1 redundancy configuration is supported. No 1:1 APS redundancy.
•Full PXM UNI support in Stand-alone configuration using all ports with policing. The UNI channels on PXM will support CBR, rt-VBR, nrt-VBR, UBR and ABR classes of service.
•BERT support on FRSM-8T1/E1, CESM-8T1/E1 and AUSM-8T1/E1 and FRSM-2CT3 cards. The BERT support is at whole T1/E1 or port level (n*DS0).
Release 1.1.22 MGX 8850 Hardware
MGX 8850 is a 45 Gbps backplane with 1.2 Gbps switching fabric for Release 1.1.22. The same backplane is used with different switching fabric cards (1.2, 45 Gbps) to achieve scalability. MGX 8850 Release 1.1.22 hardware components and their revisions that are supported are as follows:
Support for embedded Cisco IOS router (Router Processor Module - RPM)
•The RPM is an embedded Cisco IOS router with integrated ATM Deluxe Port Adapter and Cellbus Controller ASIC for internal connections to the backplane Cellbus. A number of port adaptors (back cards) can be configured with the RPM front card (FDDI, Ethernet, Fast Ethernet).
–4E Adapter
–FE Adapter (UTP, MMF)
–FDDI Adapter (full duplex, half duplex, SMF, MMF)
MGX 8220 Hardware not supported on Release 1.1.22 of the MGX 8850
The following cards are not supported in Release 1.1.22:
•AX-SRM-T1E1
•AX-VISM-8E1
•AX-SMB-8E1
•AX-R-SMD-8E1
•AX-RJ48-8E1
•AX-R-RJ48-8E1
MGX 8220 Hardware that has been superseded on the MGX 8850 by MGX 8850-specific Hardware
• AX-SRM-3T3-A and AX-BNC-3T3 card set
The MGX-SRM-3T3-B 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-B/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 redunancy should have been supported in those slots with the model A card.
•AX-SCSI2-2HSSI
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.
•AX-IMATM
Superseded by MGX-AUSM-8T1/B and MGX-AUSM-8E1/B
•AX-IMATM-B
Superseded by MGX-AUSM-8T1/B and MGX-AUSM-8E1/B
MGX 8220 Hardware that will not be supported on the MGX 8850
•AX-FRASM-8T1
•All four port MGX 8820 cards
•AX-AUSM-8T1
•AX-AUSM-8E1
Software Platform Features
MGX 8850 provides high speed native ATM interfaces which can be configured as ATM UNI ports or trunks
Support for 1:N and 1:1 Service Module Redundancy, as indicated in the table below:
Support for Bulk Distribution using SRM-3T3B card.
Service module and PXM upgrades
Features not Supported in this Release:
•RPM 1:1 redundancy
•RPM statistics
•Layer 2 support as an autoroute routing node
•SRM T1E1
•IPX endpoints with the MGX 8850
•E1 users circuits
•T1/CAS Backhaul
•Interworking with SGCP 1.1+ compliant call agent (Bellcore CA SM1.5)
•Interworking with Cisco 3810
•G.726 and G.729 voice compression
•G729b voice activity detection
•Voice Circuit Admission Control (CAC)
•Bearer continuity testing
•Ring back tone on Ground Start
•Separate PVCs for signaling and bearer channels
Note Code for the above features may be included in the VISM code image. However, no specific mechanism has been included to prevent the use of these unsupported features. If the user attempts to use these unsupported features, there is no guarantee that the features will operate correctly.
Major Network Management Features
•CWM Connection Management
•CiscoView support for equipment management
•CLI support
•Service MIB support
•Connection Management for connections to RPM with associated CM GUI support.
•Topology subsystem enhancements to support the MGX 8850 as a stand-alone switch.
•Statistics
For more details refer to the CWM Release 9.2.07 release notes part number 78-6659-07.
Connection Limits
•Up to 4000 connections per VHS card.
•Up to 1000 connections per 8 port card (up to 898 per port with LMI enabled)
•Up to 200 connections per HS1 card
•Up to 12000 connections per shelf
SNMP MIB:
The SNMP MGX 8850 MIB is being provided with the delivery of Release 1.1.22 of the MGX 8850 software on CCO. The MIB is in standard ASN.1 format and is located in the ASCII text files MGX8800Mib.my file which is included in the same directory within CCO. These files may be compiled with most standards-based MIB compilers. For changes in this MIB from release 1.1.21 please refer to the MIB release notes on CCO.
Notes & Cautions
CLI modification and changes:
•A few modifications have been made to the IP configuration commands. (cnfifip and bootChange) See CLI Change section:
–the cnfifip command has an additional option to up/down one of the ip interfaces (ethernet, slip, atm) dynamically. No reboot is required to up/down interface. Turned down interfaces are persistent across resets.
– the cnfifip command is now an active only command
– dspifip will now display the state of each interface and indicate if it is up or down.
–bootChange now checks the ip values set and will complain if it detects incorrect values.
–bootChange values are sent and updated on standby card automatically. Both bootlines are kept in sync.
–bootChange command is now an active only command from CLI.
– cnfenetgw command has been added to establish the ethernet gateway route permanently. (command is active only)
–dspenetgw command will display ethernet gateway address set.
–A shelf can now either have one or two ip addresses for ethernet. The shelf ip address set using cnfifip will always be the active card ip address. The bootChange ip address will be used for the standby card and backup boot if it is different than the shelf ip address. If the bootChange ip address is same as the shelf ip address then the ethernet interface on the standby card or in backup boot will be left in the down state.
–If the "255.255.255.252" netmask is used for the SLIP interface, the PXM will automatically add host route for its peer whenever the interface is turned ON
–If the FW fails to reach the CLI prompt or comes up in backup boot, the ethernet interface could be down if the shelf ip address and boot change address are the same. In this case the bootChange command could be used from the shell to set another ip address and then usrEnetEnable should be called to activate that address. (see example)
–Commands and Examples
– cnfifip:
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 database.
> cnfifip atm down
This will bring down the ATM interface and preserve the information in the database.
–delifip
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
–dspifip:
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 3 interfaces. The data shown for the SLIP interface will apply when it is turned UP with, say, "cnfifip slip on".
–cnfenetgw
Syntax:
cnfenetgw IPAddr
Example:
> cnfenetgw 172.29.37.1This command will set the default gateway and add the appropriate routes necessary to it.
– dspenetgw
Example:
> dspenetgwEnet Gateway: 172.29.37.1– bootChange:
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.
–usrEnetEnable:
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 which are related to FRSM-2CT3 line level loopbacks.
•Remote Loopback at DS3:-
This loopback can be configured in FRSM-2CT3 using the following commands.
addds3rmtloop <lineno>
xcnfln -ds3 <lineno> -e 3 -lpb 2
•Local Loopback at DS3:-
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
•Remote Loopback at DS1:-
This loopback can be configured in FRSM-2CT3 using the following commands:
cnfbert (from PXM)
addrmtloop <lineno>
xcnfln -ds1 <lineno> -e 3 -lpb 2
•Local Loopback at DS1:-
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
•Inband loopback for DS1 are supported only using bert diagnostics. The status of inband loopbacks are displayed with <dspalm> and <dspalms> commands. It is not displayed with <dspln> command. Before configuring the DS1 line in Inband loopback from bert diagnostics, user should use following command to enable code detection on FRSM-2CT3:
xcnfln -ds1 <lineno> -e 3 -detect 2
•Ctrl-X has been disabled from resetting PXM on the firmware.
•This release has the fix to meet the Bellcore jitter specs. The way to fix the jitter problem is having FW to disable the force_signal_detect_enable register and let the optical receiver to control the signal-detect input. The OC3 transmit data jitter now measured is below 0.10UI.
•Due to the concerns about the too frequent message exchanging between the two PXM cards, the current command "dspbecnt" is limited by following:
–"dspbecnt" only displays the bit error counts after the last APS switch, i.e. every APS switch will clear the counts for both working and protection line.
–"dspbecnt" displays the active line bit error counts correctly. The bit error counts for non-active line is inaccurate and requires a state change(since the last state) in the protection line for display of any bit error counts.
–A state change indicates a change of line status, such as from SD to SF.
Node Related
At most one BERT test can be performed per shelf at any point in time. BERT can only be activated through the CLI.
Do not execute the restoreallcnf command in the middle of the installation process. If you follow the following steps:
Step 1 saveallcnf
Step 2 restoreallcnf
Step 3 install
Step 4 newrev
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 saveallcnf
Step 2 install
Step 3 newrev
Step 4 restoreallcnf
(for more information, refer to CSCdm57683)
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:
•addln
•delln
•cnfln
•dspln
•dsplns
•addlnloop
•dellnloop
•cnfsrmclksrc
•dspsrmclksrc
•dspalm
•dspalms
•dspalmcnt
•clralmcnt
•clralm
•dspalmcnf
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 indeed needs 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 Use ftp to port the Axis 5 common boot image for the service module to a workstation
Step 2 Plug in the card into the MGX 8220 shelf
Step 3 Download the proper MGX 8220 shelf release 5.0 boot image using the following commands from the workstation:
tftp <ip address of the MGX 8220 shelf >binput <boot filename> AXIS_SM_1_<slot#>.BOOTInsure that tftp downloaded the appropriate boot code by verifying the flash checksums.
Step 1 Log into the shelf.
cc <slot #>'Step 2 Verify that the two checksums are the same.
chkflash'If NOT, repeat the process until they are the same. If they are the same, then you can safely remove the card. At this point the service module can be used in the MGX 8850 shelf.
Caution If the checksums are not the same when you remove the service module then the service module will not boot when it is plugged in and the service module will have to be returned using the Cisco Returned Material Authorization process.
Whenever an MGX 8850 is added as a feeder to a BPX 8600, SWSW automatically programs a channel with a VPI.VCI of 3.8 for use as the IP Relay channel. IP Relay is used to send IP data between nodes via the network handler; allowing every node in the domain to be directly addressable via IP addressing and CWM workstations to communicate with every node (especially feeders) using TELNET, SNMP and CWM protocols. If the user tries to add a channel with a VPI.VCI of 3.8, the BPX 8600 does not prevent the user channel from being added, but the MGX 8850 rejects it. To delete the added channel on the BPX 8600, and to get IP relay working you need to reset the BXM card.
In addition to clearing all the 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.
–The copychan command does not work on the MGX 8850
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 at all with the shelf through the console ports. If after switchcc standby PXM loses the downlevel port then it is due to a downlevel Beta version of UIA backcard that were 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 "ping" will work:tigers.1.7.PXM.a > ping 171.71.54.53 1171.71.54.53 is aliveConfiguration save and restore is only supported 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 only supported 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 acctuator. 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 on-line PXM you lose the broadcast address. Use the "cnfifip" command to configure the broadcast address. To re-define 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 5 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.
lines 1 to 14 -- 128 ports (A)
lines 15 to 28 -- 128 ports (B)
lines 29 to 42 -- 128 ports (C)
lines 43 to 56 -- 128 ports (D)
So, to add 256 ports on one T3 one should 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 1st FREEDM and (B) and (C) are connected to the 2nd FREEDM. Each FREEDM supports only 128 ports. If 128 ports are added on one T3 as in (A), then there cannot be any more ports as in (D). The 129th port should be on lines 15 to 42 (as in B or C).
If the user adds a connection between an RPM and a PXM and then deletes the connection the RPM shows no connection but the PXM still has the connection. The MGX was designed and implemented in such a way that only the connections that have the master end show up on PXM (by dspcons command). Consider these three connections:
c1 - has only slave end,
c2 - has only master end,
c3 - has both master and slave end.
When using the dspcons command, c2 & 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 4 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 backcard on that line. This is a hardware limitation on the backcard and has been mentioned in the Release-notes in bug# CSCdm44993
RPM Related
The RPM is a NPE-150 based router card capable of sustaining 150,000 pps. With RPM versions earlier than 12.O.7T1, some limitations in Inter-Process Communication between the can cause the PXM to declare that the RPM has Failed, when the RPM is at high loads. To avoid this, with RPM 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 700 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. Currently, the RPM supports 700 subinterfaces, and hence 700 networks with BGP, RIP or static routing.
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. Using such configurations, the RPM with IOS software release 12.0.7T1 supports 700 customer networks which use OSPF internally. (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.
Recommendations for Booting:
The current implementation provides the following options:
From PXM Disk
NetBoot (TFTP server)
Booting from PXM Disk is faster than NetBoot.
----------------------------------------------------------------------------------------------------------------------
Recommendations for saving RPM configuration
The current implementation provides the following options:
a. Save on flash / boot-flash.
b. Save on PXM Disk.
c. Save on network (TFTP server)
d. Save on RPM NVRAM (comes up faster; only for limited configuration size)
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, one 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) one 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 Insert the new card into an unreserved empty slot. A previously used slot can be unreserved by giving the "clrsmcnf" command.
Step 2 Copy the old RPM's configuration (from the PXM disk or the network server) to the new card's bootflash (For example copying from PXM disk: "copy c: <image name> bootflash:").
Step 3 Configure the new card to use the configuration in its bootflash using the "boot config bootflash: <config-file-name>" command.
Step 4 Save the changes using "write mem" command.
Step 5 Insert the new card into the old slot.
Please note that in RPM context the "config save/restore" feature of the PXM only restores 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 Re-sync process is supported in the 12.04T and higher releases. This feature checks for consistency between the RPM and PXM connection databases. ----------------------------------------------------------------------------------------------------------------------
Limitations
restoreallcnf
The MGX 8850 does not support CESM endpoints with MGX 8220 Release 4.1 through CWM, but is supported through the CLI (CSCdm11835).
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 Execute the saveallcnf command.
Step 2 Execute the install command.
Step 3 Execute the newrev command.
Step 4 Execute the restoreallcnf command
.(for more information, refer to CSCdm57683)
The Service MIB does not support resource partitions.
LIP is supported on the maintenance port, but there is no PPP support on the maintenance port.
BIS messages are constantly being sent from BPX to various nodes. This affects the frequency of TFTP updates, which may affect CWM performance and/or CWM database consistency.
Unable to provision virtual trunks in SWSW 9.1.10.
clrsmcnf
As a speedy way to wipe out all configuration on an SM, you can use clrsmcnf. This command works in the following scenarios:
•1.1 SM not in slot
•1.2 SM in slot and in active (good) state
•1.3 SM in slot but in failed state or boot state or whatever state.
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 FRSM8t1e1 in the slot with some configuration and the customer wants to use this slot for an AUSM8t1e1 card.
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:
•Saving a configuration of an SM from one shelf and restoring it to the same slot on another shelf.
•Saving a configuration of an SM in a slot and restoring it to another slot of the same card type.
•If the SM configuration is corrupted on disk, but the run-time image is okay and the FAT is corrupted.
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 CLI command timeout 600 (to set the timeout value back to the default)
Note clrsmcnf does not work with the VISM card.
Core Dump Mask
There are no system performance implication unless you take a core dump, currently the default error mask to take coredump is attached, you can change the mask or take it manually.
Set the core dump mask to its default value. If you enable core dumps with power on reset and shell reset core dumps enabled you will end up with a PXM that continuously dumps the core and resets. The only way out is to use a download boot that does not have the core dump feature.
Default setting 0x262eeOFF 0001 Power ON ResetON 0002 DRAM Parity ErrorON 0004 WatchDog Timeout ResetON 0008 Resource OverflowOFF 0010 Clear All ConfigurationON 0020 Missing TaskON 0040 Reset because of PXM Low VoltageON 0080 Reset By Event Log TaskOFF 0100 Reset from ShellON 0200 UnknownOFF 0400 Reset from PXMOFF 0800 Reset SystemOFF 1000 Switch Core CardON 2000 Secondary Cache ErrorON 4000 Software Error ResetOFF 8000 S/W reset due to upgradeOFF 10000 Restore All ConfigurationON 20000 Device Driver ErrorNODENAME.1.8.PXM.a > core hot-dumpDo you want to proceed (Yes/No)? yDumping PXM Core Image[0]:......................................................................................... .......................................Done.NODENAME.1.7.PXM.s > core save 2 core.zipCreating core.zip.................................Core dump basics.There are two steps to save a core dump.1. The system will store a raw core dump image on the disk (this image ison a portion of the disk that is not used for the filesystem).2. After the raw core dump image is saved on the disk, use the cli command"core" to zip the image and save it in a file on the disk.Use the "core mask" command to display and to set the mask which determineswhich conditions will cause an autmatic core dump.NODENAME.1.7.PXM.s > core maskAutomatic Core Dumping is enabled..The Current Core slot is 0The Current Core mask is 0x4004OFF 0001 Power ON ResetOFF 0002 DRAM Parity ErrorON 0004 WatchDog Timeout ResetOFF 0008 Resource OverflowOFF 0010 Clear All ConfigurationOFF 0020 Missing TaskOFF 0040 Reset because of PXM Low VoltageOFF 0080 Reset By Event Log TaskOFF 0100 Reset from ShellOFF 0200 UnknownOFF 0400 Reset from PXMOFF 0800 Reset SystemOFF 1000 Switch Core CardOFF 2000 Secondary Cache ErrorON 4000 Software Error ResetOFF 8000 S/W reset due to upgradeOFF 10000 Restore All ConfigurationOFF 20000 Device Driver ErrorNODENAME.1.7.PXM.s > core mask 0x2e2eeAutomatic Core Dumping is enabled..The Current Core slot is 0The Current Core mask is 0x2e2eeOFF 0001 Power ON ResetON 0002 DRAM Parity ErrorON 0004 WatchDog Timeout ResetON 0008 Resource OverflowOFF 0010 Clear All ConfigurationON 0020 Missing TaskON 0040 Reset because of PXM Low VoltageON 0080 Reset By Event Log TaskOFF 0100 Reset from ShellON 0200 UnknownOFF 0400 Reset from PXMOFF 0800 Reset SystemOFF 1000 Switch Core CardON 2000 Secondary Cache ErrorON 4000 Software Error ResetON 8000 S/W reset due to upgradeOFF 10000 Restore All ConfigurationON 20000 Device Driver ErrorNODENAME.1.7.PXM.s >Use the "core mask default" command to set the mask back to the default.NODENAME.1.7.PXM.s > core mask defaultAutomatic Core Dumping is enabled..The Current Core slot is 0The Current Core mask is 0x262eeOFF 0001 Power ON ResetON 0002 DRAM Parity ErrorON 0004 WatchDog Timeout ResetON 0008 Resource OverflowOFF 0010 Clear All ConfigurationON 0020 Missing TaskON 0040 Reset because of PXM Low VoltageON 0080 Reset By Event Log TaskOFF 0100 Reset from ShellON 0200 UnknownOFF 0400 Reset from PXMOFF 0800 Reset SystemOFF 1000 Switch Core CardON 2000 Secondary Cache ErrorON 4000 Software Error ResetOFF 8000 S/W reset due to upgradeOFF 10000 Restore All ConfigurationON 20000 Device Driver ErrorNODENAME.1.7.PXM.s >Use the "core enable" command to enable autmatic core dumps.NODENAME.1.7.PXM.s > core enableAutomatic Core Dumping is enabled..NODENAME.1.7.PXM.s >Use the "core disable" command to disable automatic core dumps.NODENAME.1.7.PXM.s > core disableAutomatic Core Dumping is disabled..NODENAME.1.7.PXM.s >Use the "core hot-dump" to dump the raw image to the disk.NODENAME.1.7.PXM.s > core hot-dumpDo you want to proceed (Yes/No)? yDumping PXM Core Image[0]:......................................................................................... .......................................Done.NODENAME.1.7.PXM.s >Use the "core" command to list the current list of raw core dumps save onthe disk.NODENAME.1.7.PXM.s > coreSaved Core Images:Slot Reset Reason Dump Time-------------------------------------------------------------0 Unknown WED DEC 29 09:38:30 19991 WatchDog Timeout Reset FRI DEC 10 08:51:52 19992 WatchDog Timeout Reset TUE DEC 14 08:01:39 19993 WatchDog Timeout Reset TUE DEC 14 12:38:01 19994 Reset from Shell TUE DEC 14 14:45:30 19995 WatchDog Timeout Reset WED DEC 22 08:20:26 1999Automatic Core Dumping is enabled.The Current Core slot is 0NODENAME.1.7.PXM.s >Use the "core save" command to save the specified raw image to thespecified zip file.NODENAME.1.7.PXM.s > core save 0 cccCreating ccc.................................NODENAME.1.7.PXM.s >To upload the zip file, you must use FTP (TFTP has a limit of 16 MBytesfor file size).Enter shellconn:NODENAME.1.7.PXM.s > shellConn->Set the and enable the user name:-> setLoginsetLoginUser Name=========ciscovalue = 0 = 0x0->The user name is "cisco" and the password is "ciscoinc".Now you can FTP the image. Be sure to use binary mode.After the image has been uploaded, disable the user name:-> clrLoginclrLoginUser Name=========value = 0 = 0x0->
Problems Fixed in Release 1.1.22
Problems Fixed in Release 1.1.21
Problems Fixed in Release 1.1.20
Problems Fixed in Release 1.1.12
Problems Fixed in Release 1.1.11
Problems Fixed in Release 1.1.10
Problems Fixed in Release 1.1.01
One of the slots on the node had a CESM-8E1 card with some connections. The connections, ports and lines on the CESM were deleted and it was replaced with an AUSM-8T1 card.The AUSM card went to mismatch state. On trying to execute the clrsmcnf command the following error message was seen: flyers4.1.7.PXM.a > clrsmcnf 20, Do you want to proceed (Yes/No)? Yes Command Failed: Resources exist on card (CSCdm29289).
Happens on an MGX 8850 switch with two PXMs (Core Redundancy). If the Active PXM while synchronizing the databases to Standby, resets, then the Standby PXM goes to Fail State. The reset PXM comes up as Active and will show the other PXM slot as Empty (CSCdm30193)
ShelfIntegrated alarm becoming Major or Minor either after switchcc or resetsys. (CSCdm33756)
One connection, CESM-PXM UNI ended up deleted in CESM, but SPM still has some incomplete data structure. Since there is only one connection per port for the CESM, and the connection is in such state that can not be removed or re-added, the port and its bandwidth become unusable (CSCdm33289)
Configuring the DS3 framing format on an FRSM-2CT3 to M13 does not permit the card to operate correctly with other devices using that framing format. (CSCdm35575
When modifying a particular protected memory address on CESM8p which causes CESM HW watchdog reset, PXM got reset or lost SAR functionality. (CSCdm15367)
Adding or modifying a connection to an RPM fails if the RPM enable password differs from the password that Conn MGR has cached. Example: A connection to an RPM is configured, then the enable password is changed on the RPM -- any subsequent connection adds or changes fail because of a bad enable password. (CSCdm34114)
When modifying the bandwidth allocation (usually from a smaller percentage to a much bigger one) of a port with "cnfport" command, it is not always possible to create more connections under that port. (CSCdm32894)
The standby PXM console is not enabled for use. Downlevel PXM board (CSCdm34030)
Adding connections through a conn proxy script. Card went to failed state after adding around 700 connections. (CSCdm32773)
SMs are shown in failed state though physically they are active. This was observed for FRSM8p and FRSM-VHS in slot 5 and 6 and 1. (CSCdm21684)
While using a script to do stress switchcc test, there is a one time occurrence where it was found that the original active card did not come back as standby, but went to fail state. (CSCdm35298)
The problem is related to the PVC's traffic parameters. We are still investigating what the PCR, average, and burst values should be set to for VBR connection. This values are related to nature of the traffic which is sent to the RPM. (CSCdm35352)
When the connection is deleted, the trap does not go to SV+. (CSCdm27489)
Major differences when add vbr.2 connections on PXM by CLI and CWM (CSCdm28075)
If "cnfcon" command is given with the CIR value of less than 8 and greater than zero then the command is never completed and later on one cannot do any modifications, display, etc. (CSCdm34047)
Restoreallcnf does not restore the saved config. Occurs when restoring a configuration taken from another physical shelf. The card the restoreallcnf was done on will not become active but the other card will which contains the previous configuration. (CSCdm37114)
AUSM Connection addition fails for VP connection from CWM. (CSCdm36674)
At low frequencies, the jitter characteristics does not fully comply with the standards. (CSCdm38833)
Problems Fixed in Release 1.1.00
Stand-alone Statistics collection does not work if the PXM is in slot 8 (CSCdm20017).
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 acctuator. When the card is reinserted the PXM automatically comes out of sleep mode.
In Release 1.0.00 Configuration Save and Restore works only for the same firmware image even if there are no database changes from one version to the other version. In Release 1.1.00 Configuration Save and Restore can be done on different firmware images if the firmware images have compatible databases.
VPI range was limited to 0 to 255 on PXM UNI and NNI on the feeder ports in Release 1.0.00. There is no VPI range limit in Release 1.1.00. (CSCdk63920)
A flood of SNMP requests can cause SNMP and CLI to be unavailable for some time (CSCdm13663).
After a user adds PXM UNI channel, VCC with VCI=0, user cannot add any more VCCs with same (CSCdm14123)
Was unable to delete a VP connection for PXM UNI channels using CWM (CSCdm15120)
While executing "cc" command to a Service Module (SM) on a telnet session, the telnet session hangs, and the console of the active PXM card has Tlb load exception message. (CSCdm15150
Telnet session gets cut off without any error messages or obvious network problem (CSCdm15166)
When adding connections using scripts utilizing Conn-Proxy, without delay between two connection additions, and when there are line alarms at either endpoint, there is a probability that the CESM card may reboot. (CSCdk12363)
FRSM-2CT3 is dropping frames due to frame aborts detected by HDLC controller. (CSCdm13123)
Traffic on connection on FRSM-8T1E1 stopped after removal and insertion (CSCdm18521)
Cannot have more than one session on FRSM-VHS (CSCdk77924)
A channel is shown in alarm even though there is no line alarm and port alarm locally on the FRSM8p service module, and there is no remote alarm on the far end of the connection. (CSCdm14383)
Port statuses at service module site might be different with those at PXM and VSI controller site.(CSCdm15183)
A port was seen that had no alarm on FRSM8p, but "dspparifs" on PXM CLI shows the interface of this port in fail state. (CSCdm15620)
Attempt to configure the external clock source using the label 0.33 does not work. (CSCdm15669)
Some FRSM-8T1E1s don't come up when the MGX8850 is power cycled. (CSCdm16401)
Using script to add ports on FRSM8P Service Module card, in case a port addition fails, FRSM8 is not backing off properly and leave the port still added locally on the card even though the port is not added on PXM side and PAR (the interface corresponding to this port will not show up in "dspparifs" CLI on PXM, but "dspports" on SM shows the port added). (CSCdm03268)
Connections in alarm while lines are OK. (CSCdm10735)
Service module & the PXM reserve different bandwidth for the same connection.(CSCdk92115)
The card, after power recycle does not come up. It gets stuck in standby. (CSCdm10416)
When removing a service module or removing a line, VSI controller prints out "swerr 20208" sometimes. (CSCdm16902)
When an MGX 8850 shelf with CESM-8T1E1s is left running for over a day with Configuration Uploads going continuously, there is a possibility of allocated large buffers not getting released. (CSCdm17868)
The interface state (port state) is inconsistent between the VSI controller and the platform as well as that at service module. (CSCdm16033)
A tftp download of backboot displays an S-objlib_OBJ_UNAVAILABLE error (CSCdm16295)
While RPM is reloading after a card reset or as a result of card removal, PXM gets reset intermittently. (CSCdm15040)
CLI commands on a PXM hang after aborting a command using Ctrl-C. (CSCdm16726)
PXM reset when OC12 trunk back card was inserted. (CSCdm20010)
Broad band connection statistics fail when the PXM is in slot 8 and statistics are enabled (CSCdm20017)
Problems Fixed for RPM in 12.0.5T1
These anomalies are fixed in IOS 12.0.5T1. For generic IOS issues, refer to the 12.0.5T1 release notes.
•CPUHOG and Traceback error during connection synch-up. (CSCdm56618)
•RPM performance degrades when two RPMs are side-by-side (CSCdk93628)
•c75 int tunnel <num> shortcut fails create when num is slot number (CSCdm26198)
•Executing show diag 3 resets RPM (CSCdm64903)
•Copy RPM config to c: drive overlay problem (CSCdm63212)
•Connection only on RPM and not on PXM shown as mismatch (CSCdm47650)
•RPM interface name changes are inconsistent (CSCdm49834)
•Dynamic VCD stored on the PXM disk cause connection mismatch (CSCdm72383)
•Spurious memory access while inserting FE card (CSCdm51327)
Problems Fixed for RPM in 12.0.4T
These anomalies are fixed in IOS 12.0.4T. For generic IOS issues, refer to the 12.0.4T release notes.
•RPM in adjacent slots share single OC3 cell-bus bandwidth, which cause a 30% drop in throughput at line speed. It is recommended not to use RPM in adjacent slots at high input rate configurations (CSCdk93626).
•Only VCI zero is supported for VPI greater than zero, therefore VP connections are limited to one VC.
•Under certain unknown condition RPM may not get the MAC addresses from the PXM. The occurrence of this conditions is quite low. It is recommended to set up the MAC address manually when such condition is detected. (CSCdk53731).
•IPC buffers exhaust after executing CC command around 70 times. This requires a reload of RPM to re-establish IPC connectivity to PXM. This condition does not cause any interruption of traffic (CSCdk89950).
•Running an extended ping from an IPC console connection may overload the IPC channel (CSCdk76558)
•Virtual template is not supported through SNMP MIB.
•The "tstcon" command to RPM is not supported in this version (CSCdm00845)
•SNMP over IPC channel is not supported in this version, therefore CV application is not supported (CSCdk47301).
•Reported CRC error counts may not be correct in this version (CSCdk70267)
•Tstcon option on CMGUI for PXM-FR connection is not displayed (CSCdk71714)
Problems Fixed for VISM in 1.1.20 release of PXM
.
Compatibility Notes
1. MGX 8850 Software Interoperability with other Products
2. Software Boot and Runtime Firmware Requirements:
Note VISM is supported by VSC 7.4(6), BPX SW 9.2.22 and CWM 9.2.07. All others are supported by BPX SW 9.2.22 and CWM 9.2.08.
1. RPM Boot and IOS Image
Note 1.1.22 platform image is co-required with the special120-5.XT image.
Special Installation and Upgrade Requirements
Existing customers should use the upgrade procedure on page 83 to upgrade from 1.1.10 to 1.1.11/1.1.12/1.1.21/1.1.22. For new customers the image will be pre-installed as 1.1.22 and they need to use the PXM installation procedure to upgrade to future maintenance releases.
No graceful downgrade is supported from 1.1.22 or any higher version to any down level version of software below 1.1.22 because of MIB changes. This also implies that if you have to abort after newrev command (and the commit command), you have to do an ungraceful downgrade.
Below is the procedure for ungraceful downgrade:
Step 1 If they have a saved configuration then do:
abort
reload old firmware code (boot code can stay at 1.1.22)
restoreallcnf
Step 2 If they don't have a saved configuration then do:
abort
reload the old code
goto shellConn
setPXMPrimary on both boards
issue clrallcnf on the active
Single PXM Installation Procedure
Step 1 Save you current configuration.
SaveallcnfStep 2 Download the 1.1.22 PXM runtime image to the PXM.
tftp <node_name or IP address>binput 1.1.22.fw POPEYE@PXM.FWquitStep 3 Download the ComMat.dat file to the C:/fw directory of the Active PXM. Use the tftp put command:
tftp <node_name or IP address>binput ComMat.datquitStep 4 On the PXM type the following when the transfer is done:
copy ComMat.dat /FW/ComMat.datStep 5 Execute the install 1.1.22 command.
Step 6 Answer Yes to the question the install command will ask.
Installation Procedure For Redundant PXMs:
This section applies to upgrades from 1.1.10 to 1.1.11 or 1.1.12 or 1.1.21 or 1.1.22.
Caution Do not remove old firmware until the upgrade is done.
During 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 backcards, they must be identical.
Note First you must ensure that the shelf IP address and the PXM IP address are set. The PXM must have its own unique IP address and there must be a another unique IP address for the shelf.
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.addressThe second argument is the shelf IP address.
The third argument is the subnet mask.
The fourth argument is the broadcast address.
Step 1 Save your current configuration.
saveallcnfStep 2 Get the filename by listing the CNF directory:
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 On the workstation, upload the saved configuration to the workstation:
unix-prompt> tftp shelf.ip.addresstftp> bintftp> get CNF/NODENAME_0409990528.zipReceived 45433 bytes in 0.4 secondsStep 4 Verify that one PXM is Active and the other Standby.
Step 5 On the workstation, download the PXM FW:
unix-prompt> tftp pxm.ip.addresstftp> bintftp> put pxm_1.1.22.fw POPEYE@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 6 Download the ComMat.dat file to the C:/fw directory of the Active PXM. Use the tftp put command:
tftp <node_name or IP address>bincd fwput ComMat.datcopy ComMat.dat to FW directory on the PXM.quitStep 7 After the transfer is done, type the following on the PXM:
copy ComMat.dat /FW/ComMat.dateEnsure that the ComMat.dat is copied to both PXMs.
Step 8 On the Active PXM, do "install 1.1.22".
The Standby card will reset at this point, and go to hold state.
Step 9 After the Standby card is reset and successfully enters the hold state, on the Active PXM, do "newrev 1.1.22".
The Active card will be reset and go to hold state.
After the newrev the firmware should now show the new revision on dspcd.
Step 10 After the Active PXM is reset and successfully enters the hold state, on the new Active PXM, do "commit 1.1.22".
PXM Flash Download Procedure
Step 1 Download the new bootcode:
unix-prompt> tftp shelf.ip.addresstftp> bintftp> put pxm_bkup_1.1.22fw POPEYE@PXM.BTSent 642232 bytes in 6.3 secondsThe byte count above is just an example. It will be different for different images. Make sure that the boot is successfully downloaded. You should see a message like the following on the console:
Program length = 642230Calculated checksum = 0x2a5a41f2 stored checksum = 0x2a5a41f2Fw checksum passedStep 2 Issue install bt "revision".
Service Module Firmware Download Procedure
Step 1 Download the selected revision of service module firmware into the service module in the selected slot.
tftp <node_name or IP address>binput <backup boot> POPEYE@SM_1_<slot#>.BOOTquittftp <node_name or IP address>
put <FW file> POPEYE@SM_1_0.FWquitYou cannot do two puts in the same tftp session.
Step 2 Install bt SM slot version.
Step 3 Answer Yes to the question the install command will ask.
Note Please consult your Support Representative before performing any software upgrade.
Service Module Installation/Upgrade and Flashdownload Requirements.
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 upgrade. Service module firmware images cannot be downloaded as specific versions in MGX 8850 Release 1.1.22 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 Download the service module firmware to the shelf:
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 If the checksums are not the same when you remove the service module then the service module will not boot when it is plugged in and the service module will have to be RMA'ed.
•- MGX 8850 MGX-FRSM-HS2, MGX-FRSM-2CT3, MGX-FRSM-2T3E3 need to have Release 10.0.01 firmware for the runtime image and Release 10.0.01 firmware for the backup boot image.
•-If you need to upgrade both flash and runtime image of MGX 8220 Release 4.0.xx service modules to Release 10.0.01 to operate within the MGX 8850 chassis please follow the procedure below, which is also outlined in the Cisco MGX 8850 Installation and Configuration publication on the documentation CD.
Step 2 For non-graceful upgrades, just reset the card and the service module will come up with the new image.
Step 3 For graceful upgrades, a secondary card should be backing up the service module that needs to be upgraded. Configure the redundancy and issue the command:
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 The concept of version is redundant here, since there is only one service module image on the disk. However we do check that the version given by the user matches the image on the disk to make it consistent with PXM upgrade/downgrade.
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 There is no abort command for service module upgrade.
Known Anomalies for Platform Software and Service Module Firmware
The following is the list of known anomalies in the MGX 8850, Release 1.1.22 delivery. 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
.
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 Engineer:
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 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."
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 signalled to the local user based on the service affecting conditions or PVC status signaled from the remote user side.
FRF 2.1 Section 4.2 Polling requirements of network-to-network interfaces
Two sets of sequence numbers and local in-channel signalling parameters are administered for the network-to-network interface as shown below; see the table for parameter ranges and default values.
user side procedures - T391, N391, N392, and N393
network side procedures - T392, N392, and N393
The table below summarizes the acceptable values when using bidirectional procedures at the NNI. The default values should be used as the actual system system parameter values. Parameter values other than the default values are a subscription time option. Procedures for starting and stopping T391 and T392 aredescribed in Q.933 Annex A.
Table 1 NNI system parameters
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 signalled in the other direction at the same NNI.
Step 1 In addition, when a PVC segment's active/inactive status has changed, or a PVC segment has been newly added or deleted, the network should respond to any poll (i.e., status enquiry) with a full status report. Alternatively, the network may generate a single PVC asynchronous status report to convey the PVC segment's status change.
Known Anomalies for VISM
LCN Upgrade Load Process
VISM 1.5.1 config is incompatible with all earlier VISM configurations. VISM does not provide MIB upgrades, so the old configuration must be cleared. The resetsys command will not clear the configuration. The clrsmcnf command is not supported on VISM cards that have ports and connections. So you must follow the procedure below to sucessfully load the new VISM configuration.
Step 1 With old PXM and VISM images still loaded, delete all:
•CIDs
•CCS (incase of a CCS config)
•connections
•endpoints
•lines
•resource partitions
•ports
on the VISM cards.
Step 2 Remove VISM cards from the shelf.
Note THIS STEP IS VERY IMPORTANT.
Step 3 Now do clrsmcnf on all VISM cards.
Step 4 Upgrade boot code on PXM using normal procedure
Step 5 TFTP the new PXM firmware image and new VISM firmware image
Step 6 resetsys --this will cause the shelf to reset.
Step 7 Insert VISM cards back into the shelf. This will rebuild the proper databases with the new images.
The following is the list of known anomalies in the MGX 8850 VISM service module, Release 1.5 delivery. 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.
The following is the list of known anomalies in the MGX 8850 VISM service module, Release 1.00 delivery. 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 RPM
These RPM anomalies are tied to its function with the MGX 8850. For generic IOS issues, refer to the 12.0.5T1 release notes.
•Under heavy load conditions from multiple sources, RPM performance may degrade (CSCdk91818)
•Some RPMs may not boot when more than 8 RPMs are booting simultaneously from the PXM hard disk (CSCdm14987)
•UBR connection for RPM is not supported from CWM, even though the CLI can support it
Note For more details refer to the CWM Release 9.2.05 release notes part number 78-6659-05
•The ABR service type is not supported in 12.0.5T1/120.5.T1 release of MGX/RPM but the CLI does not restrict the provisioning.
•Under heavy load conditions the counter (input queue size, packet output byte size) values reported may be incorrect particularly with Tag VP configuration.
•It is required to allow OSPF and MPLS to converge while adding connections continuously. Otherwise, it will load the CPU and cause CPUHOG condition. Under such condition the IPC channel is not serviced which in turn will cause PXM to declare RPM in Failed state.
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.
•It is not recommended to shut the switch interface. Doing so will remove the connection to the MGX cell-bus and all connections will go down. It also generates some trace back error messages, which are benign. The 120-5.T image does not provide any caution or warning when the command is entered.
•In some instances you may see RPM_VIRTUAL_PORT-3-IPCERR indicating that RPM was not able to convey the existing virtual port information to PXM. This situation is more likely to happen after "clrallcnf" is executed or the card is reset. At this point the connection database gets out of sync between RPM and PXM, and RPM experienced a problem in connection resync. However the connection eventually comes up successfully.
If not, the saved config needs to be copied to running config by "copy" command.
•In multi-point configuration with inverse ARP, it is recommended to decrease the frequency from the default value of 15 min to 1 min.
•If you are unable to overwrite on an existing config file on PXM disk and are getting the:
%error opening c: filename (bad file number)
message then delete:
(rm <filename>)
the existing file and then copy the new file.
•In 120-5.T release when RPM re-loads, the "Status" column in the output of the "show switch connections" command show "MISMATCH" for all the connections or for a few connections even though the connections are fine and traffic passes through them without any problem.
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 Both RPMs are in the same shelf or chassis.
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#Obtaining Service and Support
For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your chassis.
Note If you purchased your product from a reseller, you can access Cisco Connection On-line (CCO) as a guest. CCO is Cisco Systems' primary, real-time support channel. Your reseller offers programs that include direct access to CCO's services.
For service and support for a product purchased directly from Cisco, use CCO.
Cisco Connection On-line
Cisco Connection On-line (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
•WWW: http://www.cisco.com
•WWW: http://www-europe.cisco.com
•WWW: http://www-china.cisco.com
•Telnet: cco.cisco.com
•Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8 kbps.
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.