AIS AI2524 user manual Create a Broadcast Queue for an Interface, No further action is required

AI2524 Router Card User’s Manual

Disable or Reenable Frame Relay Inverse ARP

Frame Relay Inverse ARP is a method of building dynamic address mappings in Frame Relay networks running IP and Novell IPX. In- verse ARP allows the router or access server to discover the protocol address of a device associated with the virtual circuit.

Inverse ARP creates dynamic address mappings, as contrasted with the frame-relay map command, which defines static mappings between a specific protocol address and a specific DLCI.

Inverse ARP is enabled by default but can be disabled explicitly for a given protocol and DLCI pair. Disable or reenable Inverse ARP under these conditions:

zDisable Inverse ARP for a selected protocol and DLCI pair when you know that the protocol is not supported on the other end of th connection.

zReenable Inverse ARP for a protocol and DLCI pair if conditions or equipment change and the protocol is then supported on the oth- er end of the connection.

Note:	If you change from a point-to-point subinterface to a
	multipoint subinterface, then change the subinterface
	number. Frame Relay Inverse ARP will be on by default,
	and no further action is required.

You do not need to enable or disable Inverse ARP if you have a point- to-point interface, because there is only a single destination and dis- covery is not required.

To select Inverse ARP or disable it, perform one of these tasks in in- terface configuration mode:

zEnable Frame Relay Inverse ARP for a specific protocol and DLCI pair, only if it was previously disabled.

frame-relay inverse-arp protocol dlci

zDisable Frame Relay Inverse ARP for a specific protocol and DLCI pair.

no frame relay inverse-arp protocol dlci

Create a Broadcast Queue for an Interface

Very large Frame Relay networks might have performance problems when many DLCIs terminate in a single router or access server that must replicate routing updates and service advertising updates on each DLCI. The updates can consume access-link bandwidth and cause sig- nificant latency variations in user traffic; the updates can also consum

Page 13-38	August 1997
	2524UM