-
Cisco IOS Switching Services Command Reference, Release 12.2
-
About the Cisco IOS Software Documentation
-
Using Cisco IOS Software
-
Switching Commands: Introduction
-
Commands: access-list rate-limit through ip cef
-
Commands: ip cef accounting through lane fssrp
-
Commands: lane global-lecs-address through name elan-id
-
Commands: name local seg-id through show interface stats
-
Commands: show interface XTagATM through show ip mds summary
-
Commands: show ip mroute through show lane client
-
Commands: show lane config through show mpoa client cache
-
Commands: show mpoa client statistics through show tag-switching tdp bindings
-
Commands: show tag-switching tdp discovery through tunnel tsp-hop
-
Index
-
Feedback
Table Of Contents
mls rp ip multicast management-interface
mpls ip (global configuration)
mpls ip (interface configuration)
mpls traffic-eng administrative-weight
mpls traffic-eng attribute-flags
mpls traffic-eng flooding thresholds
mpls traffic-eng link-management timers bandwidth-hold
mpls traffic-eng link-management timers periodic-flooding
mpls traffic-eng link timers bandwidth-hold
mpls traffic-eng link timers periodic-flooding
mpls traffic-eng logging tunnel
mpls traffic-eng multicast-intact
mpls traffic-eng reoptimize events
mpls traffic-eng reoptimize timers frequency
mpls traffic-eng signalling advertise implicit-null
mpls traffic-eng tunnels (global)
mpls traffic-eng tunnels (interface)
mpoa server name trigger ip-address
lane global-lecs-address
To specify a list of LECS addresses to use when the addresses cannot be obtained from the 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
You must configure the same list of addresses on each interface that contains a LANE entity.
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 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 adds a static entry to the LE ARP table:
lane le-arp 0800.aa00.0101 47.000014155551212f.00.00.0800.200C.1001.01The following example adds a static entry to the LE ARP table binding segment number 1, bridge number 1 to the ATM address:
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 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 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 uses 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:
lane server-atm-address ...0800.200C.1001.**The following example uses 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:
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 LANE server and a broadcast and unknown server (BUS) on the specified subinterface with the 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 | tokenring} elan-name [elan-id id]
no lane server-bus {ethernet | tokenring} 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.
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 enables a LANE server and BUS for a Token Ring ELAN named MYELAN:
lane server-bus tokenring myelanRelated Commands
list
To show all or part of the explicit path or paths, use the list IP explicit path configuration command.
list [starting-index-number]
Syntax Description
starting-index-number
Index number at which the explicit path(s) will start to be displayed. Valid values are from 1 to 65535.
Defaults
No default behavior or values.
Command Modes
IP explicit path configuration
Command History
Examples
The following example shows the explicit path starting at index number 2:
Router(cfg-ip-expl-path)# listExplicit Path name Joe:1:next-address 10.0.0.12:next-address 10.0.0.2Router(cfg-ip-expl-path)# list 2Explicit Path name Joe:2:next-address 10.0.0.2Router(cfg-ip-expl-path)#Related Commands
mask destination
To specify the destination mask, use the mask destination destination-prefix aggregation cache configuration command. To disable the destination mask, use the no form of this command.
mask destination minimum value
no mask destination minimum value
Syntax Description
minimum
Configures the minimum value for the mask.
value
Specifies the value for the mask. Range is from 1 to 32.
Defaults
0
Command Modes
Destination-prefix aggregation cache configuration
Command History
Usage Guidelines
This command is only available with router-based aggregation. Minimum masking capability is not available if router-based aggregation is not enabled.
Examples
The following example shows how to configure the destination-prefix aggregation cache with a minimum mask value:
ip flow-aggregation cache destination-prefixmask destination minimum 32Related Commands
mask source
To specify the source mask, use the mask source source-prefix aggregation cache configuration command. To disable the source mask, use the no form of this command.
mask source minimum value
no mask source minimum value
Syntax Description
minimum
Configures the minimum value for the mask.
value
Specifies the value for the mask. Range is from 1 to 32.
Defaults
0
Command Modes
Source-prefix aggregation cache
Command History
Usage Guidelines
This command is only available with router-based aggregation. Minimum masking capability is not available if router-based aggregation is not enabled.
Examples
The following example shows how to configure the source-prefix aggregation cache with a minimum mask value:
ip flow-aggregation cache source-prefixmask source minimum 30Related Commands
maximum routes
To limit the maximum number of routes in a VRF to prevent a PE router from importing too many routes, use the maximum routes command in VRF configuration submode. To remove the limit on the maximum number of routes allowed, use the no form of this command.
maximum routes limit {warn threshold | warn-only}
no maximum routes
Syntax Description
Defaults
No default behavior or values.
Command Modes
VRF configuration
Command History
Usage Guidelines
To use the maximum routes command, you must enter the VRF configuration submode. In this submode you create a VRF routing table and assign a route distinguisher in one of the following formats:
•
•
You then create a route-target extended community for a VRF and specify the import, export, or both arguments for the route-target command. These arguments allow you to configure a router to import and export routing information to the target VPN extended community.
Examples
In the following example, the route distinguisher ASN is 100, and the maximum number of VRF routes to allow is set to 1000. When the maximum routes for the VRF reaches 1000, the router issues a syslog error message, but continues to accept new VRF routes.
ip vrf vrf1rd 100:1route-target import 100:1maximum routes 1000 warn-onlyRelated Commands
metric-style narrow
To configure a router running IS-IS so that it generates and accepts old-style type, length, and value objects (TLVs), use the metric-style narrow router configuration command. To disable this feature, use the no form of this command.
metric-style narrow [transition ] [ { level-1 | level-2 | level-1-2 }]
no metric-style narrow [transition ] [ { level-1 | level-2 | level-1-2 }]
Syntax Description
Defaults
The MPLS traffic engineering image generates only old-style TLVs. To do MPLS traffic engineering, a router must generate new-style TLVs that have wider metric fields.
Command Modes
Router configuration
Command History
Examples
In the following example, the router is instructed to generate and accept old-style TLVs on router level 1:
Router(config-router)# metric-style narrow level-1Related Commands
Configures a router to generate both old-style and new-style TLVs.
Configures a router to generate and accept only new-style TLVs.
metric-style transition
To configure a router running IS-IS so that it generates and accepts both old-style and new-style type, length, and value objects (TLVs), use the metric-style transition router configuration command. To disable this feature, use the no form of this command.
metric-style transition [{level-1 | level-2 | level-1-2}]
no metric-style transition [{level-1 | level-2 | level-1-2}]
Syntax Description
level-1
(Optional) Enables this command on routing level 1.
level-2
(Optional) Enables this command on routing level 2.
level-1-2
(Optional) Enables this command on routing levels 1 and 2.
Defaults
The MPLS traffic engineering image generates only old-style TLVs. To do MPLS traffic engineering, a router must generate new-style TLVs that have wider metric fields.
Command Modes
Router configuration
Command History
Examples
In the following example, a router is configured to generate and accept both old-style and new-style TLVs on router level 2:
Router(config-router)# metric-style transition level-2Related Commands
Configures a router to generate and accept old-style TLVs.
Configures a router to generate and accept only new-style TLVs.
metric-style wide
To configure a router running IS-IS so that it generates and accepts only new-style type, length, and value objects (TLVs), use the metric-style wide router configuration command. To disable this feature, use the no form of this command.
metric-style wide [transition][{level-1 | level-2 | level-1-2}]
no metric-style wide [transition][{level-1 | level-2 | level-1-2}]
Syntax Description
Defaults
The MPLS traffic engineering image generates only old-style TLVs. To do MPLS traffic engineering, a router must generate new-style TLVs that have wider metric fields.
Command Modes
Router configuration
Command History
Usage Guidelines
If you enter the metric-style wide command, a router generates and accepts only new-style TLVs. Therefore, the router uses less memory and other resources than it would if it generated both old-style and new-style TLVs.
This style is appropriate for enabling MPLS traffic engineering across an entire network.
Note
Examples
In the following example, a router is configured to generate and accept only new-style TLVs on level 1:
Router(config-router)# metric-style wide level-1Related Commands
Configures a router to generate and accept old-style TLVs.
Configures a router to generate and accept both old-style and new-style TLVs.
mls rp ip
To enable Multilayer Switching Protocol (MLSP), use the mls rp ip command in global configuration mode. To disable MLS, use the no form of this command.
mls rp ip
no mls rp ip
Syntax Description
There are no arguments or keywords for this command.
Defaults
The default is MLS disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to enable MLS, either globally or on a specific interface. MLSP is the protocol that runs between the switches and routers.
Examples
The following example enables MLS:
mls rp ipRelated Commands
mls rp ip multicast
To enable IP multicast Multilayer Switching (hardware switching) on an external or internal router in conjunction with Layer 3 switching hardware for the Catalyst 5000, use the mls rp ip multicast command in interface configuration mode. To disable IP multicast Multilayer Switching (MLS) on the interface or VLAN, use the no form of this command.
mls rp ip multicast
no mls rp ip multicast
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This feature is available only on specific router platforms connected to a Catalyst 5000 switch. Use this feature to reduce multicast load on the router. The switch will perform the multicast packet replication and forwarding.
IP multicast MLS is enabled by default on an interface once IP multicast routing and PIM are enabled.
Examples
The following example disables IP multicast MLS:
interface fastethernet1/0.1 no mls rp ip multicastRelated Commands
mls rp ip multicast management-interface
To assign a different interface (other than the default) to act as the management interface for Multilayer Switching Protocol (MLSP), use the mls rp ip multicast management-interface command in interface configuration mode. To restore the default interface as the management interface, use the no form of this command.
mls rp ip multicast management-interface
no mls rp ip multicast management-interface
Syntax Description
This command has no arguments or keywords.
Defaults
When IP multicast MLS is enabled, the subinterface (or VLAN interface) that has the lowest VLAN ID and is active (in the "up" state) is automatically selected as the management interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
When you enable IP multicast MLS, the subinterface (or VLAN interface) that has the lowest VLAN ID and is active (in the "up" state) is automatically selected as the management interface. The one-hop protocol MLSP is used between a router and a switch to pass messages about hardware-switched flows. MLSP packets are sent and received on the management interface. Typically, the interface in VLAN 1 is chosen (if that interface exists). Only one management interface is allowed on a single trunk link.
In most cases, we recommend that the management interface be determined by default. However, you can optionally use this command to specify a different router interface or subinterface as the management interface. We recommend using a subinterface with minimal data traffic so that multicast MLSP packets can be sent and received more quickly.
If the user-configured management interface goes down, the router uses the default interface (the active interface with the lowest VLAN ID) until the user-configured interface comes up again.
Examples
The following example configures the Fast Ethernet interface as the management interface:
interface fastethernet1/0.1 mls rp ip multicast management-interfaceRelated Commands
Enables IP multicast MLS (hardware switching) on an external or internal router in conjunction with Layer 3 switching hardware for the Catalyst 5000 switch.
mls rp ipx (global)
To enable the router as an IPX Multilayer Switching (MLS) Route Processor (RP), use the mls rp ipx command in global configuration. To disable IPX MLS on the router, use the no form of this command.
mls rp ipx
no mls rp ipx
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
Multilayer Switching Protocol (MLSP) is the protocol that runs between the MLS Switching Engine and the MLS RP.
Examples
The following example enables IPX MLS on the MLS RP:
mls rp ipxRelated Commands
mls rp ipx (interface)
To enable IPX MLS on a router interface, use the mls rp ipx command in interface configuration mode. To disable IPX MLS on a router interface, use the no form of this command.
mls rp ipx
no mls rp ipx
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
Multilayer Switching Protocol (MLSP) is the protocol that runs between the MLS Switching Engine and the MLS RP.
Examples
The following example enables IPX MLS on a router interface:
mls rp ipxRelated Commands
mls rp locate ipx
To display information about all switches currently shortcutting for the specified IPX flows, use the mls rp locate ipx command in privileged EXEC mode.
mls rp locate ipx destination-network.destination-node [source-network]
Syntax Description
Defaults
None
Command Modes
Privileged EXEC
Command History
Examples
This example displays the switch that is shortcutting routed flows to the specified IPX flow:
mls rp locate ipx 30.0000.1111.2222locator response from switch id 0010.1400.601fRelated Commands
mls rp management-interface
To specify an interface as the management interface, use the mls rp management-interface command in interface configuration mode. To remove an interface as the management interface, use the no form of this command.
mls rp management-interface
no mls rp management-interface
Syntax Description
This command has no keywords or arguments.
Defaults
None
Command Modes
Interface configuration
Command History
Usage Guidelines
Multilayer Switching Protocol (MLSP) packets are sent and received through the management interface.
Select only one IPX Multilayer Switching (MLS) interface connected to the switch. If you fail to select this interface, no connection between the MLS Route Processor (RP) and the MLS Switching Engine will occur, and any routing updates or changes to access lists will not be reflected on the switch.
Examples
The following example selects a management interface:
mls rp management-interfaceRelated Commands
mls rp nde-address
To specify a NetFlow Data Export address, use the mls rp nde-address command in global configuration mode.
mls rp nde-address ip-address
Syntax Description
Defaults
No default behaviors or values.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command on an RP to specify the NetFlow Data Export address for a router. If you do not specify an NDE IP address for the MLS RP, the MLS RP automatically selects one of its interface's IP addresses and uses that IP address as its NDE IP address and its MLS IP address.
Examples
The following example sets the NDE address to 170.25.2.1:
mls rp nde-address 170.25.2.1Related Commands
mls rp vlan-id
To assign a virtual LAN (VLAN) identification number to an IPX MLS interface, use the mls rp vlan-id command in interface configuration mode. To remove a VLAN identification number, use the no form of this command.
mls rp vlan-id vlan-id-number
no mls rp vlan-id vlan-id-number
Syntax Description
Defaults
None
Command Modes
Interface configuration
Command History
Usage Guidelines
The assigned IPX MLS interface must be either an Ethernet or Fast Ethernet interface—both without subinterfaces.
Examples
The following example assigns the VLAN identification number 23 to an IPX MLS interface:
mls rp vlan-id 23Related Commands
mls rp vtp-domain
To assign a Multilayer Switching (MLS) interface to a specific Virtual Trunk Protocol (VTP) domain on the MLS Route Processor (RP), use the mls rp vtp-domain command in interface configuration mode. To remove a VTP domain, use the no form of this command.
mls rp vtp-domain domain-name
no mls rp vtp-domain domain-name
Syntax Description
Defaults
The interface is assigned to the null domain.
Command Modes
Interface configuration
Command History
Usage Guidelines
The assigned IPX MLS interface must be either an Ethernet or Fast Ethernet interface—both without subinterfaces.
Examples
The following example assigns the MLS interface to the VTP domain named engineering:
mls rp vtp-domain engineeringRelated Commands
mpls atm control-vc
To configure the VPI and VCI to be used for the initial link to the label switching peer device, use the mpls atm control-vc interface configuration command. To clear the interface configuration, use the no form of this command.
mpls atm control-vc vpi vci
no mpls atm control-vc vpi vci
Syntax Description
Defaults
If the subinterface has not changed to a VP tunnel, the default is 0/32. If the subinterface corresponds to VP tunnel VPI X, the default is X/32.
Command Modes
Interface configuration
Command History
11.1 CT
This command was introduced.
12.1(3)T
This command was modified to reflect new MPLS IETF terminology.
Usage Guidelines
The initial link is used to establish the TDP session and to carry non-IP traffic. For a router interface (for example, an AIP), ATM label switching can be enabled only on a label-switch subinterface.
Note
On the Cisco LightStream 1010 ATM switch, a subinterface corresponds to a VP tunnel; thus, the entry in the VPI field of the control-vc must match the entry in the VPI field of the VP tunnel.
Examples
The following commands create a label switching subinterface on a router and select VPI 1 and VCI 34 as the control VC:
Router(config)# interface atm4/0.1 mplsRouter(config-if)# mpls ipRouter(config-if)# mpls atm control-vc 1 34Related Commands
show mpls interfaces
Displays information about one or more interfaces for which label switching has been enabled.
mpls atm vpi
To configure the range of values to be used in the VPI field for label VCs, use the mpls atm vpi interface configuration command. To clear the interface configuration, use the no form of this command.
mpls atm vpi vpi [- vpi]
no mpls atm vpi vpi [- vpi]
Syntax Description
vpi
Virtual path identifier (low end of range).
- vpi
(Optional) Virtual path identifier (high end of range).
Defaults
The default is 1-1.
Command Modes
Interface configuration
Command History
11.1 CT
This command was introduced.
12.1(3)T
This command was modified to reflect new MPLS IETF terminology.
Usage Guidelines
To configure ATM label switching on a router interface (for example, an ATM interface processor), you must enable a label switching subinterface.
Note
Use this command to select an alternate range of VPI values for ATM label assignment on this interface. The two ends of the link negotiate a range defined by the intersection (overlapping of labels in common) of the range configured at each end of the connection.
Examples
In the following example, a subinterface is created and a VPI range from 1 to 3 is selected:
Router(config)# interface atm4/0.1 mplsRouter(config-if)# mpls ipRouter(config-if)# mpls atm vpi 1-3Related Commands
mpls atm control-vc
Configures the VPI and VCI to be used for the initial link to the label switching peer device.
mpls ip (global configuration)
To enable MPLS forwarding of IPv4 packets along normally routed paths for the platform, use the mpls ip global configuration command. To disable this feature, use the no form of this command.
mpls ip
no mpls ip
Syntax Description
This command has no arguments or keywords.
Defaults
Label switching of IPv4 packets along normally routed paths is enabled for the platform.
Command Modes
Global configuration
Command History
Usage Guidelines
This command enables MPLS forwarding of IPv4 packets along normally routed paths (sometimes called dynamic label switching). For a given interface to perform dynamic label switching, this function must be enabled for the interface and the platform.
The no form of this command stops dynamic label switching for all platform interfaces, regardless of the interface configuration; it also stops distribution of labels for dynamic label switching. However, the no form of this command does not affect the sending of labeled packets through TSP tunnels.
For an LC-ATM interface, the no form of this command prevents the establishment of label VCs originating at, terminating at, or passing through the platform.
Examples
In the following example, dynamic label switching is disabled for the platform, terminating all label distribution for the platform:
Router(config)# no mpls ipRelated Commands
Enables label switching of IPv4 packets along normally routed paths for the associated interface.
mpls ip (interface configuration)
To enable MPLS forwarding of IPv4 packets along normally routed paths for a particular interface, use the mpls ip interface configuration command. To disable this feature, use the no form of this command.
mpls ip
no mpls ip
Syntax Description
This command has no arguments or keywords.
Defaults
MPLS forwarding of IPv4 packets along normally routed paths for the interface is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
MPLS forwarding of IPv4 packets along normally routed paths is sometimes called dynamic label switching. If dynamic label switching has been enabled for the platform when this command is issued on an interface, you can start label distribution for the interface by initiating periodic transmission of neighbor discovery hello messages on the interface. When the outgoing label for a destination routed through the interface is known, packets for the destination are labeled with that outgoing label and forwarded through the interface.
The no form of this command causes packets routed out through the interface to be sent unlabeled; it also ends label distribution for the interface. The no form of this command does not affect the sending of labeled packets through any TSP tunnels that might use the interface.
For an LC-ATM interface, the no form of this command prevents the establishment of label VCs beginning at, terminating at, or passing through the interface.
Examples
In the following example, label switching is enabled on Ethernet interface o/2:
Router(config)# configure terminalRouter(config-if)# interface e0/2Router(config-if)# mpls ipRelated Commands
show mpls interfaces
Displays information about one or more interfaces that have been configured for label switching.
mpls ip default-route
To enable the distribution of labels associated with the IP default route, use the mpls ip default-route global configuration command.
mpls ip default-route
Syntax Description
This command has no arguments or keywords.
Defaults
No distribution of labels for the IP default route.
Command Modes
Global configuration
Command History
11.1 CT
This command was introduced.
12.1(3)T
This command was modified to reflect new MPLS IETF terminology.
Usage Guidelines
Dynamic label switching (that is, distribution of labels based on routing protocols) must be enabled before you can use the mpls ip default-route command.
Examples
The following commands enable the distribution of labels associated with the IP default route:
Router# configure terminalRouter(config)# mpls ipRouter(config)# mpls ip default-routeRelated Commands
mpls ip propagate-ttl
To control the generation of the time to live (TTL) field in the MPLS header when labels are first added to an IP packet, use the mpls ip propagate-ttl global configuration command. To use a fixed TTL value (255) for the first label of the IP packet, use the no form of this command.
mpls ip propagate-ttl
no mpls ip propagate-ttl [forwarded | local]
Syntax Description
forwarded
(Optional) Prevents the traceroute command from showing the hops for forwarded packets.
local
(Optional) Prevents the traceroute command from showing the hops only for local packets.
Defaults
By default, this command is enabled. The TTL field is copied from the IP header. A traceroute command shows all of the hops in the network.
Command Modes
Global configuration
Command History
12.1(3)T
This command was introduced.
12.1(5)T
The keywords forwarded and local were added to this command.
Usage Guidelines
By default, the mpls ip propagate-ttl command is enabled and the IP TTL value is copied to the MPLS TTL field during label imposition. To disable TTL propagation for all packets, use the no mpls ip propagate-ttl command. To disable TTL propagation for only forwarded packets, use the no mpls ip propagate forward command. Disabling TTL propagation of forwarded packets allows the structure of the MPLS network to be hidden from customers, but not the provider.
This feature supports the IETF draft document ICMP Extensions for Multiprotocol Label Switching, draft-ietf-mpls-label-icmp-01.txt. The document can be accessed at the following URL:
http://www2.ietf.org/internet-drafts/draft-ietf-mpls-label-icmp-01.txt
Related Commands
traceroute
Displays the routes that packets take through a network to their destinations.
mpls ip ttl-expiration pop
To specify how a packet with an expired time to live (TTL) value is forwarded, use the mpls ip ttl-expiration pop privileged EXEC command. To disable this feature, use the no form of the command.
mpls ip ttl-expiration pop labels
no mpls ip ttl-expiration pop labels
Syntax Description
labels
The maximum number of labels in the packet necessary for the packet to be forwarded by means of the global IP routing table.
Defaults
By default, the packets are forwarded by the original label stack. However, in previous versions of Cisco IOS software, the packets were forwarded by the global routing table by default.
Command Modes
Global configuration
Command History
Usage Guidelines
You can specify that the packet be forwarded by the global IP routing table or by the packet's original label stack. The forwarding method is determined by the number of labels in the packet. You specify the number of labels as part of the command. If the packet contains the same or fewer labels than you specified, it is forwarded through the use of the global IP routing table. If the packet contains more labels than you specified, the packet is forwarded through the use of the original label stack.
This command is useful if expired TTL packets do not get back to their source, because there is a break in the Interior Gateway Protocol (IGP) path. Currently, MPLS forwards the expired TTL packets by reimposing the original label stack and forwarding the packet to the end of a label switched path (LSP). (For provider edge routers forwarding traffic over a Virtual Private Network (VPN), this is the only way to get the packet back to the source.) If there is a break in the IGP path to the end of the LSP, the packet never reaches its source.
If packets have a single label, that label is usually a global address or terminal VPN label. Those packets can be forwarded through the use of the global IP routing table. Packets that have more than one label can be forwarded through the use of the original label stack. Enter the mpls ip ttl-expiration pop 1 command to enable forwarding based on more than one label. (This is the most common application of the command.)
Related Commands
traceroute
Displays the routes that packets take through a network to their destinations.
mpls label range
To configure the range of local labels available for use on packet interfaces, use the mpls label range global configuration command. To revert to the platform defaults, use the no form of this command.
mpls label range min max
no mpls label range
Syntax Description
min
The smallest label allowed in the label space. The default is 16.
max
The largest label allowed in the label space. The default is 1048575.
Defaults
min: 16
max: 1048575
Command Modes
Global configuration
Command History
11.1CT
This command was introduced.
12.1(3)T
This command was modified to reflect new MPLS IETF terminology and CLI command syntax.
Usage Guidelines
The labels 0 through 15 are reserved by the IETF (see draft-ietf-mpls-label-encaps-07.txt for details) and cannot be included in the range specified by the mpls label range command.
The label range defined by the mpls label range command is used by all MPLS applications that allocate local labels (for dynamic label switching, MPLS traffic engineering, MPLS VPNs, and so on).
If you specify a new label range that does not overlap the range currently in use, the new range will not take effect until the router is reloaded again.
Examples
The following example configures the size of the local label space. In this example, the min argument is set with the value of 200, and the max value is set with the value of 120000. Because the new range does not overlap the current label range (assumed to be the default, that is, the min argument of 16 and the max argument of 100000), the new range will not take effect until the router is reloaded.
Router# configure terminalRouter(config)# mpls label range 200 120000% Label range changes will take effect at the next reload.Router(config)#If you had specified a new range that overlaps the current range (for example, new range of the min argument of 16 and the max argument of 120000), then the new range would take effect immediately.
Related Commands
mpls mtu
To set the per-interface Multiprotocol Label Switching (MPLS) maximum transmission unit (MTU) for labeled packets, use the mpls mtu interface configuration command. To restore the default, use the no form of this command.
mpls mtu bytes
no mpls mtu
Syntax Description
Defaults
The default MPLS MTU is the MTU configured for the interface. The minimum allowable value is 64; the maximum allowable value is interface dependent.
Command Modes
Interface configuration
Command History
11.1 CT
This command was introduced.
12.1(3)T
This command was modified to reflect new MPLS IETF terminology.
Usage Guidelines
•
Note
•
•
•
•
•
–
–
•
•
–
–
Examples
The following example sets the maximum labeled packet size for the Fastethernet interface to 1508, which is common in an MPLS core carrying MPLS VPN traffic, for example:
interface Fastethernet0mpls mtu 1508mpls netflow egress
To enable MPLS egress NetFlow accounting on an interface, use the mpls netflow egress interface configuration command. To disable MPLS egress NetFlow accounting, use the no form of this command.
mpls netflow egress
no mpls netflow egress
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
12.0(10)ST
This command was introduced.
12.1(5)T
This command was integrated into Cisco IOS Release 12.1(5)T.
Usage Guidelines
Use this command to configure the PE-CE interface of a PE router.
Examples
In the following example, MPLS egress NetFlow accounting is enabled on the egress PE interface that connects to the CE interface at the destination VPN site:
Router(config-if)# mpls netflow egressRelated Commands
mpls traffic-eng
To configure a router running IS-IS so that it floods MPLS traffic engineering link information into the indicated IS-IS level, use the mpls traffic-eng router configuration command. To disable this feature, use the no form of this command.
mpls traffic-eng {level-1 | level-2}
no mpls traffic-eng {level-1 | level-2}
Syntax Description
level-1
Floods MPLS traffic engineering link information into IS-IS level 1.
level-2
Floods MPLS traffic engineering link information into IS-IS level 2.
Defaults
Flooding is disabled.
Command Modes
Router configuration
Command History
Usage Guidelines
This command, which is part of the routing protocol tree, causes link resource information (such as available bandwidth) for appropriately configured links to be flooded in the IS-IS link-state database.
Examples
In the following example, MPLS traffic engineering is turned on for IS-IS level 1:
Router(config-router)# mpls traffic-eng level-1Related Commands
mpls traffic-eng router-id
Specifies that the traffic engineering router identifier for the node is the IP address associated with a given interface.
mpls traffic-eng administrative-weight
To override the Interior Gateway Protocol (IGP) administrative weight (cost) of the link, use the mpls traffic-eng administrative-weight interface configuration command. To disable this feature, use the no form of this command.
mpls traffic-eng administrative-weight weight
no mpls traffic-eng administrative-weight
Syntax Description
Defaults
IGP cost of the link.
Command Modes
Interface configuration
Command History
Examples
In the following example, the IGP cost of the link is overridden, and the cost is set to 20:
Router(config-if)# mpls traffic-eng administrative-weight 20Related Commands
mpls traffic-eng area
To configure a router running Open Shortest Path First (OSPF) MPLS so that it floods traffic engineering for the indicated OSPF area, use the mpls traffic-eng area router configuration command. To disable this feature, use the no form of this command.
mpls traffic-eng area num
no mpls traffic-eng area num
Syntax Description
Defaults
No default behavior or values.
Command Modes
Router configuration
Command History
Usage Guidelines
This command is in the routing protocol configuration tree and is supported for both OSPF and IS-IS. The command affects the operation of MPLS traffic engineering only if MPLS traffic engineering is enabled for that routing protocol instance. Currently, only a single level can be enabled for traffic engineering.
Examples
In the following example, a router running OSPF MPLS is configured to flood traffic engineering for OSPF 0:
Router(config-router)# mpls traffic-eng area 0Related Commands
mpls traffic-eng attribute-flags
To set the user-specified attribute flags for the interface, use the mpls traffic-eng attribute-flags interface configuration command. To disable this feature, use the no form of this command.
mpls traffic-eng attribute-flags attributes
no mpls traffic-eng attribute-flags
Syntax Description
Defaults
0x0
Command Modes
Interface configuration
Command History
Usage Guidelines
This command assigns attributes to a link so that tunnels with matching attributes (represented by their affinity bits) prefer this link instead of others that do not match.
The interface is flooded globally so that it can be used as a tunnel head-end path selection criterion.
Examples
In the following example, the attribute flags are set to 0x0101:
Router(config-if)# mpls traffic-eng attribute-flags 0x0101Related Commands
mpls traffic-eng flooding thresholds
To set a link's reserved bandwidth thresholds, use the mpls traffic-eng flooding thresholds interface configuration command. To return to the default settings, use the no form of this command.
mpls traffic-eng flooding thresholds {down | up} percent [percent ...]
no mpls traffic-eng flooding thresholds {down | up}
Syntax Description
The default for down is 100, 99, 98, 97, 96, 95, 90, 85, 80, 75, 60, 45, 30, 15.
The default for up is 15, 30, 45, 60, 75, 80, 85, 90, 95, 97, 98, 99, 100.
Command Modes
Interface configuration
Command History
Usage Guidelines
When a threshold is crossed, MPLS traffic engineering link management advertises updated link information. If no thresholds are crossed, changes can be flooded periodically unless periodic flooding was disabled.
Examples
In the following example, the link's reserved bandwidth is set for decreased resource availability (down) and for increased resource availability (up) thresholds:
Router(config-if)# mpls traffic-eng flooding thresholds down 100 75 25Router(config-if)# mpls traffic-eng flooding thresholds up 25 50 100Related Commands
mpls traffic-eng interface
To enable OSPF to advertise an MPLS Traffic Engineering (TE) interface to area 0, use the mpls traffic-eng interface command in router configuration mode. To remove the interface from area 0, use the no form of this command.
mpls traffic-eng interface interface area area
no mpls traffic-eng interface interface area area
Syntax Description
interface
The interface where the virtual link exists.
area
The area where the link should be advertised. This is generally area 0.
Defaults
No default behaviors.
Command Modes
Router configuration
Command History
12.0(11)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T.
Usage Guidelines
This command is useful in MPLS TE configurations that use virtual links between Area Border Routers (ABRs) with OSPF.
Often, OSPF ABRs have a link between them which is in a non-zero area, and a virtual link that in effect puts that link into area 0 as well as the non-zero area. This command allows you to advertise the link between ABRs into area 0, even though the link is in a non-zero area. This solves for TE the same problem that virtual links solve for IP routing.
Examples
In the following example, OSPF announces interface pos0/0 to area 0:
Router(config)# router ospf 1Router(config-router)# mpls traffic-eng interface pos0/0 area 0mpls traffic-eng link-management timers bandwidth-hold
To set the length of time that bandwidth is held for an RSVP path (setup) message while you wait for the corresponding RSVP Resv message to come back, use the mpls traffic-eng link-management timers bandwidth-hold router configuration command. To disable this feature, use the no form of this command.
mpls traffic-eng link-management timers bandwidth-hold hold-time
no mpls traffic-eng link-management timers bandwidth-hold
Syntax Description
Defaults
15 seconds.
Command Modes
Router configuration
Command History
Examples
In the following example, bandwidth is set to be held for 10 seconds:
Router(config)# mpls traffic-eng link-management timers bandwidth-hold 10Related Commands
show mpls traffic-eng link-management bandwidth-allocation
Displays current local link information.
mpls traffic-eng link-management timers periodic-flooding
To set the length of the interval for periodic flooding, use the mpls traffic-eng link-management timers periodic-flooding router configuration command. To disable this feature, use the no form of this command.
mpls traffic-eng link-management timers periodic-flooding interval
no mpls traffic-eng link-management timers periodic-flooding
Syntax Description
interval
Length of the interval (in seconds) for periodic flooding. Valid values are from 0 to 3600. A value of 0 turns off periodic flooding. If you set this value from 1 to 29, it is treated as 30.
Defaults
180 seconds (3 minutes)
Command Modes
Router configuration
Command History
Usage Guidelines
Use this command to advertise link state information changes that do not trigger immediate action. For example, a change to the amount of allocated bandwidth that does not cross a threshold.
Examples
In the following example, the interval length for periodic flooding is set to 120 seconds:
Router(config)# mpls traffic-eng link-management timers periodic-flooding 120Related Commands
mpls traffic-eng link timers bandwidth-hold
To set the length of time that bandwidth is "held" for a RSVP PATH (Set Up) message while waiting for the corresponding RSVP RESV message to come back, use the mpls traffic-eng link timers bandwidth-hold command in global configuration mode.
mpls traffic-eng link timers bandwidth-hold hold-time
Syntax Description
Defaults
15 seconds
Command Modes
Global configuration
Command History
Examples
The following example sets the length of time that bandwidth is held to 10 seconds.
mpls traffic-eng link-management timers bandwidth-hold 10Related Commands
show mpls traffic-eng link-management bandwidth-allocation
Displays current local link information.
mpls traffic-eng link timers periodic-flooding
To set the length of the interval used for periodic flooding, use the mpls traffic-eng link timers periodic-flooding command in global configuration mode.
mpls traffic-eng link timers periodic-flooding interval
Syntax Description
Defaults
3 minutes
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to set the interval for periodic flooding of TE topology information.
Changes in the MPLS TE topology database are flooded by the link state Interior Gateway Protocol (IGP). Some changes, such as those to link status (up/down) or configured parameters, trigger immediate flooding. Other changes are considered less urgent and are flooded periodically. For example, changes to the amount of link bandwidth allocated to TE tunnels are flooded periodically unless the change causes the bandwidth to cross a configurable threshold.
Examples
The following example sets the interval length for periodic flooding to advertise flooding changes to 120 seconds.
mpls traffic-eng timers periodic-flooding 120Related Commands
mpls traffic-eng flooding thresholds
Sets the reserved bandwidth thresholds of a link.
mpls traffic-eng logging lsp
To log certain traffic engineering label-switched path (LSP) events, use the mpls traffic-eng logging lsp router configuration command. To disable this feature, use the no form of this command.
mpls traffic-eng logging lsp {path-errors | reservation-errors | preemption | setups | teardowns}[aclnum]
no mpls traffic-eng logging lsp {path-errors | reservation-errors | preemption | setups | teardowns}[aclnum]
Syntax Description
Defaults
Logging of LSP events is disabled.
Command Modes
Router configuration
Command History
Examples
In the following example, path errors are logged for LSPs that match access list 3:
Router(config)# mpls traffic-eng logging lsp path-errors 3Related Commands
mpls traffic-eng logging tunnel
To log certain traffic engineering tunnel events, use the mpls traffic-eng logging tunnel router configuration command. To disable this feature, use the no form of this command.
mpls traffic-eng logging tunnel lsp-selection [aclnum]
no mpls traffic-eng logging tunnel lsp-selection [aclnum]
Syntax Description
Defaults
Logging of tunnel events is disabled.
Command Modes
Router configuration
Command History
Examples
In the following example, traffic engineering tunnel events associated with access list 3 are logged:
Router(config)# mpls traffic-eng logging tunnel lsp-selection 3Related Commands
mpls traffic-eng multicast-intact
To configure a router running Intermediate System-to-Intermediate System (IS-IS) or Open Shortest Path First (OSPF) so that Protocol-Independent Multicast (PIM) and Multiprotocol Label Switching (MPLS) traffic engineering (TE) can work together, use the mpls traffic-eng multicast-intact command in router configuration mode. To disable interoperability between PIM and MPLS TE, use the no form of this command.
mpls traffic-eng multicast-intact
no mpls traffic-eng multicast-intact
Syntax Description
This command has no arguments or keywords.
Defaults
PIM and MPLS TE do not work together.
Command Modes
Router configuration
Command History
Usage Guidelines
The mpls traffic-eng multicast-intact command allows PIM to use the native hop-by-hop neighbors while unicast routing is using MPLS TE tunnels.
This command works only for OSPF and IS-IS protocols.
Examples
The following example shows how to enable PIM and MPLS TE to interoperate:
Router(config-router)# mpls traffic-eng multicast-intactRelated Commands
mpls traffic-eng reoptimize
To force immediate reoptimization of all traffic engineering tunnels, use the mpls traffic-eng reoptimize EXEC command.
mpls traffic-eng reoptimize
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Examples
In the following example, all traffic engineering tunnels are immediately reoptimized:
Router2# mpls traffic-eng reoptimizempls traffic-eng reoptimize events
To turn on automatic reoptimization of MPLS traffic engineering when certain events occur, such as when an interface becomes operational, use the mpls traffic-eng reoptimize events router configuration command. To disable this feature, use the no form of this command.
mpls traffic-eng reoptimize events {link-up}
no mpls traffic-eng reoptimize events {link-up}
Syntax Description
Defaults
Event-based reoptimization is disabled.
Command Modes
Router configuration
Command History
Examples
In the following example, automatic reoptimization is turned on whenever an interface becomes operational:
Router(config)# mpls traffic-eng reoptimize events link-upRelated Commands
mpls traffic-eng logging lsp
Controls the frequency with which tunnels with established LSPs are checked for better LSPs.
mpls traffic-eng reoptimize (EXEC mode)
Reoptimizes all traffic engineering tunnels immediately.
mpls traffic-eng reoptimize timers frequency
To control the frequency with which tunnels with established label-switched paths (LSPs) are checked for better LSPs, use the mpls traffic-eng reoptimize timers frequency router configuration command. To disable this feature, use the no form of this command.
mpls traffic-eng reoptimize timers frequency seconds
no mpls traffic-eng reoptimize timers frequency
Syntax Description
Defaults
3600 seconds (1 hour), with a range of 0 to 604800 seconds (1 week)
Command Modes
Router configuration
Command History
Usage Guidelines
A device with traffic engineering tunnels periodically examines tunnels with established LSPs to learn if better LSPs are available. If a better LSP seems to be available, the device attempts to signal the better LSP; if the signalling is successful, the device replaces the old, inferior LSP with the new, better LSP.
Note
Examples
In the following example, the reoptimization frequency is set to 1 day:
Router(config)# mpls traffic-eng reoptimize timers frequency 86400Related Commands
tunnel mpls traffic-eng path-option
If lockdown is specified, does not do a reoptimization check on this tunnel.
mpls traffic-eng reoptimize (EXEC mode)
Reoptimizes all traffic engineering tunnels immediately.
mpls traffic-eng router-id
To specify that the traffic engineering router identifier for the node is the IP address associated with a given interface, use the mpls traffic-eng router-id router configuration command. To disable this feature, use the no form of this command.
mpls traffic-eng router-id interface-name
no mpls traffic-eng router-id
Syntax Description
Defaults
No default behavior or values.
Command Modes
Router configuration
Command History
Usage Guidelines
This router's identifier acts as a stable IP address for the traffic engineering configuration. This IP address is flooded to all nodes. For all traffic engineering tunnels originating at other nodes and ending at this node, you must set the tunnel destination to the destination node's traffic engineering router identifier, because that is the address that the traffic engineering topology database at the tunnel head uses for its path calculation.
Examples
In the following example, the traffic engineering router identifier is specified as the IP address associated with interface Loopback0:
Router(config-router)# mpls traffic-eng router-id Loopback0Related Commands
Turns on flooding of MPLS traffic engineering link information in the indicated IGP level/area.
mpls traffic-eng signalling advertise implicit-null
To use MPLS encoding for the implicit-null label in signalling messages sent to neighbors that match the specified access list, use the mpls traffic-eng signalling advertise implicit-null router configuration command. To disable this feature, use the no form of this command.
mpls traffic-eng signalling advertise implicit-null [aclname | aclnum]
no mpls traffic-eng signalling advertise implicit-null
Syntax Description
Defaults
Use the Cisco encoding for the implicit-null label in signalling messages.
Command Modes
Router configuration
Command History
Examples
In the following example, the router is configured to use MPLS encoding for the implicit-null label when it sends signalling messages to certain peers:
Router(config)# mpls traffic-eng signalling advertise implicit-nullmpls traffic-eng tunnels (global)
To enable MPLS traffic engineering tunnel signaling on a device, use the mpls traffic-eng tunnels global configuration command. To disable this feature, use the no form of this command.
mpls traffic-eng tunnels
no mpls traffic-eng tunnels
Syntax Description
This command has no arguments or keywords.
Defaults
The feature is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
This command enables MPLS traffic engineering on a device. For you to use the feature, MPLS traffic engineering must also be enabled on the desired interfaces.
Examples
In the following example, MPLS traffic engineering tunnel signalling is turned on:
Router(config)# mpls traffic-eng tunnelsRelated Commands
mpls traffic-eng tunnels (interface)
To enable MPLS traffic engineering tunnel signalling on an interface (assuming that it is enabled on the device), use the mpls traffic-eng tunnels interface configuration command. To disable this feature, use the no form of this command.
mpls traffic-eng tunnels
no mpls traffic-eng tunnels
Syntax Description
This command has no arguments or keywords.
Defaults
The feature is disabled on all interfaces.
Command Modes
Interface configuration
Command History
Usage Guidelines
To enable MPLS traffic engineering on the interface, MPLS traffic engineering must also be enabled on the device. An enabled interface has its resource information flooded into the appropriate IGP link-state database and accepts traffic engineering tunnel signalling requests.
Examples
In the following example, MPLS traffic engineering is enabled on Ethernet interface 0/0:
Router(config)# interface Ethernet0/0Router(config-if)# mpls traffic-eng tunnelsRelated Commands
mpoa client config name
To define an 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
This command has no default setting.
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 creates or modifies the MPC named ip_mpc:
mpoa client config name ip_mpcRelated Commands
mpoa client name
To attach an 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 attaches the MPC named 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 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 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 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. Note that the specified MPS must have already 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 interface configuration command.
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 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.7name elan-id
To configure the emulated LAN (ELAN) ID of an ELAN in the LECS database to participate in 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 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 sets the ELAN ID to 10 for an ELAN named MYELAN:
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.
