Scenario: SNA direct connection of two System i models
This example shows a direct Systems Network Architecture (SNA) connection between two System i™ models.
The following figure shows a connection between a System i model in Minneapolis and a System i model in Madison over a frame-relay network.
Figure 1. SNA direct connection between Minneapolis and Madison systemsThe two systems have an Advanced Peer-to-Peer Networking® (APPN) connection that is configured on the frame-relay data link connection identifier (DLCI). Note that the frame-relay link in Minneapolis has much more traffic and operates at 1 536 000 bps. The link in Madison operates at 64 000 bps. The frame-relay network allows for this difference in subscriptions at the two sites.
The Minneapolis connection to the network uses DLCI 23. In Madison, the DLCI number is 21. If the connection uses a frame-relay network, the DLCI numbers have only local (terminal end (TE) to frame handler (FH)) significance and might be different on the two interfaces. The network is responsible for setting up the connection between the DLCIs at administration time.
If you require more than one Advanced Program-to-Program Communication (APPC) connection between the two sites, define additional source service access point (SSAP) and destination service access point (DSAP) values on the lines, and the additional controllers need different SSAP and DSAP combinations.
- Scenario details: Configuration for the System i model in Minneapolis
To configure the System i model in Minneapolis, use these commands.- Scenario details: Configuration for the System i model in Madison
To configure the System i model in Madison, use these commands.
Parent topic:
Scenarios: SNA direct connection for frame relay