Table Of Contents
Preparing to Install ISM
Planning Who Should Install ISM
Overview of the Installation Tasks
Enabling ISM to Monitor Routers
Verifying the NetView Environment
Installing ISM
Configuring ISM
System Requirements
Mainframe Hardware Requirements
Mainframe Software Requirements
Cisco IOS Software Requirements
Planning the ISM Installation
Verifying the ISM DASD Storage Requirements
Installation Storage Requirements
Production Storage Requirements
VSAM Storage Requirements
ISM Installation File Contents
Getting Started
Preparing to Install ISM
CiscoWorks Blue Internetwork Status Monitor (ISM) for NetView is a program that runs on a Multiple Virtual Storage (MVS) mainframe using NetView, IBM's network management platform, and manages Cisco routers. ISM bridges the worlds of mainframe network management and management of distributed routers in LAN and WAN topologies.
This chapter provides the following information to help you prepare to install ISM:
•
Planning Who Should Install ISM
• Overview of the Installation Tasks
• System Requirements
• Getting Started
Planning Who Should Install ISM
Installing ISM requires that you perform tasks for configuration of the mainframe and router sides of the network environment, in addition to actually installing and enabling the ISM software on the mainframe.
Often in the mixed network environment of mainframes and LANs, an MVS system programmer installs and maintains the mainframe side of the network, while a network engineer manages the routers on the LAN side of the network. In such an environment, the successful installation and operation of ISM requires the close coordination between these job functions at a customer site.
Readers who perform the following job functions are the target audience for this installation guide:
•The MVS or Virtual Telecommunications Access Method (VTAM) system programmer responsible for installing and configuring ISM on the mainframe system.
ISM works in the VTAM and NetView communications environment. Because the mainframe installation tasks for ISM involve VTAM and NetView integration, a VTAM system programmer installs ISM. However, any MVS system programmer can perform the tasks in coordination with the site's VTAM system programmer.
•The network engineer responsible for installing and configuring the routers to be managed by ISM.
Overview of the Installation Tasks
ISM installation is accomplished in four stages as reflected by the following chapters:
• Configuring the Mainframe-to-Router Link
• Installing ISM
• Migrating from a Prior Release of ISM
• Configuring ISM
Each stage ends with verification of successful completion in order to isolate and troubleshoot problems immediately, if they occur.
This section summarizes the installation tasks. Detailed instructions are provided in subsequent chapters. Use the following list to ensure you perform all the ISM installation steps applicable to your site's environment.
Note Be sure that the mainframe and routers meet the minimum hardware and software requirements to install and operate ISM. See the "System Requirements" section.
Enabling ISM to Monitor Routers
The tasks in this section are the only ones that require the involvement of network engineers responsible for configuring the router. For detailed instructions, see "Configuring the Mainframe-to-Router Link"
Step 1 Configure a VTAM physical unit (PU) to support the Service Point (SP) for each router to manage using ISM.
Step 2 Configure each router to support the SNA SP you defined in VTAM.
Step 3 Verify that the routers can connect to VTAM and can communicate with NetView using RUNCMDs.
Verifying the NetView Environment
Step 1 Verify the timeout value for RUNCMDs to ensure that the values of the costime and max reply options are set correctly in NetView to support the ISM autotasks.
Step 2 Verify whether NetView supports RUNCMDs to ensure proper configuration of the NetView VTAM definition for LU 6.2 support.
Step 3 Verify the router's mainframe connection.
Step 4 Verify the router connection from NetView to ensure that network devices are configured properly and that the router can attach to the network.
Step 5 Verify the router connection from VTAM to ensure that the router is communicating with the mainframe from VTAM.
Installing ISM
Step 1 Load the ISM software onto the mainframe using either the direct or System Modification Program Extended (SMP/E) installation methods.
Step 2 Update SYS1.PARMLIB to authorize the ISM load library.
Step 3 Update the members of the NetView DSIPARM data set.
Step 4 Install the VTAM XID Configuration Services exit routine.
Step 5 Verify the ISM software installation so ISM can communicate with NetView.
Configuring ISM
Step 1 Configure the ISM management environment.
Step 2 Define the ISM user profiles.
System Requirements
This release of ISM requires the components described below for both the mainframe and router environments. Be sure to note the Cisco IOS software levels required in your routers for the type of router management you want to support.
Mainframe Hardware Requirements
The following hardware is required to install the ISM program on the mainframe:
•Direct access storage in the following amounts, according to the ISM installation method that you select:
–For the direct installation method, approximately 50 megabytes.
–For the SMP/E installation method, approximately 70 megabytes.
Note For detailed information about the allocation of storage for the ISM installation files, see Chapter 3, "Installing ISM."
Mainframe Software Requirements
The following operating system and application software is required to install the ISM program on the mainframe:
•OS/390-MVS mainframe running MVS/ESA Version 4.1 or later, OS/390, or z/OS
•SMP/E Release 7 or later (required for SMP/E installation method only)
•TME/10 NetView for OS/390 (Version 1.2 or later)
•VTAM Version 4.1 or later for support of ISM's SNA Session Monitoring application
•Any version of VTAM for support of the other ISM applications
Cisco IOS Software Requirements
Your routers must meet the following Cisco IOS software levels for the type of router management that you want to support in ISM:
•For Remote Source-Router Bridging (RSRB) support, Cisco IOS Release 11.0 or later
•For data-link switching (DLSw+) support, Cisco IOS Release 11.1 or later
•For Cisco mainframe channel connection (CMCC) routing information field (RIF) support, Cisco IOS Release 11.3 or later
Planning the ISM Installation
Before you install the ISM software, complete the following planning tasks:
•Choose the direct or SMP/E method of installing ISM software. The method you choose changes the storage requirements for the installation.
•Review the "Verifying the ISM DASD Storage Requirements" section to select the appropriate direct access storage device (DASD) locations to accommodate the ISM installation and production files.
•Determine the volume serial numbers of the DASD to use for your ISM installation and production files.
•Determine the high-level qualifier (or prefix) you will use to identify your ISM data sets.
Verifying the ISM DASD Storage Requirements
The following sections will help you determine the amount of ISM DASD storage required for your site's ISM installation:
• Installation Storage Requirements
• Production Storage Requirements
• VSAM Storage Requirements
Installation Storage Requirements
The amount of storage that ISM requires for the installation data sets varies based on the method you use to install the software. The DASD storage requirements for the target libraries shown in Table 1-1, apply to both the direct method and SMP/E method of installation.
Table 1-1 lists the data set name and provides a brief description, along with the minimum storage requirements for the ISM installation target libraries.
Note Through the remainder of this chapter, the file specifications use the variable prefix to represent the high-level file qualifier. When you run the jobs in the sample members of the installation data sets, change the occurrences of prefix to the high-level qualifier selected for ISM.
Table 1-1 DASD Storage Requirements for Target Libraries
Data Set Name
|
Description
|
Space
|
prefix. NSPI202.NSPNINST
|
Installation jobs
|
1 MB
|
prefix. NSPI202.NSPNLOAD
|
Load library; command modules and exits
|
1 MB
|
prefix. NSPI202.NSPNCLST
|
CLIST and REXX routines
|
15 MBs
|
prefix. NSPI202.NSPNHTML
|
HTML routines
|
6 MBs
|
prefix .NSPI202.NSPNPANL
|
Presentation panels
|
4 MBs
|
prefix .NSPI202.NSPNSAMP
|
Sample installation and customization procedures
|
2 MBs
|
Additional SMP/E Installation Storage Requirements
In addition to the storage requirements for the target libraries, the SMP/E method requires at least 20 additional megabytes for the distribution libraries.
Table 1-2 lists the data set name, a brief description of each data set, and the minimum storage required for the ISM installation distribution libraries when you use SMP/E to install the software.
Table 1-2 DASD Storage Requirements for SMP/E Distribution Libraries
Data Set Name
|
Description
|
Storage
|
prefix. NSPI202.NSPNINST
|
Installation jobs
|
1 MB
|
prefix. NSPI202.ANSPNLOA
|
Load library; command modules and exits
|
1 MB
|
prefix. NSPI202.ANSPNCLS
|
CLIST and REXX routines
|
15 MB
|
prefix. NSPI202.ANSPNHTM
|
HTML routines
|
6 MB
|
prefix. NSPI202.ANSPNPAN
|
Presentation panels
|
4 MB
|
prefix. NSPI202.ANSPNSAM
|
Sample installation and customization procedures
|
2 MB
|
Production Storage Requirements
Table 1-3 lists the recommended storage requirements for the ISM production members for NetView. The production storage requirements apply to both the direct and SMP/E installation methods.
Table 1-3 ISM Storage Requirements
Name
|
Storage
|
NETVIEW.USER.DSICLD (NSPNCLST or ANSPNCLS)
|
15 MB
|
NETVIEW.USER.DSICLD (NSPNHTML or ANSPNHTM)
|
6 MB
|
NETVIEW.USER.LOADLIB (NSPNLOAD or ANSPNLOA)
|
1 MB
|
NETVIEW.USER.CNMPNL1 (NSPNPNLS or ANSPNPAN)
|
4 MB
|
NETVIEW.USER.DSIPARM (ISMTBL, ISMDMN, ISMCMD, and ISMOPF)
|
1 MB
|
VSAM Storage Requirements
Table 1-4 lists the initial VSAM storage allocations for the data sets that ISM uses. The maximum storage required depends on the number of routers and interfaces monitored and on the ISM functions enabled. Some of the data sets are optional depending on the ISM functions you plan to implement at your site.
The first four required data sets may use 12 MBs of storage. Full implementation of the ISM functions and their corresponding data sets allocates additional storage of 30 MBs.
The VSAM storage requirements in Table 1-4 apply to both the direct and SMP/E installation methods.
Table 1-4 VSAM Storage Requirements
Data Set Name
|
Description
|
Storage
|
prefix. ISMDSA
|
ISM management data
|
5 MBs
|
prefix. ISMDSH
|
Router and Cisco mainframe channel connection archive data
|
5 MBs
|
prefix. ISMDSM
|
Primary event log data
|
1 MB
|
prefix. ISMDSN
|
Alternate event log data
|
1 MB
|
| |
|
Total:
12 MBs
|
Optional Data Sets
|
prefix. ISMDSI
|
Interface statistics and performance data
|
5 MBs
|
prefix. ISMDSC
|
Router configuration data
|
5 MBs
|
prefix. ISMDSR
|
SNA session data
|
10 MBs
|
prefix. ISMDSD
|
Router memory dump data
|
5 MBs
|
prefix. ISMDSW
|
SNASw statistics and performance data
|
5 MBs
|
| |
|
Total:
30 MBs
|
VSAM Record Requirements for ISM Configuration
Table 1-5 lists the number of VSAM records required for ISM configuration. Use this information to evaluate the size of the VSAM data sets for your site's installation.
Table 1-5 VSAM Record Requirements for ISM Configuration
Record Name
|
Number of Records
|
Setup definition
|
2
|
Router management
|
2 per router
|
Interface management
|
1 per interface
|
Operator security
|
1 per operator
|
DSPU management
|
1 per VTAM DSPU
|
Router statistics
|
1 header record plus wrap count per router
|
Interface statistics
|
1 header record plus wrap count per interface
|
Interface performance
|
1 header record plus wrap count per interface
|
RIF history
|
1 header record plus wrap count per PU
|
Router configuration
|
1 header record plus 1 record per configuration statement
|
SNASw configuration
|
1 per SNASw instance
|
Cisco mainframe channel connection management
|
1 per Cisco mainframe channel connection
|
Cisco TN3270 Statistics
|
1 header record plus wrap count per interface
|
CMCC statistics
|
1 header plus wrap count
|
TN3270 statistics
|
1 header plus wrap count
|
ISM Installation File Contents
Table 1-6 describes the format of the files after you receive them from the CCO site.
Table 1-6 ISM Zip File Contents
Name
|
Record Format
|
Logical Record Length
|
Block Size
|
Distribution Library
|
NSPI202.SMPMCS.XMIT
|
FB
|
80
|
3120
|
|
NSPI202.F1.XMIT
|
FB
|
80
|
3120
|
JCLIN
|
NSPI202.F2.XMIT
|
U
|
0
|
6144
|
ANSPNLOAD
|
NSPI202.F3.XMIT
|
FB
|
80
|
3120
|
ANSPNSAMP
|
NSPI202.F4.XMIT
|
FB
|
80
|
3120
|
ANSPNCLST
|
NSPI202.F5.XMIT
|
FB
|
80
|
3120
|
ANSPNPANL
|
NSPI202.F6.XMIT
|
FB
|
80
|
3120
|
ANSPNHTML
|
NSPI202.NSPNINST.XMIT
|
FB
|
80
|
3120
|
ANSPNINST
|
Getting Started
The installation steps that you perform depend, in part, upon your site's environment and how you plan install this release of ISM.
If your site currently has ISM V1R3.0 installed, read the following chapters:
• Chapter 3, "Installing ISM"
• "Migrating from a Prior Release of ISM"
• "Configuring ISM"
If your site does not have any version of ISM installed, read the following chapters:
•Chapter 2, "Configuring the Mainframe-to-Router Link"
•Chapter 3, "Installing ISM"
•Chapter 5, "Configuring ISM"
