cc/td/doc/product/rtrmgmt/nsp/nsp2
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Installing and Configuring Native Service Point

Installing and Configuring Native Service Point

This chapter describes how to install, configure, and start NSP. Before installing NSP, ensure that the steps described in the "Preparing to Install Native Service Point" chapter have been completed.

This chapter provides information on the following:

Installation and Configuration Overview

The following is a list of the tasks that must be completed when installing and configuring NSP. The procedure for completing each task follows this summary.


  1. Upload the NSP data sets to the MVS host

  2. Convert the NSP data sets to partitioned data sets

  3. Modify NetView data sets for NSP

  4. Start the NSP setup and configure the NSP management environment

  5. Create an NSP administrator profile

After completing these tasks, you can migrate existing router definitions if you are using NSP Version 1.0 and initialize NSP.

Installing NSP Software

This section contains information on the following:


Note The NSP software is contained on two disks. For a description of each file and the contents and format of each file, see the "General Reference" appendix.

Uploading the NSP Files

While the NSP files can be uploaded using different methods, NSP provides an installation utility that automatically uploads the NSP compressed files to an MVS host in binary format to data sets that have a fixed block (FB) record format (RECFM) and 80-byte record size (LRECL). The NSP installation utility uses the SEND command supported by the IBM Communications Manager/2 Release 1.11 or later running on IBM Operating System/2 (OS/2).

If you are not installing from OS/2 using Communications Manager/2, use the upload utility available with your TN3270 package and ensure that the NSP files are uploaded with a FB, RECFM, and LRECL=80 file format. This is the required format in which the NSP files must be uploaded to convert them to partition data sets during the NSP installation.

Caution Using File Transfer Protocol (FTP) to upload the NSP compressed files to an MVS host is not recommended. Complications could develop with producing the proper file format.

To upload the NSP files to an MVS host from OS/2:

Step 1 Start a TN3270 session and log in to TSO.

Step 2 On the TSO main menu panel, type 6 in the Select Option field and press Enter. The TSO Command Processor panel is displayed.

Step 3 Insert NSP disk 1 into the disk drive of your PC.

Step 4 At the OS/2 command prompt, type the letter representing the drive in which the NSP disk is located and press Enter.

Step 5 At the OS/2 command prompt, type the following command and press Enter:

Where:


Step 6 When the upload process is complete, insert NSP disk 2 into the disk drive of your PC.

Step 7 At the OS/2 command prompt, type the following command and press Enter:

Where:


Step 8 When the upload process is complete, verify that the NSP files uploaded to the MVS host by returning to your TSO session. On the TSO main menu, type 3.4 in the Select Option field, and press Enter. The Data Set List Utility panel is displayed.

Step 9 In the DSNAME LEVEL field, type userid.nsp* (where userid is your TSO ID or system prefix) and press Enter. The following NSP data sets should be listed on the DSLIST panel:

Converting NSP Data Sets to Partitioned Data Sets

Once you have uploaded the NSP data sets to the MVS host, you must convert the NSP data sets to partitioned data sets.

To convert the NSP data sets to partitioned data sets:

Step 1 On the DSLIST panel, position the cursor in the Command column to the left of the first data set (NSP2CL1.SEQ).

Step 2 Type receive inds (/) and press Enter.

Step 3 When prompted, press Enter. The partitioned data set should be created.

If the receive command is terminated, type an S in the command column to the left of the data set to display details about the data set. From the data set details, verify that the data set was uploaded to the MVS with an F or FB record format and a record size of 80.


If these values are correct, type a B in the command column to the left of the data set to browse the NSP data set. The data should be skewed but readable. If you cannot read the data, then either an ASCII or CRLF format may have been used to upload the data set.


If these formats were used, repeat the upload procedure as described in the "Uploading the NSP Files" section and ensure that the proper format is used.


Step 4 Press Tab to move to the next file, type receive inds (/), and press Enter.

Step 5 When prompted, press Enter.

Step 6 Repeat Steps 4 and 5 for the remaining NSP data sets.

Step 7 When you have completed converting the NSP data sets to partitioned data sets, press F3 to return to the Data Set List Utility and then press Enter. The DSLIST panel is displayed with a refreshed list of data sets.

In addition to the original five data sets, the list should now include the following data sets:


Modifying the NetView Data Sets

This section describes the modifications that need to be made to the NetView data sets to use NSP.


Note It is recommended that an MVS programmer complete the following procedures.

To modify the NetView data sets for NSP:

Step 1 Copy the members from the NSPV1R2.CLISTS1 and NSPV1R2.CLISTS2 data sets to the NetView DSICLD data set.

Step 2 Copy the members from the NSPV1R2.PANELS to the NetView CNMPNL1 data set.

Step 3 Copy the members from the NSPV1R2.NSPLOAD to the user's authorized NetView USERLIB data set.

Step 4 Copy the following members from the NSPV1R2.SAMPLIB data set to NetView DSIPARM data set:

Step 5 If you are using CiscoWorks Blue SNA View, copy the NSPHISTR member from the NSPV1R2.SAMPLIB data set to the NetView DSIPARM data set.

Step 6 If using NetView Release 2 Version 3, select and copy the DSITBLRT member from the NSPV1R2.SAMPLIB data set to the NetView DSPARM data set.

Step 7 Open the NSPV1R2.SAMPLIB data set and copy the:

Step 8 If you are using CiscoWorks Blue SNA View, copy the NSPPROC2 member of the NSPV1R2.SAMPLIB data set into the NetView CNMPROC data set.

Step 9 Open each of the following members (located in the NSPV1R2.SAMPLIB data set) and replace each occurrence of the dddddd argument and the prefix argument with the appropriate volume serial number and prefix:

These members create the VSAM data sets used by NSP.


Step 10 Execute each member you edited in Step 9 to create the data sets you defined.

Step 11 If you are using CiscoWorks Blue SNA View and have Step 8, open the ALLHISTR member (located in the NSPV1R.SAMPLIB data set), replace each occurrence of the dddddd argument and the prefix argument with the appropriate volume serial number and prefix and then execute the ALLHISTR member.

Step 12 Restart NetView.

Modifying the NetView RUNCMD Default Timeout Value

The NetView RUNCMD default timeout value can be 24 hours or more. This may result in NSP pausing for long amounts of time waiting for a response from a RUNCMD. It is recommended that you change the NetView RUNCMD timeout default to a value that does not exceed 2 minutes.

To set the NetView RUNCMD timeout value:

Step 1 Modifying and reassemble the NetView DSICTMOD data set. For information on modifying and reassembling the NetView DSICTMOD data set, see the appropriate NetView manual.

OR


Open your NetView initial CLIST (the NetView default is CNME1035) and add the following statement and save and exit the CLIST:


After adding the statement, issue the statement issue the statement to set the new timeout value.


Enabling Automatic Status Update

To enable NSP to automatically obtain and provide an updated status of your Cisco routers:

Step 1 Using a text editor, open the NetView automation table.

Step 2 Open the DSIBLRT member (located in the NSPV1R2.SAMPLIB data set).

Step 3 Copy and merge the following statements into the NetView automation table:



Step 4 If you are using NetView Version 2 Release 2 or later, and automation already exists for any of the statements in Step 3, ensure that each statement is satisfied by removing the semicolon following NETLOG(Y) from each of the statements, coding a CONTINUE(Y) at the end of each existing statement, and inserting each NSP statement before its existing entry.

Step 5 If you are using NetView Version 1 Release 3 or NetView Version 2 Release 1 and automation already exists for any of the statements in Step 3, merge the existing statements with the new NSP statements by add an EXEC (CMD('command') for each statement using the following model:

Step 6 If you are using NetView Version 2 Release 2 or higher, copy and merge the following statements into the NetView automation table:


OR


If you are using NetView Version 1 Release 3 or NetView Version 2 Release 1, copy and merge the following statement into the NetView automation table:


Create the BNJ146I messages by entering the following at a command prompt:


NDPA SRF OPER PASS E PERM


Step 7 If you are using CiscoWorks Blue SNA View and you plan to collect routing information field (RIF) data, insert the following statements:

Step 8 Save your changes and exit the NetView automation table.

Step 9 Recycle the NetView automation table.

For more information on editing the NetView automation table, refer to the appropriate NetView manual.

Configuring NSP

This section contains information on the following:

Starting the NSP Setup

To start the NSP setup, from a NetView command line, type nsp, and press Enter. The NSP Main Menu panel is displayed.


Figure 3-1: NSP Main Menu

Defining the NSP Management Environment and Administrator Profile

Before starting NSP, you must define the NSP management environment and create an NSP administrator profile.

Defining the management environment includes specifying:

The first NSP operator profile is, by default, an NSP administrator profile. This ensures that after you have configured and started NSP, the existing operator profile is authorized to configure and maintain the NSP management environment and assign authority levels to other user's operator profiles that dictate the NSP actions that user can perform.

NSP administrators can be either an enabled or disabled user. An enabled user is an operator who is authorized to log in to a router in enable mode and issue control and configuration commands to the router.

A disabled NSP administrator can:

An enabled NSP administrator can:

To define the NSP management environment and administrator profile:

Step 1 On the NSP main menu, position the cursor on the * SETUP option and press Enter. The NSP Router Management Setup panel is displayed.


Figure 3-2: NSP Router Management Setup Panel

The following information is displayed on this panel:


Step 2 Specify information in the following fields:

Step 3 To view and specify interface monitoring settings, press F8. The NSP monitoring setup parameters are displayed.


Figure 3-3: Interface Monitoring Setup Parameters Panel

The following information is displayed on this panel:


Step 4 Specify information in the following fields:

Step 5 To view NSP defaults for database constants, variables, and wrap counts, press F8. The Router Management Constants Setup panel is displayed.


Figure 3-4: Router Management Constants Setup Panel

Caution The database IDs on this panel can only be modified before initializing NSP.

Step 6 To display the common globals used by NSP, press F10. The NSP Common Globals panel is displayed.

Step 7 Press F3 to return to the NSP Management Constants Setup panel and press F4 to save and exit the NSP Router Management setup. The Cisco Router User Administration panel is displayed.


Figure 3-5: Cisco Router User Administration Panel

The following information is displayed on the Cisco Router User Administration panel:


Step 8 Specify information for the following fields:

Logical groups are defined by an NSP administrator in the router definition for filtering purposes. The logical group or groups to which a router may belong are displayed on the Router Status Extended panel.
For more information on filtering routers, see the "Filtering Routers" section of the "Monitoring Routers" chapter of this manual.

Step 9 When you have completed the administrator profile, press Enter to verify the changes and then F4 to save the profile.

Migrating from NSP Version 1.0

NSP provides a migration utility that allows you to migrate existing NSP Version 1.0 router definitions to NSP Version 2.0.

To migrate your existing NSP Version 1.0 router definitions:

Step 1 From a NetView command line, type nspinit reset and press Enter. The NSP Common Globals panel is displayed.

Step 2 Start NSP Version 1.0 by typing nspsinit and pressing Enter.

Step 3 Type nsprmgrt and press Enter. As NSP collects the interface data for each router that was defined to NSP Version 1.0, the following message is displayed where ROUTER_NAME is the name of the router whose definition is being migrated:

When all the NSP Version 1.0 router definitions have been migrated to NSP Version 2.0, the following message is displayed:


Initializing NSP

The NSP program is designed to be started and left running so that your Cisco routers, interfaces, and DSPU and CIP resources are being monitored at all times. To have NSP start when NetView is started, add the NSP autotask commands to the NetView initialization CLIST.

Caution Ensure that you have completed the procedure in the "Defining the NSP Management Environment and Administrator Profile" section before starting NSP.

NSP provides three autotasks that you can use to start NSP automatically when NetView starts. It is recommended that one autotask be used for every 300 hundred routers that you plan to monitor using NSP. The three autotasks provided by NSP are:

To have NSP automatically start when NetView starts:

Step 1 Open you NetView initial CLIST (the NetView default is CNME1035) and, depending on the number of routers you plan to monitor, add one or more of the following statements:

Step 2 Save and exit the CLIST.

Step 3 To start the NSP autotask, either recycle NetView

OR


Type autotask opid=nspmgr and press Enter and if using more than one NSP autotask, repeat this step and substitute the opid value with the name of each NSP autotask you are starting.



Note If you added the NSP autotasks to the NetView initial CLIST as described in Step 1, then NSP will automatically start each time NetView is started. Therefore, you will not have to issue the autotask opid=nspmgr command each time to start NSP.

Step 4 To access the NSP Version 2.0 main menu, type nsp and press Enter.

Reviewing General Guidelines for Using NSP

The following sections provide general information about using the NSP main menu, panels, and function keys.

Using the NSP Main Menu

This section explains the NSP main menu, describes the NSP applications available on the NSP main menu, and describes how to access each of those applications.

To access the NSP main menu:

Step 1 From a NetView command prompt, type nsp and press Enter. The NSP main menu is displayed.


Figure 3-6: NSP Main Menu

The following applications are available on the NSP main menu:


Step 2 To select an NSP application, place the cursor on the option representing the application and press Enter.

Using the NSP Panels

As you use the NSP panels, follow these guidelines:

Press To
F1 Display help for the panel or help for a field.
F2 Quit NSP and return to the NetView main menu.
F3 Return to the previous panel.
F6 Toggle between the NSP panel and a NetView panel.
F8 Page down (F8 displays only if the information exceeds the length of one panel).
F7 Page up (F7 displays with F8).
F10 Shift the panel to the left (F10 displays with F11).
F11 Shift the panel to the right (F11 displays only if the information exceeds the width of the panel).

Note Function keys that are specific to a panel are described in context throughout this manual.
To display the Router Management popup menu, select a router from the Router Status panel and press Enter. The Router Status panel with the menu is displayed.

Note Once the popup menu is displayed, you can type the SPname of a router in the field above the popup menu in which the SPname of the router you selected is displayed to use the popup menu to perform management functions on another router. This enables you to bypass having to return to the Router Status panel to locate and select a router and then display the popup menu.

Figure 3-7: Router Status with Menu Panel

To select an option from the popup menu, place your cursor over the function you want to perform and press Enter.
OR
In the field located at the top of the popup menu, type the number or letter representing the option and press Enter.
The following table summarizes the functions located on the Router Management popup menu. Each of these functions are described in detail in the following sections.
To Select
Issue commands to the router. Cmd Interface (1)
View a list of interfaces supported by the router and the status and details of each interface. Show Protocols (2)
Display the management data of a router. Show MGMT Data (3)
View the total count of events generated by a router from NetView. Show Total Events (4)
Display router information as it appears in VTAM. VTAM Display (5)
Display a list of archived configuration files that can be used for disaster recovery. Show Conf History (6)
Collect and archive the current configuration of the router. Collect Config (7)
View in a list of the most recent events generated by a router in reverse chronological order. Last Alert (8)
Release a session between a router and an operator and reset its status. Reset Status (9)
Collect and display CPU and memory usage and percentages. Router Perf Hist (A)
Collect additional information about a router using Cisco IOS software show commands. Show Commands (B)
View a list of interfaces, by type, enabled within a router and obtain additional information about those interfaces. Interface Status (C)

Adding Router Definitions

You can define the routers you want to monitor to NSP. You can also modify or delete existing router definitions. The following instructions on defining a router to NSP assume that the router you are defining has been configured as described in the "Preparing to Install Native Service Point" chapter.


Note If a generated alert is received from a router that has not yet been defined to NSP, then NSP automatically obtains the necessary information to define that router and adds the router to those monitored by NSP.

To define, change, or delete a router:

Step 1 On the NSP main menu, press Tab to move to the Service Point Name field.

Step 2 Type in the service point name of the router you are adding and press Enter. The Router Command Interface panel is displayed.


Figure 3-8: Router Command Interface Panel

Step 3 Press F3 to return to the NSP main menu.

Step 4 Position the cursor on the * MGR option and press Enter. The Router Status panel is displayed.

Step 5 Position the cursor on the SPname of the router you are adding and press Enter or F10. The popup menu is displayed.


Figure 3-9: Router Status with Menu Panel

Step 6 Type 3 in the field at the top of the popup menu and press Enter. The Router Data Management panel for that router is displayed.


Figure 3-10: Router Management Data Panel

Step 7 Press F4. The Router Resource Definition panel is displayed.


Figure 3-11: Cisco Router Resource Definition Panel

The following information is displayed on the Cisco Router Resource Definition panel:


  • Index number--Pointer to the control block in which the router definition is stored.

  • VTAM Definition Member--Name of the VTAM member that contains the router definition.

  • Autotask Monitor--NSP autotask that is monitoring the router.

  • VSAM KSD Contents--Details of the VSAM data record containing the NSP configuration data.

Step 8 Specify information in the following fields:

  • Change Type--Indicates whether you are adding a definition for a new router, changing an existing router definition, or deleting a router definition. To specify an option for this field, type the number representing the option.

  • Action Type--Indicates whether you want to implement the changes to the router definition at the next startup of NSP, implement them in the current session only, or implement them in the current session and save the changes for future sessions. To specify an option for this field, type the number representing the option.

  • Router Service Point Name--Service point name of the router as defined in the VTAM configuration file (can be up to 8 characters).

  • NetView Domain Name--NetView domain in which the router is located. If a router is discovered by NSP, this information is automatically retrieved from the router.

  • Router Host Name--Host name of the router as specified in the router and VTAM configuration files. If a router is discovered by NSP, this information is automatically retrieved from the router.

  • Router IP Address--User-defined IP address of the router.

  • Router Description--User-defined description of the router.

  • Configuration Data--User-defined pointer to where the configuration information is stored.

  • Operation Group ID(s)--Logical group or groups to which the router belongs for filtering purposes. A router can belong to two groups. For information on filtering routers by logical groups, see the "Filtering Routers" section of the "Monitoring Routers" chapter of this manual.

Step 9 When completed, press Enter to verify your changes and then F4 to save the router definition.

You can obtain additional information from the Cisco Router Resource Definition panel using the function keys located at the bottom of the panel.

To Press
View the router information as it is defined to VTAM. F10
View the values of common globals used to manage the router. F11

Defining Operator Profiles

The NSP operator profile management function provides two operator types. Each of these operator types dictates the actions an operator can perform using NSP.

The two types of NSP operators are:

  • NSP administrator

  • NSP operator

NSP Administrator

NSP administrators maintain the NSP management environment. NSP administrators also are responsible for assigning "authority levels" for users, which dictate the NSP actions a user can perform. NSP administrators can also be enabled users.

An disabled NSP administrator can:

  • Create operator profiles and assign user authority.

  • Configure and change the NSP management environment.

An enabled NSP administrator can:

  • Issue the Cisco IOS software enable command and issue commands that control and configure Cisco routers.

  • Add, modify, and delete router and DSPU resource definitions.

  • Modify interface settings.


Note An enabled NSP user must know the password to a router to issue the enable command.

NSP Operator

NSP operators can create their own profiles for user-identification purposes and for filtering purposes.

An disabled NSP operator can:

  • Collect and display data that enables them to monitor the status of the Cisco routers, interfaces, and other resources in their network.

  • Set group and status filters.

An enabled NSP operator can:

  • Issue the Cisco IOS software enable command and issue commands that control and configure Cisco routers.

  • Add, modify, and delete router and DSPU resource definitions.

  • Modify interface settings.


Note An enabled NSP user must know the password to a router to issue the enable command.

Creating, Changing, or Deleting Operator Profiles

All NSP operators should create an operator profile for themselves. They can use their profile for user identification and group and status filtering purposes. However, while all NSP operators can create their own profiles, it is only the NSP administrator that can specify or change an authority level to an operator profile.

To create or change an operator profile:

Step 1 Access the Cisco Router User Administration panel using one of the following methods:

  • If you are creating or changing your own profile, position the cursor on the * USER option on the NSP main menu and press Enter.

  • If you are an NSP administrator and are creating or changing an operator's profile, position the cursor in the Userid field on the NSP main menu, type the ID of the operator and press Enter.


Figure 3-12: Cisco Router User Administration Panel

The following information is displayed on the Cisco Router User Administration panel:


  • Operator ID--ID of the operator whose profile is being created or changed. If you are an NSP administrator, this field should automatically display the user ID you typed on the NSP main menu or, if you are not an NSP administrator, it should display your user ID.

  • VSAM Record--Details of the VSAM data record containing the NSP configuration data.

Step 2 Specify information for the following fields:

  • Change Type--Indicates whether you are defining a new operator profile, changing an existing profile, or deleting a profile. To specify an option for this field, type the number representing the option. Only an NSP administrator can specify the Delete option.

  • Action Type--Indicates whether you want to implement your changes at the next startup of NSP, implement them in the current session only, or implement them in the current session and save the changes for future sessions. To specify an option for this field, type the number representing the option.

  • NSP User Administrator--Indicates whether this operator is an NSP administrator. Type Y to specify the operator as an NSP administrator or N to specify that an operator has display-only authority. Only an NSP administrator can define or change this field.

  • Operator Name--Name of the user assigned to the user ID. When creating a profile, type the name of user in this field or, if you are creating your own profile, type your name.

  • Authority--Indicates whether the operator can only view information or can log in to a router in enabled mode and perform router configuration functions. Only an NSP administrator can define or change this field.

  • Group Filters--Logical groups by which you may want to filter routers. To enable group filtering, type a Y to the right of the Group Filters field. In the Group 1 and Group 2 fields, type one or two logical groups through which you want to filter routers.

Logical groups are defined by an NSP administrator in the router definition. The logical group or groups to which a router belongs can be viewed on the Router Status Extended panel. For more information on filtering routers, see the "Filtering Routers" section of the "Monitoring Routers" chapter of this manual.

  • Status Filters--Status by which you want to filter routers. To enable status filtering, type a Y to the right of the Status Filters field. Type an X or I to the right of the Exclude/Include field to indicate whether you are filtering to include or exclude routers that match a status. In the Filter 1, Filter 2, and Filter 3 fields, type one to three statues by which you want to filter routers.

For more information on filtering routers, see the "Filtering Routers" section of the "Monitoring Routers" chapter of this manual.

Step 3 When you have completed the operator profile, press Enter to verify the changes and then F4 to save the profile.


Note To display users defined to NSP, issue the NSP nspulist command to display a list of users with each user's name, ID, and the NSP authority level defined in their profile.

hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1997 © Cisco Systems Inc.