cc/td/doc/product/rtrmgmt/ism/ism_v2r2
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Installing ISM

Downloading the ISM Installation Data Set

Downloading and Running NSPI202.EXE

Sending the Installation Files to the Host

Receiving the Installation Files

Contents of the Installation Data Set

Choosing an ISM Installation Method

Installing ISM Directly

Installing ISM Using SMP/E

Authorizing the ISM Load Library

Allocating the VSAM Data Sets

Updating VTAM

Verifying VTAM Message Support

Supporting SNA Session Monitoring

Installing and Configuring SNMP

Software Requirements for SNMP

Data Sets Provided by IBM's TCP/IP

Installing SNMP on the Mainframe

Updating NetView

Verifying SNMP on the Mainframe

Restarting NetView

Integrating ISM with STATMON

Verifying the ISM Installation

Verifying the ISM Commands from NetView

Verifying the Operation of the ISM Tasks

Verifying the ISM Commands and Panels

Verifying the ISM Autotasks

Verifying the ISM VSAM Commands

Planning the Next Steps

Installing ISM

This chapter provides detailed instructions for installing and verifying ISM. It includes the following sections:

• Downloading the ISM Installation Data Set

• Choosing an ISM Installation Method

• Authorizing the ISM Load Library

• Allocating the VSAM Data Sets

• Updating VTAM

• Installing and Configuring SNMP

• Updating NetView

• Verifying the ISM Installation

This chapter assumes you have read Chapter 1 and performed the tasks described in "Configuring the Mainframe-to-Router Link"

To install ISM, complete the following steps:

Step 1 The ISM licensing scheme enables Cisco to distribute ISM via the CCO website. To enable ISM licensing, request a license key through Cisco's online ordering system.

The ordering system prompts you for a CPU serial number and for the type of license you want, either permanent or evaluation. Evaluation licenses are good for between 30 and 120 days.

The ordering system e-mails you the terms of your license and a 40-byte license key, similar to the following sample key:

301B2D301B203C383D11C1EA4CC0EE41CEC8CDE1

Make a note of this license key. You will use it in the "Updating the DSIPARM Members" section.

During initialization, ISM reads the license key, verifies the CPU serial number, and checks the license key expiration date. If the CPU serial numbers do not match, or if the license key has expired, ISM halts initialization. If the license key has less than 30 days left before expiring, ISM completes initialization and issues a reminder that a new license is required.

Step 2 Download the ISM installation data set.

Step 3 Install the ISM program using either the direct method or SMP/E method.

Step 4 Authorize the ISM load library, prefix.NSPI202.NSPNLOAD.

Step 5 Allocate the VSAM data sets.

Step 6 Update VTAM:

•Make sure you are not filtering message IST590I from reaching ISM

•If desired, install the VTAM exit when implementing the SNA session monitoring application of ISM

Step 7 Install and configure SNMP (Optional).

Step 8 Update NetView by performing the following tasks:

•Update the NetView procedure

•Update the DSIPARM members

•Optionally integrate ISM with NetView's STATMON utility

•Update the DSIPRF profiles

Step 9 Verify the installation.

Downloading the ISM Installation Data Set

This section describes how to install ISM. It includes the following sections:

• Downloading and Running NSPI202.EXE

• Sending the Installation Files to the Host

• Receiving the Installation Files

• Contents of the Installation Data Set

Downloading and Running NSPI202.EXE

All the files required to install ISM are packaged in a self-extracting WINZIP file named NSPI202.EXE, which you can download from the following location:

•http://www.cisco.com/cgi-bin/tablebuild.pl/ism-v2

Step 1 Download NSPI202.EXE to a PC using binary mode. (The files contained in NSPI202.EXE are in EBCDIC format. Transferring the files in binary mode ensures correct character translation.)

Step 2 Double-click on NSPI202.EXE. The WINZIP self-extractor dialog appears.

Step 3 Enter the name of the directory in which you want to store the extracted files.

Step 4 Click Unzip. The following eight files are extracted and stored in the specified directory:

•NSPI202.NSPNINST.XMIT

•NSPI202.F1.XMIT

•NSPI202.F2.XMIT

•NSPI202.F3.XMIT

•NSPI202.F4.XMIT

•NSPI202.F5.XMIT

•NSPI202.F6.XMIT

•NSPI202.SMPMCS.XMIT

These files now are converted to XMIT format using the TSO Transmit facility.

Sending the Installation Files to the Host

Send the extracted files to the OS/390 host. Transfer the eight files to the OS/390 host using binary mode. Set the OS/390 host FTP SITE options as follows:

LRECL=80 BLOCKSIZE=3120 RECFM=FB CYLINDERS PRIMARY=1 SECONDARY=1

The following example shows a sample FTP session for sending the files to the OS/390 host:

ftp mvshost.com user: ibmuser password: xxxxxxxx bin quote site lrecl=80 blocksize=3120 recfm=fb cylinders primary=1 secondary=1 put nspi202.nspninst.XMIT quote site lrecl=80 blocksize=3120 recfm=fb cylinders primary=1 secondary=1 put nspi202.f1.XMIT quote site lrecl=80 blocksize=3120 recfm=fb cylinders primary=1 secondary=1 put nspi202.f2.XMIT quote site lrecl=80 blocksize=3120 recfm=fb cylinders primary=2 secondary=1 put nspi202.f3.XMIT quote site lrecl=80 blocksize=3120 recfm=fb cylinders primary=9 secondary=1 put nspi202.f4.XMIT quote site lrecl=80 blocksize=3120 recfm=fb cylinders primary=4 secondary=1 put nspi202.f5.XMIT quote site lrecl=80 blocksize=3120 recfm=fb cylinders primary=3 secondary=1 put nspi202.f6.XMIT quote site lrecl=80 blocksize=3120 recfm=fb cylinders primary=1 secondary=1 put nspi202.smpmcs.XMIT quit

Receiving the Installation Files

The Receive TSO option converts the sequential data sets that you sent to the OS/390 host into PDS format. You do not need to pre-allocate the data sets. Follow these steps to receive the installation files:

Step 1 After you transfer the files to the host, use TSO option 3.4 to list the eight data sets. Your list should resemble the following list, except for the userid and volume:

Menu Options View Utilities Compilers Help ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss DSLIST - Data Sets Matching xxxx.NSPW* Row 1 of 6 Command ===> Scroll ===> PAGE Command - Enter "/" to select action Message Volume ---------------------------------------------------------------------- xxxx.NSPI202.NSPNINST.XMIT SMSC1F xxxx.NSPI202.F1.XMIT SMSC1F xxxx.NSPI202.F2.XMIT SMSC1F xxxx.NSPI202.F3.XMIT SMSC1F xxxx.NSPI202.F4.XMIT SMSC1F xxxx.NSPI202.F5.XMIT SMSC1F xxxx.NSPI202.F6.XMIT SMSC1F xxxx.NSPI202.SMPMCS.XMIT SMSC1F ***************************** End of Data Set list **************

Step 2 At the beginning of the first line of the list, enter Receive inds(/) as shown below:

Command - Enter "/" to select action Message Volume ------------------------------------------------------------------------------- receive inds(/).XMIT SMSC1F xxxx.NSPI202.F1.XMIT SMSC1F xxxx.NSPI202.F2.XMIT SMSC1F xxxx.NSPI202.F3.XMIT SMSC1F xxxx.NSPI202.F4.XMIT SMSC1F xxxx.NSPI202.F5.XMIT SMSC1F xxxx.NSPI202.F6.XMIT SMSC1F xxxx.NSPI202.SMPMCS.XMIT SMSC1F ***************************** End of Data Set list ****************************

The following message is displayed:

Enter restore parameters or 'DELETE' or 'END'

The first data set is restored.

Step 3 Press Enter.

Step 4 At the beginning of the second line of the list, enter an equal sign (=) to repeat the previous command, and press Enter. The second data set is restored.

Step 5 Repeat Step 4 to restore the remaining six data sets.

Step 6 Press PF3, then press Enter to list the sixteen data sets (the eight sequential data sets and the eight PDS data sets). Your list should resemble the following:

DSLIST - Data Sets Matching HAL1.NSPW* Row 1 of 17 Command ===> Scroll ===> PAGE Command - Enter "/" to select action Message Volume ------------------------------------------------------------------------------- xxxx.NSPI202.NSPNINST SMSC18 xxxx.NSPI202.NSPNINST.XMIT SMSC1F xxxx.NSPI202.F1 SMSC18 xxxx.NSPI202.F1.XMIT SMSC1F xxxx.NSPI202.F2 SMSC18 xxxx.NSPI202.F2.XMIT SMSC1F xxxx.NSPI202.F3 SMSC18 xxxx.NSPI202.F3.XMIT SMSC1F xxxx.NSPI202.F4 SMSC18 xxxx.NSPI202.F4.XMIT SMSC1F xxxx.NSPI202.F5 SMSC18 xxxx.NSPI202.F5.XMIT SMSC1F xxxx.NSPI202.F6 SMSC18 xxxx.NSPI202.F6.XMIT SMSC1F xxxx.NSPI202.SMPMCS SMSC18 xxxx.NSPI202.SMPMCS.XMIT SMSC1F ***************************** End of Data Set list ****************************

Contents of the Installation Data Set

Table 3-1 describes the members in the installation data set, prefix.NSPI202.NSPNINST. If you are installing ISM directly, use only the COPYISM member. The remaining members are used for an SMP/E installation of ISM.

Table 3-1 ISM Installation Data Set Contents 

Member
Description

ALLOC

SMP/E allocate target and distribution files job.

ALLOCSMP

SMP/E allocate SMP work and temporary files job.

COPYISM

Direct installation procedure to copy installation files from tape to DASD.

ISMACCPT

SMP/E procedure to accept ISM.

ISMAPPLY

SMP/E procedure to apply ISM.

ISMCSI

SMP/E procedure to create and initialize ISM CSI files.

ISMRECV

SMP/E procedure to receive ISM.

ISMREJCT

SMP/E procedure to reject ISM.


Choosing an ISM Installation Method

You can install the ISM program using either the direct method, or the SMP/E, but first run prefix.NSPI202.NSPINST, to unload the ISM installation data set.

Note When you run any of the sample ISM installations described in this chapter, make sure you follow the instructions specific to each job to customize the JCL for your installation.

Installing ISM Directly

If you chose the direct method, run the sample job provided in the COPYISM member of the installation data set, prefix.NSPI202.NSPINST.

COPYISM copies the following ISM data sets from the Relfiles to DASD:

•prefix.NSPI202.NSPNLOAD

•prefix.NSPI202.NSPNCLST

•prefix.NSPI202.NSPNHTML

•prefix.NSPI202.NSPNPANL

•prefix.NSPI202.NSPNSAMP

Example

The following example is an excerpt of the COPYISM sample JCL to install ISM directly. Follow the directions to unload the data set. The remaining statements of the COPYISM job are similar and unload the rest of the ISM installation data sets.

//COPYISM JOB ('ACCOUNTING INFO'),PGMRNAME,MSGLEVEL=(1,1), // MSGCLASS=A,CLASS=A,TIME=5 //* //***************************************************************** //* * //* ISM 2 COPY PROCEDURE * //* * //* THIS JOB WILL COPY THE ISM INSTALLATION DATASETS FROM * //* THE DISTRIBUTION files TO DASD. MODIFY THIS JOB ACCORDING * //* TO THE FOLLOWING INSTRUCTIONS, THEN SUBMIT THE JOB. * //* * //* 1) CHANGE THE JOB CARD FOR YOUR SITE. * //* * //* 2) CHANGE ALL OCCURRENCES OF "prefix" TO YOUR * //* PRODUCTION DATASETS' HIGH-LEVEL QUALIFIER. * //* * //* 3) CHANGE ALL OCCURRENCES OF "volser" TO YOUR OUTPUT DASD * //* VOLUME SERIAL NUMBER. * //* * //* 4) CHANGE ALL OCCURRENCES OF "relhlq" TO THE HIGH-LEVEL * //* QUALIFIER YOU RECIEVED THE RELFILES UNDER. * //* * //* 5) CHANGE ALL OCCURRENCES OF "sysunit" TO THE UNIT TYPE OF * //* YOUR OUTPUT DASD DRIVE. * //* * //***************************************************************** //* //* //LOAD1 EXEC PGM=IEBCOPY //SYSPRINT DD SYSOUT=* //SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(1,1)) //SYSUT4 DD UNIT=SYSDA,SPACE=(CYL,(1,1)) //* //ILOAD DD DISP=SHR,DSN=relhlq.NSPI202.F2 //OLOAD DD DSN=prefix.NSPI202.NSPNLOAD, // UNIT=sysunit,VOL=SER=volser, // DISP=(NEW,CATLG),DCB=(RECFM=U, // BLKSIZE=6144),SPACE=(CYL,(1,1,25)) //* //ISAMP DD DISP=SHR,DSN=relhlq.NSPI202.F3 //OSAMP DD DSN=prefix.NSPI202.NSPNSAMP, // UNIT=sysunit,VOL=SER=volser, // DISP=(NEW,CATLG),DCB=(RECFM=FB,LRECL=80, // BLKSIZE=3120),SPACE=(CYL,(1,1,25)) //* //ICLIST DD DISP=SHR,DSN=relhlq.NSPI202.F4 //OCLIST DD DSN=prefix.NSPI202.NSPNCLST, // UNIT=sysunit,VOL=SER=volser, // DISP=(NEW,CATLG),DCB=(RECFM=FB,LRECL=80, // BLKSIZE=3120),SPACE=(CYL,(10,1,99)) //* //IHTML DD DISP=SHR,DSN=relhlq.NSPI202.F5 //OHTML DD DSN=prefix.NSPI202.NSPNHTML, // UNIT=sysunit,VOL=SER=volser, // DISP=(NEW,CATLG),DCB=(RECFM=FB,LRECL=80, // BLKSIZE=3120),SPACE=(CYL,(5,1,50)) //* //IPANEL DD DISP=SHR,DSN=relhlq.NSPI202.F6 //OPANEL DD DSN=prefix.NSPI202.NSPNPANL, // UNIT=sysunit,VOL=SER=volser, // DISP=(NEW,CATLG),DCB=(RECFM=FB,LRECL=80, // BLKSIZE=3120),SPACE=(CYL,(3,1,99)) //* //SYSIN DD * LOAD COPYMOD INDD=ILOAD,OUTDD=OLOAD SAMP COPY INDD=ISAMP,OUTDD=OSAMP CLIST COPY INDD=ICLIST,OUTDD=OCLIST HTML COPY INDD=IHTML,OUTDD=OHTML PANEL COPY INDD=IPANEL,OUTDD=OPANEL

Installing ISM Using SMP/E

Use the following procedure to install ISM in a zone other than the MVS zone on your mainframe using SMP/E:

Step 1 Use the sample SMP/E member named ALLOC, in prefix.NSPI202.NSPNINST, to allocate your target and distribution libraries.

Step 2 Submit the SMP/E member named ALLOCSMP located in the prefix.NSPI202.NSPNINST data set. This job allocates and initializes SMP work and temporary files.

Step 3 Edit and submit the SMP/E member named ISMCSI in the prefix.NSPI202.NSPNINST data set. This job allocates and initializes the SMP CSIs.

Step 4 Edit the prefix.NSPI202.SMPMCS data set, changing the value of ++VER(Z038) to the preferred zone.

Step 5 Submit the SMP/E member named ISMRECV, in the prefix.NSPI202.NSPNINST data set, to receive ISM.

Step 6 Use the sample SMP/E member named ISMAPPLY, in prefix.NSPI202.NSPNINST, to apply ISM.

Step 7 Use the sample SMP/E member named ISMACCPT, in prefix.NSPI202.NSPNINST, to accept ISM.

Note ISM can be installed into an existing SMP/E zone. If you prefer to install ISM into an existing zone, omit steps 2 and 3 (ALLOCSMP and ISMCSI).

Authorizing the ISM Load Library

After installing the ISM program files, authorize the library prefix.NSPI202.NSPNLOAD by adding it to SYS1.PARMLIB or by copying it to one of your site's authorized user libraries. This allows ISM to process some authorized commands and perform security checks.

To authorize the ISM load library, complete the following steps:

Step 1 Add the data set prefix.NSPI202.NSPNLOAD and its DASD volume name to your list of authorized program facility (APF) authorized data sets in SYS1.PARMLIB(IEAAPFxx) or SYS1.PARMLIB(PROGxx).

Step 2 Reload (IPL) MVS if necessary. If your system is enabled to use dynamic APF services, you can avoid reloading MVS by using the SETPROG command to dynamically update the APF list. See the Initialization and Tuning Reference manual for your MVS/ESA system for more information about authorizing data sets.

Allocating the VSAM Data Sets

There are six jobs to run when allocating the VSAM data sets that ISM uses. Two are required and four are optional, depending upon the ISM functions you plan to implement.

Member
Description

ISMALLAH (Required)

Allocates the ISM management data set (ISMDSA) and resource and Cisco mainframe channel connection archive data set (ISMDSH).

ISMALLMN (Required)

Allocates the ISM primary event log (ISMDSM) and alternate event log (ISMDSN).

ISMALLI (Required)

Allocates the interface statistics and performance data set (ISMDSI).

ISMALLC (Optional)

Allocates the resource configuration data set (ISMDSC).

ISMALLR (Optional)

Allocates the SNA session archive data set (ISMDSR).

ISMALLD (Optional)

Allocates the router memory dump data set (ISMDSD).

ISMALLW (Optional)

Allocates the SNASw statistics and perfomance data set (ISMDSW).


For storage requirements see Table 1-4.

To allocate the VSAM data sets, modify and run each member (located in prefix.NSPI202.NSPNSAMP) described in Table 1-5.

Note All but two of the VSAM-keyed sequence data sets have a record size of 230 with a key of 24. The resource configuration (ISMDSC) and router memory dump (ISMDSD) data sets use a key of 28 and record size of 128.

Updating VTAM

The following sections describe the updates required in VTAM to support ISM:

• Verifying VTAM Message Support

• Supporting SNA Session Monitoring

Verifying VTAM Message Support

The ISM program must receive the IST590I VTAM message over the PPI or PPO interface. Do not block the message from reaching NetView.

Supporting SNA Session Monitoring

If you plan to use the SNA session monitoring application in ISM, you must install the functional VTAM XID configuration services exit routine called NSPEMGR, which is provided by the ISM program. The NSPEMGR routine calls a service routine that writes a message (NSP2015I) containing Media Access Control (MAC), SAP, and RIF data (when available) each time a switched PU connects into the network.

If you are not using your own ISTEXCCS exit routine, install the ISM version, as described in the section "Installing the VTAM XID Exit Routine" section.

If you have your own ISTEXCCS exit routine, or have installed the CiscoWorks Blue SNA View exit, call the Cisco Customer Technical Assistance Center (TAC) for instructions on modifying your existing routine to work with ISM.

Overview of the VTAM XID Exit Routine

The VTAM exit NSPEMGR is driven under a VTAM subtask when VTAM initializes or when activated by a F NET,EXIT,ID=ISTEXCCS,OPT=ACT command. When this command is issued, the exit is driven with a BEGIN vector allowing the exit to do any required initialization. It allocates two bytes of memory required for sending information back to VTAM in a BUILD vector. The exit then opens the primary and backup VSAM datasets.

Finally, the BEGIN vector is modified to indicate to VTAM that the exit should be called when VTAM receives an XID for defined PUs. When VTAM receives an XID for a defined PU the exit is once again invoked. The exit is given information about the PU including the PU name, local and remote MAC and SAP addresses for the PU session, the IDBLK/IDNUM for the PU, and finally RIF data if present. All of this data is written to a message (NSP2015I) containing MAC, SAP, and RIF data (when available), each time a switched PU connects to the network. The exit then returns a BUILD vector indicating that VTAM should allow the connection.

At VTAM termination, or when the exit is deactivated using the F NET,EXIT,ID=ISTEXCCS,OPT=INACT command, the exit is driven with the END vector. At this point the exit frees the allocated memory.

This process should produce minimal impact to VTAM connection performance.

Installing the VTAM XID Exit Routine

If you are not using your own ISTEXCCS exit routine, you can install the ISM VTAM XID exit routine distributed with your ISM installation files.

To install the ISM VTAM exit routine, complete the following steps:

Step 1 Copy the member named NSPEMGR from the prefix.NSPI202.NSPNLOAD data set, to SYS1.VTAMLIB.

Step 2 Use the sample member ISMMPF provided in the prefix.NSPI202.NSPNSAMP data set to update the MVS system's MPF table in SYS1.PARMLIB. This allows the ISM message NSP2015I, created by the VTAM exit, to be automated by NetView:

NSP*,AUTO(YES),RETAIN(NO),SUP(NO) /* GENERIC ENTRY */

Step 3 To verify that the VTAM XID exit is installed properly, run the following VTAM command:

F NET,EXIT,ID=ISTEXCCS,OPT=ACT,MODULE=NSPEMGR

When message NSP2015I is returned to the console, the exit is working correctly.

Step 4 After verifying that the VTAM XID exit executed properly, rename the NSPEMGR member to ISTEXCCS in SYS1.VTAMLIB.

Reassembling the VTAM XID Exit Routine

If you contacted the Cisco TAC for instructions and were told that you need to reassemble and link-edit the VTAM XID exit, complete the following steps:

Step 1 Modify the sample member NSPECCSL provided in the prefix.NSPI202.NSPNSAMP data set as required for your site's exit name.

Step 2 Modify the sample member ASMEMGR provided in the prefix.NSPI202.NSPNSAMP data set according to your site's requirements as specified in the beginning of the sample job. Be sure to assemble and link-edit the NSPEMGR exit into an authorized user library which is concatenated to SYS1.VTAMLIB (specified in the SYSLMOD statement).

Installing and Configuring SNMP

This section describes the process of installing and enabling SNMP on your mainframe and on the SNMP resources you want to manage. It includes the following sections:

• Software Requirements for SNMP

• Data Sets Provided by IBM's TCP/IP

• Installing SNMP on the Mainframe

• Updating NetView

• Verifying SNMP on the Mainframe

• Restarting NetView

• Integrating ISM with STATMON

Software Requirements for SNMP

The data sets described in this chapter are provided by IBM TCP/IP for MVS/ESA 3.2.0. The platform supported for using SNMP on the mainframe is Tivoli's TME10 NetView for OS/390 version 1, Release 2.

Data Sets Provided by IBM's TCP/IP

Table 3-2 lists the data sets created when you install IBM's TCP/IP on the mainframe.

Table 3-2 IBM TCP/IP Data Sets

Data set Name
Contents

prefix.SEZAINST

Procedures, instructions, and MIB table

prefix.SEZADSIM

SNMP messages

prefix.SEZADSIP

SNMPARMS

prefix.SEZANPNL

SNMP panels

prefix.SEZADSIL

SNMP load modules

prefix.SEZANCLS

CLISTs and code point tables


Because the environment to be managed from NetView is known, ISM can improve response times and reduce TCP/IP overhead by doing some of the conversions in NetView.

To improve the performance of SNMP management of Cisco devices from the mainframe, ISM does the following:

•Queries hosts using their IP address

•Uses ASN.1 notation in SNMP commands

Installing SNMP on the Mainframe

To install SNMP on the mainframe, complete the following tasks:

• Adding SNMP Configuration Statements to TCP/IP Profile Data Set

• Identifying SNMP Port Numbers

• Configuring the SNMP Query Engine

For additional information on installing SNMP, refer to your SNMP product documentation.

Adding SNMP Configuration Statements to TCP/IP Profile Data Set

To modify the prefix.PROFILE.TCPIP data set to include SNMP configuration statements, complete the following steps:

Step 1 To start the SNMP query engine (SNMPQE) and SNMP agent (SNMPD) address spaces simultaneously with the TCPIP address space, include SNMPQE and SNMPD in the AUTOLOG statement, as shown below:

AUTOLOG   SNMPQE            ; SNMP Query Engine   SNMPD             ; SNMP Agent ENDAUTOLOG

Step 2 SNMP uses raw sockets for the SNMP PING functions and for the Distributed Program Interface (DPI). To allow the SNMPQE and the SNMPD to create raw sockets, add SNMPQE and SNMPD to the OBEY statement, as follows:

OBEY   IBMUSER SNMPD SNMPQE ENDOBEY

Or create an equivalent RACF profile.

Step 3 SNMP requires that port 161 be reserved for all messages sent to the MVS agent, and that port 162 be reserved for SNMP messages that report traps to the MVS client. Make sure that the following statements are part of the prefix.PROFILE.TCPIP data set:

PORT   161 UDP SNMPD     ; SNMP Agent   162 UDP SNMPQE    ; SNMPQE Agent

Step 4 Add a statement similar to the following example to identify the contact person for this managed node:

SYSCONTACT   Mickey Mouse, extension 1234 ENDSYSCONTACT

SYSCONTACT is the MIB II variable that identifies the contact person for this managed node.

Step 5 Add a statement similar to the following example to identify the physical location of this managed node:

SYSLOCATION   123 North Main Street   Anytown, NC 99999 ENDSYSLOCATION

SYSLOCATION is the MIB II variable that identifies the physical location of this managed node.

Identifying SNMP Port Numbers

The SNMP agent, SNMPD, uses the prefix.ETC.SERVICES data set to determine its port numbers. To identify the SNMP port numbers, modify the prefix.ETC.SERVICES data set to add the following statements:

snmp       161/udp     # snmp request port snmp-trap  162/udp     # snmp monitor trap port

The entries in prefix.ETC.SERVICES data set are case sensitive and column sensitive. They must be in lowercase and begin in column one.

Configuring the SNMP Query Engine

To configure the SNMP query engine, follow these steps:

Step 1 Update the SNMP query engine using the prefix.SEZAINST(SNMPPROC) data set.

Step 2 Create the MIB data set by creating a MIBDESC. To create a MIBDESC, enter the following command from option 6 of the TSO:

Receive inds ('prefix.NSPI202.NSPNSAMP(MIBDESC)')

This creates a data set userid TCPIP1.MIBDESC.DATA. You can replace the existing TCP.MIBDESC.DATA data set with this data set.

Step 3 To enable the optional data set for NLS support, use the prefix.SEZAINT(MSSNMP) data set. This data set specifies the SNMP message repository.

Step 4 To explicitly identify the data set used to obtain the TCPIP.DATA parameters, use the prefix.SEZAINST(TCPDATA) data set.

Updating NetView

This section describes the following procedures for modifying NetView data sets:

• Updating the NetView Procedure

• Updating the DSIPARM Members

• Using ISM SNMP Support

• Updating DSIPRF Profiles

• Configuring NetView to Initialize ISM

• Configuring the Standard Interface as an SNMP Monitor

Updating the NetView Procedure

This sample procedure specifies the ISM load library, CLIST library, panel library, and VSAM data sets which must be updated in your sites's NetView procedure.

To update your existing NetView procedure, perform the following steps:

Step 1 Update the data set high-level qualifiers in the sample JCL provided in member ISMPROC of the prefix.NSPI202.NSPNSAMP library for the following DD names, according to your site's ISM implementation.

The following data sets are required:

•STEPLIB—Specifies the ISM load library

•DSICLD—Specifies the ISM CLIST library and ISM HTML procedure library

•CNMPNL1—Specifies the ISM panels library

•NSPDSA—Specifies the ISM configuration data set

•NSPDSH—Specifies the resource history data set

•NSPDSM—Specifies the ISM primary event log

•NSPDSN—Specifies the ISM alternate event log

•NSPDSI—Specifies the resource interface statistics and performance data set

The following data sets are optional:

•NSPDSR—Specifies the ISM SNA session archive data set

•NSPDSC—Specifies the resource configuration data set

•NSPDSD—Specifies the router memory dump data set

•NSPDSW—Specifies the SNASw statistics and performance data set.

Step 2 Add modified statements from the ISMPROC sample to the NetView procedure. The following example shows an updated NetView procedure with the DD statements to support ISM.

//STEPLIB DD --------------------------- // DD DISP=SHR,DSN=prefix.NSPNLOAD ISM LOAD LIBRARY //* //DSICLD DD ------------------------- // DD DSN=SHR,DSN=prefix.NSPNCLST ISM CLISTS // DD DSN=SHR,DSN=prefix.NSPNHTML ISM HTML PROCEDURES //* //CNMPNL1 DD --------------------------- // DD DSN=SHR,DSN=prefix.NSPNPANL ISM PANELS //* //* ISM VSAM DATA BASES //* ISM V1R3 CONFIG DATA BASE //NSPDSA DD DSN=prefix.NSPDSA, // DISP=SHR,AMP=AMORG //* ISM V1R3 ROUTER HISTORY DATA BASE //NSPDSH DD DSN=prefix.NSPDSH, // DISP=SHR,AMP=AMORG //* ISM V1R3 DATA BASE FOR ISM EVENTS //NSPDSM DD DSN=prefix.NSPDSM, // DISP=SHR,AMP=AMORG //NSPDSN DD DSN=prefix.NSPDSN, // DISP=SHR,AMP=AMORG //* ISM INTERFACE DATA BASE //NSPDSI DD DSN=prefix.NSPDSI, // DISP=SHR,AMP=AMORG //* ISM V1R3 SESSION DATA //NSPDSR DD DSN=prefix.NSPDSR, // DISP=SHR,AMP=AMORG //* ISM V1R3 DATA BASE FOR ROUTER CONFIGURATIONS //NSPDSC DD DSN=prefix.NSPDSC, // DISP=SHR,AMP=AMORG //* ISM V1R3 DATA BASE FOR ROUTER MEMORY DUMPS //NSPDSD DD DSN=prefix.NSPDSD, // DISP=SHR,AMP=AMORG //* ISM V2R2 DATA BASE FOR SNASW //NSPDSW DD DSN= prefix.NSPDSW, // DISP=SHR,AMP=AMORG

Updating the DSIPARM Members

This section describes the updates required to enable the following ISM functions in the NetView user DSIPARM data set:

•ISM commands

•SNMP commands

•ISM VSAM tasks

•SNMP task

•ISM automation operators

•SNMP automation operators

•ISM automation table entries

•SNMP automation table entries

•ISM licensing

If you are using a release of NetView that does not use CNMSTYLE, complete the following steps to update the members of the NetView DSIPARM user data set to support ISM.

Step 1 Copy the following members from the prefix.NSPI202.NSPNSAMP data set to the NetView DSIPARM user data set:

•ISMCMD2—ISM Version 2 commands

•ISMCNM2—ISM STATMON Interface

•ISMDMN2—ISM Tasks

•ISMLICSE—ISM licensing information

•ISMOPF2—ISM Autotasks

•ISMTBL2—ISM automation table entries

•NSPDSA—ISM VSAM task member for ISM control files

•NSPDSC—ISM VSAM task member for resource configurations

•NSPDSD—ISM VSAM task member for resource dumps

•NSPDSH—ISM VSAM task member for resource, TN3270, and CMC statistics

•NSPDSI ISM—VSAM task member for interface statistics

•NSPDSM ISM—VSAM task member for event data base (1 of 2)

•NSPDSN ISM—VSAM task member for event data base (2 of 2)

•NSPDSR ISM—VSAM task member for interface statistics

•NSPDSW ISM—VSAM taskl member for SNASw

Step 2 Enable the ISM commands by adding a %INCLUDE ISMCMD2 statement to the DSICMD or DSICMDU member.

Step 3 Enable the ISM VSAM tasks by adding a %INCLUDE ISMDMN2 statement to the DSIDMN or DSIDMNU member.

Step 4 Enter your license key (see Step 1 on page 3-2) in member ISMLICSE. The ISMLICSE member has the following format:

ISMLICENSE=301B2D301B203C383D11C1EA4CC0EE41CEC8CDE1

The ISMLICSE member can contain comments, identified by an asterisk (*) in column 1. You can include multiple ISMLICENSE entries in the ISMLICSE member, but ISM recognizes only the first.

Step 5 Enable the ISM automation operator profiles by adding a %INCLUDE ISMOPF2 statement to the DSIOPF or DSIOPFU member. The operators defined in ISMOPF2 might have to be added to the s security system for your site.

Step 6 Enable the ISM automation table entries by adding a %INCLUDE ISMTBL2 statement to the current production version of the NetView automation table (such as DSITBL01).

Step 7 If you are running a release of NetView that uses CNMSTYLE, copy member ISMSTGEN from prefix.NSPI202.NSPNSAMP to DSIPARM(CNMSTGEN) to define the ISM VSAM tasks, SNMP, etc. Update the member with the name of your TCP/IP task and VTAM network id.

Step 8 Ensure that the ISM tasks have the authority to issue AUTOTASK, PURGE, RESETDB, START TASK, and STOP commands. The data set prefix.NSPI202.NSPNSAMP(ISMSCAT2) contains a sample ISMSCAT2 member.

Note To integrate ISM commands in the STATMON utility, update and restart NetView, then complete the tasks described in the "Integrating ISM with STATMON" section.

Caution Do not install both ISM V2 and ISM V1R3.0 in NetView. The combination of these systems causes ISM compatibility issues.

Using ISM SNMP Support

To use ISM SNMP support, complete the following steps:

Step 1 Copy the following members from prefix.NSPI202.NSPNSAMP data set to NetView DSIPARM user data set:

•SNMPDMN—SNMP task member

•SNMPOPF—SNMP Autotasks

•SNMPARMS—SNMP task member

•SNMPTBL—SNMP automation table entries

Step 2 Enable the SNMP IUCV task by adding a %INCLUDE SNMPDMN statement to the DSIDMN or DSIDMNU member.

Step 3 Enable the SNMP automation operator profiles by adding a %INCLUDE SNMPOPF statement to the DSIOPF or DSIOPFU member. The operators defined in SNMPOPF might have to be added to your site's security system.

Step 4 Enable the SNMP automation table entries by adding a %INCLUDE SNMPTBL statement to the current production version of the NetView automation table (such as DSITBL01).

Updating DSIPRF Profiles

This section describes the NetView user DSIPRF data set updates. These updates enable the ISM profiles used by the following ISM automation tasks:

•ISMPROFI—Profile for ISMMGRS (ISM refresh autotask) and ISMMGRI (Interface monitoring autotask)

•ISMPROF1—Profile for ISMMGR (ISM primary automation manager)

•ISMPROF2—Profile for NSPMGRM (ISM message automation autotask)

•ISMPROF3—Profile for additional managers (such as ISMMGRA and ISMMGRB)

•ISMPROFS—Profile for SNA Session monitor autotask ISMEXIT

•ISMPROFW—Profile for the SNASw monitor autotask SNASWMON

To update the members of the NetView DSIPRF user data set to support SNMP, copy the following members from prefix.NSPI202.NSPNSAMP to the DSIPRF user data set.

•SNMPPRF1—Profile for primary SNMP autotask

•SNMPPRF2—Profile for SNMP automation autotask

Configuring NetView to Initialize ISM

To start NetView and ISM together, add the following autotask command to the site's production NetView initialization CLIST:

AUTOTASK OPID=ISMMGR

or add to CNMSTYLE

AUTOTASK.ISMMGR.CONSOLE=*NONE*

This command is included in the sample CNMSTGEN.

The ISM program uses autotasks for the following:

•ISMMGR—Primary ISM manager

•ISMMGRM—Automates actions when messages are received

•ISMMGRS—Creates the data used for the ISM status summary display

•ISMMGRI—Collects statistics from interfaces

•SNASWMON—Monitors and collects SNASw

•ISMEXIT—SNA Session Monitor dispatcher task

•ISMEXIT1-9—SNA Session Monitor tasks

The following autotasks are provided by ISM for SNMP management:

•SNMPMGRI—Primary SNMP manager

•SNMPOPER—Autotask used to automate actions when SNMP messages are received

Note If you are using Tivoli NetView 1.2, the CLIST is usually CNME1035. In Tivoli NetView 1.3, the CLIST is CNME1034. In Tivoli NetView 1.4, ISMMGR is started from CNMSTGEN.

Configuring the Standard Interface as an SNMP Monitor

This section describes how to customize NetView to support SNMP. For specific details on installing SNMP, refer to the IBM publication, eNetwork CS IP Configuration Guide.

To customize NetView to support SNMP, follow these steps:

Step 1 Add the SNMP task using the following statement in DSIDMNxx:

SNMP TASK     MOD=SNMPIUCV,TSKID=SNMPIUCV,PRI=5,INIT=Y

SNMPIUCV is the NetView optional task that handles IUCV communication between the NetView program and the SNMP query engine. SNMPIUCV resides in the prefix.SEZADSIL data set.

The SNMPIUCV task tries to connect through IUCV to the SNMP query engine. If the task fails, it tries to reconnect as specified by the SNMPQERT keyword in the SNMPARMS member of the prefix.SEZADSIP data set. The retry default is every 60 seconds.

Step 2 Add the SNMP command using the following statement:

SNMP CMDMDL MOD=SNMP,ECHO=Y,TYPE=R,RES=Y

SNMP is the command processor that allows NetView operators and CLISTs to issue SNMP commands. SNMP resides in the prefix.SEZADSIL data set. This data set should be concatenated to the STEPLIB DD statement in the NetView start procedure.

Step 3 Add the SNMP parameters (SNMPARMS) data set. The contents of this data set are shown below:

Member name: SNMPARMS * * SNMPQE SNMPQE     * Userid of SNMP Query Engine   SNMPQE OESNMQD1   * Userid of SNMP Query Engine   SNMPQERT 60       * Retry time (seconds) for IUCV CONNECT   SNMPRCNT 2        * Retry count for sending SNMP requests   SNMPRITO 10       * Retry initial timeout (10ths of a second)   SNMPRETO 2        * Retry backoff exponent                     (1=linear,2=exponential)   SNMPMMLL 80       * Line length for Multiline Messages 38/44

Step 4 Add SNMP messages to DSIMSG as follows:

DSIMSG     prefix.SDSIMSG1            prefix.SEZADSIM

The SNMP messages reside in the prefix.SEZADSIM data set as DSISNMnn, where nn is the number of the member. The valid message members are DSISNM00 through DSISNM055, DSISNM10, DSISNM12, and DSISNM99. The data set containing these members should be added to the DSIMSG DD statement in the NetView start procedure.

Step 5 Add the SNMP CLISTs to NetView by creating two data sets using the following command. Then copy the IBM-provided members into these data sets.

DSICLD     prefix.USER.SEZANCLS            prefix.DSICLD

Step 6 Add the SNMP panels to NetView by creating two data sets using the following command, then copy the IBM-provided members into these data sets.

CNMPNL1    prefix.USER.SEZANPNL            prefix.CNMPNL1

Step 7 Make the SNMPIUCV modules available to NetView using either steplib or by adding to the linklist.

Step 8 Add the SNMP automation table by modifying the NetView automation table to include the SNMPAUTO (prefix.SEZANCLS(SNMPAUTO)) data set.

Step 9 Add at least two autotasks to support the SNMP data set with the following functions:

•Initialize the SNMP manager and execute the timers associated with the active monitoring of target hosts.

•Recover the connection between NetView and TCP/IP to automate the trap to alert conversion.

Verifying SNMP on the Mainframe

To verify that SNMP is correctly installed on the mainframe, use the snmp ping command to test the connection to an existing device. At the NetView command prompt, issue the following command:

snmp ping ip_address

Where ip_address is the IP address of a device that you know is running and is SNMP-enabled.

If SNMP is correctly installed and is currently active, you get a response time message. Otherwise, you get an error message notifying you that SNMP is not installed or is not active.

To verify that the SNMP command is available from NetView use the dispmod snmp command. At the NetView command prompt, issue the following command:

dispmod snmp

If the SNMP command is available from NetView, you get the following response.

CNM263I MODULE LENGTH CSECT DATE PTF EPA AM ATTR CNM263I SNMP 0011E8 SNMPSNMP 12/09/97 ------- -------- 31 CNM265I END OF DISPLAY

To verify that the SNMPIUCV task is available from NetView, use the dispmod snmpiucv command. At the NetView command prompt, issue the following command:

dispmod snmpiucv

If the SNMPIUCV task is available from NetView, you get the following response:

CNM263I MODULE LENGTH CSECT DATE PTF EPA AM ATTR CNM263I SNMPIUCV 002E40 SNMPIUCV 12/09/97 ------- -------- 31 CNM265I END OF DISPLAY

Restarting NetView

After you update the NetView procedure, the DSIPARM data set, and the DSIPRF data set to enable NetView to initialize ISM, restart NetView to install all of the modifications.

When you restart NetView, the ISMMGR autotask begins, which initiates ISM. If you need to stop the autotask while NetView is running, you can use the isminit reset command.

Integrating ISM with STATMON

As an option, after you updated NetView for ISM and restarted NetView, you can integrate ISM with STATMON.

You can add ISM commands to the Command Menu in STATMON (Figure 3-1) by updating the DSICNM member in your NetView DSIPARM user data set. When you integrate the following ISM commands, you can go directly to certain areas of the ISM program from STATMON:

•ISMCMD—ISM full-screen resource panel

•ISM—Main menu

•ISMR—Resource menu

•ISMSUM—Status summary

•ISMMGR—List ISM resources

To integrate the ISM commands on the STATMON Command Menu, follow these steps:

Step 1 Enter Edit mode for the DSICNM member of your DSIPARM data set.

Step 2 Copy member ISMCNM2 from prefix.NSPI202.NSPNSAMP after the C STATS statement.

Step 3 To enable the commands on the menu, type the following commands from a NetView command prompt and press Enter:

STOPCNM STATMON

STARTCNM STATMON

Figure 3-1 STATMON Menu with ISM Commands

Verifying the ISM Installation

After you complete all installation tasks and update and restart NetView, make sure the installation was successful by completing the following verification tasks:

• Verifying the ISM Commands from NetView

• Verifying the Operation of the ISM Tasks

• Verifying the ISM Commands and Panels

• Verifying the ISM Autotasks

• Verifying the ISM VSAM Commands

Verifying the ISM Commands from NetView

The following procedure verifies that the ISM commands have been added to the NetView procedure:

Step 1 From a NetView command prompt, type the following command and press Enter:

DISPMOD NSPDS

Step 2 Verify that the following text is displayed after you enter the DISPMOD NSPDS command. The data on the second line of the display might vary depending upon your maintenance level.

CNM263I MODULE LENGTH CSECT DATE PTF EPA AM ATTR CNM263I NSPDS 000BC0 -------- -------- ------- 0004E440 24 RN RU CNM265I END OF DISPLAY

Verifying the Operation of the ISM Tasks

This section describes the procedure to verify that the ISM tasks have been started and that member ISMDMN is included in NetView. It also verifies that the task member statements for each of the VSAM tasks are located in the NetView DSIPARM.

To verify that the ISM tasks are working properly, complete the following steps:

Step 1 From a NetView command prompt, type the following command and press Enter:

LIST NSPDSA

Step 2 Verify the following text after you enter the LIST NSPDSA command:

* CNM56 LIST NSPDSA - CNM56 TYPE: OPT TASKID: NSPDSA TASKNAME: NSPDSA STATUS: ACTIVE - CNM56 MEMBER: NSPDSA - CNM56 PRIMARY:NSPDSA STATUS:ACTIVE SECONDARY:NONE STATUS:INACTIVE - CNM56 LOADMOD: DSIZDST - CNM56 Task Serial: 13 - CNM56 Messages Pending: 0 Held: 0 - CNM56 END OF STATUS DISPLAY

If this text does not appear, see "Troubleshooting"

Step 3 Repeat Steps 1 and 2 with the following commands and verify that a corresponding display for each task appears:

•LIST NSPDSC

•LIST NSPDSD

•LIST NSPDSH

•LIST NSPDSI

•LIST NSPDSM

•LIST NSPDSN

•LIST NSPDSR

•LIST NSPDSW

Verifying the ISM Commands and Panels

This section describes the procedure to verify that the ISMCMD member has been included in NetView. To verify that the ISM commands and panels are available, complete the following step:

Step 1 From a NetView command prompt, type the following command and press Enter:

BR ISM

Verify the NSPMAIN4 CLIST is displayed, as shown in Figure 3-2.

Figure 3-2 Verify ISM Clist Installation

Verifying the ISM Autotasks

Complete the following steps to verify that the ISMOPF member has been included in NetView:

Step 1 From a NetView command prompt, type the following command and press Enter:

LIST ISMADMIN

Step 2 Verify that the following message is displayed after you enter the LIST ISMADMIN command:

DSI008I 'ISMADMIN' NOT ACTIVE

If the message "DSI077A 'ISMADMIN' STATION NAME UNKNOWN" appears, then the ISM autotask has not been included in NetView. See the "ISM Task Not Known to NetView" section under the "Troubleshooting ISM Installation Problems" section in "Troubleshooting"

Verifying the ISM VSAM Commands

Complete the following steps to verify that the ISM VSAM commands are working correctly:

Step 1 From a NetView command prompt, type the following command and press Enter:

NSPDS A UPD ISMTEST THIS IS A TEST

Step 2 Verify that the following messages are displayed:

NSP1910I REQUEST HAS BEEN QUEUED NSP1900I ISMTEST INSERTED

Step 3 Repeat Step 1 replacing ISMTEST with ISMTEST1.

Step 4 Type the following command and press Enter to display the ISMTEST record:

NSPDS A REDK ISMTEST

Step 5 Verify that the following messages are displayed:

NSP1910I REQUEST HAS BEEN QUEUED NSP1900I ISMTEST THIS IS A TEST

Step 6 Type the following command and press Enter to display the records:

NSPDS A LIST ISMTEST ISMTEST1

Step 7 Verify that the following messages are displayed:

NSP1910I REQUEST HAS BEEN QUEUED NSP1900I ISMTEST THIS IS A TEST NSP1900I ISMTEST1 THIS IS A TEST NSP1901I END OF LISTING

Step 8 Type the following command and press Enter to remove the records from the database:

NSPDS A KEYD ISMTEST ISMTEST1

Step 9 Verify that the following messages are displayed:

NSP1910I REQUEST HAS BEEN QUEUED NSP1900I ISMTEST ERASED NSP1900I ISMTEST1 ERASED NSP1901I TOTAL RECORDS ERASED = 2

Planning the Next Steps

The following sections describe the next steps you should perform to install ISM according to your site's current configuration.

•If you are an existing ISM V1R3.0 site and you have completed the installation and verification procedures, you are ready to convert your files. Proceed with the tasks in "Migrating from a Prior Release of ISM"

•If this is the first time for ISM to be installed at your site and you have completed the installation and verification procedures, you are ready to configure the ISM program to manage your resources. Proceed with the tasks in "Configuring ISM"

hometocprevnextglossaryfeedbacksearchhelp

Posted: Wed Sep 1 11:01:22 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.