[ Pobierz całość w formacie PDF ]

LLC2 connections are needed, define additional XCA major nodes. Multiple XCA major nodes can
also be configured for availability, with each one pointing to a different CIP.
The CSNA feature is defined to the host control program (MVS or VM) as being a
channel-to-channel adapter or machine (CTCA), for example, a 3088. VTAM identifies the CSNA
gateway through a combination of the following:
" ADAPNO Adapter number
" CUADD Subchannel address
" SAPADDR SAP address
XCANAME VBUILD TYPE=XCA ** EXTERNAL COMMUNICATION ADAPT**
PORTNAME PORT ADAPNO=?, ** RELATIVE ADAPTER NUMBER ** X
CUADDR=???, ** CHANNEL UNIT ADDRESS ** X
MEDIUM=RING, ** LAN TYPE ** X
SAPADDR=4 ** SERVICE ACCESS POINT ADDRESS**
GRPNAME GROUP ANSWER=ON, ** PU DIAL INTO VTAM CAPABILITY** X
AUTOGEN=(5,L,P), ** AUTO GENERATE LINES AND PUS ** X
CALL=INOUT, ** IN/OUT CALLING CAPABILITY ** X
DIAL=YES, ** SWITCHED CONNECTION ** X
ISTATUS=ACTIVE ** INITIAL ACTIVATION STATUS **
Switched Major Node Definition
Configure one or more switched major nodes. Within a switched major node definition, configure
every SNA PU that will access VTAM through the CIP. For each PU, configure its associated LUs.
Many networks today already have the SNA devices defined in a switched major node. For example,
if the devices attach to a FEP over Token Ring, they are already defined as part of a switched major
node. In this case, the only change is to add the XCA major node.
SWMSNAME VBUILD TYPE=SWNET, ** X
MAXGRP=14, ** X
MAXNO=64 **
PUNAME PU ADDR=01, ** X
PUTYPE=2, ** X
IDBLK=???, ** X
IDNUM=?????, ** X
3-2 Data Center Design and Implementation: SNA Internetworking
Router Configuration
ISTATUS=ACTIVE **
LUNAME1 LU LOCADDR=02
LUNAME2 LU LOCADDR=03
LUNAME3 LU LOCADDR=04
LUNAME4 LU LOCADDR=05
LUNAME5 LU LOCADDR=06
Router Configuration
The router must be configured to:
" Bridge traffic from a physical LAN or a router component (DLSw+, SRB, SR/TLB, and so forth)
onto the router virtual ring
" Bridge data from the router virtual ring to one of the CIP internal rings, or connect a data link
user (APPN, DSPU) to one of the CIP internal rings
" Connect the CIP to VTAM
Figure 3-2 shows the major configuration parameters of the CIP and of the Token Ring interfaces
and how they are logically combined using the source-bridge definition. The CIP ring is referred to
as an internal ring. The RSP ring is referred to as a virtual ring.
Figure 3-2 Using Virtual Rings to Provide Connectivity
CIP Router Configuration
adapter 0 4000.7513.0001
CSNA lan tokenring 0
Internal Ring
300
source-bridge 300 1 100
Bridge 1
Virtual Ring
Group 100
source-bridge ring-group 100
interface tokenring 1
Bridge 1 source-bridge 1 1 100
TRIP
Token
Ring
Real Segment
Configure an adapter on the CIP to be associated with the XCA major node definition. For each
adapter configured, CSNA creates an internal Token Ring. A virtual bridge connects the CSNA
internal ring to a virtual ring group in the router. The Token Ring interface processor (TRIP) is also
configured to connect to the same virtual ring group as the CIP.
Migration Scenarios 3-3
Router Configuration
Configuration Relationships in the ESCON Environment
Figure 3-3 shows the relationship among router configuration, VTAM parameters, and MVS IOCP
generation commands when the CIP connects via an Escon director. Figure 3-4 shows the
relationship among router configuration, VTAM parameters, and MVS IOCP generation commands
when the CIP connects via bus and tag.
Figure 3-3 Relationship among MVS, VTAM, and Router Configurations: ESCON
Router Configuration IOCP
ESCON Director
source-bridge ring-group 100 resource part=((lpar1,1), (lpar2 2 ))
interface channel 1/0
chpid path=((21)),type=cnc,
A2 C1
csna C1 2 0 10
shared,switch=3,
partition=( lpar2 )
interface channel 1/2
lan tokenring 0
cntlunit cunumbr= 000e,
source-bridge 1 2 100
path=(21),unit=sctc,
adapter 0 4000.7513.0001
unitadd=(( 10,16 )),
link= a2, cuadd= 0
VTAM Configuration iodevice address= (110,16) ,
cunumbr=( 000e ),
vbuild type=xca
unit=sctc
port adapno= 0 ,cuaddr= 110,
sapaddr=04, medium=ring
group answer=no, autogen=(25,I,p),
call=inout,dial=yes
3-4 Data Center Design and Implementation: SNA Internetworking
Scenario 1: Single CIP to Single Host
Configuration Relationships in the Bus and Tag Environment
Figure 3-4 Relationship among MVS, VTAM, and Router Configurations: Bus and Tag
Router Configuration IOCP
source-bridge ring-group 100 chpid path=((21)),type=bl
interface channel 1/0
cntlunit cunumber= 000e,
csna 0100 10
path=(21),unit=3088,
protocol s4
unitadd=(( 10,16 )),
interface channel 1/2
shared=n ,protocl=s4
lan tokenring 0
source-bridge 300 1 100
iodevice address= ( 110,16 ) ,
adapter 0 4000.7513.0001
cunumbr=( 000e ),
unit=ctc
VTAM Configuration
vbuild type=xca
port adapno= 0 ,cuaddr= 110,
sapaddr=04, medium=ring
group answer=no, autogen=(25,I,p),
call=inout,dial=yes
Scenario 1: Single CIP to Single Host
The first scenario is a network that replaces a FEP with a CIP. As shown in Figure 3-5, there is a
single mainframe in this network. Historically, IBM SNA networks were built using the IBM FEP,
and remote terminals were connected via SDLC links. In the Before scenario, a second FEP was in
place for backup only.
In the After scenario, one FEP has been replaced with a channel-attached router with a CIP. Both the
CIP and the remaining FEP have the same MAC address. Eventually the second FEP will also be
replaced, but for now it provides SNI connectivity to a supplier and can also function as a backup to
the CIP. DLSw+ is used to transport SNA traffic from remote sites to the central site.
Once data reaches the headquarters site, DLSw+ sends most traffic to the CIP, which will typically
be the first to respond to explorers, but in the event that the CIP is not available, the FEP is
automatically used.
Migration Scenarios 3-5
Scenario 1: Single CIP to Single Host
Figure 3-5 Single CIP to Single Host
Before
Cluster Controller
Token
Host A
Ring
Cluster Controller
After
Cluster
Controller CIP Router A
Token
Ring
Cluster
Controller
Host A
Reasons for Change
The FEP was at capacity and the customer preferred to use their information services dollars on
technology that would carry them into the future as well as address today s requirement. In addition,
the Cisco channel-attached router replacing the leased FEP would pay for itself in 18 months with
savings coming from lease costs and monthly NCP licensing costs. Migrating from an SDLC/FEP
network to a LAN/channel-attached router network simplified SNA system configuration
significantly and reduced the downtime for planned outages. Finally, the customer planned to use
TCP mainframe applications in the near future and wanted to build an infrastructure that enabled
them to do that.
Design Choices
This customer opted to combine SNA functionality (DLSw+) and WAN connections in the CIP
router, because the network was very small (25 sites). The design provides a very safe fallback to the
FEP, but at the same time enables SRB dynamics and configuration simplicity.
3-6 Data Center Design and Implementation: SNA Internetworking
Scenario 2: Redundant CIP to Single Host
Configuration
XCA Major Node Configuration
XCANODE VBUILD TYPE=XCA
PRTNODE PORT ADAPNO=0,CUADDR=770,SAPADDR=04,MEDIUM=RING,TIMER=30
*
GRPNODE GROUP ANSWER=ON, X
AUTOGEN=(100,L,P), X
CALL=INOUT, X
DIAL=YES, X
ISTATUS=ACTIVE
Router Configuration
!
source-bridge ring-group 100
!
interface tokenring 1/0
no ip address [ Pobierz całość w formacie PDF ]