Table Of Contents
Accessing the Command-Line Interface
Verifying the LEC Configuration
Using the show interface Command
Configuring Support for an RFC-1483 PVC
Configuration Example for an RFC-1483 PVC
Monitoring and Maintaining the MPC
Using the show mpoa client Command
Using the show mpoa client statistics Command
Monitoring and Maintaining the MPS
Using the show mpoa server Command
Verifying MPOA Server Statistics
Using the show mpoa server statistics Command
Configuring the ATM Module
This chapter provides the following procedures for configuring the ATM module through the command-line interface (CLI):
•
Configuring the ATM LAN emulation (LANE) client (LEC)
•
•
•
Additionally, this chapter explains and how to configure an MPS. For information about the trunking and nontrunking features, see the Cisco IOS Desktop Switching Enterprise Edition Software Configuration Guide. For detailed information about commands used in this chapter, see the "" appendix.
Accessing the Command-Line Interface
You can enter Cisco IOS commands to configure the ATM module. To start an ATM session, enter the session session-number command in privileged EXEC mode at the switch prompt.
switch# session 1ATM>Entering Console for module in slot 1Type "^G" to end this sessionPress RETURN to get started!ATM>If the ATM module is installed in Slot 1, the session displays interface 1; if the module is installed in Slot 2, the session displays interface 2.
Configuring the LEC
This section explains how to configure the ATM module LEC from the CLI at the
Catalyst 2900 XL switch management console. The ATM module does not forward any frames from the switch until you define LEC. Once you define a LEC with an ELAN mapped to a VLAN, the ATM module forwards the traffic to the appropriate ELAN.Before you configure the LEC, ensure that the LES is configured. Refer to the "LANE Configuration Requirements" section in the "" chapter.
Configuring the LEC specifies the ELAN in the ATM network to which your LAN is connected.
lists the Cisco IOS commands used to configure (and verify) the LEC.
In the configuration procedure example that follows, the following information applies:
•
•
•
To configure the LEC from the CLI, follow these steps:
Step 1
ATM> enableATM#Step 2
ATM# configure terminalEnter configuration commands, one per line. End with CNTL/Z.ATM(config)#Step 3
ATM(config)# interface atm1.1 multipointATM(config-if)#Step 4
ATM(config-if)# lane client ethernet 1 marketingATM(config-if)#Step 5
ATM(config-if)# ^ZATM#Step 6
ATM# write memoryATM#This step saves the commands you used in Steps 1 through 5 in the NVRAM file. You can use this file the next time you access the module.
When you have configure the LEC, the ATM module is ready to transmit and receive data between your LAN and the ATM network.
Verifying the LEC Configuration
After the LEC is configured, you can verify that the configuration is complete. This section tells you how to verify the ATM and LANE status and view the port statistics for the LEC.
Verifying ATM and LANE Status
You can verify the ATM and LANE status by using the show lane command.
Using the show lane Command
Use the show lane command to verify that the LEC is operational and to show the ATM NSAP addresses of the LANE configuration.
To verify ATM and LANE status from the CLI, enter the show lane EXEC command:
ATM> show laneLE Client ATM1.1 ELAN name: marketing Admin: up State: operationalClient ID: 2 LEC up for 6 minutes 14 secondsELAN ID: 2Join Attempt: 2HW Address: 00c0.1dfc.a2fc Type: ethernet Max Frame Size: 1516VLANID: 1ATM Address: 39.000000000000000000000000.00C01DFCA2FC.00VCD rxFrames txFrames Type ATM Address0 0 0 configure 39.000000000000000000000000.00605C28DA23.004 0 2 direct 39.000000000000000000000000.00605C28DA21.015 0 0 distribute 39.000000000000000000000000.00605C28DA21.016 0 20 send 39.000000000000000000000000.00605C28DA22.0113 0 0 forward 39.000000000000000000000000.00605C28DA22.018 58 55 data 39.000000000000000000000000.00605C28DA20.01ATM>Verifying ATM Port Statistics
The port statistics verify that the ATM module is transmitting and receiving data across the ATM network. For example, the display shows the number of ATM Adaptation Layer 5 (AAL5) frames and ATM cells transmitted and received. You can verify ATM port statistics by using the show interface command.
Using the show interface Command
Use the show interface command to verify that the ATM port is connected to the network. This command displays information such as the operational state of the ATM interface and the rate at which packets are transferred.
To verify ATM port statistics from the CLI, enter the show interface EXEC command as follows:
ATM# show interfaceATM1 is up, line protocol is upHardware is Catalyst 2900 ATMInternet address is 199.90.198.195MTU 1500 bytes, sub MTU 1500, BW 156250 Kbit, DLY 100 usec, rely 255/255, load1/255Encapsulation ATM, loopback not set, keepalive set (10 sec)Encapsulation(s): AAL5, PVC mode1024 maximum active VCs, 1024 VCs per VP, 22 current VCCsVC idle disconnect time: 300 secondsSignalling vc = 1, vpi = 0, vci = 5UNI Version = 3.1, Link Side = userLast input 00:00:07, output never, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 3000 bits/sec, 3 packets/sec5 minute output rate 2000 bits/sec, 3 packets/sec82111 packets input, 10186865 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort82152 packets output, 10176265 bytes, 0 underruns0 output errors, 0 collisions, 3 interface resets0 output buffer failures, 0 output buffers swapped outATM1.1 is up, line protocol is upHardware is Catalyst 2900 ATMMTU 1500 bytes, BW 156250 Kbit, DLY 100 usec, rely 255/255, load 1/255Encapsulation ATM-LANEARP type: ARPA, ARP Timeout 04:00:00ATM#Configuring Support for an RFC-1483 PVC
You must manually configure the ATM module to support RFC-1483 LLC encapsulation. By using RFC 1483, you can transport Ethernet frames over permanent virtual connections (PVCs). You can create a PVC for RFC-1483 LLC encapsulation support.
For RFC-1483 LLC encapsulation, you must bind PVCs to the VLAN, and the VLAN ID must match the VLAN used on the switch. Each ATM trunk supports a maximum of
64 active VLANs at one time. You can logically group users on Ethernet and ATM networks by mapping VLANs on the Ethernet network to PVCs on the ATM network.
Note
Using LECs
You cannot create both LECs and RFC-1483 PVCs on an ATM module. If you want to create a LEC after an RFC-1483 PVC has been configured, you must first remove all PVCs. Use the CLI command no atm pvc vcd to remove all RFC-1483 PVCs. Then use the CLI command lane client ethernet to create a LEC.
Using RFC-1483 PVCs
If you create an RFC-1483 PVC, you cannot create a LEC on the ATM module. If you want to create an RFC-1483 PVC after a LEC is configured, you must first remove all existing LECs. Use the CLI command no lane client ethernet to remove LECs. After you create a PVC, you must bind it to the VLAN. For more information on binding the PVC, refer to the following section, "Configuration Example for an RFC-1483 PVC." A detailed example with a Cisco router and an LS1010 ATM switch is discussed in the "Configuration Examples" appendix.
Configuration Example for an RFC-1483 PVC
The following example shows how to manually configure the ATM module to support
an RFC-1483 PVC:
Note
Step 1
atm> enable atm#Step 2
atm# configure terminal atm(config)#Step 3
atm(config)# int atm1Step 4
atm(config-if)# atm pvc 100 0 100 aal5snap 20000 20000 32atm(config-if)# atm pvc 101 0 101 aal5snapatm(config-if)# atm pvc 200 0 200 aal5snapStep 5
atm(config-if)# int atm1.1 multipoint atm(config-subif)#Step 6
atm(config-subif)# atm bind pvc vlan 100 1 atm(config-subif)# atm bind pvc vlan 101 1Step 7
atm(config-subif)# int atm 1.2 multipointStep 8
atm(config-subif)# atm bind pvc vlan 200 2Step 9
ATM(config-if)# ^ZATM#For a detailed configuration example, refer to the "" appendix.
How an MPC Works
An MPC identifies packets sent to an MPOA-capable router over the nonbroadcast multi-access (NBMA) network and establishes a shortcut VCC to the egress MPC, if possible. The MPC then routes these packets directly over this shortcut VCC, bypassing the intermediate routers and enabling the fast routing of internetwork-layer packets across an NBMA network. The ATM module can be designated as an MPC.
A router is usually designated as an MPS, but can also be designated as an MPC. MPC on the router is primarily meant to provide router-initiated and router-terminated shortcuts for non-NBMA networks.
Configuring an MPC
This section describes the required and optional tasks for configuring an MPC. For a complete description of the MPC commands used in this chapter, refer to the "MPOA Commands" chapter in the Cisco IOS Switching Services Command Reference. For documentation of other commands that appear in this chapter, you can use the command reference master index or search online.
The MPC functionality includes ingress and egress cache management, data-plane and control-plane VCC management, MPOA frame processing, and in MPOA protocol and MPOA flow detection.
To configure an MPC on your network, perform the following tasks. Only the first two tasks are required. Each task is described in the following subsections:
•
•
•
•
Configuring the ELAN ID
For MPOA to work properly, a LEC must have an ELAN ID for all ELANs represented by the LECs. To configure an ELAN ID, use either of the following commands in lane database configuration mode or in interface configuration mode when starting up the LES for that ELAN:
Note
CautionIf an ELAN ID is supplied, make sure both commands use the same id value.
Defining and Binding the MPC
To define and bind an MPC on your network, use the following commands in the appropriate configuration modes:
Note
Configuring the MPC Variables
An MPC has to be defined with a specified name before you can change its variables. Following are the variables you can define or specify:
•
•
•
•
To change the variables for an MPC, use the following commands, beginning in global configuration mode:
Monitoring and Maintaining the MPC
To monitor and maintain the configuration of an MPC, use any of these commands in EXEC mode:
Verifying MPC Status
You can verify the ATM and MPC status by using the show mpoa client command.
Using the show mpoa client Command
Use the show mpoa client command to verify that the MPC is operational and to show the addresses of the MPC configuration.
To verify ATM and MPC status from the CLI, enter the show mpoa client EXEC command:
ATM> show mpoa clientMPC Name:mpclient, Interface:ATM1, State:UpMPC actual operating address:47.00918100000000D058EFB301.005080562665.00Shortcut-Setup Count:10, Shortcut-Setup Time:1Lane clients bound to MPC mpclient:ATM1.1Discovered MPS neighbours kp-alv vcd rxPkts txPkts47.00918100000000D058EFB301.00502AA54404.00 27 10 26 0ATM>Other show mpoa client options include the following:
ATM# show mpoa client remote-deviceMPC Name:mpclient, Interface:ATM1, State:UpMPC actual operating address:47.00918100000000D058EFB301.005080562665.00Shortcut-Setup Count:10, Shortcut-Setup Time:1Remote devices:MPS (id 1) 47.00918100000000D058EFB301.00502AA54404.00mac addr 0050.2aa5.4400 learned from LEC on ATM1.1ATM#ATM# show mpoa client cacheMPC Name:mpclient, Interface:ATM1, State:UpMPC actual operating address:47.00918100000000D058EFB301.005080562665.00Shortcut-Setup Count:10, Shortcut-Setup Time:1Number of Egress cache entries:0MPC Ingress Cache Information:Dst IP addr State Egress MPC Atm addressNumber of Egress cache entries:0MPC Egress Cache Information:Dst IP addr Dst MAC Src MAC MPSid Elan Expires CacheId Tag0ATM#ATM# show mpoa default-atm-addressesinterface ATM1:MPOA Server:47.00918100000000D058EFB301.005080562664.**MPOA Client:47.00918100000000D058EFB301.005080562665.**note:** is the MPS/MPC instance number in hexATM#Verifying MPOA Statistics
The MPOA statistics show transmit (Tx) and receive (Rx) information for MPC control packets. You can display MPOA statistics by using the show mpoa client statistics command.
Using the show mpoa client statistics Command
Use the show mpoa client statistics command to verify that the MPC is connected to the network. This command displays information such as the operational state of the MPC.
To verify MPOA statistics from the CLI, enter the show mpoa client statistics EXEC command as follows:
ATM# show mpoa client statisticsMPC Name:mpclient, Interface:ATM1, State:UpMPC actual operating address:47.00918100000000D058EFB301.005080562665.00Shortcut-Setup Count:10, Shortcut-Setup Time:1Transmitted ReceivedMPOA Resolution Requests 0 0MPOA Resolution Replies 0 0MPOA Cache Imposition Requests 0 0MPOA Cache Imposition Replies 0 0MPOA Cache Purge Requests 0 0MPOA Cache Purge Replies 0 0MPOA Trigger Request 0 0NHRP Purge Requests 0 0Invalid MPOA Data Packets Received:0ATM#Configuration Example for MPC
This section contains an example of the commands needed to configure an MPC. shows an example of how you can configure your system to use MPOA.
Figure 3-1 MPOA Configuration Example
The following procedure shows how to configure the MPC and attach the MPC to a hardware interface (as shown in the above example).
Step 1
ATM> enableATM# configure terminalATM(config)# mpoa client config name mympcATM(mpoa-client-config)#Step 2
ATM(mpoa-client-config)# exitStep 3
ATM(config)# interface atm 1Step 4
ATM(config-if)# mpoa client name mympcStep 5
ATM(config-if)# interface atm 1.1Step 6
ATM(config-subif)# lane client mpoa client name mympcStep 7
ATM(config-subif)# exitATM#For a detailed configuration example, refer to the "" appendix.
How an MPS Works
The following sections describe the functions of an MPS:
•
•
MPS-NHRP-Routing Interaction
An MPS has to interact with the NHRP module in the router to smoothly propagate MPOA/NHRP packets end to end. MPOA frames are identical to NHRP frames except for some specific op-codes and extensions for MPOA.
The following process explains the interaction of MPS and NHRP:
1
2
3
Shortcut Domains
Within a router, it is possible to permit shortcuts within one group of LECs and deny it within some groups of LECs. By default, all the MPSs in a router get a network ID of 1.
To segregate traffic, assign MPSs different network IDs, which prevents shortcuts between LECs served by different MPSs. Network IDs can be configured in the definition of an MPS database.
If a router has both MPS and NHRP configured, then the same network ID is required to facilitate requests, replies, and shortcuts across the MPS and NHRP. The interface-specific NHRP command (ip nhrp network-id) must be the same for an MPS; otherwise, there will be a disjointed network.
Configuring the MPS
This section describes the required and optional tasks for configuring the MPS. For a complete description of the MPS commands used in this chapter, refer to the "MPOA Commands" chapter in the Cisco IOS Switching Services Command Reference. For documentation of other commands that appear in this chapter, you can use the command reference master index or search online.
The MPS supplies the forwarding information used by the MPCs. The MPS responds with the information after receiving a query from a client. To support the query and response functions, MPOA has adopted the Next Hop Resolution Protocol (NHRP). The MPS on the router can also terminate shortcuts.
To configure an MPS on your network, perform the following tasks. Only the first two tasks are required. Each task is described in the following subsections:
•
•
•
•
Configuring the ELAN ID
For MPOA to work properly, a LEC must have an ELAN ID for all ELANs represented by the LECs. To configure an ELAN ID, use either of the following commands in lane database configuration mode or in interface configuration mode when starting up the LES for that ELAN:
CautionIf an ELAN ID is supplied by both commands, make sure both commands use the same id value.
Defining and Binding the MPS
To define and bind an MPS, use the following commands. The MPS starts functioning only after it is attached to a specific hardware interface:
Configuring the MPS Variables
An MPS has to be defined with a specified name before you can change its variables.
To change MPS variables specific to one MPS, use the following commands starting in MPOA configuration mode:
Monitoring and Maintaining the MPS
To monitor and maintain the configuration of an MPS, use the following commands in EXEC mode:
Verifying MPS Status
You can verify the MPS status by using the show mpoa server command.
Using the show mpoa server Command
Use the show mpoa server command to verify that the MPS is operational and to show the ATM NSAP addresses of the MPS configuration.
To verify MPS status from the CLI, enter the show mpoa server EXEC command:
router> show mpoa serverMPS Name: lsil-mps, MPS id: 0, Interface: ATM1/0, State: upnetwork-id: 1, Keepalive: 10 secs, Holding time: 1200 secsKeepalive lifetime: 35 secs, Giveup time: 40 secsMPS actual operating address: 47.009181000000001007394B01.00E08F6E6024.00Lane clients bound to MPS lsil-mps: ATM1/0.1 ATM1/0.2Discovered neighbours:MPC 47.009181000000001007394B01.00503EEBC86E.00 vcds: 452(L,A)MPC 47.009181000000001007394B01.0050D1D98725.00 vcds: 427(R,A)router>Verifying MPOA Server Statistics
The statistics verify that the ATM module is transmitting and receiving data across the ATM network. For example, the display shows the number of ATM Adaptation Layer 5 (AAL5) frames and ATM cells transmitted and received. You can verify ATM statistics by using the show mpoa server statistics command.
Using the show mpoa server statistics Command
Use the show mpoa server statistics command to verify that the MPS is connected to the network.
To verify ATM statistics from the CLI, enter the show mpoa server statistics EXEC command as follows:
Router> show mpoa server statisticsMPS Name: lsil-mps, MPS id: 0, Interface: ATM1/0, State: upnetwork-id: 1, Keepalive: 10 secs, Holding time: 1200 secsKeepalive lifetime: 35 secs, Giveup time: 40 secsMPS actual operating address: 47.009181000000001007394B01.00E08F6E6024.00Opcode Transmitted Received---------------------------------------------------------MPOA Resolution Requests 4585MPOA Resolution Replies 4585MPOA Cache Imposition Requests 4068MPOA Cache Imposition Replies 4068MPOA Egress Cache Purge Requests 6MPOA Egress Cache Purge Replies 0NHRP Resolution Requests 0 0NHRP Resolution Replies 0 4548NHRP Purge Requests 66 0Router>Configuration Example for MPS
This section contains an example of the commands needed to configure an MPS. shows an example of how you can configure your system to use MPOA.
Figure 3-2 MPOA Configuration Example
The following procedure shows how to configure the MPS and attach the MPS to a hardware interface (as shown in the above example):
Step 1
Router> enableRouter# configure terminalRouter(config)# mpoa server configure name mympsRouter(mpoa-server-config)#Step 2
Router(mpoa-server-config)# exitStep 3
Router> enableRouter# configure terminalRouter(config)# interface atm 1/0Router(config-if)#Step 4
Router> enableRouter# configure terminalRouter(config)# interface atm 1/0Router(config-if)# mpoa server name mympsRouter(config-if)#Step 5
Router(config)# exitRouter#Step 6
Router> enableRouter# configure terminalRouter(config)# interface atm1/0.1Router(config-if)# lane client mpoa server name mympsRouter(config-if)# ^ZRouter#The following example shows a typical MPS configuration file:
Note
version 11.3hostname MPS! Define the MPS "mps"mpoa server config name mps! Specify the ATM interface to which the MPS is attachedinterface ATM4/0no ip addressatm pvc 1 0 5 qsaalatm pvc 2 0 16 ilmilane config auto-config-atm-addressmpoa server name mps! Specify the ATM interface that contains the LEC to which you will bind the MPSinterface ATM4/0.1 multipointip address 1.1.1.2 255.255.255.0lane client mpoa server name mpslane client ethernet elan1interface ATM4/0.2 multipointip address 1.1.2.1 255.255.255.0lane client mpoa server name mpslane client ethernet elan2endFor a detailed configuration example, refer to the "" appendix.
