Devices That Do Not Use Arp; Reverse Arp - Cisco Nexus 3000 Series Configuration Manual

Nx-os unicast routing configuration guide, nx-os release 5.0(3)u1(1)
Hide thumbs Also See for Nexus 3000 Series:
Table of Contents

Advertisement

Information About IPv4
S e n d d o c u m e n t c o m m e n t s t o n e x u s 3 k - d o c f e e d b a c k @ c i s c o . c o m

Devices that Do Not Use ARP

When a network is divided into two segments, a bridge joins the segments and filters traffic to each
segment based on MAC addresses. The bridge builds its own address table, which uses MAC addresses
only, as opposed to a switch, which has an ARP cache that contains both IP addresses and the
corresponding MAC addresses.
Passive hubs are central-connection switches that physically connect other switches in a network. They
send messages out on all their ports to the switches and operate at Layer 1 but do not maintain an address
table.
Layer 2 switches determine which port is connected to a device to which the message is addressed and
send only to that port, unlike a hub, which sends the message out all its ports. However, Layer 3 switches
are switches that build an ARP cache (table).

Reverse ARP

Reverse ARP (RARP) as defined by RFC 903 works the same way as ARP, except that the RARP request
packet requests an IP address instead of a MAC address. RARP often is used by diskless workstations
because this type of device has no way to store IP addresses to use when they boot. The only address that
is known is the MAC address because it is burned into the hardware.
Use of RARP requires an RARP server on the same network segment as the router interface.
illustrates how RARP works.
Figure 2-2
There are several limitations of RARP. Because of these limitations, most businesses use DHCP to assign
IP addresses dynamically. DHCP is cost effective and requires less maintenance than RARP. The
following are the most important limitations:
Cisco Nexus 3000 Series NX-OS Unicast Routing Configuration Guide, NX-OS Release 5.0(3)U1(1)
2-4
Reverse ARP
Since RARP uses hardware addresses, if the internetwork is large with many physical networks, a
RARP server must be on every segment with an additional server for redundancy. Maintaining two
servers for every segment is costly.
Each server must be configured with a table of static mappings between the hardware addresses and
IP addresses. Maintenance of the IP addresses is difficult.
RARP only provides IP addresses of the hosts and not subnet masks or default gateways.
Chapter 2
Configuring IPv4
Figure 2-2

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents