. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NOTE: This USRBOOTP file is only an example. For information about the
appropriate file for your specific BOOTP server, refer to the BOOTP
If the repeater receives no response for any the BOOTP or RARP requests and
if the repeater already has a valid IP address stored in NVRAM, the NVRAM
IP address is used.
Once in Runtime, if there is not a valid IP address in NVRAM and the
nw2BootpRarpRequests MIB variable is set to doBootpRarp(1), the firmware
loops until it receives a valid IP address. The following information describes
various repeater operations and limitations of the IP address search loop.
Every 5 minutes, the repeater makes a BOOTP request. If the repeater
does not receive a BOOTP response within 5 seconds, it makes a RARP
request. If the repeater does not receive a RARP response within 5
seconds, it waits 5 minutes and then re-issues the
The repeater can receive an IPX set request during the 5-minute interval
when it is not making BOOTP/RARP requests. If an IPX set request
occurs during the 10-second BOOTP/RARP period, the repeater ignores
the request (i.e., the request times out).
You can use SNMP over IPX to set the repeater's IP address during the
5-minute interval when the repeater is not making BOOTP/RARP
requests If an SNMP over IPX set request occurs during the 10-second
BOOTP/RARP period, the repeater ignores the request (i.e., the request
VT100 can be used at any time.
NOTE: The repeater may periodically disable SNMP requests during the BOOT/RARP
request intervals, reducing network management performance for IPX-only
networks. To prevent this from occurring, either assign an IP address to each
repeater or set the nw2BootpRarpRequests MIB object to noBootpRarp(2), which
disables the periodic BOOTP/RARP requests in Runtime and in Boot if you have
Netelligent 2008/2016 10Base-T Repeater User Guide