|
|
This chapter provides detailed instructions on setting up the link between the mainframe host and a router, which is stage one of the ISM installation process. In this chapter you will find the following information:
To ensure successful configuration of the mainframe-to-router link, the network engineer should coordinate setup of the router configuration with the MVS systems programmer responsible for configuring the router's VTAM connection on the mainframe.
This section describes installation information that is relevant for the network engineer.
This section describes installation information that is relevant to the MVS systems programmer.
Before you can use ISM to view and manage a Cisco router from your NetView console, the router must be connected to the VTAM host through a systems services control point-to-physical unit (SSCP-to-PU) session. This connection is established by defining a PU for each router in the VTAM configuration file.
The following example shows a sample PU definition in VTAM:
SWDRTRS VBUILD TYPE=SWNET | x | ||
| SERVICE_POINT_NAME | PU | ADDR=01, PUTYPE=2, IDBLK=idblock number, IDNUM=id number, DISCNT=(NO), ISTATUS=ACTIVE, MAXDATA=521, IRETRY=YES, MAXOUT=7, PASSLIM=5, MAXPATH=4 | x x x x x x x x |
Table 2-1 defines each of the VTAM arguments. For information about how these arguments correspond to the router configuration, see the "Correlating the Router and VTAM Configuration Information" section of this chapter.
For detailed information about configuring and connecting Cisco routers, refer to the "Related Documentation" section in the preface "About This Guide".
To specify the name of your router, use the following command in global configuration mode:
hostname nameFor more information about using this command, see the Cisco IOS Configuration Fundamentals Configuration Guide.
To specify the privilege level and password that users type to enter enable mode on the router, use the following command:
enable password [level level]{password | encryption-type encrypted-password}For more information about using this command, see the Cisco IOS Security Command Reference.
To configure SNA service point support on the router, you need to add Cisco IOS software sna host commands to the configuration file of your router. The specific commands that you add depend upon the type of connection that you wish to establish. For detailed information on configuring SNA service point support and the Cisco IOS software command for your interface type, refer to the Cisco IOS Bridging and IBM Networking Configuration Guide and Command Reference publications.
The following procedure shows the basic steps to define SNA service point support for Ethernet and Token Ring connections. Again, the actual commands that you use will depend upon the type of connection that you wish to establish. If you want to view some specific configuration examples, see the "Router Configuration Samples" section in this chapter.
Step 1 Define a link to an SNA host in global configuration mode using the sna host command.
The following example shows the syntax of the sna host command for Token Ring, Ethernet, FDDI, RSRB, or virtual data-link control (VDLC) connections:
Step 3 Start an outgoing connection when you are in interface configuration mode, using the command syntax:
For more information about these commands and their options, see the Cisco IOS Bridging and IBM Networking Command Reference.
The following is an example of the lines that would appear in the configuration file of a router with an interface configured through a local ring to 3745 Token Ring Interface Connector:
!
sna host CWBC02 xid-snd 05dcc002 rmac 4001.3745.1088 rsap 4 lsap 4 focalpoint !
interface TokenRing0/1
ip address 172.18.9.129 255.255.255.240
ring-speed 16
sna enable-host lsap 4
sna start CWBC02
!
The following example shows the lines that would appear in the configuration file of a router that contains a Cisco mainframe channel connection with an interface configured for RSRB:
!
dspu rsrb 325 1 900 4000.7000.0001
dspu rsrb enable-host lsap 4
!
dspu host CWBC01 xid-snd 05dcc001 rmac 4000.3333.4444 rsap 4 lsap 4 focalpoint
!
dspu rsrb start CWBC01
!
interface Channel4/1
no ip address
no keepalive
csna C010 C0
!
interface Channel4/2
ip address 172.18.9.145 255.255.255.240
no keepalive
lan TokenRing 0
source-bridge 28 1 900
adapter 4 4000.3333.4444
The following example shows the lines that would appear in the configuration file of a router with an interface configured for DSPU with RSRB:
source-bridge ring-group 600
source-bridge remote-peer 600 tcp 172.18.9.19
!
dspu host CWBC09 xid-snd 05dcc009 rmac 4001.3745.1089 rsap 4 lsap 4 focalpoint dspu pool lupool host CWBC09 lu 2 16
!
dspu pu DSPUPC8 xid-rcv 05dcca18
dspu lu 2 9 pool lupool
!
interface TokenRing0
ip address 172.18.9.19 255.255.255.240
ring-speed 16
multiring all
source-bridge 85 3 600
dspu enable-host lsap 4
dspu start CWBC09
The following example shows the lines that would appear in the configuration file of a router with RSRB and an interface configured with loopback:
!
source-bridge ring-group 600
source-bridge remote-peer 600 tcp 172.18.10.97
source-bridge remote-peer 600 tcp 172.18.10.98
!
sna rsrb 1011 3 600 4000.ffff.00cb
sna rsrb enable-host lsap 4
!
sna host CWBC0B xid-snd 05dcc00b rmac 4001.3745.1089 rsap 4 lsap 4 focalpoint sna rsrb start CWBC0B
!
interface Loopback0
ip address 172.18.10.97 255.255.255.252
!
The following is an example of the lines that would appear in the configuration file of a router that uses virtual data-link control over DLSw+:
source-bridge ring-group 99
dlsw local-peer peer-id 150.10.16.2
dlsw remote-peer 0 tcp 150.10.16.1
!
sna vdlc 99 4000.4500.01f0
sna vdlc enable-host lsap 12
!
sna host HOST-B xid-snd 065bbbb0 rmac 4000.7000.01f1 rsap 4 lsap 12 focalpoint
!
sna vdlc start HOST-B
!
interface serial 3
description IP connection to dspu7k
ip address 150.10.16.2 255.255.255.0
clockrate 4000000
!
The following example shows the format of a Cisco IOS software sna host command that you use to configure the router for SNA Service Point support:
sna host host_name xid-snd xid rmac remote_mac [rsap rsap_addr] [lsap local_sap] [focalpoint]The values for the host_name and xid in the router configuration correspond to the VTAM PU definition in the following way:
SWDRTRS VBUILD TYPE=SWNET | x | ||
| GLENDUSK | PU | ADDR=01, PUTYPE=2, IDBLK=05D, IDNUM=BB000, DISCNT=(NO), ISTATUS=ACTIVE, MAXDATA=521, IRETRY=YES, MAXOUT=7, PASSLIM=5, MAXPATH=4 | x x x x x x x x x |
The sna host command in the router configuration for the router should appear:
sna host glendusk xid-snd 05dbb000 rmac 4001.3745.1088 rsap= 4001.3745.1088 fsap 4 lsap 4 focalpointFor more information about the sna host command, see the Cisco IOS Bridging and IBM Networking Command Reference.
The costime option specifies the amount of time (in seconds) that ISM waits before detecting that a timeout of the RUNCMD has occurred. The ISM autotasks will wait for a RUNCMD to complete, and all other ISM processing stops until it is done. This may result in ISM pausing for long periods of time waiting for a response from a RUNCMD.
The maxreply option specifies the amount of time (in seconds) that NetView waits before detecting that a timeout of the RUNCMD has occurred. If the value is 86400, NetView will timeout the RUNCMD after 24 hours have passed.
When a RUNCMD times out, ISM places the router in an inoperable (INOP) state until an operator resets the router's status. To verify the value for the costime option and change it if necessary, complete the following steps:
Step 1 From a NetView command prompt, type the command list defaults and press Enter.
Note the value for the costime argument. A value of 120 seconds is suggested for the costime argument.
Step 2 To change the value of the costime argument, complete one of the following tasks:
To verify NetView's RUNCMD support, browse the VTAM definition for NetView and verify that your site's NetView application major node contains the following information in the second and third lines:
CNM01 APPL AUTH=(VPACE,ACQ,PASS),PRTCT=CNM01
MODETAB=AMODETAB,DLOGMOD=DSIL6MOD
APPC=YES,PARSESS=YES,
DMINWNL=4,DMINWNR=4,DSESLIM=8,VPACING=10,
AUTOSES=2
* STATOPT='NETVIEW'
If the verification procedures indicate a problem with the link, see the "Troubleshooting" chapter to diagnose the source of the error.
Step 1 From a NetView command prompt, issue the following command for each router, where router_name is the hostname and service point name of the router that you are verifying:
If properly configured and connected, the router status will display with an active (ACTIV) status. If the router does not display an active status, it is not successfully configured and attached to the network or the service point is not defined correctly in the configuration file of the router. See the "Troubleshooting" chapter to further diagnose the problem.
Step 2 Repeat Step 1 for each router that you plan to monitor using ISM.
ISM uses NetView's RUNCMD facility to support communication between ISM and the router. To verify that the router can communicate with NetView using RUNCMDS, use the following procedure:
Step 1 From a NetView console, type the following command:
Where:
| SP=router_name | Specifies the name of the service point to execute the command. This is the name of the router and the service point name that you configured in VTAM. |
| APPL=applname | Specifies the name of the link connection subsystem manager to execute the command. This is the service point application name. This example specifies console. |
| CLISTVAR= | Specifies whether replies are saved in command list variables. This example specifies no. |
| show? | The command that the router should execute. The show? command produces a list of the supported show commands for the router. |
Step 2 Verify that you receive a list of the commands supported by that router. If you receive a response indicating a router problem (such as not defined to VTAM, not active, disabled service point, or RUNCMD timeout) see the "Troubleshooting" chapter to further diagnose the problem.
Step 1 From the MVS console, issue the following command for each router name, where router_name is the hostname and service point name of the router that you are verifying:
Step 2 Repeat Step 1 for each router that you plan to monitor using ISM.
|
|