25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Basic InATMARP operates essentially the same as ARP, with the exception that<br />

InATMARP does not broadcast requests. This is because the hardware address<br />

of the destination station is already known. A requesting station simply formats a<br />

request by inserting its source hardware <strong>and</strong> <strong>IP</strong> address <strong>and</strong> the known target<br />

hardware address. It then zero fills the target protocol address field <strong>and</strong> sends it<br />

directly to the target station. For every InATMARP request, the receiving station<br />

formats a reply using the source address from the request as the target address<br />

of the reply. Both sides update their ARP tables. The hardware type value for<br />

ATM is 19 decimal <strong>and</strong> the EtherType field is set to 0x806, which indicates ARP,<br />

according to RFC 3232.<br />

Address resolution in a PVC environment<br />

In a PVC environment, each station uses the InATMARP protocol to determine<br />

the <strong>IP</strong> addresses of all other connected stations. The resolution is done for those<br />

PVCs that are configured for LLC/SNAP encapsulation. It is the responsibility of<br />

each <strong>IP</strong> station supporting PVCs to revalidate ARP table entries as part of the<br />

aging process.<br />

Address resolution in an SVC environment<br />

SVCs require support for ATMARP in the non-broadcast environment of ATM. To<br />

meet this need, a single ATMARP server must be located within the Logical <strong>IP</strong><br />

Subnetwork (LIS) (see “The Logical <strong>IP</strong> Subnetwork (LIS)” on page 53). This<br />

server has authoritative responsibility for resolving the ATMARP requests of all <strong>IP</strong><br />

members within the LIS. For an explanation of ATM terms, refer to 2.10.2,<br />

“Classical <strong>IP</strong> over ATM” on page 50.<br />

The server itself does not actively establish connections. It depends on the<br />

clients in the LIS to initiate the ATMARP registration procedure. An individual<br />

client connects to the ATMARP server using a point-to-point VC. The server,<br />

upon the completion of an ATM call/connection of a new VC specifying<br />

LLC/SNAP encapsulation, will transmit an InATMARP request to determine the<br />

<strong>IP</strong> address of the client. The InATMARP reply from the client contains the<br />

information necessary for the ATMARP server to build its ATMARP table cache.<br />

This table consists of:<br />

► <strong>IP</strong> address<br />

► ATM address<br />

► Time stamp<br />

► Associated VC<br />

This information is used to generate replies to the ATMARP requests it receives.<br />

48 <strong>TCP</strong>/<strong>IP</strong> <strong>Tutorial</strong> <strong>and</strong> <strong>Technical</strong> <strong>Overview</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!