Table Of Contents

ip load-sharing

ip multicast netflow egress

ip multicast netflow ingress

ip multicast netflow rpf-failure

ip multicast-routing

ip route-cache

ip route-cache policy

ip route static inter-vrf

ip route vrf

ip vrf

ip vrf forwarding (interface configuration)

keepalive-lifetime

keepalive-time

lane auto-config-atm-address

lane bus-atm-address

lane client

lane client-atm-address

lane client flush

lane client mpoa client name

lane client mpoa server name

lane config-atm-address

lane config database

lane database

lane fixed-config-atm-address

lane fssrp

lane global-lecs-address

lane le-arp

lane server-atm-address

lane server-bus

list

ip load-sharing

To enable load balancing for Cisco Express Forwarding (CEF), use the ip load-sharing command in interface configuration mode.

ip load-sharing [per-packet] [per-destination]

Syntax Description

per-packet	(Optional) Enables per-packet load balancing on the interface.
per-destination	(Optional) Enables per-destination load balancing on the interface.

Defaults

Per-destination load balancing is enabled by default when you enable CEF.

Command Modes

Interface configuration

Command History

Release	Modification
11.2 GS	This command was introduced.
11.1 CC	Multiple platform support was added.

Usage Guidelines

Per-packet load balancing allows the router to send data packets over successive equal-cost paths without regard to individual destination hosts or user sessions. Path utilization is good, but packets destined for a given destination host might take different paths and might arrive out of order.

---

Note Per-packet load balancing via CEF is not supported on Engine 2 Gigabit Switch Router (GSR) line cards (LCs).

---

Per-destination load balancing allows the router to use multiple, equal-cost paths to achieve load sharing. Packets for a given source-destination host pair are guaranteed to take the same path, even if multiple, equal-cost paths are available. Traffic for different source-destination host pairs tend to take different paths.

---

Note If you want to enable per-packet load sharing to a particular destination, then all interfaces that can forward traffic to the destination must be enabled for per-packet load sharing.

---

Examples

The following example shows how to enable per-packet load balancing:

Router(config)# interface E0

Router(config-if)# ip load-sharing per-packet

The following example shows how to enable per-destination load balancing:

Router(config)# interface E0

Router(config-if)# ip load-sharing per-destination

Related Commands

Command	Description
ip cef	Enables CEF on the RP card.

ip multicast netflow egress

To enable multicast egress NetFlow accounting on an interface, use the ip multicast netflow egress command in interface configuration mode. To disable multicast egress NetFlow accounting, use the no form of this command.

ip multicast netflow egress

no ip multicast netflow egress

Syntax Description

This command has no arguments or keywords.

Defaults

Multicast egress NetFlow accounting is disabled.

Command Modes

Interface configuration

Command History

Release	Modification
12.3(1)	This command was introduced.

Usage Guidelines

You must enable multicast egress NetFlow accounting on all interfaces for which you want to count outgoing multicast streams:

Examples

The following example shows how to enable multicast egress NetFlow accounting on the egress Ethernet interface 0/0:

Router# configure terminal

Router(config)# interface ethernet 0/0

Router(config-if)# ip multicast netflow egress

Router(config-if)# end

Related Commands

Command	Description
ip multicast netflow ingress	Enables multicast ingress NetFlow accounting on an interface.
ip multicast netflow rpf-failure	Enables accounting for multicast data that fails the RPF (reverse path forwarding) check.
show ip flow interfaces	Displays multicast configuration information.

ip multicast netflow ingress

To enable multicast ingress NetFlow accounting on an interface, use the ip multicast netflow ingress command in interface configuration mode. To disable multicast ingress NetFlow accounting, use the no form of this command.

ip multicast netflow ingress

no ip multicast netflow ingress

Syntax Description

This command has no arguments or keywords.

Defaults

Multicast ingress NetFlow accounting is enabled.

Command Modes

Interface configuration

Command History

Release	Modification
12.3(1)	This command was introduced.

Usage Guidelines

The output of the show running-config command does not indicate when multicast ingress accounting is enabled (but it does indicate when multicast ingress NetFlow accounting is disabled).

Examples

The following example shows how to enable multicast ingress NetFlow accounting on the ingress Ethernet 1/0 interface:

Router# configure terminal

Router(config)# interface ethernet 1/0

Router(config-if)# ip multicast netflow ingress

Router(config-if)# end

Related Commands

Command	Description
ip multicast netflow egress	Enables multicast egress NetFlow accounting on an interface.
ip multicast netflow rpf-failure	Enables accounting for multicast data that fails the RPF (reverse path forwarding) check.
show ip flow interfaces	Displays multicast configuration information.

ip multicast netflow rpf-failure

To enable accounting for multicast data that fails the Reverse Path Forwarding (RPF) check (meaning any IP packets that lack a verifiable IP source address), use the ip multicast netflow rpf-failure command in global configuration mode. To disable accounting for multicast data that fails the RPF check, use the no form of this command.

ip multicast netflow rpf-failure

no ip multicast netflow rpf-failure

Syntax Description

This command has no arguments or keywords.

Defaults

Accounting for multicast data that fails the RPF check is disabled.

Command Modes

Global configuration

Command History

Release	Modification
12.3(1)	This command was introduced.

Examples

The following example shows how to enable accounting for multicast data that fails the RPF check:

Router# configure terminal

Router(config)# ip multicast netflow rpf-failure

Router(config)# end

Related Commands

Command	Description
ip multicast netflow egress	Enables multicast egress NetFlow accounting on an interface.
ip multicast netflow ingress	Enables multicast ingress NetFlow accounting on an interface.
show ip flow interfaces	Displays multicast configuration information.

ip multicast-routing

To enable IP multicast routing, use the ip multicast-routing command in global configuration mode. To disable IP multicast routing, use the no form of this command.

ip multicast-routing [vrf vrf-name] [distributed]

no ip multicast-routing [vrf vrf-name]

Syntax Description

vrf	(Optional) Supports the Multicast Virtual Private Network (VPN) routing/forwarding instance (VRF).
vrf-name	(Optional) Name assigned to the VRF.
distributed	(Optional) Enables Multicast Distributed Switching (MDS).

Defaults

IP multicast routing is disabled.

Command Modes

Global configuration

Command History

Release	Modification
10.0	This command was introduced.
11.2(11)GS	The distributed keyword was added.
12.0(5)T	The effect of this command was modified. If IP multicast Multilayer Switching (MLS) is enabled, using the no form of this command now disables IP multicast routing on the Multicast MultiLayer Switching (MMLS) route processor (RP) and purges all multicast MLS cache entries on the MMLS-SE.
12.0(23)S	The vrf keyword and vrf-name argument were added.
12.2(13)T	This command was integrated into Cisco IOS Release 12.2(13)T.

Usage Guidelines

When IP multicast routing is disabled, the Cisco IOS software does not forward any multicast packets.

Examples

The following example shows how to enable IP multicast routing:

Router(config)# ip multicast-routing

Related Commands

Command	Description
ip pim	Enables PIM on an interface.

ip route-cache

To control the use of switching methods for forwarding IP packets use the ip route-cache command in interface configuration mode. To disable any of these switching methods, use the no form of this command.

ip route-cache [same-interface | flow | distributed | cef | policy]

no ip route-cache [same-interface | flow | distributed | cef | policy]

Syntax Description

same-interface	Enables fast-switching packets to forward IP packets back out through the interface on which they arrived.
flow	Enables NetFlow accounting for packets that are received by the interface.
distributed	Enables distributed switching on the interface.
cef	Enables Cisco Express Forwarding (CEF) operation on an interface.
policy	Enables fast-switching for packets that are forwarded using Policy Based Routing (PBR).

Defaults

Fast Switching

The default behavior for Fast Switching varies by interface and media.

Distributed Switching

Distributed switching is disabled.

CEF and dCEF

When CEF or dCEF operation is enabled globally, all interfaces that support CEF or dCEF are enabled by default.

NetFlow Accounting

NetFlow accounting is disabled

Fast Switching for PBR (FSPBR)

FSPBR is disabled

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.
11.1	The flow keyword was added.
11.2GS	The cef and distributed keywords were added.
11.1CC	Support for multiple platforms was added for cef keyword.
12.0	The policy keyword was added.

Usage Guidelines

•ip route-cache

•ip route-cache same-interface

•ip route-cache flow

•ip route-cache distributed

•ip route-cache cef

•ip route-cache policy

ip route-cache

Using the route cache is often called fast switching. The route cache allows outgoing packets to be load-balanced on a per-destination basis rather than on a per-packet basis. The ip route-cache command with no additional keywords enables fast switching.

Entering the ip route-cache command has no effect on a subinterface. Subinterfaces accept the no form of the command; however, this disables CEF or dCEF on the physical interface as well as all subinterfaces associated with the physical interface

ip route-cache same-interface

You can enable IP fast switching when the input and output interfaces are the same interface, using the ip route-cache same-interface command. This configuration normally is not recommended, although it is useful when you have partially meshed media, such as Frame Relay or you are running Web Cache Communication Protocol (WCCP) redirection. You could use this feature on other interfaces, although it is not recommended because it would interfere with redirection of packets to the optimal path.

ip route-cache flow

Enables (ingress) NetFlow accounting for traffic arriving on an interface.

ip route-cache distributed

The distributed option is supported on Cisco routers with line cards and Versatile Interface Processors (VIPs) that support both CEF and flow switching.

On Cisco routers with Route Switch Processor (RSP) and VIP controllers, the VIP hardware can be configured to switch packets received by the VIP with no per-packet intervention on the part of the RSP. When VIP distributed switching is enabled, the input VIP interface tries to switch IP packets instead of forwarding them to the RSP for switching. Distributed switching helps decrease the demand on the RSP

ip route-cache cef

In some instances, you might want to disable CEF or dCEF on a particular interface because that interface is configured with a feature that CEF or dCEF does not support. Because all interfaces that support CEF or dCEF are enabled by default when you enable CEF operation globally, you must use the no form of the ip route-cache cef command in the interface configuration mode to turn CEF operation off a particular interface. To reenable CEF or dCEF operation, use the ip route-cache cef command.

Disabling CEF or dCEF on an interface disables CEF switching for packets forwarded to the interface, but has no effect on packets forwarded out of the interface.

Additionally when you disable CEF or dCEF, Cisco IOS software switches packets using the next-fastest switching path. In the case of dCEF, the next-fastest switching path is CEF on the RSP.

---

Note On the Cisco 12000 Series Internet Router, you must not disable dCEF on an interface

---

ip route-cache policy

1. If Cisco Express Forwarding (CEF) is already enabled, this command is not needed because PBR packets are CEF switched by default.

2. Before you can enable fast-switched PBR, PBR itself must be configured.

3. FSPBR supports all of PBR's match commands and most of PBR's set commands, with the following restrictions:

–The set ip default next-hop and set default interface commands are not supported.

–The set interface command is supported only over point-to-point links, unless a route cache entry exists using the same interface specified in the set interface command in the route map.
Also, at the process level, the routing table is consulted to determine if the interface is on a reasonable path to the destination. During fast switching, the software does not make this check. Instead, if the packet matches, the software blindly forwards the packet to the specified interface.

Examples

•Configuring Fast Switching and Disabling CEF Switching

•Configuring Fast Switching for Traffic That is Received and Transmitted Over the Same Interface

•Enabling NetFlow Accounting

•Configuring Distributed Switching

•Configuring Fast Switching for PBR

Configuring Fast Switching and Disabling CEF Switching

The following example shows how to enable fast switching and disable CEF switching:

Router(config)# interface ethernet 0/0/0

Router(config-if)# ip route-cache

The following example shows that fast switching is enabled:

Router# show ip interface fastEthernet 0/0/0   

FastEthernet0/0/0 is up, line protocol is up

  Internet address is 10.1.1.254/24

  Broadcast address is 255.255.255.255

  Address determined by non-volatile memory

  MTU is 1500 bytes

  Helper address is not set

  Directed broadcast forwarding is disabled

  Multicast reserved groups joined: 224.0.0.10

  Outgoing access list is not set

  Inbound  access list is not set

  Proxy ARP is enabled

  Security level is default

  Split horizon is enabled

  ICMP redirects are always sent

  ICMP unreachables are always sent

  ICMP mask replies are never sent

  IP fast switching is enabled

  IP fast switching on the same interface is disabled

  IP Flow switching is disabled

  IP Distributed switching is disabled

  IP Feature Fast switching turbo vector

  IP Null turbo vector

  IP multicast fast switching is enabled

The following example shows that CEF switching is disabled:

Router# show cef interface fastEthernet 0/0/0

FastEthernet0/0/0 is up (if_number 3)

  Corresponding hwidb fast_if_number 3

  Corresponding hwidb firstsw->if_number 3

  Internet address is 10.1.1.254/24

  ICMP redirects are always sent

  Per packet load-sharing is disabled

  IP unicast RPF check is disabled

  Inbound access list is not set

  Outbound access list is not set

  IP policy routing is disabled

  Hardware idb is FastEthernet0/0/0

  Fast switching type 1, interface type 18

  IP CEF switching disabled

  IP Feature Fast switching turbo vector

  IP Null turbo vector

  Input fast flags 0x0, Output fast flags 0x0

  ifindex 1(1)

  Slot 0 Slot unit 0 VC -1

  Transmit limit accumulator 0x48001A02 (0x48001A02)

  IP MTU 1500

The following example shows the configuration information for interface fastethernet 0/0/0

Router# show running-config

.

.

!

interface FastEthernet0/0/0

 ip address 10.1.1.254 255.255.255.0

 no ip route-cache cef

 no ip route-cache distributed

!

Configuring Fast Switching for Traffic That is Received and Transmitted Over the Same Interface

The following example shows how to enable fast switching and disable CEF switching:

Router(config)# interface ethernet 0/0/0

Router(config-if)# ip route-cache same-interface

The following example shows that fast switching on the same interface is enabled for interface fastethernet 0/0/0:

Router# show ip interface fastEthernet 0/0/0  

FastEthernet0/0/0 is up, line protocol is up

  Internet address is 10.1.1.254/24

  Broadcast address is 255.255.255.255

  Address determined by non-volatile memory

  MTU is 1500 bytes

  Helper address is not set

  Directed broadcast forwarding is disabled

  Multicast reserved groups joined: 224.0.0.10

  Outgoing access list is not set

  Inbound  access list is not set

  Proxy ARP is enabled

  Security level is default

  Split horizon is enabled

  ICMP redirects are always sent

  ICMP unreachables are always sent

  ICMP mask replies are never sent

  IP fast switching is enabled

  IP fast switching on the same interface is enabled

  IP Flow switching is disabled

  IP Distributed switching is disabled

  IP Feature Fast switching turbo vector

  IP Null turbo vector

  IP multicast fast switching is enabled

  IP multicast distributed fast switching is disabled

  IP route-cache flags are Fast

  Router Discovery is disabled

  IP output packet accounting is disabled

  IP access violation accounting is disabled

  TCP/IP header compression is disabled

  RTP/IP header compression is disabled

  Probe proxy name replies are disabled

  Policy routing is disabled

  Network address translation is disabled

  WCCP Redirect outbound is disabled

  WCCP Redirect inbound is disabled

  WCCP Redirect exclude is disabled

  BGP Policy Mapping is disabled

  IP multicast multilayer switching is disabled

The following example shows the configuration information for interface fastethernet 0/0/0

Router# show running-config

.

.

!

interface FastEthernet0/0/0

 ip address 10.1.1.254 255.255.255.0

 ip route-cache same-interface

 no ip route-cache cef

 no ip route-cache distributed

!

Enabling NetFlow Accounting

The following example shows how to enable NetFlow switching:

Router(config)# interface ethernet 0/0/0

Router(config-if)# ip route-cache flow

The following example shows that NetFlow accounting is enabled for interface fastethernet 0/0/0:

Router# show ip interface fastEthernet 0/0/0 

FastEthernet0/0/0 is up, line protocol is up

  Internet address is 10.1.1.254/24

  Broadcast address is 255.255.255.255

  Address determined by non-volatile memory

  MTU is 1500 bytes

  Helper address is not set

  Directed broadcast forwarding is disabled

  Multicast reserved groups joined: 224.0.0.10

  Outgoing access list is not set

  Inbound  access list is not set

  Proxy ARP is enabled

  Security level is default

  Split horizon is enabled

  ICMP redirects are always sent

  ICMP unreachables are always sent

  ICMP mask replies are never sent

  IP fast switching is enabled

  IP fast switching on the same interface is disabled

  IP Flow switching is enabled

  IP Distributed switching is disabled

  IP Flow switching turbo vector

  IP Null turbo vector

  IP multicast fast switching is enabled

  IP multicast distributed fast switching is disabled

  IP route-cache flags are Fast, Flow

  Router Discovery is disabled

  IP output packet accounting is disabled

  IP access violation accounting is disabled

  TCP/IP header compression is disabled

  RTP/IP header compression is disabled

  Probe proxy name replies are disabled

  Policy routing is disabled

  Network address translation is disabled

  WCCP Redirect outbound is disabled

  WCCP Redirect inbound is disabled

  WCCP Redirect exclude is disabled

  BGP Policy Mapping is disabled

  IP multicast multilayer switching is disabled

Configuring Distributed Switching

The following example shows how to enable distributed switching:

Router(config)# ip cef distributed

Router(config)# interface ethernet 0/0/0

Router(config-if)# ip route-cache distributed

The following example shows that distributed CEF switching is for interface fastethernet 0/0/0:

Router# show cef interface fastEthernet 0/0/0

FastEthernet0/0/0 is up (if_number 3)

  Corresponding hwidb fast_if_number 3

  Corresponding hwidb firstsw->if_number 3

  Internet address is 10.1.1.254/24

  ICMP redirects are always sent

  Per packet load-sharing is disabled

  IP unicast RPF check is disabled

  Inbound access list is not set

  Outbound access list is not set

  IP policy routing is disabled

  Hardware idb is FastEthernet0/0/0

  Fast switching type 1, interface type 18

  IP Distributed CEF switching enabled

  IP Feature Fast switching turbo vector

  IP Feature CEF switching turbo vector

  Input fast flags 0x0, Output fast flags 0x0

  ifindex 1(1)

  Slot 0 Slot unit 0 VC -1

  Transmit limit accumulator 0x48001A02 (0x48001A02)

  IP MTU 1500

Configuring Fast Switching for PBR

The following example shows how to configure a simple policy based routing scheme and to enable FSPBR:

Router(config)# access-list 1 permit 10.1.1.0 0.0.0.255

Router(config)# route-map my_pbr_tag permit 10

Router(config-route-map)# match ip address 1

Router(config-route-map)# set ip next-hop 10.1.1.195

Router(config-route-map)# exit

Router(config)# interface fastethernet 0/0/0

Router(config-if)# ip route-cache policy

Router(config-if)# ip policy route-map my_pbr_tag

The following example shows that FSPBR is enabled for interface fastethernet 0/0/0:

Router# show ip interface fastEthernet 0/0/0

FastEthernet0/0/0 is up, line protocol is up

  Internet address is 10.1.1.254/24

  Broadcast address is 255.255.255.255

  Address determined by non-volatile memory

  MTU is 1500 bytes

  Helper address is not set

  Directed broadcast forwarding is disabled

  Multicast reserved groups joined: 224.0.0.10

  Outgoing access list is not set

  Inbound  access list is not set

  Proxy ARP is enabled

  Security level is default

  Split horizon is enabled

  ICMP redirects are always sent

  ICMP unreachables are always sent

  ICMP mask replies are never sent

  IP fast switching is enabled

  IP fast switching on the same interface is disabled

  IP Flow switching is disabled

  IP CEF switching is enabled

  IP Distributed switching is enabled

  IP Feature Fast switching turbo vector

  IP Feature CEF switching turbo vector

  IP multicast fast switching is enabled

  IP multicast distributed fast switching is disabled

  IP route-cache flags are Fast, Distributed, Policy, CEF

  Router Discovery is disabled

  IP output packet accounting is disabled

  IP access violation accounting is disabled

  TCP/IP header compression is disabled

  RTP/IP header compression is disabled

  Probe proxy name replies are disabled

  Policy routing is enabled, using route map my_pbr_tag

  Network address translation is disabled

  WCCP Redirect outbound is disabled

  WCCP Redirect inbound is disabled

  WCCP Redirect exclude is disabled

  BGP Policy Mapping is disabled

  IP multicast multilayer switching is disabled

Related CommandsRouter(config-if)# ip route-cache distributed

Command	Description
ip cef	Enables CEF on the RP card.
ip cef distributed	Enables distributed CEF (dCEF) operation.
show ip interface	Displays the usability status of interfaces configured for IP.
show cef interface	Displays detailed Cisco Express Forwarding (CEF) information for interfaces.

ip route-cache policy

To enable fast-switch Policy Based Routing (PBR), use the ip route-cache policy command in interface configuration mode. To disable fast-switched PBR, use the no form of this command.

ip route-cache policy

no ip route-cache policy

Syntax Description

This command has no arguments or keywords.

Defaults

Fast-switched PBR is disabled.

Command Modes

Interface configuration

Command History

Release	Modification
12.0	This command was introduced.

Usage Guidelines

1. If Cisco Express Forwarding (CEF) is already enabled, the present command is not needed because PBR packets are CEF switched by default.

2. Before you can enable fast-switch PBR, PBR itself must be configured.

3. FSPBR supports all of PBR's match commands and most of PBR's set commands, with the following restrictions:

–The set ip default next-hop and set default interface commands are not supported.

–The set interface command is supported only over point-to-point links, unless a route cache entry exists using the same interface specified in the set interface command in the route map.
Also, at the process level, the routing table is consulted to determine if the interface is on a reasonable path to the destination. During fast switching, the software does not make this check. Instead, if the packet matches, the software blindly forwards the packet to the specified interface.

Examples

The following example shows how to enable fast-switch Policy Based Routing on an Ethernet interface:

Router# configure terminal

Enter configuration commands, one per line.  End with CNTL/Z.

Router(config)# interface ethernet 1/3

Router(config-if)# ip route-cache policy

Router(config-if)# end

Related Commands

Command	Description
show ip cache policy	Displays cache entries in the policy route-cache.

ip route static inter-vrf

To allow static routes to point to Virtual Private Network (VPN) routing/forwarding instance (VRF) interfaces in VRFs other than those to which the static route belongs, use the ip route static inter-vrf command in global configuration mode. To prevent static routes from pointing to VRF interfaces in VRFs to which they do not belong, use the no form of this command.

ip route static inter-vrf

no ip route static inter-vrf

Syntax Description

This command has no arguments or keywords.

Defaults

By default, static routes are allowed to point to VRF interfaces in any VRF.

Command Modes

Global configuration

Command History

Release	Modification
12.0(23)S	This command was introduced.
12.2(13)T	This command was integrated into Cisco IOS Release 12.2(13)T.

Usage Guidelines

The ip route static inter-vrf command is turned on by default. The no ip route static inter-vrf command causes the respective routing table (global or VRF) to reject the installation of static routes if the outgoing interface belongs to a different VRF than the static route being configured. This prevents security problems that can occur when static routes that point to a VRF interface in a different VRF are misconfigured. You are notified when a static route is rejected, then you can reconfigure it.

For example, a static route is defined on a provider edge (PE) router to forward Internet traffic to a customer on the interface pos1/0, as follows:

Router(config)# ip route 10.1.1.1 255.255.255.255 pos 1/0

Mistakenly, the same route is configured with the next-hop as the VRF interface pos10/0:

Router(config)# ip route 10.1.1.1 255.255.255.255 pos 10/0

By default, Cisco IOS accepts the command and starts forwarding the traffic to both pos1/0 (Internet) and pos10/0 (VPN) interfaces.

If the static route is already configured that points to a VRF other than the one to which the route belongs when you issue the no ip route static inter-vrf command, the offending route is uninstalled from the routing table and a message similar to the following is sent to the console:

01:00:06: %IPRT-3-STATICROUTESACROSSVRF: Un-installing static route x.x.x.x/32 from global 
routing table with outgoing interface intx/x

If you enter the no ip route static inter-vrf command before a static route is configured that points to a VRF interface in a different VRF, the static route is not installed in the routing table and a message is sent to the console.

In the following example, configuring the no ip route static inter-vrf command prevents traffic from following an unwanted path. A VRF static route points to a global interface or any other VRF interface as shown in the following ip route vrf commands:

•Interface serial 1/0.0 is a global interface:

Router(config)# no ip route static inter-vrf

Router(config)# ip route vrf vpn1 10.10.1.1 255.255.255.255 serial 1/0.0 

•Interface serial 1/0.1 is in vpn2:

Router(config)# no ip route static inter-vrf

Router(config)# ip route vrf vpn1 10.10.1.1 255.255.255.255 serial 1/0.1 

With the no ip route static inter-vrf command configured, these static routes are not installed into the vpn1 routing table because the static routes point to an interface that is not in the same VRF.

If you require a VRF static route to point to a global interface, you can use the global keyword with the ip route vrf command:

Router(config)# ip route vrf vpn1 10.12.1.1 255.255.255.255 ser1/0.0 7.0.0.1 global 

The global keyword allows the VRF static route to point to a global interface even when the no ip route static inter-vrf command is configured.

Examples

The following example shows how to prevent static routes that point to VRF interfaces in a different VRF:

Router(config)# no ip route static inter-vrf

Related Commands

Command	Description
ip route vrf	Establishes static routes for a VRF.

ip route vrf

To establish static routes for a Virtual private Network (VPN) routing/ forwarding instance (VRF), use the ip route vrf command in global configuration mode. To disable static routes, use the no form of this command.

ip route vrf vrf-name prefix mask [next-hop-address] [interface interface-number] [global] [distance] [permanent] [tag tag]

no ip route vrf vrf-name prefix mask [next-hop-address] [interface interface-number] [global] [distance] [permanent] [tag tag]

Syntax Description

vrf-name	Name of the VPN routing/forwarding instance (VRF) for the static route.
prefix	IP route prefix for the destination, in dotted-decimal format.
mask	Prefix mask for the destination, in dotted-decimal format.
next-hop-address	(Optional) IP address of the next hop (the forwarding router that can be used to reach that network).
interface	(Optional) Type of network interface to use: atm, ethernet, loopback, pos, or null.
interface-number	(Optional) Number identifying the network interface to use.
global	(Optional) Specifies that the given next hop address is in the non-VRF routing table.
distance	(Optional) An administrative distance for this route.
permanent	(Optional) Specifies that this route will not be removed, even if the interface shuts down.
tag tag	(Optional) Label (tag) value that can be used for controlling redistribution of routes through route maps.

Defaults

No static routes are established.

Command Modes

Global configuration

Command History

Release	Modification
12.0(5)T	This command was introduced.

Usage Guidelines

Use a static route when the Cisco IOS software cannot dynamically build a route to the destination.

If you specify an administrative distance when you set up a route, you are flagging a static route that can be overridden by dynamic information. For example, Interior Gateway Routing Protocol (IGRP)-derived routes have a default administrative distance of 100. To set a static route to be overridden by an IGRP dynamic route, specify an administrative distance greater than 100. Static routes each have a default administrative distance of 1.

Static routes that point to an interface are advertised through the Routing Information Protocol (RIP), IGRP, and other dynamic routing protocols, regardless of whether the routes are redistributed into those routing protocols. That is, static routes configured by specifying an interface lose their static nature when installed into the routing table.

However, if you define a static route to an interface not defined in a network command, no dynamic routing protocols advertise the route unless a redistribute static command is specified for these protocols.

Examples

The following command shows how to reroute packets addressed to network 172.23.0.0 in VRF vpn3 to router 172.31.6.6:

Router(config)# ip route vrf vpn3 172.23.0.0 255.255.0.0 172.31.6.6

Related Commands

Command	Description
show ip route vrf	Displays the IP routing table associated with a VRF.

ip vrf

To configure a Virtual Private Network (VPN) routing/forwarding instance (VRF) routing table, use the ip vrf command in global configuration mode or router configuration mode. To remove a VRF routing table, use the no form of this command.

ip vrf vrf-name

no ip vrf vrf-name

Syntax Description

vrf-name

Name assigned to a VRF.

Defaults

No VRFs are defined. No import or export lists are associated with a VRF. No route maps are associated with a VRF.

Command Modes

Global configuration

Router configuration

Command History

Release	Modification
12.0(5)T	This command was introduced.

Usage Guidelines

The ip vrf vrf-name command creates a VRF routing table and a Cisco Express Forwarding (CEF) table, both named vrf-name. Associated with these tables is the default route distinguisher value route-distinguisher.

Examples

The following example shows how to import a route map to a VRF:

Router(config)# ip vrf vpn1

Router(config-vrf)# rd 100:2

Router(config-vrf)# route-target both 100:2

Router(config-vrf)# route-target import 100:1

Related Commands

Command	Description
ip vrf forwarding (interface configuration)	Associates a VRF with an interface or subinterface.

ip vrf forwarding (interface configuration)

To associate a Virtual Private network (VPN) routing/forwarding instance (VRF) with an interface or subinterface, use the ip vrf forwarding command in interface configuration mode. To disassociate a VRF, use the no form of this command.

ip vrf forwarding vrf-name

no ip vrf forwarding vrf-name

Syntax Description

vrf-name

Name assigned to a VRF.

Defaults

The default for an interface is the global routing table.

Command Modes

Interface configuration

Command History

Release	Modification
12.0(5)T	This command was introduced.

Usage Guidelines

Use this command to associate an interface with a VRF. Executing this command on an interface removes the IP address. The IP address should be reconfigured.

Examples

The following example shows how to link a VRF to ATM interface 0/0:

Router(config)# interface atm0/0

Router(config-if)# ip vrf forwarding vpn1

Related Commands

Command	Description
ip route vrf	Establishes static routes for a VRF.
ip vrf	Configures a VRF routing table.

keepalive-lifetime

To specify the duration that a keepalive message from a Multiprotocol over ATM server (MPS) is considered valid by the Multiprotocol over ATM client (MPC), use the keepalive-lifetime command in global configuration mode.

keepalive-lifetime seconds

Syntax Description

seconds

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

Defaults

The default is 35 seconds.

Command Modes

Global configuration

Command History

Release	Modification
12.0(3)T	This command was introduced.

Usage Guidelines

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

Examples

The following example shows how to specify a keepalive lifetime of 60 seconds:

Router(config)# keepalive-lifetime 60

Related Commands

Command	Description
keepalive-time	Specifies the keepalive time value for the MPS-p1 variable of an MPS.

keepalive-time

To specify the keepalive time value for the Multiprotocol over ATM (MPOA) server (MPS)-p1variable of an MPS, use the keepalive-time command in MPS configuration mode. To revert to the default value, use the no form of this command.

keepalive-time seconds

no keepalive-time seconds

Syntax Description

seconds

Specifies the keepalive time value (in seconds). The default value is 10 seconds.

Defaults

The default keepalive time is 10 seconds.

Command Modes

MPS configuration

Command History

Release	Modification
11.3(3a)WA4(5)	This command was introduced.

Examples

The following example shows how to set the keepalive time to 25 seconds:

Router(mpoa-server-config)# keepalive-time 25

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

config

(Optional) When the config keyword is used, this command applies only to the LAN Emulation Configuration Server (LECS). This keyword indicates that the LECS should use the auto computed LECS address.

Defaults

No specific ATM address is set.

Command Modes

Interface configuration

Command History

Release	Modification
11.0	This command was introduced.

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 network1

Router(lane-config-dat)# name eng server-atm-address 
39.020304050607080910111213.0800.AA00.1001.02

Router(lane-config-dat)# name mkt server-atm-address 
39.020304050607080910111213.0800.AA00.4001.01

Router(config)# interface atm 1/0

Router(config-if)# lane config database network1

Router(config-if)# lane config auto-config-atm-address

The 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.1

Router(config-if)# ip address 172.16.0.4 255.255.255.0

Router(config-if)# lane client ethernet

Router(config-if)# lane server-bus ethernet eng

Router(config-if)# lane auto-config-atm-address

Related Commands

Command	Description
lane config-atm-address	Specifies the ATM address of the configuration server explicitly.
lane database	Creates a named configuration database that can be associated with a configuration server.
lane fixed-config-atm-address	Specifies that the fixed configuration server ATM address assigned by the ATM Forum will be used.

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

atm-address-template

ATM address or a template in which wildcard characters are replaced by any nibble or group of nibbles of the prefix bytes, the end-system identifier (ESI) bytes, or the selector byte of the automatically assigned ATM address.

Defaults

For the broadcast and unknown server, the default is automatic ATM address assignment.

Command Modes

Interface configuration

Command History

Release	Modification
11.0	This command was introduced.

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:

–AFI (Authority and Format Identifier) field (1 byte)

–DCC (Data Country Code) or ICD (International Code Designator) field (2 bytes)

–DFI field (Domain Specific Part Format Identifier) (1 byte)

–Administrative Authority field (3 bytes)

–Reserved field (2 bytes)

–Routing Domain field (2 bytes)

–Area field (2 bytes)

•A 6-byte ESI

•A 1-byte selector field

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

Command	Description
lane server-bus	Enables a LANE server and a broadcast and unknown server on the specified subinterface with the ELAN ID.

lane 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 | tokenring} [elan-name]

no lane client {ethernet | tokenring} [elan-name]

Syntax Description

ethernet	Identifies the emulated LAN (ELAN) attached to this subinterface as an Ethernet ELAN.
tokenring	Identifies the ELAN attached to this subinterface as a Token Ring ELAN.
elan-name	(Optional) Name of the ELAN. This argument is optional because the client obtains its ELAN name from the configuration server. The maximum length of the name is 32 characters.

Defaults

No LANE clients are enabled on the interface.

Command Modes

Interface configuration

Command History

Release	Modification
11.0	This command was introduced.

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 a Token Ring LANE client on an interface:

Router(config-if)# lane client tokenring

Related Commands

Command	Description
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

atm-address-template

ATM address or a template in which wildcard characters are replaced by any nibble or group of nibbles of the prefix bytes, the end-system identifier (ESI) bytes, or the selector byte of the automatically assigned ATM address.

Defaults

Automatic ATM address assignment

Command Modes

Interface configuration

Command History

Release	Modification
11.0	This command was introduced.

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:

•A 13-byte prefix that includes the following fields defined by the ATM Forum:

–AFI (Authority and Format Identifier) field (1 byte)

–DCC (Data Country Code) or ICD (International Code Designator) field (2 bytes)

–DFI field (Domain Specific Part Format Identifier) (1 byte)

–Administrative Authority field (3 bytes)

–Reserved field (2 bytes)

–Routing Domain field (2 bytes)

–Area field (2 bytes)

•A 6-byte ESI

•A 1-byte selector field

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

Command	Description
lane client	Activates a LANE client on the specified subinterface.

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

Release	Modification
12.1(2)T	This command was introduced.

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 Configuring the no lane client flush command on a Cisco networking device does not guarantee the orderly delivery of incoming packets. There is a chance of receiving out-of-order packets at the destination during the establishment of a LANE data direct VCC.

---

Examples

The following example shows how to disable the flush mechanism of a LEC:

Router(config)# no lane client flush

Related Commands

Command	Description
lane client	Activates a LANE client on the specified subinterface.
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 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

mpc-name

Name of the specific MPC.

Defaults

No LEC is bound to a named MPC.

Command Modes

Interface configuration

Command History

Release	Modification
11.3(3a)WA4(5)	This command was introduced.

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_mpc

lane 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

mps-name

Name of the specific MPS.

Defaults

No LEC is bound to a named MPS.

Command Modes

Interface configuration

Command History

Release	Modification
11.3(3a)WA4(5)	This command was introduced.

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 MYMPS

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

config	(Optional) When the config keyword is used, this command applies only to the LANE Configuration Server (LECS). This keyword indicates that the LECS should use the 20-byte address that you explicitly entered.
atm-address-template	ATM address or a template in which wildcard characters are replaced by any nibble or group of nibbles of the prefix bytes, the end-system identifier (ESI) bytes, or the selector byte of the automatically assigned ATM address.

Defaults

No specific ATM address or method is set.

Command Modes

Interface configuration

Command History

Release	Modification
11.0	This command was introduced.

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:

•A 13-byte prefix that includes the following fields defined by the ATM Forum:

–AFI (Authority and Format Identifier) field (1 byte)

–DCC (Data Country Code) or ICD (International Code Designator) field (2 bytes)

–DFI field (Domain Specific Part Format Identifier) (1 byte)

–Administrative Authority field (3 bytes)

–Reserved field (2 bytes)

–Routing Domain field (2 bytes)

–Area field (2 bytes)

•A 6-byte ESI

•A 1-byte selector field

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 network1

Router(lane-config-dat)# name eng server-atm-address 
39.020304050607080910111213.0800.AA00.1001.02

Router(lane-config-dat)# name mkt server-atm-address 
39.020304050607080910111213.0800.AA00.4001.01

Router(config)# interface atm 1/0

Router(config-if)# lane config database network1

Router(config-if)# lane config config-atm-address 
39.020304050607080910111213.0800.AA00.3000.00

The 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.1

Router(config-if)# ip address 172.16.0.4 255.255.255.0

Router(config-if)# lane client ethernet

Router(config-if)# lane server-bus ethernet eng

Router(config-if)# lane config-atm-address 39.020304050607080910111213.0800.AA00.3000.00

Related Commands

Command	Description
lane auto-config-atm-address	Specifies that the configuration server ATM address is computed by the Cisco automatic method.
lane config database	Associates a named configuration table (database) with the configuration server on the selected ATM interface.
lane database	Creates a named configuration database that can be associated with a configuration server.
lane fixed-config-atm-address	Specifies that the fixed configuration server ATM address assigned by the ATM Forum will be used.

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

database-name

Name of the LAN emulation (LANE) database.

Defaults

No configuration server is defined, and no database name is provided.

Command Modes

Interface configuration

Command History

Release	Modification
11.0	This command was introduced.

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 network1

Router(lane-config-dat)# name eng server-atm-address 
39.020304050607080910111213.0800.AA00.1001.02

Router(lane-config-dat)# name mkt server-atm-address 
39.020304050607080910111213.0800.AA00.4001.01

Router(config)# interface atm 1/0

Router(config-if)# lane config database network1

Router(config-if)# lane config auto-config-atm-address

Related Commands

Command	Description
lane auto-config-atm-address	Specifies that the configuration server ATM address is computed by the Cisco automatic method.
lane config-atm-address	Specifies the ATM address of the configuration server explicitly.
lane database	Creates a named configuration database that can be associated with a configuration server.
lane fixed-config-atm-address	Specifies that the fixed configuration server ATM address assigned by the ATM Forum will be used.

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

database-name

Database name (32 characters maximum).

Defaults

No name is provided.

Command Modes

Global configuration

Command History

Release	Modification
11.0	This command was introduced.

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 network1

Router(lane-config-dat)# name eng server-atm-address 
39.020304050607080910111213.0800.AA00.1001.02

Router(lane-config-dat)# name mkt server-atm-address 
39.020304050607080910111213.0800.AA00.4001.01

Router(lane-config-dat)# default-name eng

Router(config)# interface atm 1/0

Router(config-if)# lane config database network1

Router(config-if)# lane config auto-config-atm-address

Related Commands

Command	Description
client-atm-address name	Adds a LANE client address entry to the configuration database of the configuration server.
default-name	Provides an ELAN name in the database of the configuration server for those client MAC addresses and client ATM addresses that do not have explicit ELAN name bindings.
lane config database	Associates a named configuration table (database) with the configuration server on the selected ATM interface.
mac-address	Sets the MAC-layer address of the Cisco Token Ring.
name	Assigns a name to the internal adapter.
name server-atm-address	Specifies or replaces the ATM address of the LANE server for the ELAN in the configuration database of the configuration server.

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

config

(Optional) When the config keyword is used, this command applies only to the LANE Configuration Server (LECS). This keyword indicates that LECS should use the well-known, ATM Forum LEC address.

Defaults

No specific ATM address or method is set.

Command Modes

Interface configuration

Command History

Release	Modification
11.0	This command was introduced.

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:

•If you configure the LECS with only the well-known address, the LECS will not participate in the SSRP, will act as a standalone master, and will listen only on the well-known LECS address. This scenario is ideal if you want a standalone LECS that does not participate in SSRP, and you would like to listen to only the well-known address.

•If only the well-known address is already assigned, and you assign at least one other address to the LECS (additional addresses are assigned using the lane auto-config-atm-address command or the lane config-atm-address command), the LECS will participate in the SSRP and act as the master or slave based on the normal SSRP rules. This scenario is ideal if you would like the LECS to participate in SSRP, and you would like to make the master LECS listen on the well-known address.

•If the LECS is participating in SSRP, has more than one address (one of which is the well-known address), and all the addresses but the well-known address are removed, the LECS will declare itself the master and stop participating in SSRP completely.

•If the LECS is operating as an SSRP slave, and it has the well-known address configured, it will not listen on the well-known address unless it becomes the master.

•If you want the LECS to assume the well-known address only when it becomes the master, configure the LECS with the well-known address and at least one other address.

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 network1

Router(lane-config-dat)# name eng server-atm-address 
39.020304050607080910111213.0800.AA00.1001.02

Router(lane-config-dat)# name mkt server-atm-address 
39.020304050607080910111213.0800.AA00.4001.01

Router(config)# interface atm 1/0

Router(config-if)# lane config database network1

Router(config-if)# lane config fixed-config-atm-address

The 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.1

Router(config-if)# ip address 172.16.0.4 255.255.255.0

Router(config-if)# lane client ethernet

Router(config-if)# lane server-bus ethernet eng

Router(config-if)# lane fixed-config-atm-address

Related Commands

Command	Description
lane auto-config-atm-address	Specifies that the configuration server ATM address is computed by the Cisco automatic method.
lane config-atm-address	Specifies the ATM address of the configuration server explicitly.
lane config database	Associates a named configuration table (database) with the configuration server on the selected ATM interface.

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

Release	Modification
12.0(4c)W5(10a)	This command was introduced.

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 fssrp

Related Commands

Command	Description
lane client	Activates a LANE client on the specified subinterface.
lane server	Activates a LANE server on the specified subinterface.
show lane client	Generates additional FSSRP information about a LANE client.
show lane config	Displays global LANE information for the configuration server configured on an interface.

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

address

Address of the LECS. You cannot use the well-known LECS address.

Defaults

No addresses are configured. The router obtains LECS addresses from the ILMI.

Command Modes

Interface configuration

Command History

Release	Modification
11.2	This command was introduced.

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 LAN emulation (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 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

mac-address	MAC address to bind to the specified ATM address.
route-desc segment segment-number	LANE segment number. The segment number ranges from 1 to 4095.
bridge bridge-number	Bridge number that is contained in the route descriptor. The bridge number ranges from 1 to 15.
atm-address	ATM address.

Defaults

No static address bindings are provided.

Command Modes

Interface configuration

Command History

Release	Modification
11.0	This command was introduced.

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.01

The 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.01

Related Commands

Command	Description
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

atm-address-template

ATM address or a template in which wildcard characters are replaced by any nibble or group of nibbles of the prefix bytes, the end-system identifier (ESI) bytes, or the selector byte of the automatically assigned ATM address.

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

Release	Modification
11.0	This command was introduced.

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:

•A 13-byte prefix that includes the following fields defined by the ATM Forum:

–AFI (Authority and Format Identifier) field (1 byte)

–DCC (Data Country Code) or ICD (International Code Designator) field (2 bytes)

–DFI field (Domain Specific Part Format Identifier) (1 byte)

–Administrative Authority field (3 bytes)

–Reserved field (2 bytes)

–Routing Domain field (2 bytes)

–Area field (2 bytes)

•A 6-byte ESI

•A 1-byte selector field

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

Command	Description
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 | tokenring} elan-name [elan-id id]

no lane server-bus {ethernet | tokenring} elan-name [elan-id id]

Syntax Description

ethernet	Identifies the ELAN attached to this subinterface as an Ethernet ELAN.
tokenring	Identifies the ELAN attached to this subinterface as a Token Ring ELAN.
elan-name	Name of the ELAN. The maximum length of the name is 32 characters.
elan-id	(Optional) Identifies the ELAN.
id	(Optional) Specifies the ELAN ID of the LAN emulation client (LEC).

Defaults

No LAN type or ELAN name is provided.

Command Modes

Interface configuration

Command History

Release	Modification
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 If an ELAN ID is supplied, make sure that it corresponds to the same ELAN ID value
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 a Token Ring ELAN named MYELAN:

Router(config-if)# lane server-bus tokenring myelan

Related Commands

Command	Description
lane server-atm-address	Specifies an ATM address and thus overrides the automatic ATM address assignment for the LANE server on a specified subinterface.
name elan-id	Configures the ELAN ID of an ELAN in the LECS database to participate in MPOA.

list

To show all or part of the explicit path or paths, use the list command in IP explicit path configuration mode.

list [starting-index-number]

Syntax Description

starting-index-number

(Optional) Index number at which the explicit path(s) will start to be displayed. Valid values are from 1 to 65535.

Defaults

Explicit paths are not shown.

Command Modes

IP explicit path configuration

Command History

Release	Modification
12.0(5)S	This command was introduced.

Examples

The following example shows how to list the explicit path:

Router(cfg-ip-expl-path)# list

Explicit Path name Joe:

    1:next-address 10.0.0.1

    2:next-address 10.0.0.2

The following example shows how to list the explicit path starting at index number 2:

Router(cfg-ip-expl-path)# list 2

Explicit Path name Joe:

    2:next-address 10.0.0.2

Router(cfg-ip-expl-path)#

Related Commands

Command	Description
append-after	Inserts the new path entry after the specified index number. Commands might be renumbered as a result.
index	Inserts or modifies a path entry at a specific index.
ip explicit-path	Enters the command mode for IP explicit paths, and creates or modifies the specified path.
next-address	Specifies the next IP address in the explicit path.
show ip explicit-paths	Displays the configured IP explicit paths.