Configuring the Multiprotocol over ATM Client

The MPC software module implements the functionality of the MPC in compliance with the ATM Forum MPOA specification. 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 Catalyst 5000 series switch can be designated as an MPC. If the Catalyst 5000 series switch is configured with an RSM/VIP2 (with an ATM interface) it can be configured as an MPC or an MPS.

A router is usually designated as an MPOA server (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. For this reason, MPC information in this chapter primarily refers to the Catalyst 5000 series switch, and MPS information refers to the router or the RSM/VIP2 with an ATM interface in a Catalyst 5000 series switch.

For MPOA to work properly, an LEC must belong to an ELAN that has a defined ELAN ID.

Caution

If an ELAN ID is supplied, make sure both commands use the same elan-id value.

To obtain an ELAN ID, use either of the following commands in LANE database configuration mode.

Note	To configure an MPC on a Catalyst 5000 series ATM module, establish a connection with the ATM module, enter privileged mode, and then enter configuration mode. For information on performing these tasks, refer to the Catalyst 5000 Series Software Configuration Guide .

Router(lane-config-dat)# name elan-name
 elan-id id

Router(lane-config-dat)# lane server-bus ethernet elan-name
 [elan-id id
]

1.    Router(config)# mpoa client config namempc-name

2.    Router(config-if)# interface atm {mod-num/port-num | number }

3.    Router(config-if)# mpoa client namempc-name

4.    Router(config-if)# interfaceatm-num.sub-interface-num

5.    Router(config-if)# lane client mpoa client namempc-name

6.    Repeat Steps 4 and 5 for every LEC to be served by the MPC/MPS.

1.    Router(mpoa-client-config)# mpoa client config namemps-name

2.    Router(mpoa-client-config)# atm-addressatm-address

3.    Router(mpoa-client-config)# shortcut-frame-countcount

4.    Router(mpoa-client-config)# shortcut-frame-timetime

1.    Router# show mpoa client [namempc-name ]

2.    Router# show mpoa client [namempc-name ] cache [ingress | egress] [ip-addrip-addr ]

3.    Router# show mpoa client [namempc-name ] statistics

4.    Router# clear mpoa client [namempc-name ] cache [ingress | egress] [ip-addrip-addr ]

5.    Router# show mpoa client [namempc-name ] [remote-device ]

6.    Router# show mpoa default-atm-addresses

This section contains an example of the commands needed to configure an MPC. The lines beginning with exclamation points (!) are comments explaining the command shown on the subsequent line. The figure below shows an example of how you can configure your system to use MPOA.

Figure 1

Example of an MPOA Configuration

The following example shows how to configure the MPC and attach the MPC to a hardware interface:

! Define the MPC "MYMPC"
 mpoa client config name MYMPC
! Leave everything as default
 exit
! Specify the ATM interface to which the MPC is attached
 interface ATM 1/0
! Attach MPC MYMPC to the HW interface
 mpoa client name MYMPC
! Specify the ATM interface that contains the LEC to which you will bind the MPC
 interface atm 1/0.1
! Bind a LANE client to the specified MPC
 lane client mpoa client name MYMPC
! Go back up to global config mode
 exit

The following example shows a typical configuration file for the first MPC:

Current configuration:
!
version 11.3
! Go to LANE database config mode
 exit
lane database mpoa-test
hostname mpc-1
! Define the ELAN ID and ATM address
name elan1 server-atm-address 47.00918100000000613E5A2F01.006070174821.01
name elan1 elan-id 101
name elan2 server-atm-address 47.00918100000000613E5A2F01.006070174821.02
name elan2 elan-id 102
! Define the MPC "mpc-1"
mpoa client config name mpc-1
interface Ethernet0
! Go back up to global config mode
 exit
! Specify the ATM interface to which the MPC is attached
interface ATM0
atm pvc 1 0 5 qsaal
atm pvc 2 0 16 ilmi
lane config auto-config-atm-address 
lane config database mpoa-test
! Attach MPC mpc-1 to the HW interface
mpoa client name mpc-1
! Specify the ATM interface that contains the LEC to which you will bind the MPC
interface ATM0.1 multipoint
lane server-bus ethernet elan1
! Bind a LANE client to the specified MPC
lane client mpoa client name mpc-1
lane client ethernet 1 elan1
! Go back up to global config mode
 exit

The following example shows a typical configuration file for the second MPC:

Current configuration:
!
version 11.3
hostname mpc-2
! Go back up to global config mode
 exit
! Define the MPC "mpc-2"
mpoa client config name mpc-2
! Specify the ATM interface to which the MPC is attached
interface ATM0
atm pvc 1 0 5 qsaal
atm pvc 2 0 16 ilmi
mpoa client name mpc-2
! Specify the ATM interface that contains the LEC to which you will bind the MPC
interface ATM0.1 multipoint
lane server-bus ethernet elan2
lane client mpoa client name mpc-2
lane client ethernet 2 elan2
! Go back up to global config mode
 exit