The addressto-DLCI mapping table displays useful information.

Example 4-16 shows the output of the show frame-relay map privileged EXEC mode command. Because dynamic Inverse ARP is enabled by default, no additional Cisco IOS command is required to enable it on an interface. For example, no dynamic Inverse ARP resolution is performed for IPX if ipx routing is not enabled globally and there is no active IPX address assigned to the interface. Packets are not sent out for network layer protocols that are not enabled on the physical interface. On Cisco routers, dynamic Inverse ARP is enabled by default for all network layer protocols enabled on the physical interface. Finally, the router places the frames targeted to the remote destination on its identified outgoing local DLCI. Subsequently, the router consults its address-to-DLCI mapping table for the local DLCI that corresponds to the next hop address. When data needs to be transmitted to a remote destination address, the router performs a lookup on its routing table to determine whether a route to that destination address exists and the next hop address or directly connected interface to use in order to reach that destination. The router builds and maintains this address-to-DLCI mapping table, which contains all resolved Inverse ARP requests, including both dynamic and static mapping entries. The responses to the Inverse ARP requests are used to populate an address-to-DLCI mapping table on the Frame Relay router or access server. The Frame Relay router sends out Inverse ARP requests on its Frame Relay PVC to discover the protocol address of the remote device connected to the Frame Relay network. Frame-Relay (a Layer 2 protocol) uses Inverse-Arp to map a know Layer 2 Address (DLCI) to a unknow Layer 3 Address.ĭynamic address mapping relies on the Frame Relay Inverse Address Resolution Protocol (Inverse ARP), defined by RFC 1293, to resolve a next hop network protocol address to a local DLCI value.

What is the purposes of arp