Visara FEP-4600 Planning Guide User Manual

Page 85

37x5 to FEP-4600 Migration and Planning Guide

707117-003

7-5

Example 2:

This example is very nearly the same, except that this time both LPARs have access
directly to the FEP-4600 (both have a CTC definition for the FEP-4600). Note that on the
FEP-4600 it will be necessary to use a separate CU definition to connect to each of the
two LPARs.

RESOURCE PARTITION=((PRODA,1),(PRODC,3))

CHPID PATH=(1F),TYPE=CNC,SWITCH=03

CHPID PATH=(27),TYPE=CNC,SWITCH=03

CNTLUNIT CUNUMBR=1F00,PATH=1F,UNITADD=((00,1)),UNIT=SCTC,CUADD=0,LINK=C5

IODEVICE CUNUMBR=1F00,ADDRESS=(680,1)UNIT=SCTC,UNITADD=00,PARTITION=(PRODA)

CNTLUNIT CUNUMBR=1800,PATH=27,UNITADD=((00,1)),UNIT=SCTC,CUADD=0,LINK=C5

IODEVICE CUNUMBR=1800,ADDRESS=(260,1)UNIT=SCTC,UNITADD=00,PARTITION=( PRODC)

This time each LPAR requires its own CHPID. Because an ESCON switch is being used,
a single ESCON interface into the FEP-4600 can be used. The FEP-4600 can
communicate with up to 16 LPARs over a single ESCON interface. However for
PU4/SNI communications, a separate CU should be used for each PU4/SNI connection.
If no ESCON switch were in use, then each LPAR would need a separate ESCON
channel. A similar configuration on a system that supports logical subsystems would
appear similar to the configuration below.

RESOURCE PARTITION=(CSS(0),(PRODA,1),(PRODC,3))

CHPID PATH=(CSS(0),1F),TYPE=CNC,SWITCH=03,PART=(PRODA),PCHID=370

CHPID PATH=(CSS(0),27),TYPE=CNC,SWITCH=03,SHARED,PART=(PRODC),PCHID=372

CNTLUNIT CUNUMBR=1F00,PATH=(CSS(0),1F),UNITADD=((00,1)),UNIT=SCTC,LINK=(CSS(0),C5)

IODEVICE CUNUMBR=1F00,ADDRESS=(680,1)UNIT=SCTC,UNITADD=00,PARTITION=(CSS(0),PRODA)

CNTLUNIT CUNUMBR=1800,PATH=(CSS(0),27),UNITADD=((00,1)),UNIT=SCTC,LINK=(CSS(0),C5)

IODEVICE CUNUMBR=1800,ADDRESS=(260,1)UNIT=SCTC,UNITADD=00,PARTITION=(CSS(0),PRODC)

FEP-4600

PRODA

PRODC

Remote Networks

CPU

SW03