. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The repeater supports SNMP over IP. This requires the full implementation of
the UDP/IP protocol stack which includes address resolution protocols (ARP,
RARP, and BOOTP), a control and error message protocol (ICMP), and IP
fragmentation (supported to a maximum packet size of 1520 bytes).
For greater management flexibility, the IP stack is supported over both
ETHERNET_II (default) and 802.2 SNAP header with 802.3 frame types.
BOOTP, RARP, and TFTP packets originate from the repeater. For BOOTP
and RARP, both 802.2 SNAP over 802.3 and ETHERNET_II frame types are
sent consecutively. If the repeater receives a response, it uses the frame type of
the response to set the nw2IPFrameType MIB variable (stored in NVRAM). All
IP reception and transmission use the same frame type. To allow the repeater to
route any IP traffic, the frame type must also match the default gateway's frame
type. The repeater supports only one frame type (802.2 SNAP or
ETHERNET_II SNMP) per IP network.
The repeater performs the follow steps to determine the IP frame type to use:
1. If a response is received from a BOOTP or RARP server, use the frame
type of the received packet.
2. If no response is received from a BOOTP or RARP server, use the value
stored in NVRAM for the frame type.
3. If no value is stored in NVRAM, use the default value of
4. You can change the frame type at any time by setting the
nw2IPFrameType MIB variable through the VT100 interface or SNMP.
The repeater supports IPX over ETHERNET_II, 802.3 RAW, 802.2 header
with 802.3, and 802.2 SNAP header with 802.3 frame types. The default frame
type used by the repeater is 802.2 over 802.3.
Netelligent 2008/2016 10Base-T Repeater User Guide