09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

Figure 3.3. The AppleTalk address structure.<br />

The <strong>network</strong> and node addresses are assigned dynamically when <strong>the</strong><br />

node joins <strong>the</strong> <strong>network</strong>.<br />

When a node first joins <strong>the</strong> <strong>network</strong>, it acquires a provisional address.<br />

The node address portion is randomly selected from <strong>the</strong> number<br />

range 1 <strong>to</strong> 254 (0 and 255 are reserved). The <strong>network</strong> portion is<br />

assigned by <strong>the</strong> Layer 2 pro<strong>to</strong>col (ELAP, LLAP, TTAP, or FDAP) from a<br />

reserved class of <strong>network</strong> addresses spanning from 65,280 (FFF0<br />

hexidecimal) <strong>to</strong> 65,534 (FFFE hexidecimal). These <strong>network</strong> addresses<br />

are recognized by all AppleTalk nodes as provisional addresses. After<br />

<strong>the</strong> provisional address is acquired, a permanent address is needed.<br />

The node <strong>the</strong>n sends a GetNetInfo request using <strong>the</strong> Zone<br />

Information Pro<strong>to</strong>col (ZIP). If a router responds, <strong>the</strong> available<br />

<strong>network</strong> number(s) is returned with <strong>the</strong> ZIP reply. The node <strong>the</strong>n uses<br />

that <strong>network</strong> number, generates ano<strong>the</strong>r random node ID, and<br />

broadcasts this number across <strong>the</strong> segment. If no nodes respond<br />

claiming rights <strong>to</strong> that address, <strong>the</strong> node uses <strong>the</strong> address. If a node<br />

responds claiming ownership <strong>to</strong> that ID, <strong>the</strong> node must repeat <strong>the</strong><br />

node generation and validation process until it selects a node address<br />

that is not in use.<br />

If no router is available or <strong>the</strong> <strong>network</strong> type is Phase 1, <strong>the</strong> <strong>network</strong><br />

address is set <strong>to</strong> 0 and <strong>the</strong> node sends a broadcast <strong>to</strong> see if its address<br />

conflicts with ano<strong>the</strong>r node. If it doesn't, it becomes <strong>the</strong> node's<br />

permanent address. After a node address is acquired, it is s<strong>to</strong>red by<br />

<strong>the</strong> end-station for later use. If <strong>the</strong> node leaves <strong>the</strong> <strong>network</strong> and<br />

returns at a later point, it attempts <strong>to</strong> validate its previous address. If<br />

<strong>the</strong>re are no conflicts, it continues <strong>to</strong> use <strong>the</strong> address.

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

Saved successfully!

Ooh no, something went wrong!