MPOA for Token Ring Networks [Cisco IOS Software Releases 12.0 T]

Table Of Contents

MPOA for Token Ring Networks

Feature Summary

Benefits

List of Terms

Restrictions

Platforms

Supported MIBs and RFCs

Functional Description

Configuration Tasks

Configuring an MPOA Server

Configure the MPS

Configure the MPS Variables

Monitor and Maintain the MPS

Configuring an MPOA Client

Configure the MPC

Configure the MPC Variables

Monitor and Maintain the MPC

Configuring Token Ring LANE

Configuring a Token Ring LEC

Configuring the LECS Database

Configuring the LES/BUS

Configuration Examples

MPOA Token Ring LANE Configuration in an IP-Routed Domain

MPOA Token Ring LANE Configuration in an IP SRB-Routed Domain

Command Reference

keepalive-lifetime

Debug Commands

debug lane client

MPOA for Token Ring Networks

Feature Summary

In an ATM network, traffic travelling between subnets is typically forwarded hop-by-hop through intermediate routers. The Multiprotocol-over-ATM (MPOA) for Token Ring Networks feature allows Token Ring hosts on an ATM network to communicate over direct paths (called shortcuts) through the ATM network. These shortcuts bypass the intermediate router hops that otherwise would be encountered in the default path.

Token Ring MPOA is an extension to LAN Emulation (LANE). It allows Token Ring LANE clients to forward IP packets between subnets to other Token Ring LANE clients through a shortcut in the ATM network. The Token Ring LANE clients have an MPOA client (MPC) communicating with an MPOA server (MPS) to establish this shortcut.

Benefits

Token Ring MPOA provides the following benefits:

•Eliminates multiple router hops between the source and destination points of the ATM cloud by establishing shortcuts for IP unicast packets.

•Frees the router for other tasks by reducing IP traffic.

•Provides backward compatibility as an ATM network by building upon LANE and is implemented using both MPOA and LANE-only devices.

These attributes of MPOA provide the overall benefit of increased performance and reduced latencies on a campus Token Ring LANE network.

List of Terms

Default path—The hop-by-hop path between routers that a packet would take in the absence of shortcuts established by MPOA.

Egress—The point where an outbound flow exits the MPOA system.

Ingress—The point where an inbound flow enters the MPOA system.

MPC—MPOA client. The protocol entity in an MPOA network that implements the client side of the MPOA protocol.

MPOA cache-imposition request—A request from an egress MPS to an egress MPC providing the MAC rewrite information for a destination protocol address.

MPOA cache-imposition reply—A reply from an egress MPC acknowledging an MPOA cache-imposition request.

MPOA resolution request—A request from an MPC to resolve a destination protocol address to an ATM address for establishing a shortcut virtual channel connection (VCC) to the egress device.

MPOA resolution reply—A reply from the ingress MPS that resolves a protocol address to an ATM address.

MPS—MPOA server. The protocol entity in an MPOA network that resides on a router and implements the server side of the MPOA protocol.

NHRP resolution request—An MPOA resolution request that has been converted to a request by the Next Hop Resolution Protocol (NHRP).

NHRP resolution reply—A NHRP resolution reply that is converted to an MPOA resolution reply.

Shortcut VCC—An ATM VCC between MPCs over which Layer 3 packets are sent in lieu of the default routed path.

Restrictions

The MPOA for Token Ring Networks feature has the following restrictions:

•The current feature does not provide support for an MPC or MPS on the Cisco Catalyst 5000 ATM line cards.

•Only IP unicast packets are supported. IP packets are supported with or without a RIF for an MPS on a Cisco router. MPC shortcuts are supported only for IP unicast packets without a RIF.

•Shortcut paths can only be made between Token Ring emulated LANs (ELANs) and not in a mixed environment between an Ethernet ELAN and Token Ring ELAN.

Platforms

This feature is supported on the following platforms:

•Cisco 7500 series with an ATM Interface Processor (AIP)

•Cisco 7500 series with second-generation Versatile Interface Processor (VIP2) plus ATM PA-A1 and PA-A3 port adapters

•Cisco 7200 series with PA-A1 and PA-A3 port adapters

•Cisco 4700 series with ATM NPM

•Route Switch Module (RSM) with a VIP2 in the Catalyst 5000

Supported MIBs and RFCs

No MIBs are supported by this feature.

No RFCs are supported by this feature.

The MPOA for Token Ring Networks feature supports the following ATM forum standards:

•LAN Emulation over ATM version 1.0

•LAN Emulation over ATM version 2.0

•Multi-Protocol over ATM version 1.0

•IETF NHRP Draft version 11.0

Functional Description

An MPOA network must have at least one MPS and one or more MPCs. It may or may not have one or more intermediate routers implementing NHRP servers. The MPSs and MPCs use LANE control frames to discover each other's presence in the LANE network.

shows how MPOA messages flow to establish a shortcut VCC between two MPOA clients.

Figure 1 MPC/MPS Message Flows to Establish a Shortcut VCC

In , an MPC (MPC-1) residing on an edge device detects a packet flow to a destination IP address and sends an MPOA resolution request. An MPS (MPS-1) residing on a router converts the MPOA resolution request to an NHRP resolution request and passes it to the neighboring MPS (MPS-2) on the routed path. When the NHRP resolution request reaches the egress point, the MPS (MPS-2) on that router sends an MPOA cache-imposition request to MPC-2. MPC-2 acknowledges the request with a cache-imposition reply and adds a tag that allows the originator of the MPOA resolution request to receive the ATM address of MPC-2. In this way the shortcut VCC is established between the two edge device MPCs (MPC-1 and MPC-2).

When traffic flows from Host A attached to MPC-1 to Host B attached to MPC-2, MPC-1 is the ingress MPC and MPC-2 is the egress MPC. The ingress MPC contains a cache entry for Host B with the ATM address of the egress MPC. The ingress MPC switches packets destined to Host B on the shortcut VCC with the appropriate tag received in the MPOA resolution reply.

Packets traversing the shortcut VCC do not contain Data Link Layer (DLL) headers. The egress MPC contains a cache entry that associates the IP address of host B and the ATM address of the ingress MPC to a DLL header. When the egress MPC switches an IP packet through a shortcut path to Host B, it appears to have come from the egress router.

Configuration Tasks

Configuring the Token Ring MPOA feature includes the following general steps to configure the MPS and MPC components:

1 Define a name for the MPS/MPC.

2 Attach the MPS/MPC to a major interface.

Multiple MPSs/MPCs can run on the same physical interface, each corresponding to a different ATM control address. Once an MPS/MPC is attached to a single interface for its control traffic, it cannot be attached to another interface unless you break the first attachment. The MPS/MPC is attached to subinterface 0 of the interface.

Note Each MPS/MPC can be attached to a single hardware interface only; however, more than one MPS/MPC can be attached to the same interface (but with different control addresses).

3 Assign an ATM address to the MPS/MPC.

4 Bind the MPS/MPC to multiple LAN emulation clients (LECs).

Any LEC running on any subinterface of a hardware interface can be bound to any MPS/MPC. However, once a LEC is bound to a particular MPS/MPC, it cannot be bound to another MPS/MPC at the same time. You must unbind the LEC from the first MPS/MPC to bind it to another MPS/MPC. Typically you do not need to configure more than one MPS in a router.

Note Be sure that the hardware interface attached to an MPS/MPC is directly reachable through the ATM network by all the LECs that are bound to it. If any of the LECs reside on a different (unreachable) ATM network form the one to which the hardware interface is connected, then MPOA will not operate properly.

The following sections describe how to perform the configuration tasks for the MPS, MPC, and Token Ring LANE:

•Configuring an MPOA Server

•Configuring an MPOA Client

•Configuring Token Ring LANE

The MPOA server and client sections also provide information about how to monitor and maintain the MPS and MPC components.

Configuring an MPOA Server

This section describes the required and optional tasks to configure the Token Ring MPOA server. For a complete description of the commands used in this section, refer to the Cisco IOS Release 12.0 command references.

Configure the MPS

The MPS starts functioning only after it is attached to a specific hardware interface. To configure the MPS, use the following commands:

Step

Command

Purpose

1

mpoa server config name mps-name

In global configuration mode, defines an MPS with the specified name.

2

interface atm {slot/port | number}

Specifies the ATM interface to attach the MPS.

3

mpoa server name mps-name

In interface configuration mode, attaches the MPS to the ATM interface.

4

interface atm {slot/port.subinterface-number | number.subinterface-number}

Specifies the ATM interface to bind the MPS to a LEC.

5

lane client mpoa server name mps-name

In subinterface configuration mode, binds a LANE client to the specified MPS.

Configure the MPS Variables

An MPS has to be defined with a specified name before you can change its variables. To change the variables for an MPS, use the following commands while you are in MPS configuration mode:

Step

Command

Purpose

1

mpoa server config name mps-name

Defines an MPS with the specified name.

2

atm-address atm-address

(Optional) Specifies the control ATM address that the MPS should use (when it is associated with a hardware interface).

3

holding-time time

(Optional) Specifies the holding time value for the MPS-p7 variable of the MPS.

4

keepalive-lifetime time

(Optional) Specifies the keepalive lifetime value for the MPS-p2 variable of the MPS.

5

keepalive-time time

(Optional) Specifies the keepalive time value for the MPS-p1 variable of the MPS.

6

network-id id

(Optional) Specifies the network ID of the MPS.

Monitor and Maintain 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

Displays default ATM addresses for an MPS.

show mpoa server [name mps-name]

Displays information about a specified MPS or all MPSs.

show mpoa server [name mps-name] cache [ingress | egress] [ip-address ip-address]

Displays ingress and egress cache entries associated with an MPS.

show mpoa server [name mps-name] statistics

Displays all the statistics collected by an MPS 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 MPS 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.

Configuring an MPOA Client

This section describes the required and optional tasks to configure the Token Ring MPOA client. For a complete description of the commands used in this section, refer to the Cisco IOS Release 12.0 command references.

Configure the MPC

To configure an MPC on your network, use the following commands:

Step

Command

Purpose

1

mpoa client config name mpc-name

In global configuration mode, defines an MPC with a specified name.

2

interface atm {mod-num/port-num | number}

In interface configuration mode, specifies the ATM interface to which the MPC is associated.

3

mpoa client name mpc-name

In interface configuration mode, attaches an MPC to the ATM interface.

4

interface atm-num.sub-interface-num

In interface configuration mode, specifies the ATM interface that contains the LEC to which you will bind the MPC.

5

lane client mpoa client name mpc-name

In interface configuration mode, binds a LANE client to the specified MPC.

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

Configure the MPC Variables

An MPC must be defined with a specified name before you can change its variables. To change the variables for an MPC, use the following commands in MPC configuration mode:

Step

Command

Purpose

1

mpoa client config name mpc-name

Defines an MPC with the specified name.

2

atm-address atm-address

(Optional) Specifies the control ATM address that the MPC should use (when it is associated with a hardware interface).

3

shortcut-frame-count count

(Optional) Specifies the maximum number of times that a packet can be routed to the default router within shortcut-frame time before an MPOA resolution request is sent.

4

shortcut-frame-time time

(Optional) Sets the shortcut-setup frame time for the MPC.

Monitor and Maintain the MPC

To monitor and maintain the configuration of an MPC, use the following commands in EXEC mode:

Command

Purpose

show mpoa client [name mpc-name]

Displays information about a specified MPC or all MPCs.

show mpoa client [name mpc-name] cache [ingress | egress] [ip-addr ip-addr]

Displays ingress and egress cache entries associated with an MPC.

show mpoa client [name mpc-name] statistics

Displays all the statistics collected by an MPC.

clear mpoa client [name mpc-name] cache [ingress | egress] [ip-addr ip-addr]

Clears cache entries.

show mpoa client [name mpc-name] [remote-device]

Displays all of the MPOA devices that this MPC has learned.

show mpoa default-atm-addresses

Displays the default ATM addresses for the MPC.

Configuring Token Ring LANE

To configure Token Ring LANE for MPOA complete the following tasks:

•Configuring a Token Ring LEC

•Configuring the LECS Database

•Configuring the LES/BUS

Configuring a Token Ring LEC

For MPOA operation, a LEC must be associated with an MPS, an MPC, or both. Once a LEC is bound to a particular MPS/MPC, it cannot be bound to another MPS/MPC at the same time.

The LEC must also be associated with a physical interface or subinterface, which may be different from the physical interface associated with the MPS or MPC. For proper operation, all interfaces must belong to the same ATM network.

To configure a Token Ring LEC, use the following commands in global configuration mode:

Step

Command

Purpose

1

interface atm {slot/port.subinterface-number | number.subinterface-number}

Specifies the ATM interface to be associated with the LEC.

2

lane client tokenring [elan-name]

Defines a Token Ring LEC on a specified ELAN name.

3

lane client mpoa server mps-name

(Optional) Binds a Token Ring LEC to an MPS.

4

lane client mpoa client mpc-name

(Optional) Binds a Token Ring LEC to an MPC.

Configuring the LECS Database

To configure the LECS database, use the following commands in global configuration mode:

Step

Command

Purpose

1

lane database database-name

Creates a named database for the LECS.

2

name elan-name server-atm-address atm-address

Binds the name of the ELAN to the ATM address of the LES.

3

name elan-name elan-id id

Defines the ELAN ID in the LECS database to participate in MPOA.

4

name elan-name local-seg-id id

Configures the local segment ID number.

Configuring the LES/BUS

To configure the LES/BUS, use the following commands in global configuration mode:

Step

Command

Purpose

1

interface atm {slot/port.subinterface-number | number.subinterface-number}

Specifies the ATM subinterface to be associated with the LES/BUS.

2

lane server-bus tokenring elan-name [elan-id elan-id]

Defines a Token Ring LES/BUS on the named ELAN. The ELAN ID is optional.

Configuration Examples

This section provides the following sample configurations of MPOA in a Token Ring LANE environment:

•MPOA Token Ring LANE Configuration in an IP-Routed Domain

•MPOA Token Ring LANE Configuration in an IP SRB-Routed Domain

MPOA Token Ring LANE Configuration in an IP-Routed Domain

Figure 2 illustrates MPOA in a Token Ring LANE environment where MPC-to-MPC shortcuts are established between Token Ring LANE edge routers that reside in different IP-routed domains.

Figure 2 Token Ring MPOA—MPC to MPC Shortcut in an IP Routed Environment

The following commands show a sample configuration for Router-1 in :
hostname Router-1
!
ip routing
!
! Define the MPOA Client (mpc-1) configuration.
!
mpoa client config name mpc-1
!
! Configure an IP address on the Token Ring interface.
!
interface TokenRing1/0
 ip address 5.5.5.2 255.255.255.0
 ring-speed 16
!
! Configure a config-server and bind it to its database (mpoa-db).
! Attach the MPOA client mpc-1 to its ATM interface.
!
interface ATM2/0
 no ip address
 atm pvc 1 0 5 qsaal
 atm pvc 2 0 16 ilmi
 lane config auto-config-atm-address
 lane config database mpoa-db
 mpoa client name mpc-1
!
! Configure a LANE server-bus and LANE client on ELAN 1. Bind the
! LANE client to its MPOA Client (mpc-1). 
!
interface ATM2/0.1 multipoint
 ip address 1.1.1.1 255.255.255.0
 lane server-bus tokenring 1
 lane client mpoa client name mpc-1
 lane client tokenring 1
!
router eigrp 1
 network 1.0.0.0
 network 5.0.0.0
!
end
The following commands show a sample configuration for Router-2 in :
hostname Router-2
!
ip routing
!
! Configure the config-server database mpoa-db with configuration
! for ELANs 1 to 3
!
lane database mpoa-db
 name 1 server-atm-address 47.0091810000000060705BFA01.00000CA05F41.01
 name 1 local-seg-id 1000
 name 1 elan-id 100
 name 2 server-atm-address 47.0091810000000060705BFA01.00000CA05B41.01
 name 2 local-seg-id 2000
 name 2 elan-id 200
 name 3 server-atm-address 47.0091810000000060705BFA01.00000CA05B41.03
 name 3 local-seg-id 3000
 name 3 elan-id 300
!
! Define the MPOA Server (mps-1) configuration.
mpoa server config name mps-1
!
! Configure the signalling and ILMI PVCs. Also configure a config-server
! and attach the MPOA server (mps-1) to its ATM interface.
!
interface ATM4/0
 no ip address
 atm pvc 1 0 5 qsaal
 atm pvc 2 0 16 ilmi
 lane config auto-config-atm-address
 lane config database mpoa-db
 mpoa server name mps-1
!
! Configure a Token Ring LANE client on ELAN 1 and bind the LANE
! client to its MPOA server (mps-1). 
!
interface ATM4/0.1 multipoint
 ip address 1.1.1.2 255.255.255.0
 lane client mpoa server name mps-1
 lane client tokenring 1
!
! Configure a Token Ring LANE client on ELAN 2 and bind the LANE
! client to its MPOA server (mps-1)
!
interface ATM4/0.2 multipoint
 ip address 2.2.2.1 255.255.255.0
 lane client mpoa server name mps-1
 lane client tokenring 2
!
router eigrp 1
 network 1.0.0.0
 network 2.0.0.0
!
end
The following commands show a sample configuration for Router-3 in :
hostname Router-3
!
ip routing
!
! Defines the MPOA Server (mps-2) configuration.
mpoa server config name mps-2
!
! Configure the signalling and ILMI PVCs and attach the MPOA
! server (mps-2) to its ATM interface.
!
interface ATM2/0
 no ip address
 atm pvc 1 0 5 qsaal
 atm pvc 2 0 16 ilmi
 mpoa server name mps-2
!
! Configure a Token Ring LANE client and LANE server-bus on ELAN 2
! and bind the LANE client to its MPOA server (mps-2)
!
interface ATM2/0.1 multipoint
 ip address 2.2.2.2 255.255.255.0
 lane server-bus tokenring 2
 lane client mpoa server name mps-2
 lane client tokenring 2
!
! Configure a Token Ring LANE client on ELAN 3 and bind the LANE
! client to its MPOA server (mps-2)
!
interface ATM2/0.3 multipoint
 ip address 3.3.3.1 255.255.255.0
 lane server-bus tokenring 3
 lane client mpoa server name mps-2
 lane client tokenring 3
!
router eigrp 1
 network 2.0.0.0
 network 3.0.0.0
!
end
The following commands show a sample configuration for Router-4 in :
hostname Router-4
!
ip routing
!
! Define the MPOA client (mpc-2) configuration.
!
mpoa client config name mpc-2
!
! Configure the Token Ring interface
!
interface TokenRing1/0
 ip address 4.4.4.1 255.255.255.0
 ring-speed 16
!
! Configure the signalling and ILMI PVCs and attach the MPOA
! client to its ATM interface.
!
interface ATM2/0
 atm pvc 1 0 5 qsaal
 atm pvc 2 0 16 ilmi
 mpoa client name mpc-2
!
! Configure a Token Ring LANE client on ELAN 3 and bind the LANE
! client to its MPOA client (mpc-2). 
!
interface ATM2/0.1 multipoint
 ip address 3.3.3.2 255.255.255.0
 lane client mpoa client name mpc-2
 lane client tokenring 3
!
router eigrp 1
 network 3.0.0.0
 network 4.0.0.0
!
end
MPOA Token Ring LANE Configuration in an IP SRB-Routed Domain

illustrates MPOA in a Token Ring LANE environment where MPC-to-MPC shortcuts are established between a Token Ring LANE edge device and a Token Ring LANE router that reside in an IP SRB domain and IP-routed domains.

Figure 3 Token Ring MPOA—MPC to MPC Shortcut in an IP SRB-Routed Environment

Note MPC support for the Cisco Catalyst 5000 ATM modules is planned for a future release.

The following commands show a sample configuration for Router-1 in :
hostname Router-1
!
ip routing
!
! Configure the config-server database mpoa-db with configuration
! for ELANs 1 to 3
lane database mpoa-db
  name 1 server-atm-address 47.0091810000000060705BFA01.00000CA05F41.01
  name 1 local-seg-id 1000
  name 1 elan-id 100
  name 2 server-atm-address 47.0091810000000060705BFA01.00000CA05B41.01
  name 2 local-seg-id 2000
  name 2 elan-id 200
  name 3 server-atm-address 47.0091810000000060705BFA01.00000CA05B41.03
  name 3 local-seg-id 3000
  name 3 elan-id 300
!
! Define the MPOA Server (mps-1) configuration.
mpoa server config name mps-1
!
! Configure the signalling and ILMI PVCs. Also configure a config-server
! and attach the MPOA server (mps-1) to its ATM interface.
interface ATM4/0
  no ip address
  atm pvc 1 0 5 qsaal
  atm pvc 2 0 16 ilmi
  lane config auto-config-atm-address
  lane config database mpoa-db
  mpoa server name mps-1 
!
! Configure a Token Ring LANE client on ELAN 1 and bind the LANE
! client to its MPOA server (mps-1). The multiring ip configuration
! is required to terminate the RIF for IP packets on the ELAN.
interface ATM4/0.1 multipoint
  ip address 1.1.1.2 255.255.255.0
  lane client mpoa server name mps-1
  lane client tokenring 1
  multiring ip
!
! Configure a Token Ring LANE client on ELAN 2 and bind the LANE
! client to its MPOA server (mps-1)
!
 interface ATM4/0.2 multipoint
   ip address 2.2.2.1 255.255.255.0
   lane client mpoa server name mps-1
   lane client tokenring 2
!
!
 router eigrp 1
   network 1.0.0.0
   network 2.0.0.0
!
end
The following commands show a sample configuration for Router-2 in :
hostname Router-2
!
ip routing
!
! Defines the MPOA Server (mps-2) configuration.
mpoa server config name mps-2
!
!
! Configure the signalling and ILMI PVCs and attach the MPOA
! server (mps-2) to its ATM interface.
interface ATM2/0
 no ip address
 atm pvc 1 0 5 qsaal
 atm pvc 2 0 16 ilmi
 mpoa server name mps-2
!
! Configure a Token Ring LANE client and LANE server-bus on ELAN 2
! and bind the LANE client to its MPOA server (mps-2)
!
interface ATM2/0.1 multipoint
 ip address 2.2.2.2 255.255.255.0
 lane server-bus tokenring 2
 lane client mpoa server name mps-2
 lane client tokenring 2
!
! Configure a Token Ring LANE client on ELAN 3 and bind the LANE
! client to its MPOA server (mps-2)
!
interface ATM2/0.3 multipoint
 ip address 3.3.3.1 255.255.255.0
 lane server-bus tokenring 3
 lane client mpoa server name mps-2
 lane client tokenring 3
!
router eigrp 1
 network 2.0.0.0
 network 3.0.0.0
!
end
The following commands show a sample configuration for Router-3 in :
hostname Router-3
!
ip routing
!
! Define the MPOA client (mpc-2) configuration.
mpoa client config name mpc-2
!
!
! Configure the Token Ring interface
interface TokenRing1/0
 ip address 4.4.4.1 255.255.255.0
 ring-speed 16
!
! Configure the signalling and ILMI PVCs and attach the MPOA
! client to its ATM interface.
!
interface ATM2/0
 atm pvc 1 0 5 qsaal
 atm pvc 2 0 16 ilmi
 mpoa client name mpc-2
!
! Configure a Token Ring LANE client on ELAN 3 and bind the LANE
! client to its MPOA client (mpc-2).
! 
interface ATM2/0.1 multipoint
 ip address 3.3.3.2 255.255.255.0
 lane client mpoa client name mpc-2
 lane client tokenring 3
!
router eigrp 1
 network 3.0.0.0
 network 4.0.0.0
!
end
Command Reference

This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command references.

•keepalive-lifetime

keepalive-lifetime

Use the keepalive-lifetime global configuration command to specify the duration that a keepalive message from an MPS is considered valid by the MPC.

keepalive-lifetime time

Syntax Description

time

Time, in seconds, for the MPS-p2 variable of the MPS. The default value is 35 seconds.

Default

The default is 35 seconds.

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 12.0(3)T.

The keepalive-lifetime (MPS-p2) must be greater than or equal to three times the value of the keepalive-time (MPS-p1). MPS-p1 specifies the frequency that a keepalive message is sent from the MPS to the MPC.

Example

The following example specifies a keepalive lifetime of 60 seconds:
keepalive-lifetime 60
Related Commands

keepalive-time

Debug Commands

This section documents new or modified commands. All other MPS and MPC debug commands are supported by Token Ring MPOA and are documented in the Cisco IOS Release 12.0 Debug Command Reference:

•debug lane client

•debug mpoa client

•debug mpoa server

debug lane client

Use the debug lane client EXEC command to display information about a LAN Emulation Client (LEC). The no form of this command disables debugging output.

[no] debug lane client {all | le-arp | mpoa | packet | signaling | state | topology} [interface interface]

Syntax Description

all

Displays all debug information related to the LEC.

le-arp

Displays debug information related to the LANE ARP table.

mpoa

Displays debug information to track the following:

•MPOA specific TLV information in le-arp requests/responses

•Elan-id and local segment TLV in lane control frames

•When a lane client is bound to an MPC/MPS

packet

Displays debug information about each packet.

signaling

Displays debug information related to client SVCs.

state

Displays debug information when the state changes.

topology

Displays debug information related to the topology of the emulated LAN.

interface interface

(Optional) Limits the debugging output to messages that relate to a particular interface or subinterface. If you enter this command multiple times with different interfaces, the last interface entered will be the one used to filter the messages.

Default

If the interface number is not specified, the default will be the number of all the mpoa lane clients.

Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 12.0(1)T.

The debug lane client all command can generate a large amount of output. Use a limiting keyword or specify a subinterface to decrease the amount of output and focus on the information you need.

Example

Sample Displays

Figure 2-164 shows sample output for debug lane client packet and debug lane client state commands for an LEC joining an emulated LAN (ELAN) called elan1.

Figure 2-164: Sample Debug LANE Client Output--Client Joining ELAN
Router# debug lane client packet
Router# debug lane client state
The LEC listens for signaling calls to its ATM address (Initial State).
LEC ATM2/0.1: sending LISTEN
LEC ATM2/0.1:   listen on       39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1: received LISTEN
The LEC calls the LAN Emulation Configuration Server (LECS) and attempts to set up the Configure Direct VC (LECS Connect Phase).
LEC ATM2/0.1: sending SETUP
LEC ATM2/0.1:   callid          0x6114D174
LEC ATM2/0.1:   called party    39.020304050607080910111213.00000CA05B43.00
LEC ATM2/0.1:   calling_party   39.020304050607080910111213.00000CA05B40.01
The LEC receives a CONNECT response from the LECS. The Configure Direct VC is established.
LEC ATM2/0.1: received CONNECT
LEC ATM2/0.1:   callid          0x6114D174
LEC ATM2/0.1:   vcd             148
The LEC sends a CONFIG REQUEST to the LECS on the Configure Direct VC (Configuration Phase).
LEC ATM2/0.1: sending LANE_CONFIG_REQ on VCD 148
LEC ATM2/0.1:   SRC MAC address 0000.0ca0.5b40
LEC ATM2/0.1:   SRC ATM address 39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1:   LAN Type        2
LEC ATM2/0.1:   Frame size      2
LEC ATM2/0.1:   LAN Name        elan1
LEC ATM2/0.1:   LAN Name size   5
The LEC receives a CONFIG RESPONSE from the LECS on the Configure Direct VC.
LEC ATM2/0.1: received LANE_CONFIG_RSP on VCD 148
LEC ATM2/0.1:   SRC MAC address 0000.0ca0.5b40
LEC ATM2/0.1:   SRC ATM address 39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1:   LAN Type        2
LEC ATM2/0.1:   Frame size      2
LEC ATM2/0.1:   LAN Name        elan1
LEC ATM2/0.1:   LAN Name size   5
The LEC releases the Configure Direct VC.
LEC ATM2/0.1: sending RELEASE
LEC ATM2/0.1:   callid          0x6114D174
LEC ATM2/0.1:   cause code      31
The LEC receives a RELEASE_COMPLETE from the LECS.
LEC ATM2/0.1: received RELEASE_COMPLETE
LEC ATM2/0.1:   callid          0x6114D174
LEC ATM2/0.1:   cause code      16
The LEC calls the LAN Emulation Server (LES) and attempts to set up the Control Direct VC (Join/Registration Phase).
LEC ATM2/0.1: sending SETUP
LEC ATM2/0.1:   callid          0x61167110
LEC ATM2/0.1:   called party    39.020304050607080910111213.00000CA05B41.01
LEC ATM2/0.1:   calling_party   39.020304050607080910111213.00000CA05B40.01
The LEC receives a CONNECT response from the LES. The Control Direct VC is established.
LEC ATM2/0.1: received CONNECT
LEC ATM2/0.1:   callid          0x61167110
LEC ATM2/0.1:   vcd             150
The LEC sends a JOIN REQUEST to the LES on the Control Direct VC.
LEC ATM2/0.1: sending LANE_JOIN_REQ on VCD 150
LEC ATM2/0.1:   Status          0
LEC ATM2/0.1:   LECID           0
LEC ATM2/0.1:   SRC MAC address 0000.0ca0.5b40
LEC ATM2/0.1:   SRC ATM address 39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1:   LAN Type        2
LEC ATM2/0.1:   Frame size      2
LEC ATM2/0.1:   LAN Name        elan1
LEC ATM2/0.1:   LAN Name size   5
The LEC receives a SETUP request from the LES to set up the Control Distribute VC.
LEC ATM2/0.1: received SETUP
LEC ATM2/0.1:   callid          0x6114D174
LEC ATM2/0.1:   called party    39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1:   calling_party   39.020304050607080910111213.00000CA05B41.01
The LEC responds to the LES call setup with a CONNECT.
LEC ATM2/0.1: sending CONNECT
LEC ATM2/0.1:   callid          0x6114D174
LEC ATM2/0.1:   vcd             151
A CONNECT_ACK is received from the ATM switch. The Control Distribute VC is established.
LEC ATM2/0.1: received CONNECT_ACK
The LEC receives a JOIN response from the LES on the Control Direct VC.
LEC ATM2/0.1: received LANE_JOIN_RSP on VCD 150
LEC ATM2/0.1:   Status          0
LEC ATM2/0.1:   LECID           1
LEC ATM2/0.1:   SRC MAC address 0000.0ca0.5b40
LEC ATM2/0.1:   SRC ATM address 39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1:   LAN Type        2
LEC ATM2/0.1:   Frame size      2
LEC ATM2/0.1:   LAN Name        elan1
LEC ATM2/0.1:   LAN Name size   5
The LEC sends an LE_ARP request to the LES to obtain the broadcast-and-unknown (BUS) ATM NSAP address (BUS Connect).
LEC ATM2/0.1: sending LANE_ARP_REQ on VCD 150
LEC ATM2/0.1:   SRC MAC address     0000.0ca0.5b40
LEC ATM2/0.1:   SRC ATM address     39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1:   TARGET MAC address     ffff.ffff.ffff
LEC ATM2/0.1:   TARGET ATM address  00.000000000000000000000000.000000000000.00
The LEC receives its own LE_ARP request via the LES over the Control Distribute VC.
LEC ATM2/0.1: received LANE_ARP_RSP on VCD 151
LEC ATM2/0.1:   SRC MAC address     0000.0ca0.5b40
LEC ATM2/0.1:   SRC ATM address     39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1:   TARGET MAC address     ffff.ffff.ffff
LEC ATM2/0.1:   TARGET ATM address  39.020304050607080910111213.00000CA05B42.01
The LEC calls the BUS and attempts to set up the Multicast Send VC.
LEC ATM2/0.1: sending SETUP
LEC ATM2/0.1:   callid          0x6114D354
LEC ATM2/0.1:   called party    39.020304050607080910111213.00000CA05B42.01
LEC ATM2/0.1:   calling_party   39.020304050607080910111213.00000CA05B40.01
The LEC receives a CONNECT response from the BUS. The Multicast Send VC is established.
LEC ATM2/0.1: received CONNECT
LEC ATM2/0.1:   callid          0x6114D354
LEC ATM2/0.1:   vcd             153
The LEC receives a SETUP request from the BUS to set up the Multicast Forward VC.
LEC ATM2/0.1: received SETUP
LEC ATM2/0.1:   callid          0x610D4230
LEC ATM2/0.1:   called party    39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1:   calling_party   39.020304050607080910111213.00000CA05B42.01
The LEC responds to the BUS call setup with a CONNECT.
LEC ATM2/0.1: sending CONNECT
LEC ATM2/0.1:   callid          0x610D4230
LEC ATM2/0.1:   vcd             154
A CONNECT_ACK is received from the ATM switch. The Multicast Forward VC is established.
LEC ATM2/0.1: received CONNECT_ACK
The LEC moves into the OPERATIONAL state.
%LANE-5-UPDOWN: ATM2/0.1 elan elan1: LE Client changed state to up 
The following output is from the show lane client command after the LEC joins the emulated LAN as shown in the debug lane client output:
Router# show lane client
LE Client ATM2/0.1  ELAN name: elan1  Admin: up  State: operational
Client ID: 1                 LEC up for 1 minute 2 seconds
Join Attempt: 1
HW Address: 0000.0ca0.5b40   Type: token ring           Max Frame Size: 4544
Ring:1      Bridge:1        ELAN Segment ID: 2048
ATM Address: 39.020304050607080910111213.00000CA05B40.01
 VCD  rxFrames  txFrames  Type       ATM Address
   0         0         0  configure  39.020304050607080910111213.00000CA05B43.00
 142         1         2  direct     39.020304050607080910111213.00000CA05B41.01
 143         1         0  distribute 39.020304050607080910111213.00000CA05B41.01
 145         0         0  send       39.020304050607080910111213.00000CA05B42.01
 146         1         0  forward    39.020304050607080910111213.00000CA05B42.01
Figure 2-165 shows sample debug lane client all output when an interface with an LECS, an LES/BUS, and an LEC is shut down.
Figure 2-165: Sample Debug LANE Client Output--Interface Shutdown
Router# debug lane client all
LEC ATM1/0.2: received RELEASE_COMPLETE
LEC ATM1/0.2:   callid          0x60E8B474
LEC ATM1/0.2:   cause code      0
LEC ATM1/0.2: action A_PROCESS_REL_COMP
LEC ATM1/0.2: action A_TEARDOWN_LEC
LEC ATM1/0.2: sending RELEASE
LEC ATM1/0.2:   callid          0x60EB6160
LEC ATM1/0.2:   cause code      31
LEC ATM1/0.2: sending RELEASE
LEC ATM1/0.2:   callid          0x60EB7548
LEC ATM1/0.2:   cause code      31
LEC ATM1/0.2: sending RELEASE
LEC ATM1/0.2:   callid          0x60EB9E48
LEC ATM1/0.2:   cause code      31
LEC ATM1/0.2: sending CANCEL
LEC ATM1/0.2:   ATM address     47.00918100000000613E5A2F01.006070174820.02
LEC ATM1/0.2: state ACTIVE event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.3: received RELEASE_COMPLETE
LEC ATM1/0.3:   callid          0x60E8D108
LEC ATM1/0.3:   cause code      0
LEC ATM1/0.3: action A_PROCESS_REL_COMP
LEC ATM1/0.3: action A_TEARDOWN_LEC
LEC ATM1/0.3: sending RELEASE
LEC ATM1/0.3:   callid          0x60EB66D4
LEC ATM1/0.3:   cause code      31
LEC ATM1/0.3: sending RELEASE
LEC ATM1/0.3:   callid          0x60EB7B8C
LEC ATM1/0.3:   cause code      31
LEC ATM1/0.3: sending RELEASE
LEC ATM1/0.3:   callid          0x60EBA3BC
LEC ATM1/0.3:   cause code      31
LEC ATM1/0.3: sending CANCEL
LEC ATM1/0.3:   ATM address     47.00918100000000613E5A2F01.006070174820.03
LEC ATM1/0.3: state ACTIVE event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.2: received RELEASE_COMPLETE
LEC ATM1/0.2:   callid          0x60EB7548
LEC ATM1/0.2:   cause code      0
LEC ATM1/0.2: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.2: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.3: received RELEASE_COMPLETE
LEC ATM1/0.3:   callid          0x60EB7B8C
LEC ATM1/0.3:   cause code      0
LEC ATM1/0.3: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.3: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.1: received RELEASE_COMPLETE
LEC ATM1/0.1:   callid          0x60EBC458
LEC ATM1/0.1:   cause code      0
LEC ATM1/0.1: action A_PROCESS_REL_COMP
LEC ATM1/0.1: action A_TEARDOWN_LEC
LEC ATM1/0.1: sending RELEASE
LEC ATM1/0.1:   callid          0x60EBD30C
LEC ATM1/0.1:   cause code      31
LEC ATM1/0.1: sending RELEASE
LEC ATM1/0.1:   callid          0x60EBDD28
LEC ATM1/0.1:   cause code      31
LEC ATM1/0.1: sending RELEASE
LEC ATM1/0.1:   callid          0x60EBF174
LEC ATM1/0.1:   cause code      31
LEC ATM1/0.1: sending CANCEL
LEC ATM1/0.1:   ATM address     47.00918100000000613E5A2F01.006070174820.01
LEC ATM1/0.1: state ACTIVE event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.1: received RELEASE_COMPLETE
LEC ATM1/0.1:   callid          0x60EBDD28
LEC ATM1/0.1:   cause code      0
LEC ATM1/0.1: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.1: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.2: received RELEASE_COMPLETE
LEC ATM1/0.2:   callid          0x60EB6160
LEC ATM1/0.2:   cause code      0
LEC ATM1/0.2: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.2: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.3: received RELEASE_COMPLETE
LEC ATM1/0.3:   callid          0x60EB66D4
LEC ATM1/0.3:   cause code      0
LEC ATM1/0.3: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.3: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.2: received RELEASE_COMPLETE
LEC ATM1/0.2:   callid          0x60EB9E48
LEC ATM1/0.2:   cause code      0
LEC ATM1/0.2: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.2: state TERMINATING event LEC_SIG_RELEASE_COMP => IDLE
LEC ATM1/0.3: received RELEASE_COMPLETE
LEC ATM1/0.3:   callid          0x60EBA3BC
LEC ATM1/0.3:   cause code      0
LEC ATM1/0.3: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.3: state TERMINATING event LEC_SIG_RELEASE_COMP => IDLE
LEC ATM1/0.1: received RELEASE_COMPLETE
LEC ATM1/0.1:   callid          0x60EBD30C
LEC ATM1/0.1:   cause code      0
LEC ATM1/0.1: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.1: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.1: received RELEASE_COMPLETE
LEC ATM1/0.1:   callid          0x60EBF174
LEC ATM1/0.1:   cause code      0
LEC ATM1/0.1: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.1: state TERMINATING event LEC_SIG_RELEASE_COMP => IDLE
LEC ATM1/0.2: received CANCEL
LEC ATM1/0.2: state IDLE event LEC_SIG_CANCEL => IDLE
LEC ATM1/0.3: received CANCEL
LEC ATM1/0.3: state IDLE event LEC_SIG_CANCEL => IDLE
LEC ATM1/0.1: received CANCEL
LEC ATM1/0.1: state IDLE event LEC_SIG_CANCEL => IDLE
LEC ATM1/0.1: action A_SHUTDOWN_LEC
LEC ATM1/0.1: sending CANCEL
LEC ATM1/0.1:   ATM address     47.00918100000000613E5A2F01.006070174820.01
LEC ATM1/0.1: state IDLE event LEC_LOCAL_DEACTIVATE => IDLE
LEC ATM1/0.2: action A_SHUTDOWN_LEC
LEC ATM1/0.2: sending CANCEL
LEC ATM1/0.2:   ATM address     47.00918100000000613E5A2F01.006070174820.02
LEC ATM1/0.2: state IDLE event LEC_LOCAL_DEACTIVATE => IDLE
LEC ATM1/0.3: action A_SHUTDOWN_LEC
LEC ATM1/0.3: sending CANCEL
LEC ATM1/0.3:   ATM address     47.00918100000000613E5A2F01.006070174820.03
LEC ATM1/0.3: state IDLE event LEC_LOCAL_DEACTIVATE => IDLE
The following output is from the debug lane client mpoa command when the lane interface is shutdown:
BLRRSP4#debug lane client mpoa
BLRRSP4#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
BLRRSP4(config)#int atm 1/1/0.1
BLRRSP4(config-subif)#shutdown
BLRRSP4(config-subif)#
00:23:32:%LANE-5-UPDOWN:ATM1/1/0.1 elan elan2:LE Client changed state to down
00:23:32:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:DOWN
00:23:32:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:DOWN
BLRRSP4(config-subif)#
BLRRSP4(config-subif)#
BLRRSP4(config-subif)#
BLRRSP4(config-subif)#exit
BLRRSP4(config)#exit
The following output is from the debug lane client mpoa command when the lane interface is started (no shutdown):
BLRRSP4#debug lane client mpoa
BLRRSP4#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
BLRRSP4(config)#int atm 1/1/0.1
BLRRSP4(config-subif)#
BLRRSP4(config-subif)#
BLRRSP4(config-subif)#no shutdown
BLRRSP4(config-subif)#
00:23:39:LEC ATM1/1/0.1:lec_process_lane_tlv:msg LANE_CONFIG_RSP, num_tlvs 14
00:23:39:LEC ATM1/1/0.1:elan id from LECS set to 300
00:23:39:LEC ATM1/1/0.1:lec_process_lane_tlv:msg LANE_JOIN_RSP, num_tlvs 1
00:23:39:LEC ATM1/1/0.1:elan id from LES set to 300
00:23:39:LEC ATM1/1/0.1:lec_append_mpoa_dev_tlv:
00:23:39:LEC ATM1/1/0.1:got mpoa client addr 47.0091810000000050E2097801.0050A
29AF42D.00
00:23:39:%LANE-5-UPDOWN:ATM1/1/0.1 elan elan2:LE Client changed state to up
00:23:39:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:UP
00:25:57:LEC ATM1/1/0.1:lec_process_lane_tlv:msg LANE_ARP_REQ, num_tlvs 1
00:25:57:LEC ATM1/1/0.1:lec_process_dev_type_tlv:    lec 47.0091810000000050E
2097801.00500B306440.02
    type MPS, mpc 00.000000000000000000000000.000000000000.00
    mps 47.0091810000000050E2097801.00500B306444.00, num_mps_mac 1, mac 0050.0b3
0.6440
00:25:57:LEC ATM1/1/0.1:create mpoa_lec
00:25:57:LEC ATM1/1/0.1:new mpoa_lec 0x617E3118
00:25:57:LEC ATM1/1/0.1:lec_process_dev_type_tlv:type MPS, num       _mps_mac
 1
00:2t 5:57:LEC ATM1/1/0.1:lec_add_mps:
    remote lec 47.0091810000000050E2097801.00500B306440.02
    mps 47.0091810000000050E2097801.00500B306444.00 num_mps_mac 1, mac 0050.0b30
.6440
00:25:57:LEC ATM1/1/0.1:mpoa_device_change:lec_nsap 47.0091810000000050E20978
01.00500B306440.02, appl_type 5
     mpoa_nsap 47.0091810000000050E2097801.00500B306444.00, opcode 4
00:25:57:LEC ATM1/1/0.1:lec_add_mps:add mac 0050.0b30.6440, mps_mac 0x617E372
C
00:25:57:LEC ATM1/1/0.1:mpoa_device_change:lec_nsap 47.0091810000000050E20978
01.00500B306440.02, appl_type 5
     mpoa_nsap 47.0091810000000050E2097801.00500B306444.00, opcode 5
00:25:57:LEC ATM1/1/0.1:     mps_mac 0050.0b30.6440
00:25:57:LEC ATM1/1/0.1:lec_append_mpoa_dev_tlv:
00:25:57:LEC ATM1/1/0.1:got mpoa client addr 47.0091810000000050E2097801.0050A
29AF42D.00
BLRRSP4(config-subif)#exit
BLRRSP4(config)#exit
The following output is from the debug lane client mpoa command when the ATM major interface is shutdown:
BLRRSP4#debug lane client mpoa
BLRRSP4#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
BLRRSP4(config)#int atm 1/1/0
BLRRSP4(config-if)#shutdown
BLRRSP4(config-if)#
00:26:28:LANE ATM1/1/0:atm hardware reset
00:26:28:%LANE-5-UPDOWN:ATM1/1/0.1 elan elan2:LE Client changed state to down
00:26:28:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:DOWN
00:26:28:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:DOWN
00:26:28:%MPOA-5-UPDOWN:MPC mpc2:state changed to down
00:26:28:LEC ATM1/1/0.1:mpoa_to_lec:appl 6, opcode 0
00:26:30:%LINK-5-CHANGED:Interface ATM1/1/0, changed state to administratively
 down
00:26:30:LANE ATM1/1/0:atm hardware reset
00:26:31:%LINEPROTO-5-UPDOWN:Line protocol on Interface ATM1/1/0, changed stat
e to down
BLRRSP4(config-if)#
00:26:31:LEC ATM1/1/0.1:mpoa_to_lec:appl 6, opcode 0
00:26:32:LANE ATM1/1/0:atm hardware reset
00:26:32:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:DOWN
00:26:34:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:DOWN
BLRRSP4(config-if)#exit
BLRRSP4(config)#exit
The following output is from the debug lane client mpoa command when the ATM major interface is started:
BLRRSP4#debug lane client mpoa
BLRRSP4#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
BLRRSP4(config)#int atm 1/1/0
BLRRSP4(config-if)#no shutdown
00:26:32:LANE ATM1/1/0:atm hardware reset
00:26:32:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:DOWN
00:26:34:%LINK-3-UPDOWN:Interface ATM1/1/0, changed state to down
00:26:34:LANE ATM1/1/0:atm hardware reset
00:26:41:%LINK-3-UPDOWN:Interface ATM1/1/0, changed state to up
00:26:42:%LINEPROTO-5-UPDOWN:Line protocol on Interface ATM1/1/0, changed stat
e to up
00:27:10:%LANE-6-INFO:ATM1/1/0:ILMI prefix add event received
00:27:10:LANE ATM1/1/0:prefix add event for 470091810000000050E2097801 ptr=0x6
17BFC0C len=13
00:27:10:    the current first prefix is now:470091810000000050E2097801
00:27:10:%ATMSSCOP-5-SSCOPINIT:- Intf :ATM1/1/0, Event :Rcv End, State :Act
ive.
00:27:10:LEC ATM1/1/0.1:mpoa_to_lec:appl 6, opcode 0
00:27:10:%LANE-3-NOREGILMI:ATM1/1/0.1 LEC cannot register 47.0091810000000050E
2097801.0050A29AF428.01 with ILMI
00:27:10:%LANE-6-INFO:ATM1/1/0:ILMI prefix add event received
00:27:10:LANE ATM1/1/0:prefix add event for 470091810000000050E2097801 ptr=0x6
17B8E6C len=13
00:27:10:    the current first prefix is now:470091810000000050E2097801
00:27:10:%LANE-5-UPDOWN:ATM1/1/0.1 elan elan2:LE Client changed state to down
00:27:10:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:DOWN
00:27:10:LEC ATM1/1/0.1:mpoa_to_lec:appl 6, opcode 0
00:27:10:%MPOA-5-UPDOWN:MPC mpc2:state changed to up
00:27:10:LEC ATM1/1/0.1:mpoa_to_lec:appl 6, opcode 1
00:27:12:LEC ATM1/1/0.1:lec_process_lane_tlv:msg LANE_CONFIG_RSP, num_tlvs 14
00:27:12:LEC ATM1/1/0.1:elan id from LECS set to 300
00:27:12:LEC ATM1/1/0.1:lec_process_lane_tlv:msg LANE_JOIN_RSP, num_tlvs 1
00:27:12:LEC ATM1/1/0.1:elan id from LES set to 300
00:27:12:LEC ATM1/1/0.1:lec_append_mpoa_dev_tlv:
00:27:12:LEC ATM1/1/0.1:got mpoa client addr 47.0091810000000050E2097801.0050A
29AF42D.00
00:27:12:%LANE-5-UPDOWN:ATM1/1/0.1 elan elan2:LE Client changed state to up
00:27:12:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:UP
BLRRSP4(config-if)#exit
BLRRSP4(config)#exit
Related Commands

•debug mpoa client

•debug mpoa server

Cisco IOS Software Releases 12.0 T

MPOA for Token Ring Networks

Hierarchical Navigation

Downloads

Table Of Contents

MPOA for Token Ring Networks

Feature Summary

Benefits

List of Terms

Restrictions

Platforms

Supported MIBs and RFCs

Functional Description

Configuration Tasks

Configuring an MPOA Server

Configure the MPS

Configure the MPS Variables

Monitor and Maintain the MPS

Configuring an MPOA Client

Configure the MPC

Configure the MPC Variables

Monitor and Maintain the MPC

Configuring Token Ring LANE

Configuring a Token Ring LEC

Configuring the LECS Database

Configuring the LES/BUS

Configuration Examples

MPOA Token Ring LANE Configuration in an IP-Routed Domain

MPOA Token Ring LANE Configuration in an IP SRB-Routed Domain

Command Reference

keepalive-lifetime

Syntax Description

Default

Command Mode

Usage Guidelines

Example

Related Commands

Debug Commands

debug lane client

Syntax Description

Default

Command Mode

Usage Guidelines

Example

Related Commands

Technology Trends