This document describes a sample scenario for connecting a Cisco MGX 8220 shelf to a LightStream 1010 (LS1010) using an ATM User-Network Interface (UNI) connection. In this example, we are using Frame Relay-ATM Software Interworking between Cisco routers as the end devices. This can be used as a general reference for interconnecting other end devices between an MGX 8220 shelf and an LS1010. For more detail on the commands used in this example, please see the command reference for the respective product.
There are no specific requirements for this document.
This document is not restricted to specific software and hardware versions.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Change the BNM cell header format. Note: This will reset the entire MGX 8220 shelf.
rtp-ax3.1.4.ASC.a > cnfbnmif -if 2
In the above example, we set the cell header format to ATM UNI. The choices are 1: STI, 2: UNI, 3: NNI. This requires 4.0 firmware or higher on the MGX 8220 using the E3, DS3, or OC3 BNM cards.
Add the line to the shelf for the FRSM:
rtp-ax3.1.8.FRSM.a > addln 1
Here we are using line 1 from an FRSM-E1.
Configure that line as needed to match your requirements:
rtp-ax3.1.8.FRSM.a > cnfln 1 3 9 2 CCS
We are using a channelized E1 connection using CCS with no CRC4.
Add the port onto the FRSM-8E1:
rtp-ax3.1.8.FRSM.a > addport 1 1 2 2 31 1
We are using port 1 configured on line 1 using channels 2-31.
Add the channel on the shelf:
rtp-ax3.1.8.FRSM.a > addchan 50 1 100 530000 3
50 = LCN number (will be used again in the LS1010 PVC configuration).
1 = Port number.
100 = DLCI used by the end device connected to this port (see 7507 configuration).
5300000 = Frame Relay CIR - ATM traffic shaping should match this on the LS1010 as well the ATM-attached router. To simplify the example we made CIR = PCR, but in reality CIR might equal SCR. This depends on your requirements.
3 = SIW Translate, meaning this is a FR-ATM SIW connection with translation.
atm connection-traffic-table-row index 10 ubr peak-cell-rate 530 ! interface ATM0/1/0 Description ***Connection to AXIS Shelf via BNM**** no atm auto-configuration no atm address-registration framing cbitplcp no atm signaling-enable ! interface ATM3/0/2 ! interface ATM3/0/3 Description **** Connection to 4700 ATM router(ATM 0) ****** atm pvc 0 100 rx-cttr 10 tx-cttr 10 interface ATM0/1/0 8 50
The important part to note in this configuration is the atm pvc command and the VPI/VCI used on the port connected to the MGX 8220 shelf. The logic is similar to connecting an MGX 8220 shelf to a BPX, where:
VPI = The Slot# in the MGX 8220 shelf for the FRSM.
VCI = The LCN number as configured for the addchan on the MGX 8220 shelf.
The rx-cttr 10 tx-cttr 10 matches the atm connection-traffic-table-row index 10 defined above. This traffic table is defined as UBR with a PCR set to 530 kbytes/sec, which matches the Frame Relay CIR channel configuration.
In this example, we are using a NP-1A directly connected to the LS1010 via an OC3 connection.
! interface ATM0 Description ***Connected to LS1010 port atm 3/0/3**** ! interface ATM0.1 point-to-point ip address 10.28.28.2 255.255.255.0 atm pvc 1 0 100 aal5snap 530 530 32
In this example, we are using a VIP-40 with a PA-2CE1 card providing the Frame Relay connection to the MGX 8220 shelf FRSM. For further information, please refer to the Cisco IOS command reference.
! controller E1 4/0/0 framing NO-CRC4 channel-group 0 timeslots 1-31 ! interface Serial4/0/0:0 Description ***Directly connection to AXIS Shelf port 8.1***** no ip address no ip mroute-cache encapsulation frame-relay IETF no keepalive ! interface Serial4/0/0:0.1 point-to-point ip address 10.28.28.1 255.255.255.0 frame-relay interface-dlci 100
There is currently no verification procedure available for this configuration.
There is currently no specific troubleshooting information available for this configuration.
The Cisco Support Community is a forum for you to ask and answer questions, share suggestions, and collaborate with your peers.
Refer to Cisco Technical Tips Conventions for information on conventions used in this document.