Example: Two APPN networks with different network IDs linked together

Figure 7 shows two APPN networks that are linked together by network nodes.

The network with the LCLNETID of NEWNET is a simple connection of one end node to one network node. Network node B might act as a network server providing routing services for node A. Although there are no other nodes in the NEWNET network, there is a need for nodes A and B to communicate with the nodes in network APPN. To accomplish this, network node B is connected to network node NN1 in the APPN network. Node B must have a line description and a controller description created to identify node A, and a line description and a controller description to identify node NN1.

The network with the LCLNETID of APPN is similar to NEWNET; with the exception that NN2 is a network node instead of an end node. In order for NN1 and NN2 to communicate with the nodes in NEWNET, NN1 must have two line descriptions, and two controller descriptions created. These identify both node B and node NN2.

After node B and node NN1 are identified to each other as adjacent nodes, all nodes in either network can communicate through nodes B and NN1.

Figure 7. Two APPN networks linked by network nodes

Each list below represents a city within the network in Figure 7 above. See the links in each list to determine the configuration requirements for each system.

New York

• Example: Configure system: New York
• Change the network attributes (New York) for two APPN networks with different IDs
• Create the line description (New York)
• Create the controller description (New York) for two-system network with different IDs

Detroit

• Example: Configure system B (Detroit)
• Change the network attributes (Detroit)
• Create the line description (Detroit to New York)
• Create the controller description (Detroit to New York)
• Create the line description (Detroit to Chicago)
• Create the controller description (Detroit to Chicago)

Chicago

• Example: Configure system NN1 (Chicago)
• Change the network attributes (Chicago) for two-system APPN network with different IDs
• Create the line description (Chicago to Minneapolis) for two-system APPN network with different IDs
• Create the controller description (Chicago to Minneapolis) for two-system APPN network with different IDs
• Create the line description (Chicago to Detroit)
• Create the controller description (Chicago to Detroit)

Minneapolis

• Example: Configure NN2 (Minneapolis)
• Change the network attributes (Minneapolis) for two networks with different ID's
• Create the line description (Minneapolis to Chicago)
• Create the controller description (Minneapolis to Chicago)