Document ID: 20375
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
SIW-Translation or SIW-Transparent on WAN Switch
Configure
Network Diagram
Configurations
Verify
Troubleshoot
NetPro Discussion Forums - Featured Conversations
Related Information
Introduction
This configuration example illustrates the design where the Service InterWorking (SIW) connections originate and terminate on different routing nodes. The same configuration steps are applicable if the connection originates and terminates on the same routing node, such as a DAX connection.
It is assumed that at least one trunk between the routing nodes is up and clear of alarms and that there is enough bandwidth available to route the SIW connection.
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
The information in this document is based on these software and hardware versions:
-
All IGX 8400 hardware platforms
-
All BPX 8600 hardware platforms
-
All Cisco Router hardware platforms that support Frame Relay and ATM encapsulations
-
WAN Switch software version 9.1.x and later
-
Cisco IOS Software 12.0 or later
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.
Conventions
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
SIW-Translation or SIW-Transparent on WAN Switch
The decision to configure the Permanent Virtual Circuit (PVC) on the WAN Switch for a SIW-Translation or SIW-Transparent type connection depends on the ATM and Frame Relay encapsulation configuration of the customer premises equipment (CPE) devices, such as routers.
For all SIW-type connections, the Frame Relay router must be configured for Internet Engineering Task Force (IETF) Frame Relay encapsulation, that is encap Frame Relay IETF.
This table contains the ATM and Frame Relay encapsulation configuration to the WAN Switch connection type configuration mapping.
|
Device |
Frame Relay Router Encapsulation |
Connection Type on the WAN Switch |
ATM Router Encapsulation |
|---|---|---|---|
|
Configuration |
encap Frame Relay IETF |
atfx or atfxfst(siw-translation) |
encap aal5snap |
|
encap Frame Relay IETF |
atft or atftfst(siw-transparent) |
encap aal5nlpid |
Refer to Configuring Frame Relay to ATM Network and Service Interworking for more information on SIW.
Configure
In this section, you are presented with the information to configure the features described in this document.
Note: To find additional information on the commands used in this document, use the Command Lookup Tool ( registered customers only) .
Network Diagram
This document uses these network setups:
SIW-Translation Type Connection:
Configurations
Complete the steps in this section to perform your configuration.
Note: Step 1, Step 2, and Step 3 are common configuration tasks applicable to all types of connections. Step 4 and Step 5 are applicable to SIW-X type connections only; and Step 6 and Step 7 are applicable to SIW-T type connections only.
-
Configure the Universal Frame Relay Module (UFM) port on node1, which is an IGX, with hostname i1_labL. All types of UFM cards on the IGX support SIW. However, this particular example uses the UFMU V.35 card.
Activate the port where the Frame relay router is connected and configure the Local Management Interface (LMI) type and settings. In this example, the router is connected to port number 5 of the UFMU card in slot 10.
i1_labL VT SuperUser IGX 8420 9.2.34 Feb. 2 2002 00:16 GMT Port States Port ID State Port ID State 4.1 0 ACTIVE 10.8 0 FAILED 4.2 0 INACTIVE 10.9 0 INACTIVE 4.3 0 INACTIVE 10.10 0 INACTIVE 4.4 0 INACTIVE 10.11 0 INACTIVE 9.2 FAILED 10.12 0 INACTIVE 10.1 0 ACTIVE 10.2 0 INACTIVE 10.3 0 ACTIVE 10.4 0 INACTIVE 10.5 0 INACTIVE 10.6 0 INACTIVE 10.7 0 ACTIVE Last Command: dspports Next Command: i1_labL TRM SuperUser IGX 8420 9.2.34 Feb. 2 2002 00:23 GMT Port: 10.5 [ACTIVE ] Interface: V35 DCE Configured Clock: 256 Kbps Clocking: Normal Measured Rx Clock: 0 Kbps Port ID 0 Min Flags / Frames 1 Port Queue Depth 65535 OAM Pkt Threshold 3 pkts ECN Queue Threshold 65535 T391 Link Intg Timer 10 sec DE Threshold 100 % N391 Full Status Poll 6 cyl Signalling Protocol None EFCI Mapping Enabled No Asynchronous Status No CLLM Enabled/Tx Timer No/ 0 msec T392 Polling Verif Timer 15 IDE to DE Mapping Yes N392 Error Threshold 3 Interface Control Template N393 Monitored Events Count 4 Lead CTS DSR DCD Communicate Priority No State ON ON ON Upper/Lower RNR Thresh 75%/ 25% Last Command: upport 10.5 Next Command: i1_labL TRM StrataCom IGX 8420 9.2.34 Feb. 2 2002 00:27 GMT Port: 10.5 [ACTIVE ] Interface: V35 DCE Configured Clock: 256 Kbps Clocking: Normal Measured Rx Clock: 256 Kbps Port ID 0 Min Flags / Frames 1 Port Queue Depth 65535 OAM Pkt Threshold 3 pkts ECN Queue Threshold 65535 T391 Link Intg Timer 10 sec DE Threshold 100 % N391 Full Status Poll 6 cyl Signalling Protocol Cisco LMI EFCI Mapping Enabled No Asynchronous Status Yes CLLM Enabled/TX Timer No/ 0 msec T392 Polling Verif Timer 15 IDE to DE Mapping Yes N392 Error Threshold 3 Interface Control Template N393 Monitored Events Count 4 Lead CTS DSR DCD Communicate Priority No State ON ON ON Upper/Lower RNR Thresh 75%/ 25% Last Command: cnfport 10.5 DCE 256 NORMAL 0 65535 65535 100 c y 15 3 4 N 75 25 3 N N Y 1 -
Log in to node2 and configure the ATM UNI port. In this case, node2 is a BPX, hostname b3_labL, with a BXM-155 card providing the ATM UNI port.
b3_labL VT StrataCom BPX 8620 9.2.34 Feb. 2 2002 00:40 GMT Line Type Current Line Alarm Status 10.2 OC3 Clear - OK Last Command: upln 10.2 256 PVCs allocated. Use cnfrsrc to configure PVCs Next Command: b3_labL VT StrataCom BPX 8620 9.2.34 Feb. 2 2002 00:40 GMT LN 10.2 Config OC3 [353208cps] BXM slot: 10 Loop clock: No Idle code: 7F hex Line framing: -- coding: -- recv impedance: -- E1 signaling: -- encoding: -- cable type: -- T1 signaling: -- length: -- HCS Masking: Yes Payload Scramble: Yes 56KBS Bit Pos: -- Frame Scramble: Yes pct fast modem: -- Cell Framing: STS-3C VC Shaping: No Last Command: dsplncnf 10.2Verify that the Payload Scramble, Frame Scramble, and Cell Framing configuration is the same as that of the router interface. Refer to When Should Scrambling Be Enabled on ATM Virtual Circuits? for more information.
b3_labL VT StrataCom BPX 8620 9.2.34 Feb. 2 2002 00:40 GMT Port: 10.2 [ACTIVE ] Interface: LM-BXM CAC Override: Enabled Type: UNI %Util Use: Disabled Shift: SHIFT ON HCF (Normal Operation) SIG Queue Depth: 640 Port Load: 0 % Protocol: NONE Protocol by Card: No SVC Channels: 0 SVC VPI Min: 0 SVC VPI Max: 0 SVC Bandwidth: 0 (cps) Last Command: upport 10.2 -
Verify that both the routing nodes, i1_labL and b3_labL, can reach each other and that there is enough bandwidth available on the trunk between them to route the connection.
b3_labL VT StrataCom BPX 8620 9.2.34 Feb. 2 2002 00:51 GMT TRK Type Current Line Alarm Status Other End 2.1 T3 Clear - OK - 4.1 T3 Clear - OK i2_labL/5 4.2 T3 Major - Loss of Sig (RED) - 4.3 T3 Clear - OK i1_labL/6 6.1 T3 Clear - OK - 6.2 T3 Clear - OK b1/1.5 6.3 T3 Major - Loss of SIG (RED) - 6.4 T3 Major - Loss of SIG (RED) - 11.2 OC3 Clear - OK - Last Command: dsptrks Next Command: b3_labL VT StrataCom BPX 8620 9.2.34 Feb. 2 2002 00:53 GMT Trunk loads for node 'b3_labL' Units Used Available Reserved Con ID TRK Xmt Rcv Xmt Rcv Xmt Rcv Xmt Rcv Used Avail 4.1 Pkt Cell 1200 501 77800 94499 1000 1000 3 1768 4.3 Pkt Cell 1200 501 77800 94499 1000 1000 3 1768 6.2 Cell Cell 0 0 95000 95000 1000 1000 0 256 Last Command: dsploadStep 4 and Step 5 are applicable to only SIW-X types of connections. If you are configuring an SIX-T type connection, proceed to Step 6.
-
Verify the configuration on the ATM and Frame Relay routers.
This is the required configuration for the ATM-attached router with a minimum of 1 PVC:
! interface ATM3/0.1 point-to-point ip address 192.168.150.2 255.255.255.252 pvc 1/100 protocol ip 192.168.150.3 broadcast encapsulation aal5snap
This example demonstrates configuration for an MC3810 with a V.35 serial interface which is connected to the Frame Relay port:
interface Serial1 ip address 192.168.150.3 255.255.255.252 encapsulation Frame Relay ietf Frame Relay map ip 192.168.150.2 100
-
Add the connection from the ATM side, BXM (10.2) to the Frame Relay side, UFMU (10.5) with the connection class as ATFX (non-ForeSight) or ATFXFST (with ForeSight). In this example the connection added is not using Foresight.
b3_labL VT StrataCom BPX 8620 9.2.34 Feb. 2 2002 01:32 GMT Local Remote Remote Route Channel NodeName Channel State Type Avoid COS O 10.2.1.100 i1_labL 10.5.100 Ok atfx 0 L This Command: addcon 10.2.1.100 i1_labL 10.5.100 atfx 150 * * * * * * * * Add these connections (y/n)? y
Note: The quality of service and bandwidth requirements must match your network requirements. The connection values are not optimized and are used for this example only. Refer to the Command Reference for more information about the addcon command parameters.
Step 6 and Step 7 are applicable to only SIW-T type connections. If you are configuring SIW-X type connections, proceed to Step 4.
-
Verify the configuration on the ATM and Frame Relay routers.
This configuration is required for the ATM-attached router with a minimum of 1 PVC:
! interface ATM3/0.1 point-to-point ip address 192.168.150.6 255.255.255.252 PVC 2/200 protocol ip 192.168.150.7 broadcast encapsulation aal5nlpid !
This example demonstrates the configuration for an MC3810 with a V.35 serial interface connected to the Frame Relay port:
Interface Serial1 ip address 192.168.150.7 255.255.255.252 encapsulation Frame Relay ietf Frame Relay map ip 192.168.150.6 200
-
Add the connection from the ATM side, BXM (10.2) to the Frame Relay side, UFMU (10.5) with the connection class as ATFT (non-Foresight) or ATFTFST (with Foresight). In this example the connection added is not using Foresight
b3_labL VT StrataCom BPX 8620 9.2.34 Feb. 2 2002 01:42 GMT Local Remote Remote Route Channel NodeName Channel State Type Avoid COs O 10.2.2.200 i1_labL 10.5.200 OK atfx 0 L This Command: addcon 10.2.2.200 i1_labL 10.5.200 atft 150 * * * * * * * * Add these connections (y/n)? y
Note: The quality of service and bandwidth requirements must match your network requirements. The connection values are not optimized and are used for this example only.
Verify
This section provides information you can use to confirm your configuration is working properly.
-
dspcons—Use this command from the BPX or IGX CLI to display a summary of all connections.
-
dspcon—Use this command from the BPX or IGX CLI to display the parameters and status for a specified connection.
b3_labL TRM StrataCom BPX 8620 9.2.34 Feb. 17 2002 04:12 GMT Conn: 10.2.1.100 i1_labL 10.5.100 atfx Status:OK PCR(0+1) % Util CDVT(0+1) FBTC SCR MBS PLC 150/150 100/100 250000/250000 y 150/150 1000/1000 3 Owner: LOCAL Restriction: NONE COs: 0 TestRTD: 0 msec Path: b3_labL 4.3-- 6i1_labL Pref: Not Configured b3_labL BXM : OK i1_labL UFMU : OK Line 10.2 : OK Port 10.5 : OK OAM Cell RX: Clear NNI : OK This Command: dspcon 10.2.1.100 Continue? y b3_labL TRM StrataCom BPX 8620 9.2.34 Feb. 17 2002 04:22 GMT Conn: 10.2.1.100 i1_labL 10.5.100 atfx Status:OK PCR(0+1) % Util CDVT(0+1) SCR MBS 150/150 100/100 250000/250000 150/150 1000/1000 Policing VC Qdepth EFCI IBS 3 1280/1280 35/35 1/1 Last Command: dspcon 10.2.1.100 -
dspchstats—Use this command from the BPX or IGX CLI to view the traffic flow of a specified connection.
Troubleshoot
Refer to Troubleshooting PVC Problems for information about how to troubleshoot PVC problems in a Cisco IGX 8400 or BPX 8600.
NetPro Discussion Forums - Featured Conversations
| NetPro Discussion Forums - Featured Conversations for WAN Switching |
| Network Infrastructure: WAN Routing and Switching |
Related Information
- Configuring Frame Relay to ATM Network and Service Interworking
- Troubleshooting PVC Problems
- When Should Scrambling Be Enabled on ATM Virtual Circuits?
- Command Reference, Release 9.3.30
- Cisco WAN Switching Solutions - Cisco Documentation
- Guide to New Names and Colors for WAN Switching Products
- Downloads - WAN Switching Software
- Technical Support - Cisco Systems
| Updated: Apr 30, 2009 | Document ID: 20375 |