|
|
This chapter describes the required and optional tasks for configuring the Multiprotocol over ATM (MPOA) Server. For a complete description of the MPOA Server 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 MPOA Server supplies the forwarding information used by the MPOA Clients (MPCs). The MPOA Server (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.
The MPS software module implements the functionality of the MPS in compliance with the ATM Forum MPOA specification. The following sections describe the functions of MPS:
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. MPS converts MPOA resolution requests to NHRP requests and sends it either to the next hop MPS or to the Next Hop Server (NHS) depending on the configuration. 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. NHS sends resolution requests to MPS when the next hop is on a LAN Emulation (LANE) cloud or when NHS is unsure of the packet destination. MPS may do further processing, such as prompt NHS to terminate the request or throw away the packet.
3. NHS sends resolution replies to MPS when the next hop interface is LANE or when the replies terminate in the router. Then MPS sends an MPOA resolution reply to the MPC.
Within a router, it is possible to permit shortcuts between one group of LAN Emulation Clients (LECs) and deny it between some other groups of LECs. Cisco introduces a notion of network ID associated with an MPS. By default, all the MPSs in a router get a network ID of 1.
If the administrator wants to segregate traffic, then MPSs can be given different network IDs, in effect preventing shortcuts between LECs served by different MPSs. This 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.
To configure an MPS on your network, perform the following tasks.
For MPOA to work properly, a LANE client must have an ELAN ID for all ELANs represented by the LANE clients. 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 LAN Emulation Client Server (LES) for that ELAN:
| Command | Purpose |
|---|---|
name elan-name elan-id id | Configures the ELAN ID in the LECS database to participate in MPOA. |
lane server-bus {ethernet | tokenring} elan-name [elan-id id] | Configures the LAN Emulation Server (LES) with the ELAN ID to participate in MPOA. |
 |
CautionIf an ELAN ID is supplied by both commands, make sure that the ELAN ID matches in both. |
To configure an MPS, use the following commands. The MPS starts functioning only after it is attached to a specific hardware interface:
An MPS has to be defined with a specified name before you can change the MPS variables specific to that MPS.
To change MPS variables specific only to a particular MPS, use the following commands starting in MPS configuration mode:
To monitor and maintain the configuration of an MPS, use the following commands in EXEC mode:
| Command | Purpose |
|---|---|
show mpoa default-atm-addresses | Displays default ATM addresses for an MPS. |
show mpoa server [name mps-name] | Displays information about a specified server or all servers depending on the specified name of the required server. |
show mpoa server [name mps-name] cache | Displays ingress and egress cache entries associated with a server. |
show mpoa server [name mps-name] statistics | Displays 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] | Clears cache entries. |
mpoa server name mps-name trigger ip-address ip-address [mpc-address mpc-address] | Originates 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. |
This section contains an example of the commands needed to configure an MPS. The lines beginning with exclamation points (!) are comments explaining the command shown on the following line. Figure 59 shows an example of how you can configure your system to utilize MPOA.
The following example configures the MPS and attaches the MPS to a hardware interface:
! Define the MPS "MYMPS" mpoa server config name MYMPS ! Leave everything as default exit ! Enter into interface config mode interface ATM 1/0 ! Attach MPS MYMPS to the HW interface mpoa server name MYMPS ! Go back up to global config mode exit
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/0no 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 multipointip address 1.1.1.2 255.255.255.0 lane client mpoa server name mps lane client ethernet elan1
interface ATM4/0.2 multipointip address 1.1.2.1 255.255.255.0 lane client mpoa server name mps lane client ethernet elan2
end
Posted: Mon Jul 17 16:56:02 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.