Table Of Contents
mpoa server name trigger ip-address
show mpoa default-atm-addresses
MPOA Commands
This chapter describes the commands available to configure and maintain Multiprotocol over ATM (MPOA).
For MPOA configuration information and examples, refer to the Cisco IOS Switching Services Configuration Guide.
atm-address
To override the control ATM address of an MPC or MPS, use the atm-address interface configuration command. Use the no form of this command to revert to the default address.
atm-address atm-address
no atm-address
Syntax Description
Defaults
The default is an auto-generated ATM address.
Command Modes
Interface configuration.
Command History
Usage Guidelines
This command specifies the control ATM address that an MPC or MPS should use when it comes up; that is, when it is associated with a hardware interface.
The atm-address command overrides the default the operational control address of the MPC or MPS. When this address is deleted (using the no form of the command), the MPC or MPS uses an auto-generated address as its control address.
Examples
The following example specifies the ATM address for an MPC:
mpoa-client-config#atm-address 47.0091810000000061705b7701.00400BFF0011.00The following example specifies the ATM address for an MPS:
mpoa-server-config#atm-address 47.0091810000000061705C2B01.00E034553024.00clear mpoa client cache
Use the clear mpoa client cache EXEC command to clear the ingress and egress cache entries of one or all MPCs.
clear mpoa client [name mpc-name] cache [ingress | egress] [ip-address ip-address]
Syntax Description
Defaults
The system defaults are:
•
All MPC cache entries are cleared.
•
•
Command Modes
EXEC
Command History
Examples
The following example clears the ingress and egress cache entries for the MPC named ip_mpc:
ATM#clear mpoa client name ip_mpc cacheRelated Commands
Displays the ingress or egress cache entries matching the IP addresses for the MPCs.
clear mpoa server cache
To clear the ingress and egress cache entries, use the clear mpoa server cache EXEC command.
clear mpoa server [name mps-name] cache [ingress | egress] [ip-address ip-address]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
This command clears cache entries.
Examples
The following example clears all cache entries:
ATM#clear mpoa server cacheRelated Commands
show mpoa server cache
Displays ingress and egress cache entries associated with a server.
holding-time
To specify the holding time value for the MPS-p7 variable of an MPS, use the holding-time MPS configuration command. To revert to the default value, use the no form of this command.
holding-time time
no holding-time time
Syntax Description
Defaults
The default holding time is 1200 seconds (20 minutes).
Command Modes
MPS configuration
Command History
Examples
The following example sets the holding time to 600 seconds (10 minutes):
holding-time 600keepalive-time
To specify the keepalive time value for the MPS-p1 variable of an MPS, use the keepalive-time MPS configuration command. To revert to the default value, use the no form of this command.
keepalive-time time
no keepalive-time time
Syntax Description
Defaults
The default keepalive time is 10 seconds.
Command Modes
MPS configuration
Command History
Examples
The following example sets the keepalive time to 25 seconds:
keepalive-time 25lane client mpoa client name
Use the lane client mpoa client name interface configuration command to bind a LEC to the named MPC. Use the no form of this command to unbind the named MPC from a LEC.
lane client mpoa client name mpc-name
no lane client mpoa client name mpc-name
Syntax Description
Defaults
No LEC is bound to a named MPC.
Command Modes
Interface configuration
Command History
Usage Guidelines
When you enter this command, the named MPC is bound to a LEC. The named MPC must exist before this command is accepted. If you enter this command before a LEC is configured (not necessarily running), a warning message is issued.
Examples
The following example binds a LEC on a subinterface to the MPC:
ATM (config-subif)#lane client mpoa client name ip_mpclane client mpoa server name
To bind a LEC with the named MPS, use the lane client mpoa server name interface configuration command. To unbind the server, use the no form of this command.
lane client mpoa server name mps-name
no lane client mpoa server name mps-name
Syntax Description
Defaults
No LEC is bound to a named MPS.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command binds a LEC to the named MPS. The specified MPS must exist before this command is accepted. If this command is entered when a LEC is not already configured (not necessarily running), a warning message will be issued.
Examples
The following example binds a LANE client with the MPS named MYMPS:
ATM (config-subif)#lane client mpoa server name MYMPSmpoa client config name
Use the mpoa client config name global configuration command to define an MPC with a specified name. Use the no form of this command to delete the MPC.
mpoa client config name mpc-name
no mpoa client config name mpc-name
Syntax Description
Defaults
This command has no default setting.
Command Modes
Global configuration
Command History
Usage Guidelines
When you configure/create an MPC, you automatically enter the MPC configuration mode. From here, you can enter subcommands to define or change MPC variables specific only to this MPC. Note that the MPC is not functional until it is attached to a hardware interface.
Examples
The following example creates or modifies the MPC named ip_mpc:
mpoa client config name ip_mpcRelated Commands
mpoa client name
Use the mpoa client name interface configuration command to attach an MPC to a major ATM interface. Use the no form of this command to break the attachment.
mpoa client name mpc-name
no mpoa client name mpc-name
Syntax Description
Defaults
No MPC is attached to an ATM interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
The mpoa client name command provides an interface to the MPC through which the MPC can set up and receive calls.
When you enter this command on a major interface that is up and operational, the named MPC becomes operational. Once the MPC is fully operational, it can register its ATM address.
Examples
The following example attaches the MPC ip_mpc to an interface:
interface atm 1/0mpoa client name ip_mpcmpoa server config name
To define an MPS with the specified name, use the mpoa server config name global configuration command. To delete an MPS, use the no form of this command.
mpoa server config name mps-name
no mpoa server config name mps-name
Syntax Description
Defaults
No MPS is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
This command defines an MPS with the specified name. The MPS does not actually start functioning until it is attached to a specific hardware interface. Once that attachment is complete, the MPS starts functioning. When you configure/create an MPS, you automatically enter the MPS configuration mode.
You can define the MPS variables specific to an MPS, only after that MPS is defined with a specified name. After this command is entered, further commands may be used to change MPS variables that are specific only to this MPS.
Examples
The following example defines the MPS named MYMPS:
mpoa server config name MYMPSmpoa server name
To attach an MPS to a major ATM interface, use the mpoa server name interface configuration command. To break the attachment, use the no form of this command.
mpoa server name mps-name
no mpoa server name mps-name
Syntax Description
Defaults
No MPS is attached to an ATM interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command attaches an MPS to a specific (major) interface. At this point, the MPS has the capability to obtain its auto generated ATM address and an interface through which it can communicate to the neighboring MPOA devices. Only when both an MPS is defined globally and attached to an interface, it is considered to be operational. Although multiple different servers may share the same hardware interface, an MPS can be attached to only a single interface at any one time. Note that the specified MPS must already have been defined when this command is entered.
Examples
The following example attaches the MPS named MYMPS to an ATM interface:
mpoa server name MYMPSmpoa server name trigger ip-address
To originate an MPOA trigger for the specified IP address to the specified MPOA client from the specified MPS, use the mpoa server name trigger ip-address EXEC command.
mpoa server name mps-name trigger ip-address ip address [mpc-address mpc-address]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
This command sends an MPOA trigger for the specified IP address to the specified MPOA client from the specified MPOA server. If an MPOA client is not specified, it is triggered to all MPOA clients.
Examples
The following example sends an MPOA trigger for the specified IP address 128.9.0.7 to all known MPOA clients from the MPOA server named MYMPS:
mpoa server name MYMPS trigger ip-address 128.9.0.7network-id
To specify the network ID of an MPS, use the network-id MPS configuration command. To revert to the default value (default value for network-id is 1), use the no form of this command.
network-id id
no network-id
Syntax Description
Defaults
The default value for network-id is 1.
Command Modes
MPS configuration
Command History
Usage Guidelines
Specifies the network ID of this MPS. This value is used in a very similar way the NHRP network ID is used. It is for partitioning NBMA clouds artificially by administration.
Examples
The following example sets the network ID to 5:
network-id 5shortcut-frame-count
Use the shortcut-frame-count MPC configuration command to specify the maximum number of times a packet can be routed to the default router within shortcut-frame time before an MPOA resolution request is sent. Use the no form of this command to restore the default shortcut-setup frame count value.
shortcut-frame-count count
no shortcut-frame-count
Syntax Description
Defaults
The default is 10 frames.
Command Modes
MPC configuration mode.
Command History
Examples
The following example sets the shortcut-setup frame count to 5 for the MPC:
shortcut-frame-count 5Related Commands
Overrides the control ATM address of an MPC or MPS.
Defines an MPC with a specified name.
Sets the shortcut-setup frame time (in seconds) for the MPC.
shortcut-frame-time
Use the shortcut-frame-time MPC configuration command to set the shortcut-setup frame time (in seconds) for the MPC. Use the no form of this command to restore the default shortcut-setup frame-time value.
shortcut-frame-time time
no shortcut-frame-time
Syntax Description
Defaults
The default is 1 second.
Command Modes
MPC configuration
Command History
Examples
The following example sets the shortcut-setup frame time to 7 for the MPC:
shortcut-frame-time 7Related Commands
show mpoa client
Use the show mpoa client EXEC command to display a summary of information regarding one or all MPCs.
show mpoa client [name mpc-name] [brief]
Syntax Description
name mpc-name
(Optional) Name of the MPC with the specified name.
brief
(Optional) Output limit of the command.
Command Modes
EXEC
Command History
Usage Guidelines
If you omit the name keyword, the command displays information for all MPCs.
Examples
The following is sample output from the show mpoa client command:
ATM#show mpoa client name ip_mpc briefMPC Name: ip_mpc, Interface: ATM1/0, State: UpMPC actual operating address: 47.00918100000000613E5A2F01.0010A6943825.00Shortcut-Setup Count: 1, Shortcut-Setup Time: 1Lane clients bound to MPC ip_mpc: ATM1/0.1Discovered MPS neighbours kp-alv vcd rxPkts txPkts47.00918100000000613E5A2F01.006070174824.00 59 30 28 2Remote Devices known vcd rxPkts txPkts47.00918100000000613E5A2F01.00000C5A0C5D.00 35 0 10Table 131 describes the fields shown in the display.
Related Commands
show mpoa client cache
Use the show mpoa client cache EXEC command to display the ingress or egress cache entries matching the IP addresses for the MPCs.
show mpoa client [name mpc-name] cache [ingress | egress] [ip-address ip-address]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show mpoa client cache command for a specific MPC:
ATM#show mpoa client ip_mpc cacheMPC Name: ip-mpc, Interface: ATM1/0, State: UpMPC actual operating address: 47.00918100000000613E5A2F01.0010A6943825.00Shortcut-Setup Count: 1, Shortcut-Setup Time: 1Number of Ingress cache entries: 1MPC Ingress Cache Information:Dst IP addr State vcd Expires Egress MPC Atm address20.20.20.1 RSVLD 35 11:38 47.00918100000000613E5A2F01.00000C5A0C5D.00Number of Egress cache entries: 1MPC Egress Cache Information:Dst IP addr Dst MAC Src MAC MPSid Elan Expires CacheId Tag10.10.10.1 0000.0c5a.0c58 0060.7017.4820 9 2 11:55 1 1Table 132 describes the fields shown in the display.
Table 132 show mpoa client cache Field Descriptions
MPC Name
Name specified for the MPC.
Interface
Interface to which the MPC is attached.
State
Current state of the MPC (up or down).
MPC actual operating address
ATM address of the MPC.
Shortcut-Setup Count
Current number specified by the shortcut-frame-count command.
Number of Ingress cache entries
Number of entries in the ingress cache.
MPC Ingress Cache Information
Dst IP addr
IP address of the destination.
State
State of the ingress cache entry1 .
vcd
Number that identifies the virtual circuit.
Expires
Time in minutes/seconds until the ingress cache entry expires.
Egress MPC Atm address
ATM address of the egress MPC.
Number of Egress cache entries
Number of entries in the egress cache.
MPC Egress Cache Information:
Dst IP addr
IP address of the destination.
Dst MAC
MAC address of the destination.
Src MAC
MAC address of the source.
MPSid
Unique number representing the egress MPS.
Elan
ELAN identifier of the ELAN serving this destination IP address.
Expires
Time in minutes/seconds until the egress cache entry expires.
CacheID
Cache identifier.
Tag
Tag identifier.
1 Valid states are initialized, trigger, refresh, hold_down, resolved, and suspended.
show mpoa client statistics
Use the show mpoa client statistics EXEC command to display all the statistics collected by an MPC.
show mpoa client [name mpc-name] statistics
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
This command displays all the statistics collected by an MPC.
Examples
The following is sample output from the show mpoa client statistics command for the MPC ip_mpc:
ATM#show mpoa client name ip_mpc statisticsMPC Name: ip_mpc, Interface: ATM1/0, State: UpMPC actual operating address: 47.00918100000000613E5A2F01.0010A6943825.00Shortcut-Setup Count: 1, Shortcut-Setup Time: 1Transmitted ReceivedMPOA Resolution Requests 2 0MPOA Resolution Replies 0 2MPOA 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: 0show mpoa default-atm-addresses
Use show mpoa default-atm-addresses EXEC command to display the default ATM addresses for the MPC.
show mpoa default-atm-addresses
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show mpoa default-atm-addresses command when the switch prefix is NOT available:
ATM#show mpoa default-atm-addressesinterface ATM1/0:MPOA Server: ...006070174824.**MPOA Client: ...006070174825.**note: ** is the MPS/MPC instance number in hexinterface ATM2/0:MPOA Server: ...006070174844.**MPOA Client: ...006070174845.**note: ** is the MPS/MPC instance number in hexThe following is sample shows output from the show mpoa default-atm-addresses command when the switch prefix is available:
ATM#show mpoa default-atm-addressesinterface ATM1/0:MPOA Server: 47.00918100000000613E5A2F01.006070174824.**MPOA Client: 47.00918100000000613E5A2F01.006070174825.**note: ** is the MPS/MPC instance number in hexinterface ATM2/0:MPOA Server: 47.100000000000000000000000.006070174844.**MPOA Client: 47.100000000000000000000000.006070174845.**note: ** is the MPS/MPC instance number in hexTable 133 describes the fields shown in the example output.
show mpoa server
To display information about any specified or all MPSs in the system depending on whether the name of the required MPS is specified or not, use the show mpoa server EXEC command.
show mpoa server [name mps-name]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
This command displays information about any specified MPS or all MPSs in the system depending on whether the name of the required MPS is specified or not. The command displays information about server configuration parameters. It also displays information about LAN Emulated Clients (LECs) that are bound to the MPOA server neighbors (both MPC and MPS).
Examples
The following is sample output from the show mpoa server command, with a specified name:
Router# show mpoa server name ip_mpsMPS Name: ip_mps, MPS id: 0, Interface: ATM1/0, State: upnetwork-id: 1, Keepalive: 25 secs, Holding time: 1200 secsKeepalive lifetime: 75 secs, Giveup time: 40 secsMPS actual operating address: 47.00918100000000613E5A2F01.006070174824.00Lane clients bound to MPS ip_mps: ATM1/0.1 ATM1/0.2Discovered neighbours:MPC 47.00918100000000613E5A2F01.00000C5A0C5D.00 vcds: 39(R,A)MPC 47.00918100000000613E5A2F01.0010A6943825.00 vcds: 40(R,A)Table 134 describes the fields shown in the display.
Related Commands
clear mpoa server name
Clears the ingress and egress cache entries of one or all MPCs.
show mpoa server cache
To display ingress and egress cache entries associated with a server, use the show mpoa server cache EXEC command.
show mpoa server [name mps-name] cache [ingress | egress] [ip-address ip-address]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
This command displays ingress and egress cache entries associated with an MPS.
Examples
The following is sample output from the show mpoa server cache command, with a specified name:
Router# show mpoa server name ip_mps cacheMPS Name: ip_mps, MPS id: 0, Interface: ATM1/0, State: upnetwork-id: 1, Keepalive: 25 secs, Holding time: 1200 secsKeepalive lifetime: 75 secs, Giveup time: 40 secsMPS actual operating address: 47.00918100000000613E5A2F01.006070174824.00Number of Ingress cache entries: 1Ingress Cache information:IP address Ingress MPC ATM Address Remaining Time20.20.20.1 47.00918100000000613E5A2F01.0010A6943825.00 19:07Number of Egress cache entries: 1Egress Cache information:Dst IP address Ingress MPC ATM Address Remaining Time20.20.20.1 47.00918100000000613E5A2F01.0010A6943825.00 19:06src IP 20.20.20.2, cache Id 1Table 135 describes the fields shown in the display.
show mpoa server statistics
To display all the statistics collected by an MPS, use the show mpoa server statistics EXEC command.
show mpoa server [name mps-name] statistics
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
This command will display all the statistics collected by an MPS. This pertains to the ingress /egress cache entry creation, deletion, and failures.
Examples
The following is a sample output from the show mpoa server statistics command, with a specified name:
Router# show mpoa server name ip_mps statisticsMPS Name: ip_mps, MPS id: 0, Interface: ATM1/0, State: upnetwork-id: 1, Keepalive: 25 secs, Holding time: 1200 secsKeepalive lifetime: 75 secs, Giveup time: 40 secsMPS actual operating address: 47.00918100000000613E5A2F01.006070174824.00Opcode Transmitted Received---------------------------------------------------------MPOA Resolution Requests 2MPOA Resolution Replies 2MPOA Cache Imposition Requests 1MPOA Cache Imposition Replies 1MPOA Egress Cache Purge Requests 0MPOA Egress Cache Purge Replies 0NHRP Resolution Requests 0 0NHRP Resolution Replies 0 0NHRP Purge Requests 0 0Table 136 describes the fields shown in the upper part of this display.