|
|
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 "Command Reference" appendix.
switch# session 1 ATM>Entering Console for module in slot 1 Type "^G" to end this session Press 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.
Before you configure the LEC, ensure that the LES is configured. Refer to the "LANE Configuration Requirements" section in the "Installing an ATM Module" chapter.
Configuring the LEC specifies the ELAN in the ATM network to which your LAN is connected.
Table 3-1 lists the Cisco IOS commands used to configure (and verify) the LEC.
| Command | Value | Description |
|---|---|---|
| Enters EXEC mode. | |
| Enters global configuration mode. | |
type number.subif multipoint | Enters interface configuration mode. | |
vlan_number elan_name | Configures LEC. | |
| Provides an immediate backup for a LANE server and BUS. You must use the lane config fssrp command on all LECSs in the system to enable FSSRP operation. | |
| Verifies that the ATM is connected to the network. Displays the operational state of the ATM interface and the rate at which packets are transferred. | |
| Verifies that the LEC is operational. Also shows the ATM network service access point (NSAP) address of the LANE configuration. | |
| Saves the configuration to nonvolatile random-access memory (NVRAM). |
In the configuration procedure example that follows, the following information applies:
To configure the LEC from the CLI, follow these steps:
Step 1 Enter privileged EXEC mode by entering the enable command:
ATM> enable ATM#
Step 2 Enter global configuration mode by entering the configure terminal command:
ATM# configure terminal Enter configuration commands, one per line. End with CNTL/Z. ATM(config)#
Step 3 Enter interface configuration mode by entering the interface type_number.subif multipoint command:
ATM(config)# interface atm1.1 multipoint ATM(config-if)#
Step 4 Configure the LEC by entering the lane client ethernet vlan_number elan_name command:
ATM(config-if)# lane client ethernet 1 marketing ATM(config-if)#
Step 5 Exit interface configuration mode and return to EXEC mode by pressing Ctrl-Z:
ATM(config-if)# ^Z ATM#
Step 6 (Optional) From EXEC mode, save the configuration to nonvolatile random-access memory (NVRAM) by entering the write memory command:
ATM# write memory ATM#
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.
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.
You can verify the ATM and LANE status by 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 lane
LE Client ATM1.1 ELAN name: marketing Admin: up State: operational
Client ID: 2 LEC up for 6 minutes 14 seconds
ELAN ID: 2
Join Attempt: 2
HW Address: 00c0.1dfc.a2fc Type: ethernet Max Frame Size: 1516
VLANID: 1
ATM Address: 39.000000000000000000000000.00C01DFCA2FC.00
VCD rxFrames txFrames Type ATM Address
0 0 0 configure 39.000000000000000000000000.00605C28DA23.00
4 0 2 direct 39.000000000000000000000000.00605C28DA21.01
5 0 0 distribute 39.000000000000000000000000.00605C28DA21.01
6 0 20 send 39.000000000000000000000000.00605C28DA22.01
13 0 0 forward 39.000000000000000000000000.00605C28DA22.01
8 58 55 data 39.000000000000000000000000.00605C28DA20.01
ATM>
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.
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 interface
ATM1 is up, line protocol is up
Hardware is Catalyst 2900 ATM
Internet address is 199.90.198.195
MTU 1500 bytes, sub MTU 1500, BW 156250 Kbit, DLY 100 usec, rely 255/255, load
1/255
Encapsulation ATM, loopback not set, keepalive set (10 sec)
Encapsulation(s): AAL5, PVC mode
1024 maximum active VCs, 1024 VCs per VP, 22 current VCCs
VC idle disconnect time: 300 seconds
Signalling vc = 1, vpi = 0, vci = 5
UNI Version = 3.1, Link Side = user
Last input 00:00:07, output never, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 3000 bits/sec, 3 packets/sec
5 minute output rate 2000 bits/sec, 3 packets/sec
82111 packets input, 10186865 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
82152 packets output, 10176265 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 output buffer failures, 0 output buffers swapped out
ATM1.1 is up, line protocol is up
Hardware is Catalyst 2900 ATM
MTU 1500 bytes, BW 156250 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation ATM-LANE
ARP type: ARPA, ARP Timeout 04:00:00
ATM#
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.
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.
The following example shows how to manually configure the ATM module to support
an RFC-1483 PVC:
Step 1 Enter the privileged EXEC mode by entering the enable command:
atm> enable
atm#
Step 2 Enter global configuration mode by entering the configure terminal command:
atm# configure terminal
atm(config)#
Step 3 Enter interface configuration mode by entering the int atm1 command:
atm(config)# int atm1
Step 4 Create PVCs for RFC 1483 by entering the atm pvc command:
atm(config-if)# atm pvc 100 0 100 aal5snap 20000 20000 32 atm(config-if)# atm pvc 101 0 101 aal5snap atm(config-if)# atm pvc 200 0 200 aal5snap
Step 5 Enter subinterface configuration mode by entering the int atm1.1 multipoint command:
atm(config-if)# int atm1.1 multipoint
atm(config-subif)#
Step 6 Bind the VLAN to PVCs by entering the atm bind command:
atm(config-subif)# atm bind pvc vlan 100 1
atm(config-subif)# atm bind pvc vlan 101 1
Step 7 Change subinterface from atm1.1 to atm1.2 by entering the int atm1.2 multipoint command:
atm(config-subif)# int atm 1.2 multipoint
Step 8 Bind the VLAN to PVCs by entering the atm bind command:
atm(config-subif)# atm bind pvc vlan 200 2
Step 9 Exit the configuration mode by pressing Ctrl-Z:
ATM(config-if)# ^Z ATM#
For a detailed configuration example, refer to the "Configuration Examples" appendix.
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.
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:
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:
| Command | Purpose |
name elan-name elan-id id | Define an ELAN ID for the LEC |
lane server-bus ethernet elan-name [elan-id id] | Configure the LEC with the ELAN ID |
 | Caution If an ELAN ID is supplied, make sure both commands use the same id value. |
To define and bind an MPC on your network, use the following commands in the appropriate configuration modes:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| mpoa client config name mpc-name | Define an MPC with a specified name. | ||
| interface atm {number} | Specify the ATM interface with which the MPC is to be associated. | ||
| mpoa client name mpc-name | Attach an MPC to the ATM interface. | ||
| interface atm atm-num.sub-interface-num mul | Specify the ATM interface that contains the LEC to which you will bind the MPC. | ||
| lane client mpoa client name mpc-name | Bind a LANE client to the specified MPC. | ||
| Repeat Steps 4 and 5 for every LEC to be served by the MPC or MPS. |
|
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:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| mpoa client config name mpc-name | Specify an MPC name. | ||
| atm-address atm-address | (Optional) Specify the control ATM address that the MPC should use when it is associated with a hardware interface. | ||
| shortcut-frame-count count | (Optional) Specify the maximum number of times a packet can be routed to the default router within shortcut-frame time before a shortcut VC is set up. | ||
| shortcut-frame-time time | (Optional) Set the shortcut-setup frame time for the MPC. |
To monitor and maintain the configuration of an MPC, use any of these commands in EXEC mode:
| Command | Purpose |
|---|---|
show controllers [icache | ecache [ip-addr ip-addr] | imac [mp-sid mpsid] | mpc-stats] | Debug and display local statistics. |
show mpoa client [name mpc-name] | Display information about a specified MPC or all MPCs. |
show mpoa client [name mpc-name] cache [ingress | egress] [ip-addr ip-addr] | Display ingress and egress cache entries associated with an MPC. |
show mpoa client [name mpc-name] statistics | Display all the statistics collected by an MPC. |
clear mpoa client [name mpc-name] cache [ingress | egress] [ip-addr ip-addr] | Clear cache entries. |
show mpoa client [name mpc-name] remote-device | Display all the MPOA devices that this MPC has learned. |
show mpoa default-atm-address | Display the default ATM addresses for the MPC. |
You can verify the ATM and MPC status by 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 client MPC Name:mpclient, Interface:ATM1, State:Up MPC actual operating address:47.00918100000000D058EFB301.005080562665.00 Shortcut-Setup Count:10, Shortcut-Setup Time:1 Lane clients bound to MPC mpclient:ATM1.1 Discovered MPS neighbours kp-alv vcd rxPkts txPkts 47.00918100000000D058EFB301.00502AA54404.00 27 10 26 0 ATM>
Other show mpoa client options include the following:
ATM# show mpoa client remote-device
MPC Name:mpclient, Interface:ATM1, State:Up
MPC actual operating address:47.00918100000000D058EFB301.005080562665.00
Shortcut-Setup Count:10, Shortcut-Setup Time:1
Remote devices:
MPS (id 1) 47.00918100000000D058EFB301.00502AA54404.00
mac addr 0050.2aa5.4400 learned from LEC on ATM1.1
ATM#
ATM# show mpoa client cache
MPC Name:mpclient, Interface:ATM1, State:Up
MPC actual operating address:47.00918100000000D058EFB301.005080562665.00
Shortcut-Setup Count:10, Shortcut-Setup Time:1
Number of Egress cache entries:0
MPC Ingress Cache Information:
Dst IP addr State Egress MPC Atm address
Number of Egress cache entries:0
MPC Egress Cache Information:
Dst IP addr Dst MAC Src MAC MPSid Elan Expires CacheId Tag
0ATM#
ATM# show mpoa default-atm-addresses
interface ATM1:
MPOA Server:47.00918100000000D058EFB301.005080562664.**
MPOA Client:47.00918100000000D058EFB301.005080562665.**
note:** is the MPS/MPC instance number in hex
ATM#
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 statistics
MPC Name:mpclient, Interface:ATM1, State:Up
MPC actual operating address:47.00918100000000D058EFB301.005080562665.00
Shortcut-Setup Count:10, Shortcut-Setup Time:1
Transmitted Received
MPOA Resolution Requests 0 0
MPOA Resolution Replies 0 0
MPOA Cache Imposition Requests 0 0
MPOA Cache Imposition Replies 0 0
MPOA Cache Purge Requests 0 0
MPOA Cache Purge Replies 0 0
MPOA Trigger Request 0 0
NHRP Purge Requests 0 0
Invalid MPOA Data Packets Received:0
ATM#
This section contains an example of the commands needed to configure an MPC. Figure 3-1 shows an example of how you can configure your system to use MPOA.
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 Define the MPC by using the mpoa client config name command:
ATM> enable ATM# configure terminal ATM(config)# mpoa client config name mympc ATM(mpoa-client-config)#
Step 2 Leave everything as default:
ATM(mpoa-client-config)# exit
Step 3 Specify the ATM interface to which the MPC is attached by using the interface atm command:
ATM(config)# interface atm 1
Step 4 Attach the MPC to the hardware interface by using the mpoa client name command:
ATM(config-if)# mpoa client name mympc
Step 5 Specify the ATM interface that contains the LEC to which you will bind the MPC by using the interface atm command:
ATM(config-if)# interface atm 1.1
Step 6 Bind a LANE client to the specified MPC by using the lane client mpoa client name command:
ATM(config-subif)# lane client mpoa client name mympc
Step 7 Go back to global configuration mode by using the exit command:
ATM(config-subif)# exit ATM#
For a detailed configuration example, refer to the "Configuration Examples" appendix.
The following sections describe the functions of an MPS:
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. The MPS converts MPOA resolution requests to NHRP requests and sends them either to the next hop MPS or to the Next Hop Server (NHS) depending on the configuration. The MPS searches for the next hop routing information to determine the interface and sends the packet with correct encapsulation to an MPS or an NHS.
2. The NHS sends resolution requests to MPS when the next hop is on a LANE cloud or when the NHS is unsure of the packet destination. The MPS may do further processing; for example, it may prompt the NHS to terminate the request or throw away the packet.
3. The NHS sends resolution replies to the MPS when the next hop interface is LANE or when the replies terminate in the router. Then the MPS sends an MPOA resolution reply to the MPC.
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.
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:
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:
| Command | Purpose |
|---|---|
name elan-name elan-id id | Configure the ELAN ID in the LECS database to participate in MPOA. |
lane server-bus {ethernet | tokenring}elan-name [elan-id id] | Configure the LES with the ELAN ID to participate in MPOA. |
 | Caution If an ELAN ID is supplied by both commands, make sure both commands use the same id value. |
To define and bind an MPS, use the following commands. The MPS starts functioning only after it is attached to a specific hardware interface:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| mpoa server config name mps-name | In global configuration mode, define an MPS with the specified name. | ||
| interface atm {slot/port | number} | Specify the ATM interface to attach the MPS. | ||
| mpoa server name mps-name | In interface configuration mode, attach the MPS to the ATM interface. | ||
| interface atm {slot/port.subinterface-number | number.subinterface-number} | Specify the ATM interface to bind the MPS to a LEC. | ||
| lane client mpoa server name mps-name | In subinterface configuration mode, bind a LEC to the specified MPS. |
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:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| mpoa server config name mps-name | Specify an MPS name. | ||
| atm-address atm-address | (Optional) Specify the control ATM address that the MPS should use when it is associated with a hardware interface. | ||
| network-id id | (Optional) Specify the network ID of the MPS. | ||
| keepalive-time time | (Optional) Specify the keepalive time value for the MPS. | ||
| holding-time time | (Optional) Specify the holding time value for the MPS. |
To monitor and maintain the configuration of an MPS, use the following commands in EXEC mode:
| Command | Purpose |
|---|---|
show mpoa default-atm-addresses | Display default ATM addresses for an MPS. |
show mpoa server [name mps-name] | Display information about a specified server or all servers depending on whether you use the name keyword and specify a server name. |
show mpoa server [name mps-name] cache [ingress | egress] [ip-address ip-address] | Display ingress and egress cache entries associated with a server. |
show mpoa server [name mps-name] statistics | Display all the statistics collected by a server including the ingress and egress cache entry creations, deletions, and failures. |
clear mpoa server [name mps-name] cache [ingress | egress] [ip-addr ip-addr] | Clear cache entries. |
mpoa server name mps-name trigger ip-address ip-address [mpc-address mpc-address] | Originate an MPOA trigger for the specified IP address to the specified client. If a client is not specified, the MPOA is triggered to all the clients. |
You can verify the MPS status by 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 server MPS Name: lsil-mps, MPS id: 0, Interface: ATM1/0, State: up network-id: 1, Keepalive: 10 secs, Holding time: 1200 secs Keepalive lifetime: 35 secs, Giveup time: 40 secs MPS actual operating address: 47.009181000000001007394B01.00E08F6E6024.00 Lane clients bound to MPS lsil-mps: ATM1/0.1 ATM1/0.2 Discovered neighbours: MPC 47.009181000000001007394B01.00503EEBC86E.00 vcds: 452(L,A) MPC 47.009181000000001007394B01.0050D1D98725.00 vcds: 427(R,A) router>
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.
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 statistics MPS Name: lsil-mps, MPS id: 0, Interface: ATM1/0, State: up network-id: 1, Keepalive: 10 secs, Holding time: 1200 secs Keepalive lifetime: 35 secs, Giveup time: 40 secs MPS actual operating address: 47.009181000000001007394B01.00E08F6E6024.00 Opcode Transmitted Received --------------------------------------------------------- MPOA Resolution Requests 4585 MPOA Resolution Replies 4585 MPOA Cache Imposition Requests 4068 MPOA Cache Imposition Replies 4068 MPOA Egress Cache Purge Requests 6 MPOA Egress Cache Purge Replies 0 NHRP Resolution Requests 0 0 NHRP Resolution Replies 0 4548 NHRP Purge Requests 66 0 Router>
This section contains an example of the commands needed to configure an MPS. Figure 3-2 shows an example of how you can configure your system to use MPOA.
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 Define the MPS by using the mpoa server configure name command:
Router> enable Router# configure terminal Router(config)# mpoa server configure name mymps Router(mpoa-server-config)#
Step 2 Leave everything as default by using the exit command:
Router(mpoa-server-config)# exit
Step 3 Enter into interface configuration mode by using the interface atm command:
Router> enable Router# configure terminal Router(config)# interface atm 1/0 Router(config-if)#
Step 4 Attach the MPS to the hardware interface by using the mpoa server name command:
Router> enable Router# configure terminal Router(config)# interface atm 1/0 Router(config-if)# mpoa server name mymps Router(config-if)#
Step 5 Go back to global configuration mode by using the exit command:
Router(config)# exit Router#
Step 6 Bind a LANE client to the specified MPS by entering the lane client mpoa server name command at the management console:
Router> enable Router# configure terminal Router(config)# interface atm1/0.1 Router(config-if)# lane client mpoa server name mymps Router(config-if)# ^Z Router#
The following example shows a typical MPS configuration file:
version 11.3
hostname MPS
! Define the MPS "mps"
mpoa server config name mps
! Specify the ATM interface to which the MPS is attached
interface ATM4/0
no ip address
atm pvc 1 0 5 qsaal
atm pvc 2 0 16 ilmi
lane config auto-config-atm-address
mpoa server name mps
! Specify the ATM interface that contains the LEC to which you will bind the MPS
interface ATM4/0.1 multipoint
ip address 1.1.1.2 255.255.255.0
lane client mpoa server name mps
lane client ethernet elan1
interface ATM4/0.2 multipoint
ip address 1.1.2.1 255.255.255.0
lane client mpoa server name mps
lane client ethernet elan2
end
For a detailed configuration example, refer to the "Configuration Examples" appendix.
Posted: Mon Mar 20 11:11:45 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.