12.07.2015 Views

Cisco IOS Wide-Area Networking Configuration Guide - Free Books

Cisco IOS Wide-Area Networking Configuration Guide - Free Books

Cisco IOS Wide-Area Networking Configuration Guide - Free Books

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Configuring Dynamic or Static Address MappingConfiguring Frame RelayStep 1Step 2CommandRouter(config)# interface typenumberRouter(config-if)# encapsulationframe-relay [ietf]PurposeSpecifies the interface, and enters interface configuration mode.Enables and specifies the Frame Relay encapsulation method.Frame Relay supports encapsulation of all supported protocols in conformance with RFC 1490, allowinginteroperability among multiple vendors. Use the Internet Engineering Task Force (IETF) form of FrameRelay encapsulation if your router or access server is connected to another vendor’s equipment across aFrame Relay network. IETF encapsulation is supported either at the interface level or on a per-VC basis.Shut down the interface prior to changing encapsulation types. Although shutting down the interface isnot required, it ensures that the interface is reset for the new encapsulation.For an example of enabling Frame Relay encapsulation on an interface, see the section “IETFEncapsulation Examples” later in this chapter.Configuring Dynamic or Static Address MappingDynamic address mapping uses Frame Relay Inverse ARP to request the next-hop protocol address fora specific connection, given its known DLCI. Responses to Inverse ARP requests are entered in anaddress-to-DLCI mapping table on the router or access server; the table is then used to supply thenext-hop protocol address or the DLCI for outgoing traffic.Inverse ARP is enabled by default for all protocols it supports, but can be disabled for specificprotocol-DLCI pairs. As a result, you can use dynamic mapping for some protocols and static mappingfor other protocols on the same DLCI. You can explicitly disable Inverse ARP for a protocol-DLCI pairif you know that the protocol is not supported on the other end of the connection. See the section“Disabling or Reenabling Frame Relay Inverse ARP” later in this chapter for more information.See the following sections for further details on configuring dynamic or static address mapping:• Configuring Dynamic Address Mapping• Configuring Static Address MappingConfiguring Dynamic Address MappingInverse ARP is enabled by default for all protocols enabled on the physical interface. Packets are not sentout for protocols that are not enabled on the interface.Because Inverse ARP is enabled by default, no additional command is required to configure dynamicmapping on an interface.Configuring Static Address MappingA static map links a specified next-hop protocol address to a specified DLCI. Static mapping removesthe need for Inverse ARP requests; when you supply a static map, Inverse ARP is automatically disabledfor the specified protocol on the specified DLCI.You must use static mapping if the router at the other end either does not support Inverse ARP at all ordoes not support Inverse ARP for a specific protocol that you want to use over Frame Relay.4

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!