Previous topic |
Next topic |
Contents |
Glossary |
Contact z/OS |
PDF
Automatic network routing (ANR) Networking on z/OS |
|
Automatic network routing (ANR) is a low-level routing mechanism that minimizes cycles and storage requirements for routing packets through intermediate nodes. An ANR node is an intermediate network node on the path of an RTP connection. ANR nodes are not aware of SNA sessions or RTP connections passing through the node. All an ANR node must do is read the header in a network layer packet and forward the information to the next node on the path. The ANR information is learned by the RTP endpoints during establishment of the RTP connection by sending a "Route Setup" message which flows through all nodes on the prospective HPR path. The ANR functions and services include:
ANR is a source-routing protocol and carries the routing information for each packet in a network header with the packet. Each node strips off the information it has used in the packet header before forwarding onto the link, so the next node can easily find its routing information at a fixed place in the header. This means that switching packets through a node can be done more quickly than in the routing table lookup method used in basic APPN. There is no restriction on the number of hops in ANR. Figure 1 shows how ANR routes messages. In the figure, the intermediate network node receives the message and strips the first routing label (A1) from the message header before forwarding the packet on link A1. The address of C5 represents the endpoint in the last HPR node. Since the routing is predetermined, the intermediate network node routes the packets very quickly, with no need to examine the request unit (RU) and/or the transmission header (TH), reserve storage or buffers, or to do link-level error recovery. The same mechanism takes place on the reverse route. |
Copyright IBM Corporation 1990, 2010
|