Statically Associating the Shared IP Interface with the Layer 2 Interface

You can specify the layer 2 interface used by a shared IP interface using the ip share-interface command. The command fails if the layer 2 interface does not yet exist. The command is not supported (that is, it fails) if you use an RSVP tunnel (for example, tunnel mpls:1) to identify the layer 2 interface.

After creating the shared IP interface, you can configure it as you do any other IP interface.

The shared interface is operationally up when the layer 2 interface is operationally up.

You can create operational shared IP interfaces in the absence of a primary IP interface.

All IP configurations will be removed from the interface when you issue the no ip interface command in Interface Configuration mode. You cannot issue the ip share-nexthop command for the IP shared interface if the ip share-interface command is issued on the IP shared interface.

To specify the layer 2 interface to be used by a shared IP interface:

• Issue the ip share-interface command in Interface Configuration mode.
  host1(config-if)#ip share-interface atm 5/3.101

  Use the no version to remove the association between the layer 2 interface and the shared IP interface. You can delete shared and primary IP interfaces independently.

Related Documentation

• Shared IP Interfaces Overview
• IP Shared Interface Statistics Overview
• Monitoring IP Shared Interfaces
• ip share-interface
• ip share-nexthop
• no ip interface