Visara FEP-4600 Planning Guide - Manual (Page 72)

Chapter 6. Support of PU 4 Connections
6-16 707117-003
In this second scenario, the 3745 continues to provide the connection to subareas 14 and
10. The FEP-4600 is providing the connection to subareas 24 and 22. By configuring the
FEP-4600 to identify itself to the NCP in SA24 to be SA04, it will not be necessary to
reconfigure the gens for SA24 and SA22. The FEP-4600 is configured to identify itself as
SA05 to the VTAM in SA03. A PATH statement must be added to identify the new
SA05. The PATH statements that identify the paths to SA24 and SA22 will need to be
modified to route the traffic through SA05.
Scenario 3: Replacing 37x5 with Links to Multiple Locations
This situation calls for the FEP-4600 to provide connections to two different remote
NCPs. (The network is the same as scenario 2, perhaps after the complete migration.) In
this case, a second subarea is assigned to the FEP-4600 on the ESCON side to be used in
addition to the subarea previously owned by the 3745. Both remote NCPs view the FEP-
4600 as SA04, requiring no changes to the gens in the remote VTAMs and NCPs. The
local VTAM sees the FEP-4600 as SA07 when it wants to communicate with SA10 or
SA14. When VTAM wants to communicate with SA24 or SA22, it views the FEP-4600
as SA05. This is required so that VTAM will use the correct link (CTC connection) to
direct the traffic to the appropriate destination.
VTAM
SA03
NCP
SA04
Before
CPU 3745
3745 CPU
NCP
SA14
VTAM
SA10
3745 CPU
NCP
SA24
VTAM
SA22