User`s guide

8-8 Preliminary November 23, 1998 MultiVoice Gateway for the MAX— User’s Guide
Configuring IP Routing
Configuring the local IP network setup
Enabling RIP on the Ethernet interface
You can configure the IP interface to send RIP updates (inform other local routers of its
routes), receive RIP updates (learn about networks that can be reached through other routers on
the Ethernet), or both.
Note: Ascend recommends that you run RIP version 2 (RIP-v2) if possible. You should not
run RIP-v2 and RIP-v1 on the same network in such a way that the routers receive each other’s
advertisements. RIP-v1 does not propagate subnet mask information, and the default-class
network mask is assumed, while RIP-v2 handles subnet masks explicitly. Running the two
versions on the same network can result in RIP-v1 class subnet mask assumptions overriding
accurate subnet information obtained via RIP-v2.
Ignoring the default route
You can configure the MultiVoice Gateway to ignore default routes advertised by routing
protocols. This configuration is recommended, because you typically do not want the default
route changed by a RIP update. The default route specifies a static route to another IP router,
which is often a local router such as an Ascend GRF400 or other kind of LAN router. When the
MultiVoice Gateway is configured to ignore the default route, RIP updates do not modify the
default route in the MultiVoice Gateway routing table.
Proxy ARP and inverse ARP
The MultiVoice Gateway can be configured to respond to ARP requests for remote devices that
have dynamically assigned addresses. It responds to the ARP request with its own MAC
address while bringing up the connection to the remote device. This feature is referred to as
Proxy ARP.
The MultiVoice Gateway also supports Inverse Address Resolution Protocol (Inverse ARP).
Inverse ARP allows the MultiVoice Gateway to resolve the protocol address of another device
when the hardware address is known. The MultiVoice Gateway does not issue any Inverse
ARP requests, but it does respond to Inverse ARP requests that have the protocol type of IP
(8000 hexadecimal), or in which the hardware address type is the two-byte Q.922 address
(Frame Relay). All other types are discarded. The Inverse ARP response packet sent by the
MultiVoice Gateway includes the following information:
• ARP source-protocol address (the MultiVoice Gateway unit’s IP address on Ethernet)
• ARP source-hardware address (the Q.922 address of the local DLCI)
(For the details of Inverse ARP, see RFCs 1293 and 1490.)
Telnet password
The Telnet password is required from all users attempting to access the MultiVoice Gateway
unit by Telnet. Users are allowed three tries to enter the correct password, after which the
connection attempt fails.
BOOTP Relay
By default, a MultiVoice Gateway does not relay BOOTP (Bootstrap Protocol) requests to
other networks. It can do so if BOOTP is enabled, but SLIP BOOTP must be disabled in