|
|
Table Of Contents
mpoa server name trigger ip-address
qos-group (ATM VC bundle member)
lane auto-config-atm-address
To specify that the configuration server ATM address is computed by the Cisco automatic method, use the lane auto-config-atm-address command in interface configuration mode. To remove the previously assigned ATM address, use the no form of this command.
lane [config] auto-config-atm-address
no lane [config] auto-config-atm-address
Syntax Description
Defaults
No specific ATM address is set.
Command Modes
Interface configuration
Command History
Usage Guidelines
When the config keyword is not present, this command causes the LANE server and LANE client on the subinterface to use the automatically assigned ATM address for the configuration server.
When the config keyword is present, this command assigns the automatically generated ATM address to the configuration server (LECS) configured on the interface. Multiple commands that assign ATM addresses to the LANE configuration server can be issued on the same interface to assign different ATM addresses to the configuration server. Commands that assign ATM addresses to the LANE configuration server include lane auto-config-atm-address, lane config-atm-address, and lane fixed-config-atm-address.
For a discussion of Cisco's method of automatically assigning ATM addresses, refer to the "Configuring LAN Emulation" chapter in the Cisco IOS Switching Services Configuration Guide.
Examples
The following example shows how to associate the LANE configuration server with the database named network1 and specifies that the configuration server's ATM address will be assigned by the Cisco automatic method:
Router(config)# lane database network1Router(lane-config-dat)# name eng server-atm-address 39.020304050607080910111213.0800.AA00.1001.02Router(lane-config-dat)# name mkt server-atm-address 39.020304050607080910111213.0800.AA00.4001.01Router(config)# interface atm 1/0Router(config-if)# lane config database network1Router(config-if)# lane config auto-config-atm-addressThe following example shows how to cause the LANE server and LANE client on the subinterface to use the automatically assigned ATM address to communicate with the configuration server:
Router(config)# interface atm 2/0.1Router(config-if)# ip address 172.16.0.4 255.255.255.0Router(config-if)# lane client ethernetRouter(config-if)# lane server-bus ethernet engRouter(config-if)# lane auto-config-atm-addressRelated Commands
lane bus-atm-address
To specify an ATM address—and thus override the automatic ATM address assignment—for the broadcast and unknown server on the specified subinterface, use the lane bus-atm-address command in interface configuration mode. To remove the ATM address previously specified for the broadcast and unknown server on the specified subinterface and thus revert to the automatic address assignment, use the no form of this command.
lane bus-atm-address atm-address-template
no lane bus-atm-address [atm-address-template]
Syntax Description
Defaults
For the broadcast and unknown server, the default is automatic ATM address assignment.
Command Modes
Interface configuration
Command History
Usage Guidelines
When applied to a broadcast and unknown server, this command overrides automatic ATM address assignment for the broadcast and unknown server. When applied to a LANE client, this command gives the client the ATM address of the broadcast and unknown server. The client will use this address rather than sending LAN Emulation Address Resolution Protocol (LE ARP) requests for the broadcast address.
When applied to a selected interface, but with a different ATM address from what was used previously, this command replaces the broadcast and unknown server's ATM address.
ATM Addresses
A LANE ATM address has the same syntax as a network service access point (NSAP) (but it is not a network-level address). It consists of the following:
•
A 13-byte prefix that includes the following fields defined by the ATM Forum:
–
–
–
–
–
–
–
•
•
Address Templates
LANE ATM address templates can use two types of wildcards: an asterisk (*) to match any single character (nibble), and an ellipsis (...) to match any number of leading, middle, or trailing characters. The values of the characters replaced by wildcards come from the automatically assigned ATM address.
The values of the digits that are replaced by wildcards come from the automatic ATM assignment method.
In LANE, a prefix template explicitly matches the prefix but uses wildcards for the ESI and selector fields. An ESI template explicitly matches the ESI field but uses wildcards for the prefix and selector.
In the Cisco implementation of LANE, the prefix corresponds to the switch, the ESI corresponds to the ATM interface, and the selector field corresponds to the specific subinterface of the interface.
Examples
The following example shows how to use an ESI template to specify the part of the ATM address corresponding to the interface; the remaining values in the ATM address come from automatic assignment:
Router(config-if)# lane bus-atm-address ...0800.200C.1001.**The following example shows how to use a prefix template to specify the part of the ATM address corresponding to the switch; the remaining values in the ATM address come from automatic assignment:
Router(config-if)# lane bus-atm-address 45.000014155551212f.00.00...Related Commands
lane server-bus
Enables a LANE server and a broadcast and unknown server on the specified subinterface with the ELAN ID.
lane client flush
To enable the flush mechanism of a LAN Emulation Client (LEC), use the lane client flush command in global configuration mode. To disable the flush mechanism of a LEC, use the no form of this command.
lane client flush
no lane client flush
Syntax Description
This command contains no arguments or keywords.
Defaults
All the LECs perform the LANE LE_FLUSH process by default.
Command Modes
Global configuration
Command History
Usage Guidelines
In Cisco IOS Release 12.1(3)T and later releases, the lane client flush command will be hidden and will not be visible in the configuration.
Configuring the no lane client flush command on a Cisco networking device is recommended to prevent the initial packet drops during the establishment of LANE data direct virtual connection (VCC).
Use the no lane client flush command to keep LANE clients from sending LE_FLUSH messages to the remote LANE client. This configuration also allows the LANE clients to process the LE_FLUSH messages from the remote LANE clients.
Note
Examples
The following example shows how to disable the flush mechanism of a LEC:
Router(config)# no lane client flushRelated Commands
lane client mpoa client name
To bind a LAN Emulation Client (LEC) to the named Multiprotocol over ATM client (MPC), use the lane client mpoa client name command in interface configuration mode. To unbind the named MPC from a LEC, use the no form of this command.
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 shows how to bind a LEC on a subinterface to the MPC:
Router(config-if)# lane client mpoa client name ip_mpclane client mpoa server name
To bind a LAN Emulation Client (LEC) with the named Multiprotocol over ATM server (MPS), use the lane client mpoa server name command in interface configuration mode. 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 shows how to bind a LANE client with the MPS named MYMPS:
Router(config-if)# lane client mpoa server name MYMPSlane client
To activate a LAN Emulation (LANE) client on the specified subinterface, use the lane client command in interface configuration mode. To remove a previously activated LANE client on the subinterface, use the no form of this command.
lane client {ethernet} [elan-name]
no lane client {ethernet} [elan-name]
Syntax Description
Defaults
No LANE clients are enabled on the interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
If a lane client command has already been used on the subinterface for a different ELAN, then the client initiates termination procedures for that ELAN and joins the new ELAN.
If you do not provide an elan-name value, the client contacts the server to find which ELAN to join. If you do provide an ELAN name, the client consults the configuration server to ensure that no conflicting bindings exist.
Examples
The following example shows how to enable an Ethernet LANE client on an interface:
Router(config-if)# lane client ethernetRelated Commands
lane client-atm-address
Specifies an ATM address—and thus overrides the automatic ATM address assignment—for the LANE client on the specified subinterface.
lane client-atm-address
To specify an ATM address—and thus override the automatic ATM address assignment—for the LAN Emulation (LANE) client on the specified subinterface, use the lane client-atm-address command in interface configuration mode. To remove the ATM address previously specified for the LANE client on the specified subinterface and thus revert to the automatic address assignment, use the no form of this command.
lane client-atm-address atm-address-template
no lane client-atm-address [atm-address-template]
Syntax Description
Defaults
Automatic ATM address assignment
Command Modes
Interface configuration
Command History
Usage Guidelines
Use of this command on a selected subinterface, but with a different ATM address from what was used previously, replaces the ATM address of the LANE client.
ATM Addresses
A LANE ATM address has the same syntax as a network service access point (NSAP) (but it is not a network-level address). It consists of the following:
•
–
–
–
–
–
–
–
•
•
Address Templates
LANE ATM address templates can use two types of wildcards: an asterisk (*) to match any single character (nibble), and an ellipsis (...) to match any number of leading, middle, or trailing characters. The values of the characters replaced by wildcards come from the automatically assigned ATM address.
In LANE, a prefix template explicitly matches the ATM address prefix but uses wildcards for the ESI and selector fields. An ESI template explicitly matches the ESI field but uses wildcards for the prefix and selector.
The Cisco implementation of LANE, the prefix corresponds to the switch, the ESI corresponds to the ATM interface, and the selector field corresponds to the specific subinterface of the interface.
For a discussion of Cisco's method of automatically assigning ATM addresses, refer to the "Configuring LAN Emulation" chapter in the Cisco IOS Switching Services Configuration Guide.
Examples
The following example shows how to use an ESI template to specify the part of the ATM address corresponding to the interface; the remaining parts of the ATM address come from automatic assignment:
Router(config-if)# lane client-atm-address...0800.200C.1001.**The following example shows how to use a prefix template to specify the part of the ATM address corresponding to the switch; the remaining parts of the ATM address come from automatic assignment:
Router(config-if)# lane client-atm-address 47.000014155551212f.00.00...Related Commands
lane config database
To associate a named configuration table (database) with the configuration server on the selected ATM interface, use the lane config database command in interface configuration mode. To remove the association between a named database and the configuration server on the specified interface, use the no form of this command.
lane config database database-name
no lane config database
Syntax Description
Defaults
No configuration server is defined, and no database name is provided.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is valid only on a major interface, not a subinterface, because only one LANE Configuration Server (LECS) can exist per interface.
The named database must exist before the lane config database command is used. Refer to the lane database command for more information.
Multiple lane config database commands cannot be used multiple times on the same interface. You must delete an existing association by using the no form of this command before you can create a new association on the specified interface.
Activating a LANE configuration server requires the lane config database command and one of the following commands: lane fixed-config-atm-address, lane auto-config-atm-address, or lane config-atm-address.
Examples
The following example shows how to associate the LECS with the database named network1 and to specify that the configuration server's ATM address will be assigned by the Cisco automatic method:
Router(config)# lane database network1Router(lane-config-dat)# name eng server-atm-address 39.020304050607080910111213.0800.AA00.1001.02Router(lane-config-dat)# name mkt server-atm-address 39.020304050607080910111213.0800.AA00.4001.01Router(config)# interface atm 1/0Router(config-if)# lane config database network1Router(config-if)# lane config auto-config-atm-addressRelated Commands
lane config-atm-address
To specify a configuration server's ATM address explicitly, use the lane config-atm-address command in interface configuration mode. To remove an assigned ATM address, use the no form of this command.
lane [config] config-atm-address atm-address-template
no lane [config] config-atm-address atm-address-template
Syntax Description
Defaults
No specific ATM address or method is set.
Command Modes
Interface configuration
Command History
Usage Guidelines
If the config keyword is not present, this command causes the LAN Emulation (LANE) server and LANE client on the subinterface to use the specified ATM address for the configuration server.
When the config keyword is present, this command adds an ATM address to the configuration server configured on the interface. A LECS can listen on multiple ATM addresses. Multiple commands that assign ATM addresses to the LECS can be issued on the same interface to assign different ATM addresses to the LECS.
ATM Addresses
A LANE ATM address has the same syntax as an NSAP (but it is not a network-level address). It consists of the following:
•
–
–
–
–
–
–
–
•
•
Address Templates
LANE ATM address templates can use two types of wildcards: an asterisk (*) to match any single character (nibble), and an ellipsis (...) to match any number of leading, middle, or trailing characters. The values of the characters replaced by wildcards come from the automatically assigned ATM address.
In LANE, a prefix template explicitly matches the ATM address prefix but uses wildcards for the ESI and selector fields. An ESI template explicitly matches the ESI field but uses wildcards for the prefix and selector.
In our implementation of LANE, the prefix corresponds to the switch prefix, the ESI corresponds to a function of the ATM interface's MAC address, and the selector field corresponds to the specific subinterface of the interface.
For a discussion of the Cisco method of automatically assigning ATM addresses, refer to the "Configuring LAN Emulation" chapter in the Cisco IOS Switching Services Configuration Guide.
Examples
The following example shows how to associate the LANE configuration server with the database named network1 and to explicitly specify the configuration server's ATM address:
Router(config)# lane database network1Router(lane-config-dat)# name eng server-atm-address 39.020304050607080910111213.0800.AA00.1001.02Router(lane-config-dat)# name mkt server-atm-address 39.020304050607080910111213.0800.AA00.4001.01Router(config)# interface atm 1/0Router(config-if)# lane config database network1Router(config-if)# lane config config-atm-address 39.020304050607080910111213.0800.AA00.3000.00The following example shows how to cause the LANE server and LANE client on the subinterface to use the explicitly specified ATM address to communicate with the configuration server:
Router(config)# interface atm 2/0.1Router(config-if)# ip address 172.16.0.4 255.255.255.0Router(config-if)# lane client ethernetRouter(config-if)# lane server-bus ethernet engRouter(config-if)# lane config-atm-address 39.020304050607080910111213.0800.AA00.3000.00Related Commands
lane database
To create a named configuration database that can be associated with a configuration server, use the lane database command in global configuration mode. To delete the database, use the no form of this command.
lane database database-name
no lane database database-name
Syntax Description
Defaults
No name is provided.
Command Modes
Global configuration
Command History
Usage Guidelines
Use of the lane database command places you in database configuration mode, in which you can use the client-atm-address name, default name, mac-address name, name restricted, name unrestricted, name new-name, and name server-atm-address commands to create entries in the specified database. When you are finished creating entries, type ^Z or exit to return to global configuration mode.
Examples
The following example shows how to create the database named network1 and associates it with the configuration server on interface ATM 1/0:
Router(config)# lane database network1Router(lane-config-dat)# name eng server-atm-address 39.020304050607080910111213.0800.AA00.1001.02Router(lane-config-dat)# name mkt server-atm-address 39.020304050607080910111213.0800.AA00.4001.01Router(lane-config-dat)# default-name engRouter(config)# interface atm 1/0Router(config-if)# lane config database network1Router(config-if)# lane config auto-config-atm-addressRelated Commands
lane fixed-config-atm-address
To specify that the fixed configuration server ATM address assigned by the ATM Forum will be used, use the lane fixed-config-atm-address command in interface configuration mode. To specify that the fixed ATM address will not be used, use the no form of this command.
lane [config] fixed-config-atm-address
no lane [config] fixed-config-atm-address
Syntax Description
Defaults
No specific ATM address or method is set.
Command Modes
Interface configuration
Command History
Usage Guidelines
When the config keyword is not present, this command causes the LAN emulation (LANE) server and LANE client on the subinterface to use that ATM address, rather than the ATM address provided by the ILMI, to locate the configuration server.
When the config keyword is present, and the LECS is already up and running, be aware of the following scenarios:
•
•
•
•
•
When you use this command with the config keyword, and the LECS is a master, the master will listen on the fixed address. If you use this command when an LECS is not a master, the LECS will listen on this address when it becomes a master. If you do not use this command, the LECS will not listen on the fixed address.
Multiple commands that assign ATM addresses to the LECS can be issued on the same interface in order to assign different ATM addresses to the LECS. Commands that assign ATM addresses to the LECS include lane auto-config-atm-address, lane config-atm-address, and lane fixed-config-atm-address. The lane config database command and at least one command that assigns an ATM address to the LECS are required to activate a LECS.
Examples
The following example shows how to associate the LECS with the database named network1 and how to specify that the configuration server's ATM address is the fixed address:
Router(config)# lane database network1Router(lane-config-dat)# name eng server-atm-address 39.020304050607080910111213.0800.AA00.1001.02Router(lane-config-dat)# name mkt server-atm-address 39.020304050607080910111213.0800.AA00.4001.01Router(config)# interface atm 1/0Router(config-if)# lane config database network1Router(config-if)# lane config fixed-config-atm-addressThe following example shows how to cause the LANE server and LANE client on the subinterface to use the fixed ATM address to communicate with the configuration server:
Router(config)# interface atm 2/0.1Router(config-if)# ip address 172.16.0.4 255.255.255.0Router(config-if)# lane client ethernetRouter(config-if)# lane server-bus ethernet engRouter(config-if)# lane fixed-config-atm-addressRelated Commands
lane fssrp
To enable the special LANE features such that LANE components (such as the LANE Configuration Server, the LANE client, the LANE server, and the BUS) become aware of the Fast Simple Server Redundancy Protocol (FSSRP), use the lane fssrp command in interface configuration mode. To disable the LANE FSSRP configuration, use the no form of this command.
lane fssrp
no lane fssrp
Syntax Description
This command contains no arguments or keywords.
Defaults
FSSRP is not enabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
You must execute this command on all ATM interfaces to enable FSSRP capability for all LANE components on that interface and hence all its subinterfaces.
Examples
The following example shows how to enable FSSRP on an ATM interface:
Router(config-if)# lane fssrpRelated Commands
lane global-lecs-address
To specify a list of LAN Emulation Configuration Server (LECS) addresses to use when the addresses cannot be obtained from the Interim Local Management Interface (ILMI), use the lane global-lecs-address command in interface configuration mode. To remove a LECS address from the list, use the no form of this command.
lane global-lecs-address address
no lane global-lecs-address address
Syntax Description
Defaults
No addresses are configured. The router obtains LECS addresses from the ILMI.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command when your ATM switches do not support the ILMI list of LECS addresses and you want to configure Simple Server Redundancy. This command will simulate the list of LECS addresses, as if they had been obtained from the ILMI. Use this command with a different address for each LECS. The order they are used determines their priority. You should enter the addresses in the same order as you would on the ATM switch.
Note
If your switches do support ILMI, this command forces the router to use the addresses specified and will not use the ILMI to obtain the LECS addresses.
Because the well-known LECS address is always used as a last resort LECS address, you cannot use the address in this command.
lane le-arp
To add a static entry to the LAN Emulation Address Resolution Protocol (LE ARP) table of the LANE client configured on the specified subinterface, use the lane le-arp command in interface configuration mode. To remove a static entry from the LE ARP table of the LANE client on the specified subinterface, use the no form of this command.
lane le-arp {mac-address | route-desc segment segment-number bridge bridge-number} atm-address
no lane le-arp {mac-address | route-desc segment segment-number bridge bridge-number} atm-address
Syntax Description
Defaults
No static address bindings are provided.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command adds or removes a static entry binding a MAC address or segment number and bridge number to an ATM address. It does not add or remove dynamic entries. Removing the static entry for a specified ATM address from a LE ARP table does not release data direct VCCs established to that ATM address. However, clearing a static entry clears any fast-cache entries that were created from the MAC address-to-ATM address binding.
Static LE ARP entries are neither aged nor removed automatically.
To remove dynamic entries from the LE ARP table of the LANE client on the specified subinterface, use the clear lane le-arp command.
Examples
The following example shows how to add a static entry to the LE ARP table:
Router(config-if)# lane le-arp 0800.aa00.0101 47.000014155551212f.00.00.0800.200C.1001.01The following example shows how to add a static entry to the LE ARP table binding segment number 1, bridge number 1 to the ATM address:
Router(config-if)# lane le-arp route-desc segment 1 bridge 1 39.020304050607080910111213.00000CA05B41.01Related Commands
clear lane le-arp
Forces a LANE server to drop a client and allow the LANE configuration server to assign the client to another ELAN.
lane server-atm-address
To specify an ATM address—and thus override the automatic ATM address assignment—for the LAN emulation (LANE) server on the specified subinterface, use the lane server-atm-address command in interface configuration mode. To remove the ATM address previously specified for the LANE server on the specified subinterface and thus revert to the automatic address assignment, use the no form of this command.
lane server-atm-address atm-address-template
no lane server-atm-address [atm-address-template]
Syntax Description
Defaults
For the LANE server, the default is automatic address assignment; the LANE client finds the LANE server by consulting the configuration server.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command also instructs the LANE client configured on this subinterface to reach the LANE server by using the specified ATM address instead of the ATM address provided by the configuration server.
When used on a selected subinterface, but with a different ATM address than was used previously, this command replaces the ATM address of the LANE server.
ATM Addresses
A LANE ATM address has the same syntax as an network service access point (NSAP) (but it is not a network-level address). It consists of the following:
•
–
–
–
–
–
–
–
•
•
Address Templates
LANE ATM address templates can use two types of wildcards: an asterisk (*) to match any single character (nibble), and an ellipsis (...) to match any number of leading, middle, or trailing characters. The values of the characters replaced by wildcards come from the automatically assigned ATM address.
In LANE, a prefix template explicitly matches the prefix, but uses wildcards for the ESI and selector fields. An ESI template explicitly matches the ESI field, but uses wildcards for the prefix and selector.
In the Cisco implementation of LANE, the prefix corresponds to the switch, the ESI corresponds to the ATM interface, and the selector field corresponds to the specific subinterface of the interface.
For a discussion of the Cisco method of automatically assigning ATM addresses, refer to the "Configuring LAN Emulation" chapter of the Cisco IOS Switching Services Configuration Guide.
Examples
The following example shows how to used an ESI template to specify the part of the ATM address corresponding to the interface; the remaining parts of the ATM address come from automatic assignment:
Router(config-if)# lane server-atm-address ...0800.200C.1001.**The following example shows how to use a prefix template to specify the part of the ATM address corresponding to the switch; the remaining part of the ATM address come from automatic assignment:
Router(config-if)# lane server-atm-address 45.000014155551212f.00.00...Related Commands
lane server-bus
Enables a LANE server and a BUS on the specified subinterface with the ELAN ID.
lane server-bus
To enable a LAN emulation (LANE) server and a broadcast and unknown server (BUS) on the specified subinterface with the emulated LAN (ELAN) ID, use the lane server-bus command in interface configuration mode. To disable a LANE server and BUS on the specified subinterface, use the no form of this command.
lane server-bus {ethernet} elan-name [elan-id id]
no lane server-bus {ethernet} elan-name [elan-id id]
Syntax Description
Defaults
No LAN type or ELAN name is provided.
Command Modes
Interface configuration
Command History
11.0
This command was introduced.
12.0
This command was modified to support the elan-id keyword.
12.3(2)T
The tokenring keyword was removed from this command.
Usage Guidelines
The LANE server and the BUS are located on the same router.
If a lane server-bus command has already been used on the subinterface for a different ELAN, the server initiates termination procedures with all clients and comes up as the server for the new ELAN.
To participate in MPOA, a LEC must have an ELAN ID. This command enables the LEC to get the ELAN ID from the LES when the LEC bypasses the LECS phase.
Caution
specified in the LECS for the same ELAN.
The LEC can also obtain the ELAN ID from the LECS by using the name elan-id command.
Examples
The following example shows how to enable a LANE server and BUS for an Ethernet ELAN named MYELAN:
Router(config-if)# lane server-bus ethernet myelanRelated Commands
logging event atm pvc state
To enable notification of ATM permanent virtual circuit (PVC) state changes, use the logging event atm pvc state command in interface configuration mode. To disable notification, use the no form of this command.
logging event atm pvc state
no logging event atm pvc state
Syntax Description
This command has no arguments or keywords.
Command Default
None
Command Modes
Interface configuration
Command History
Usage Guidelines
For monitoring purposes, this command can be used to log the state changes for all PVCs associated with an ATM interface.
Examples
The following example shows how to enable notification of ATM PVC state changes:
Router(config-if)# logging event atm pvc stateRelated Commands
loopback (ATM)
To configure the ATM interface into loopback mode, use the loopback interface configuration command. To remove the loopback, use the no form of this command.
loopback [cell | line | payload]
no loopback [cell | line | payload]
Syntax Description
Defaults
line
Command Modes
Interface configuration
Command History
11.0
This command was introduced.
11.1
The following keywords were removed:
•
•
Usage Guidelines
This command is useful for testing because it loops all packets from the ATM interface back to the interface as well as directing the packets to the network.
Use the loopback line command to check that the PA-A3 port adapter is working by looping the receive data back to the transmit data.
Examples
The following example loops all packets back to the ATM interface:
interface atm 4/0loopbackRelated Commands
loopback
To loop packets back to the interface for testing, use the loopback interface configuration command with or without an optional keyword. To remove the loopback, use the no form of this command.
Cisco 2600 and 3600 Series
loopback [line | local | payload | remote]
no loopback [line | local | payload | remote]
Cisco 7100, 7200, and 7500 Series
For T1 lines:
loopback {diagnostic | local {payload | line} | remote {iboc | esf {payload | line}}}
For E1 lines:
loopback {diagnostic | local {payload | line}}
no loopback
Syntax Description
Defaults
The line keyword is the default.
Loopback is disabled by default.Command Modes
Interface configuration
Command History
Usage Guidelines
You can use a loopback test on lines to detect and distinguish equipment malfunctions caused either by line and channel service unit/digital service unit (CSU/DSU) or by the interface. If correct data transmission is not possible when an interface is in loopback mode, the interface is the source of the problem.
The local loopback does not generate any packets automatically. Instead, the ping command is used.
Examples
The following example sets up local loopback diagnostics:
interface atm 1/0 loopback localmac-address (ATM)
To configure the MAC address on ATM permanent virtual circuits (PVCs) in a broadband access (BBA) group for using a different MAC address for PPP over Ethernet over ATM (PPPoEoA), use the mac-address command in BBA group configuration mode. To remove a MAC address, use the no form of this command.
mac-address {autoselect | mac-address}
no mac-address {autoselect | mac-address}
Syntax Description
Defaults
No MAC address change. Any change in the usage of MAC addresses will not happen unless this command is explicitly configured.
Command Modes
BBA group configuration mode
Command History
Usage Guidelines
Except for using a different MAC address, this command does not change the way PPPoE works.
Use the mac-address command to configure the MAC address on ATM PVCs in a BBA group so there will be a different MAC address for PPPoEoA.
If a PPP over Ethernet (PPPoE) profile is not specified by using the group option, PPPoE sessions will be established using values from the global PPPoE profile. PPPoE profiles must be configured using the bba-group pppoe command.
Examples
The following example configures the MAC address on an ATM PVC in a BBA group using values from the global PPPoE profile by specifying the MAC address:
Router(config)# bba-group pppoe globalRouter(config-bba-group)# virtual-template 1Router(config-bba-group)# mac-address 1.1.3The following example configures the MAC address automatically on an ATM PVC in a BBA group using group profile by using the autoselect option:
Router(config)# bba-group pppoe vpn1Router(config-bba-group)# virtual-template 1Router(config-bba-group)# mac-address autoselectRelated Commands
bba-group pppoe
Creates a PPPoE profile on the BBA group.
protocol pppoe
Establishes PPPoE sessions on PVCs.
map-class atm
This command is no longer supported.
mid
To set the range of message identifier (MID) values on a permanent virtual circuit (PVC), use the mid interface-ATM-VC configuration command. To remove MID value range settings, use the no form of this command.
mid midlow midhigh
no mid midlow midhigh
Syntax Description
midlow
Starting MID number for this PVC. This can be set between 0 and 1023.
midhigh
Ending MID number for this PVC. This can be set between 0 and 1023.
Defaults
0
Command Modes
Interface-ATM-VC configuration
Command History
Usage Guidelines
This command is only available when SMDS encapsulation is configured on a PVC.
Use this command to assign different ranges of message identifiers to different PVCs.
Examples
In the following example, the atm mid-per-vc command limits the maximum number of message identifiers to 32 for each VC on the ATM interface. Using the mid command, the selected range of numbers that are available for the message identifiers on PVC 1/40 is 0 to 31. For PVC 2/50, the range is 32 to 63.
interface atm 2/0atm mid-per-vc 32pvc 1/40 smdsmid 0 31pvc 2/50 smdsmid 32 63mpoa client config name
To define a Multiprotocol over ATM (MPOA) client (MPC) with a specified name, use the mpoa client config name command in global configuration mode. To delete the MPC, use the no form of this command.
mpoa client config name mpc-name
no mpoa client config name mpc-name
Syntax Description
Defaults
No MPC is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
When you configure or 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 shows how to create or modify the MPC named ip_mpc:
Router(config)# mpoa client config name ip_mpcRelated Commands
mpoa client name
To attach a Multiprotocol over ATM (MPOA) client (MPC) to a major ATM interface, use the mpoa client name command in interface configuration mode. To break the attachment, use the no form of this command.
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 shows how to attache the MPC named ip_mpc to an interface:
Router(config)# interface atm 1/0Router(config-if)# mpoa client name ip_mpcmpoa server config name
To define a Multiprotocol over ATM (MPOA) server (MPS) with the specified name, use the mpoa server config name command in global configuration mode. 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 or create an MPS, you automatically enter the MPS configuration mode.
You can define the MPS variables specific to an MPS only after that MPS has been defined with a specified name. After this command is entered, further commands can be used to change MPS variables that are specific only to this MPS.
Examples
The following example shows how to define the MPS named MYMPS:
Router(config)# mpoa server config name MYMPSmpoa server name trigger ip-address
To originate a Multiprotocol over ATM (MPOA) trigger for the specified IP address to the specified MPOA client from the specified Multiprotocol over ATM server (MPS), use the mpoa server name trigger ip-address command in interface configuration mode.
mpoa server name mps-name trigger ip-address ip-address [mpc-address mpc-address]
Syntax Description
Command Modes
Interface configuration
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 shows how to send an MPOA trigger for the specified IP address 128.9.0.7 to all known MPOA clients from the MPOA server named MYMPS:
Router(config)# interface atm 1/0Router(config-if)# mpoa server name MYMPS trigger ip-address 128.9.0.7mpoa server name
To attach a Multiprotocol over ATM (MPOA) server (MPS) to a major ATM interface, use the mpoa server name command in interface configuration mode. 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 can obtain its autogenerated ATM address and an interface through which it can communicate to the neighboring MPOA devices. Only when an MPS is both defined globally and attached to an interface is it 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. The specified MPS must already be defined when this command is entered.
Examples
The following example attaches the MPS named MYMPS to an ATM interface:
Router(config)# interface atm 1/0Router(config-if)# mpoa server name MYMPSmultiqueue
To enable two queues to prioritize multiple classes of packet streams over the same PVC, use the multiqueue command in PVC- or VC-class configuration mode To return to a single-queue approach, use the no form of this command.
multiqueue
no multiqueue
Syntax Description
This command has no arguments or keywords.
Command Default
Only a single queue per PVC is enabled.
Command Modes
PVC-class configuration
VC-class configurationCommand History
12.4(2)XA
This command was introduced.
12.4(6)T
This command was integrated into Cisco IOS Release 12.4(6)T.
Usage Guidelines
This command enables a priority queue and a regular (nonpriority) queue for traffic streams. When the multiqueue command is enabled and multiple classes of packet streams exist over the same PVC, packets coming from the streams that have priority values configured in a policy map are sent to the high-priority queue. Packets from all other streams are sent to the low-priority queue.
This command applies only to DSL ATM interfaces. Multiqueueing is intended for configuring DSL lines and allows configuring one data flow in a priority queue. If you have configured more than one flow in a priority queue, the latency for delay-sensitive traffic flow might not be guaranteed.
Multiqueueing does not work well with applications such as Multilink PPP (MLP) with interleave and Crypto. This is because MLP uses the same sequence numbering scheme for interleaved packets as multiqueueing. For example, if there are a voice packet and two data packets interleaved, the MLP sequence numbers for these packets could be 1 for the first data packet, 2 for the voice packet, and 3 for a second data packet. With multiqueueing, the voice packet with MLP sequence number 2 goes out before the data packet with MLP sequence number 1. This causes out-of-order sequencing of packets as far as MLP is concerned and causes unexpected behavior. The same problems apply to the Crypto application.
Multiqueueing is disabled by default, so that when MLP and the Crypto applications are used with DSL, the network is disrupted by upgrading to an image with multiqueueing support.
Examples
The following example shows how to enter the command from PVC configuration mode:
Router(config-if-atm-vc)# multiqueueThe following example shows how to enter the command from VC-class configuration mode:
Router(config)# vc-class atm xRouter(config-vc-class)# multiqueueThe following example shows how to return the queues to the default state:
Router(config-if-atm-vc)# no multiqueueRelated Commands
tx-ring-limit
Limits the number of packets that can be used on a transmission ring on the DSL WIC or interface.
name elan-id
To configure the emulated LAN (ELAN) ID of an ELAN in the LAN Emulation Configuration Server (LECS) database to participate in Multiprotocol over ATM (MPOA), use the name elan-id command in LANE database configuration mode. To disable the ELAN ID of an ELAN in the LECS database to participate in MPOA, use the no form of this command.
name name elan-id id
no name name elan-id id
Syntax Description
Defaults
No ELAN ID is configured.
Command Modes
LANE database configuration
Command History
Usage Guidelines
To participate in MPOA, a LAN Emulation Client (LEC) must have an ELAN ID. The LEC obtains the ELAN ID from the LECS. In case the LEC bypasses the LECS phase, the LEC can get the ELAN ID from the LES when the name elan-id command is used.
Examples
The following example shows how to set the ELAN ID to 10 for an ELAN named MYELAN:
Router(lane-config-dat)# name MYELAN elan-id 10Related Commands
lane server-bus
Enables a LANE server and a broadcast and unknown server on the specified subinterface with the ELAN ID.
name local-seg-id
To specify or replace the ring number of the emulated LAN (ELAN) in the configuration server's configuration database, use the name local-seg-id command in database configuration mode. To remove the ring number from the database, use the no form of this command.
name elan-name local-seg-id segment-number
no name elan-name local-seg-id segment-number
Syntax Description
elan-name
Name of the ELAN. The maximum length of the name is 32 characters.
segment-number
Segment number to be assigned to the ELAN. The number ranges from 1 to 4095.
Defaults
No ELAN name or segment number is provided.
Command Modes
LANE database configuration
Command History
Usage Guidelines
This command is ordinarily used for Token Ring LANE.
The same LANE ring number cannot be assigned to more than one ELAN.
The no form of this command deletes the relationships.
Examples
The following example shows how to specify a ring number of 1024 for the ELAN named red:
Router(lane-config-dat)# name red local-seg-id 1024Related Commands
name preempt
To set the emulated LAN (ELAN) preempt, use the name preempt command in LANE database configuration mode. To disable preemption, use the no form of this command.
name elan-name preempt
no name elan-name preempt
Syntax Description
Defaults
Preemption is disabled by default.
Command Modes
LANE database configuration
Command History
Usage Guidelines
Prior to Cisco IOS Release 11.3, when the primary LAN Emulation Server (LES) failed, the Cisco Simple Server Redundancy Protocol (SSRP) switched over to a secondary LES. But when a LES that is ranked higher in the list came back up, the SSRP protocol switched the active LES to the new LES, which had a higher priority. This forced the network to flap multiple times. We have prevented the network flapping by staying with the currently active master LES regardless of the priority. If a higher priority LES comes back online, SSRP will not switch to that LES.
LES preemption is off by default. The first LES that comes on becomes the master. Users can revert to the old behavior (of switching to the higher-priority LES all the time) by specifying the name elan-name preempt command in the LECS database.
Examples
The following example shows how to set the ELAN preempt for the ELAN named MYELAN:
Router(lane-config-dat)# name MYELAN preemptname server-atm-address
To specify or replace the ATM address of the LAN Emulation (LANE) server for the emulated LAN (ELAN) in the configuration server's configuration database, use the name server-atm-address command in database configuration mode. To remove it from the database, use the no form of this command.
name elan-name server-atm-address atm-address [restricted | un-restricted] [index number]
no name elan-name server-atm-address atm-address [restricted | un-restricted] [index number]
Syntax Description
Defaults
No emulated LAN name or server ATM address is provided.
Command Modes
Database configuration
Command History
11.0
This command was introduced.
11.2
The following keywords were added:
•
•
Usage Guidelines
ELAN names must be unique within one named LANE configuration database.
Specifying an existing ELAN name with a new LANE server ATM address adds the LANE server ATM address for that ELAN for redundant server operation or simple LANE service replication. This command can be used multiple times.
The no form of this command deletes the relationships.
Examples
The following example shows how to configure the example3 database with two restricted and one unrestricted ELANs. The clients that can be assigned to the eng and mkt ELANs are specified using the client-atm-address commands. All other clients are assigned to the man ELAN.
Router(config)# lane database example3Router(lane-config-dat)# name eng server-atm-address 39.000001415555121101020304.0800.200c.1001.02 restrictedRouter(lane-config-dat)# name man server-atm-address 39.000001415555121101020304.0800.200c.1001.01Router(lane-config-dat)# name mkt server-atm-address 39.000001415555121101020304.0800.200c.4001.01 restrictedRouter(lane-config-dat)# client-atm-address 39.000001415555121101020304.0800.200c.1000.02 name engRouter(lane-config-dat)# client-atm-address 39.0000001415555121101020304.0800.200c.2000.02 name engRouter(lane-config-dat)# client-atm-address 39.000001415555121101020304.0800.200c.3000.02 name mktRouter(lane-config-dat)# client-atm-address 39.000001415555121101020304.0800.200c.4000.01 name mktRouter(lane-config-dat)# default-name manRouter(lane-config-dat)# exitRelated Commands
network-clock-select (ATM)
To establish the sources and priorities of the requisite clocking signals for an ATM-CES port adapter, use the network-clock-select command in global configuration mode. To remove the clock source, use the no form of this command.
network-clock-select priority {cbr | atm} slot/port
no network-clock-select priority {cbr | atm} slot/port
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
To support synchronous or synchronous residual time stamp (SRTS) clocking modes on the CBR interface, you must specify a primary reference source to synchronize the flow of CBR data from its source to its destination.
You can specify up to four clock priorities. The highest priority active interface in the router supplies primary reference source to all other interfaces that require network clock synchronization services. The fifth priority is the local oscillator on the ATM-CES port adapter.
Use the show network-clocks command to display currently configured clock priorities on the router.
Examples
The following example defines two clock priorities on the router:
network-clock-select 1 cbr 2/0network-clock-select 2 atm 2/0Related Commands
network-id
To specify the network ID of a Multiprotocol over ATM (MPOA) server (MPS), use the network-id command in MPS configuration mode. To revert to the default value (default value is 1), use the no form of this command.
network-id id
no network-id
Syntax Description
Defaults
The default value for the 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 nonbroadcast multiaccess (NBMA) clouds artificially by administration.
Examples
The following example shows how to set the network ID to 5:
Router(mpoa-server-config)# network-id 5oam ais-rdi
To configure an ATM permanent virtual circuit (PVC) to be brought down after a specified number of Operation, Administration, and Maintenance (OAM) alarm indication signal/remote defect indication (AIS/RDI) cells have been received on the PVC or brought up if no OAM AIS/RDI cells have been received in a specified interval, use the oam ais-rdi command in ATM VC configuration or VC class configuration mode. To return OAM AIS/RDI behavior to the default, use the no form of this command.
oam ais-rdi [down-count [up-count]]
no oam ais-rdi [down-count [up-count]]
Syntax Description
Defaults
Down count: 1
Up count: 3Command Modes
ATM VC configuration
VC class configurationCommand History
Usage Guidelines
The default values for the OAM AIS/RDI down count and up count are used in the following situations:
•
•
•
If the oam ais-rdi command is entered without the up-count or down-count argument, the command will not appear in the show running-config command output.
Examples
In the following example, PVC 0/400 will be brought down after 25 consecutive OAM AIS/RDI cells have been received on the PVC. The PVC will be brought up when no OAM AIS/RDI cells have been received for 5 seconds.
interface ATM2/0/0ip address 172.2.222.20 255.255.255.0no ip route-cache cefno ip route-cache distributedno atm ilmi-keepalivepvc 0/400protocol ip 172.2.223.21oam-pvc manage 30oam ais-rdi 25 5oam retry cc
To set the frequency at which ATM Operation, Administration, and Maintenance (OAM) F5 continuity check (CC) activation and deactivation requests are sent to a device at the other end of a segment or permanent virtual circuit (PVC), use the oam retry cc command in ATM virtual circuit configuration mode. To remove the retry settings, use the no form of this command.
oam retry cc {end | segment} [activation-count [deactivation-count [retry-frequency]]]
no oam retry cc {end | segment} [activation-count [deactivation-count [retry-frequency]]]
Syntax Description
Defaults
Activation count: 3
Deactivation count: 3
Retry frequency: 30 secondsCommand Modes
ATM virtual circuit configuration
Command History
Examples
The following example shows how to configure ATM OAM F5 CC support over the segment and configure the router to function as the source. The frequency at which CC activation and deactivation requests will be sent over the segment is also configured.
interface atm 0ip address 10.0.0.3 255.255.255.0pvc 0/40oam-pvc manage cc segment direction sourceoam retry cc segment 10 10 30Related Commands
oam-pvc manage cc deny
Configures ATM OAM F5 CC management.
oam-pvc manage cc deny
Disables ATM OAM F5 CC support and configures the PVC to deny CC activation requests.
oam retry
To configure parameters related to Operation, Administration, and Maintenance (OAM) management for an ATM permanent virtual circuit (PVC), switched virtual circuit (SVC), VC class, or VC bundle, or label-controlled ATM (LC-ATM) VC, use the oam retry command in the appropriate command mode. To remove OAM management parameters, use the no form of this command.
oam retry up-count down-count retry-frequency
no oam retry
Syntax Description
Defaults
ATM PVCs and SVCs
up-count: 3
down-count: 5
retry-frequency: 1 secondLC-ATM VCs
up-count: 2
down-count: 2
retry-frequency: 2 secondsCommand Modes
Interface-ATM-VC configuration (for an ATM PVC or SVC)
VC-class configuration (for a VC class)
Bundle configuration mode (for a VC bundle)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)
Control-VC configuration (for an LC-ATM VC)Command History
Usage Guidelines
The following guidelines apply to PVCs, SVCs, and VC classes. They do not apply to LC-ATM VCs.
•
–
–
–
–
•
•
–
–
–
Examples
The following example shows how to configure the OAM management parameters with an up count of 3, a down-count of 3, and the retry frequency set at 10 seconds:
Router(cfg-mpls-atm-cvc)# oam retry 3 3 10Related Commands
oam-pvc manage cc deny
To disable ATM Operation, Administration, and Maintenance (OAM) F5 continuity check (CC) support and configure a permanent virtual circuit (PVC) to deny CC activation requests, use the oam-pvc manage cc deny command in ATM virtual circuit configuration mode. To reenable OAM F5 CC support and allow CC activation requests, use the no form of this command.
oam-pvc manage cc {end | segment} deny
no oam-pvc manage cc {end | segment} deny
Syntax Description
Defaults
If the peer device sends the activation message, F5 CC management will be enabled on the PVC.
Command Modes
ATM virtual circuit configuration
Command History
Usage Guidelines
Use the oam-pvc manage cc deny command to configure a permanent virtual circuit (PVC) to respond to activation requests from a peer device with "activation denied" messages. The oam-pvc manage cc deny command prevents ATM OAM F5 CC management from being activated on the PVC.
Use the no oam-pvc manage cc command to send a deactivation request to the peer device. The no oam-pvc manage cc command will disable ATM OAM F5 CC management on the PVC until the PVC receives an activation request. When the PVC receives an activation request, ATM OAM F5 CC management will be reenabled.
Examples
The following example shows how to disable ATM OAM F5 CC support and configure the VC to deny CC activation requests:
interface atm 0ip address 10.0.0.3 255.255.255.0pvc 0/40oam-pvc manage cc segment denyRelated Commands
oam-pvc manage cc
To configure ATM Operation, Administration, and Maintenance (OAM) F5 continuity check (CC) management, use the oam-pvc manage cc command in ATM virtual circuit configuration mode. To disable OAM F5 continuity checking, use the no form of this command.
oam-pvc manage cc {end | segment} [direction {both | sink | source}] [keep-vc-up [end aisrdi failure | seg aisrdi failure]]
no oam-pvc manage cc {end | segment} [deactivate-down-vc] [direction {both | sink | source}] [keep-vc-up [end aisrdi failure | seg aisrdi failure]]
Syntax Description
Defaults
The default direction is sink.
Command Modes
ATM virtual circuit configuration
Command History
Usage Guidelines
ATM OAM F5 continuity checking enables OAM to support the use of F5 segment and end-to-end CC cells to detect connectivity failures.
It is not necessary to enter a CC configuration on the router at the other end of a segment. The router on which CC management has been configured sends a CC activation request to the router at the other end of the segment, directing it to act as either a source or a sink.
Use the oam-pvc manage cc deny command to configure a permanent virtual circuit (PVC) to respond to activation requests from a peer device with "activation denied" messages. The oam-pvc manage cc deny command prevents ATM OAM F5 CC management from being activated on the PVC.
Use the no oam-pvc manage cc command to send a deactivation request to the peer device. The no oam-pvc manage cc command will disable ATM OAM F5 CC management on the PVC until the PVC receives an activation request. When the PVC receives an activation request, ATM OAM F5 CC management will be reenabled.
The no oam-pvc manage cc {end | segment} deactivate-down-vc command does not disable ATM OAM F5 CC support. This command causes OAM F5 CC deactivation messages to be sent over the VC when the VC goes down.
To enable the SNMP notifications that support ATM OAM F5 continuity checking, use the snmp-server enable traps atm pvc extension command.
Examples
ATM OAM F5 CC Support on a PVC Configuration Example
The following example shows how to configure ATM OAM F5 CC support over the segment and configure the router to function as the source. The frequency at which CC activation and deactivation requests will be sent over the segment is also configured.
interface atm 0ip address 10.0.0.3 255.255.255.0pvc 0/40oam-pvc manage cc segment direction sourceoam retry cc segment 10 10 30Deactivation of ATM OAM F5 CC upon VC Failure Example
The following example shows how to configure OAM to send a CC deactivation request across the segment when PVC 0/1 goes down:
interface atm 0ip address 10.0.0.3 255.255.255.0pvc 0/40no oam-pvc manage cc segment deactivate-down-vcRelated Commands
oam-pvc
To enable end-to-end F5 Operation, Administration, and Maintenance (OAM) loopback cell generation and OAM management for an ATM permanent virtual circuit (PVC), virtual circuit (VC) class, or label-controlled ATM (LC-ATM) VC, use the oam-pvc command in the appropriate command mode. To disable generation of OAM loopback cells and OAM management, use the no form of this command.
ATM VC or VC Class
oam-pvc [manage] [frequency]
no oam-pvc [manage]
LC-ATM VC
oam-pvc manage [frequency]
no oam-pvc manage
Loopback Mode Detection
oam-pvc manage [frequency] loop-detection
no oam-pvc manage loop-detection
Syntax Description
Command Default
Disabled.
Command Modes
Interface-ATM-VC configuration (for an ATM PVC or Loopback Mode Detection)
VC-class configuration (for a VC class)
PVC-in-range configuration (for an individual PVC within a PVC range)
Control-VC configuration (for enabling OAM management on an LC-ATM VC)Command History
Usage Guidelines
If OAM management is enabled, further control of OAM management is configured using the oam retry command.
ATM VCS or VC Classes
If the oam-pvc command is not explicitly configured on an ATM PVC, the PVC inherits the following default configuration (listed in order of precedence):
•
•
•
•
Loopback Mode Detection
When a PVC traverses an ATM cloud and OAM is enabled, the router sends a loopback cell to the other end and waits for a response to determine whether the circuit is up. If an intervening router within the ATM cloud is in loopback mode, however, the router considers the circuit to be up, when in fact the other end is not reachable.
When enabled, the Loopback Mode Detection Through OAM feature detects when an intervening router is in loopback mode, in which case it sets the OAM state to NOT_VERIFIED. This prevents traffic from being routed on the PVC for as long as any intervening router is detected as being in loopback mode.
Examples
The following example shows how to enable end-to-end F5 OAM loopback cell transmission and OAM management on an ATM PVC with a transmission frequency of 3 seconds:
Router(cfg-mpls-atm-cvc)# oam-pvc manage 3The following example shows how to enable end-to-end F5 OAM loopback cell transmission and OAM management on an LC-ATM interface with a transmission frequency of 2 seconds:
Router(config)# interface Switch1.10 mplsRouter(config-subif)# ip unnumbered Loopback0Router(config-subif)# mpls atm control-vc 0 32Router(cfg-mpls-atm-cvc)# oam-pvc manage 2The following example shows how to create a PVC and enable loopback detection:
Router(config)# interface ATM1/0Router(config-if)# pvc 4/100Router(config-if-atm-vc)# oam-pvc manage loop-detectionRelated Commands
oam-range
To enable end-to-end F5 Operation, Administration, and Maintenance (OAM) loopback cell generation and OAM management for an ATM permanent virtual circuit (PVC) range, use the oam-range command in PVC range configuration mode. To disable generation of OAM loopback cells and OAM management, use the no form of this command.
oam-range [manage] [frequency]
no oam-range [manage] [frequency]
Syntax Description
manage
(Optional) Enables OAM management.
frequency
(Optional) Time delay (0 to 600 seconds) between transmissions of OAM loopback cells.
Defaults
10 seconds
Command Modes
PVC range configuration
Command History
Usage Guidelines
If OAM management is enabled, further control of OAM management is configured using the oam retry command.
If the oam-range command is not explicitly configured for an ATM PVC range, the range inherits the following default configuration (listed in order of precedence):
•
•
•
•
Examples
The following example enables end-to-end F5 OAM loopback cell transmission and OAM management on an ATM PVC range called "range1" with a transmission frequency of 11 seconds:
interface atm 6/0.1range range1 pvc 7/101 7/103oam-range manage 11oam retry 8 9 10Related Commands
oam-svc
To enable end-to-end F5 Operation, Administration, and Maintenance (OAM) loopback cell generation and OAM management for an ATM switched virtual circuit (SVC) or virtual circuit (VC) class, use the oam-svc command in the appropriate command mode. To disable generation of OAM loopback cells and OAM management, use the no form of this command.
oam-svc [manage] [frequency]
no oam-svc [manage] [frequency]
Syntax Description
manage
(Optional) Enable OAM management.
frequency
(Optional) Time delay (0 to 600 seconds) between transmitting OAM loopback cells.
Defaults
10 seconds
Command Modes
Interface-ATM-VC configuration (for an ATM SVC)
VC-class configuration (for a VC class)Command History
Usage Guidelines
If OAM management is enabled, further control of OAM management is configured using the oam retry command.
Note
If the oam-svc command is not explicitly configured on an ATM SVC, the SVC inherits the following default configuration (listed in order of precedence):
•
•
•
•
Examples
The following example enables end-to-end F5 OAM loopback cell transmission and OAM management on an ATM SVC with a transmission frequency of 3 seconds:
oam-svc manage 3Related Commands
oam retry
Configures parameters related to OAM management for an ATM PVC, SVC, or VC class.
partial-fill
To configure the number of AAL1 user octets per cell for the ATM circuit emulation service (CES) on the OC-3/STM-1 Circuit Emulation Service network module, use the partial-fill command in interface-CES-VC mode. To delete the CES partial-fill value, use the no form of this command.
partial-fill octet
no partial-fill octet
Syntax Description
Defaults
No partial-fill
Command Modes
Interface-CES-VC configuration
Command History
Usage Guidelines
The partial-fill command applies to CES switched virtual circuits (SVCs) and permanent virtual circuits (PVCs) configured on Cisco 2600 series and Cisco 3600 series routers that have OC-3/STM-1 ATM CES network modules.
Examples
The following example sets the CES partial cell fill to 50 octets per cell for SVC "ces1":
interface atm 1/0svc ces1 nsap 47.00.00......01.01.00 cespartial fill 40Related Commands
svc
Creates an ATM SVC and specifies the destination NSAP address on a main interface or subinterface.
ping atm interface atm
To perform an ATM Operation Administration Maintenance (OAM) ping on a specific permanent virtual circuit (PVC), use the ping atm interface atm command in privileged EXEC mode.
ping atm interface atm interface-number vpi-value vci-value [end-loopback [repeat [timeout]] | seg-loopback [repeat [timeout]]]
Syntax Description
Defaults
End loopback
Repeats: 5
Timeout interval: 2 secondsCommand Modes
Privileged EXEC
Command History
Usage Guidelines
The ping atm interface atm command sends an OAM packet and indicates when a response is received. It can be used either in normal mode or in interactive mode. The ping atm interface atm command provides two ATM OAM ping options:
•
•
Examples
In the following example, an ATM OAM ping with a 15-second timeout verifies end-to-end connectivity for PVC 0/500 in the normal mode:
Router# ping atm interface atm1/1.1 0 500 end-loopback 30 15Type escape sequence to abort.Sending 30, 53-byte end-to-end OAM echoes, timeout is 15 seconds:!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Success rate is 100 percent (30/30), round-trip min/avg/max = 1/1/4 msIn the following example, an ATM OAM ping verifies connectivity to the first-hop ATM switch on PVC 1/100 in the normal mode:
Router# ping atm interface atm1/1.1 0 500 seg-loopback 30 10Type escape sequence to abort.Sending 30, 53-byte segment OAM echoes, timeout is 10 seconds:!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Success rate is 100 percent (30/30), round-trip min/avg/max = 1/1/4 msTable 2 describes the output of the ping atm interface atm command.
The following example verifies connectivity to the neighboring ATM device for the ATM PVC with the virtual path identifier (VPI) / virtual channel identifier (VCI) value 0/500 in the interactive mode:
Router# pingProtocol [ip]:atmATM Interface:atm1/1.1VPI value [0]:0VCI value [1]:500Loopback - End(0), Segment(1) [0]:1Repeat Count [5]:Timeout [2]:Type escape sequence to abort.Sending 5, 53-byte segment OAM echoes, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 msTable 3 describes the ping fields shown in the display.
Related Commands
protect
To configure a virtual circuit (VC) class with protected group or protected VC status for application to a VC bundle member, use the protect command in vc-class configuration mode. To remove the protected status from the VC class, use the no form of this command.
To configure a specific VC or permanent virtual circuit (PVC) as part of a protected group of the bundle or to configure it as an individually protected VC or PVC bundle member, use the protect command in bundle-vc configuration mode. To remove the protected status from the VC or PVC, use the no form of this command.
protect {group | vc}
no protect {group | vc}
Syntax Description
group
Configures the VC or PVC bundle member as part of the protected group of the bundle.
vc
Configures the VC or PVC member as individually protected.
Defaults
The VC or PVC neither belongs to the protected group nor is it an individually protected VC or PVC.
Command Modes
VC-class configuration (for a VC class)
Bundle-vc configuration (for ATM VC bundle members)
Command History
Usage Guidelines
Use the protect command in vc-class configuration mode to configure a VC class to contain protected group or individual protected VC status. When the class is applied to the VC bundle member, that VC is characterized by the protected status. You can also apply this command directly to a VC in bundle-vc configuration mode.
When a protected VC goes down, it takes the bundle down. When all members of a protected group go down, the bundle goes down.
To use the protect command in vc-class configuration mode, first enter the vc-class atm global configuration command.
The protect command has no effect if the VC class that contains the command is attached to a standalone VC, that is, if the VC is not a bundle member.
To use the protect command in bundle-vc configuration mode, first enter the bundle command to enact bundle configuration mode for the bundle containing the VC member to be configured. Then enter the pvc-bundle configuration command to add the VC to the bundle as a member of it.
VCs in a VC bundle are subject to the following configuration inheritance guidelines (listed in order of next highest precedence):
•
•
•
Examples
The following example configures a class called "control-class" to include a protect command, which, when applied to a VC bundle member, configures the VC as an individually protected VC bundle member. When this protected VC goes down, it takes the bundle down.
vc-class atm control-classprotect vcRelated Commands
protocol (ATM)
To configure a static map for an ATM permanent virtual circuit (PVC), switched virtual circuit (SVC), or virtual circuit (VC) class or to enable Inverse Address Resolution Protocol (ARP) or Inverse ARP broadcasts on an ATM PVC, use the protocol command in the appropriate mode. To remove a static map or disable Inverse ARP, use the no form of this command.
protocol protocol {protocol-address [virtual-template] | inarp} [[no] broadcast]
no protocol protocol {protocol-address [virtual-template] | inarp} [[no] broadcast]
Syntax Description
Defaults
Inverse ARP is enabled for IP and IPX if the protocol is running on the interface and no static map is configured.
Command Modes
Interface-ATM-VC configuration (for an ATM PVC or SVC)
VC-class configuration (for a VC class)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)Command History
Usage Guidelines
Command Application
Use this command to perform either of the following tasks:
•
•
PVC range and PVC-in-range configuration modes support only the protocols that do not require static map configuration. Those protocol options are ip and ipx.
Default Configurations
If the protocol command is not explicitly configured on an ATM PVC or SVC, the VC inherits the following default configuration (listed in order of precedence):
•
•
•
•
Examples
The following example creates a static map on a VC, indicates that 10.68.34.237 is connected to this VC, and sends ATM pseudobroadcasts:
protocol ip 10.68.34.237 broadcastThe following example enables Inverse ARP for IPX and does not send ATM pseudobroadcasts:
protocol ipx inarp no broadcastThe following example removes a static map from a VC and restores the default behavior for Inverse ARP (Refer to the "Default" section described above):
no protocol ip 10.68.34.237In the following example, the VC carries PPP traffic and its associated parameters.
protocol ppp 10.68.34.237 virtual-templatepvc
To create or assign a name to an ATM permanent virtual circuit (PVC), to specify the encapsulation type on an ATM PVC, and to enter ATM virtual circuit configuration mode, use the pvc command in interface configuration mode or subinterface configuration mode. To remove an ATM PVC from an interface, use the no form of this command.
pvc [name] vpi/vci [ces | ilmi | qsaal | smds | l2transport]
no pvc [name] vpi/vci [ces | ilmi | qsaal | smds | l2transport]
Syntax Description
Defaults
No PVC is defined. When a PVC is defined, the global default of the encapsulation command applies (aal5snap).
Command Modes
Interface configuration
Subinterface configurationCommand History
Usage Guidelines
Creating and Configuring PVCs
The pvc command replaces the atm pvc command. Use the pvc command to configure a single ATM VC only, not a VC that is a bundle member. We recommend that you use the pvc command in conjunction with the encapsulation and random-detect attach commands instead of the atm pvc command.
The pvc command creates a PVC and attaches it to the VPI and VCI specified. Both the vpi and vci arguments cannot be simultaneously specified as 0; if one is 0, the other cannot be 0.
When configuring an SVC, use the pvc command to configure the PVC that handles SVC call setup and termination. In this case, specify the qsaal keyword. See the second example that follows.
ATM PVC Names
Once you specify a name for a PVC, you can reenter ATM virtual circuit configuration mode by simply entering the pvc name command. You can remove a PVC and any associated parameters by entering no pvc name or no pvc vpi/vci.
Note
Encapsulation Types on ATM PVCs
Specify CES, ILMI, QSAAL, or SMDS as the encapsulation type on an ATM PVC. (To configure other encapsulations types, see the encapsulation command.)
Configuring CES encapsulation on a PVC is equivalent to creating a constant bit rate (CBR) class of service.
Rate Queues
The Cisco IOS software dynamically creates rate queues as necessary to satisfy the requests of the pvc commands.
Default Configurations
If ilmi, qsaal, or smds encapsulation is not explicitly configured on the ATM PVC, the PVC inherits the following default configuration (listed in order of precedence):
•
•
•
•
Examples
The following example creates a PVC with VPI 0 and VCI 16, and communication is set up with the ILMI:
pvc cisco 0/16 ilmiexitThe following example creates a PVC used for ATM signaling for an SVC. It specifies VPI 0 and VCI 5:
pvc cisco 0/5 qsaalexitThe following example configures the PVC called "cisco" to use class-based weighted fair queueing (CBWFQ). It attaches a policy map called "policy1" to the PVC. The classes that make up "policy1" determine the service policy for the PVC:
pvc cisco 0/5 service-policy output policy1vbr-nrt 2000 2000 encap aal5snapRelated Commands
atm vc-per-vp
Sets the maximum number of VCIs to support per VPI.
pvc-bundle
Adds a PVC to a bundle as a member of the bundle.
qos-group (ATM VC bundle member)
To associate a quality of service (QoS) group or groups with a permanent virtual circuit (PVC) bundle member, use the qos-group command in ATM VC bundle-member configuration mode. To disassociate a QoS group or groups from a PVC bundle member, use the no form of this command.
qos-group qos-groups
no qos-group qos-groups
Syntax Description
Command Default
No QoS groups are associated with the PVC bundle member.
Command Modes
ATM VC bundle-member configuration
Command History
Examples
The following example associates a single QoS group with a PVC bundle member:
Router> enablePassword:Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface atm 2/0Router(config-subif)# bundle ciscoRouter(config-if-atm-bundle)# selection-method qos-groupRouter(config-if-atm-bundle)# pvc 1/32Router(config-if-atm-member)# qos-group 1Router(config-if-atm-member)# endThe following example associates a range of QoS groups from 1 to 5 with a PVC bundle member:
Router> enablePassword:Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface atm 2/0Router(config-subif)# bundle ciscoRouter(config-if-atm-bundle)# selection-method qos-groupRouter(config-if-atm-bundle)# pvc 1/32Router(config-if-atm-member)# qos-group 1-5Router(config-if-atm-member)# endThe following example associates QoS groups 1 and 7 with a PVC bundle member:
Router> enablePassword:Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface atm 2/0Router(config-subif)# bundle ciscoRouter(config-if-atm-bundle)# selection-method qos-groupRouter(config-if-atm-bundle)# pvc 1/32Router(config-if-atm-member)# qos-group 1,7Router(config-if-atm-member)# endThe following example associates a range of QoS groups 1 to 5 and a range of QoS groups 7-10 with a PVC bundle member:
Router> enablePassword:Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface atm 2/0Router(config-subif)# bundle ciscoRouter(config-if-atm-bundle)# selection-method qos-groupRouter(config-if-atm-bundle)# pvc 1/32Router(config-if-atm-member)# qos-group 1-5,7-10Router(config-if-atm-member)# endRelated Commands
inarp-vc
Enables InARP for a PVC bundle member.
selection-method
Specifies the method for selection of the PVC bundle member.
retry (SVC)
To configure a router to periodically attempt to bring up an active switched virtual circuit (SVC) connection after the initial call setup failed, use the retry command in interface-CES-VC configuration mode. To disable the retry mechanism, use the no form of this command.
retry timeout-value [retry-limit] [first-retry-interval]
no retry
Syntax Description
Defaults
There is no default timeout-value.
retry-limit: 0
first-retry-interval: 10 secondsCommand Modes
Interface-CES-VC configuration
Command History
Usage Guidelines
This command is used on Cisco 2600 series and 3600 series routers that have OC-3/STM-1 ATM CES network modules.
The retry command applies only to active SVCs.
Examples
In the following example, the router is configured to make up to 20 attempts to bring up a connection on SVC "ces1". The interval between attempts is set at 10 seconds.
interface atm 1/0svc ces1 nsap 47.0091.81.000000.0040.0B0A.2501.ABC1.3333.3333.05 cesretry 10 20Related Commands
ces
Configures CES on a router port and enters CES configuration mode.
svc
Creates an ATM SVC and specifies the destination NSAP address on a main interface or subinterface.
Posted: Tue Feb 6 16:23:39 PST 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
