background image
Advanced Peer-to-Peer Networking (APPN) 491
Second-Generation SNA: APPN
APPN was designed by IBM to meet the following requirements:
·
Provide an effective routing protocol to allow SNA traffic to flow natively and
concurrently with other protocols
·
Allow sessions to be established between end users without the involvement of the
mainframe
·
Reduce requirements for predefined resources and paths
·
Maintain and enhance Class of Service (COS) to provide prioritization within SNA traffic
·
Provide an environment that supports both legacy and APPN traffic
APPN Terminology
It is important to define APPN terms before moving on to the rest of this section. APPN has
what is known as a network node, usually defined as a Cisco router. The network node is a PU
2.1 in IBM terminology. Network nodes typically have control points (CPs) that communicate
with neighboring network node control points and exchange information. There are also end
nodes, which could be PU 2.1. End nodes provide end-user services and are usually located on
the outskirts of the APPN network. A third type of node is called the low entry node (LEN),
which represents dumb nodes. LENs were developed before APPN, and they need to have
resources defined to them. The fourth and final type of node is the mainframe, which is called
a composite network node.
Control points activate resources in a node. Control points are also where local resources are
defined.
The question arises: What routing protocol is used to propagate this SNA information from
router to router? Two routing protocols are used. The first one, developed by IBM, was
intermediate session routing (ISR). The new development is high-performance routing (HPR).
ISR and HPR
End stations can use two methods to communicate over the routers. The first is intermediate
session routing (ISR). A single session is divided into stages, as shown in Figure 13-15. Each
session has a unique identifier, called the Local-Form Session Identifier (LFSID). In Figure
13-15, there is a session 123 between the Token Ring PC and the router. There is also a unique
session between the two routers, labeled 456. As a message traverses the routers, the entire
message must be buffered. Error detection, error correction, flow control, and resegmentation
might occur at each point, not at the end stations. At each router, the incoming unique LFSID
is swapped for the outgoing unique LFSID. So the only things that must be remembered are the
label and port in both directions. The major drawback of ISR is that it is very much like IP static
routing and cannot reroute around failures. In addition, much checking and verifying are done
at each stop rather than just at the connection's endpoints.
87200333.book Page 491 Wednesday, August 22, 2001 1:41 PM