|
|
This document contains important information related to hardware and software requirements, and installing, licensing, and starting the 4.2 version of the Cisco Netsys Service-Level Management Suite (hereafter referred to as Cisco NSM) software.
With this 4.2 release, the Cisco NSM software has been made Year 2000 (Y2K) compliant. All previous versions of the Cisco NSM software do not meet Y2K requirements, therefore, Cisco strongly recommends you upgrade to this new version.
Cisco NSM 4.2 only operates with Sun's Solaris 2.6, Hewlett Packard's HP-UX 10.20, and IBM's AIX 4.3.1 operating systems. See Section, Year 2000 Support in the Cisco NSM 4.2 - READ THIS FIRST, for information about specific operating system requirements for Year 2000 support and compatibility information.
This document contains the following sections:
This section describes the hardware and software required to run the Cisco NSM 4.2 software.
The following hardware, minimum disk space, and memory are required:
The following requirements are for each simultaneous user:
The following software is required:
The INSTALL installation script can be run from either a locally attached or remote CD-ROM drive. When you invoke the installation script from a remote drive, the remote and local platforms do not have to be running the same operating system. Following is the sequence of steps to follow to load and mount the CD-ROM, install the Cisco NSM software, obtain a license, and start the Cisco NSM software:
Step 1 Load the CD-ROM into the CD-ROM drive. See "Loading the CD-ROM".
Step 2 Mount the CD-ROM drive. See "Mounting the Locally Attached CD-ROM Drive".
Step 3 Export the CD-ROM drive to make it available to other machines when you are installing the software on a remote machine. See Section, "Mounting a Remotely Attached CD-ROM Drive".
Step 4 Install the Cisco NSM software. See Section, "Installing the Cisco NSM Software".
Step 5 Obtain a license for running the Cisco NSM software. See Section, "Obtaining a License".
Step 6 Invoke the Cisco NSM software. See Section, "Starting the Cisco NSM Software".
The Cisco NSM software can be loaded from either a locally attached or remote CD-ROM drive.
Step 1 Remove the Cisco NSM CD-ROM from the case and insert it into the CD-ROM drive.
Step 2 Log in as the root user:
host% su
host% Password: (specify your su root password)
host#
The mount instructions for a locally attached CD-ROM drive for the various operating systems supported by the Cisco NSM software are provided in this section.
Step 1 When a CD-ROM drive mount point does not exist, create one as follows:
host# mkdir /cdrom
Step 2 Mount the CD-ROM drive on the mount point.
The mount instructions for a remotely attached CD-ROM drive for the various Operating Systems supported by the Cisco NSM software are provided in this section. The CD-ROM drive must be mounted on the remote system (following the steps provided in the previous section), the mount point must then be exported, and it must be mounted on the machine where the Cisco NSM software is to be installed.
Prior to mounting the CD-ROM drive from the remote host, the device must be made accessible. The following procedures are performed on the remote system where the CD-ROM drive is attached.
Step 1 When they are not already running, start the following NFS mount daemons:
host# /usr/lib/nfs/nfsd 8
host# /usr/lib/nfs/mountd
Step 2 Share the mount point from the remote system:
host# /usr/sbin/share -F nfs -o ro /cdrom/<Cisco_NSM_directory>
Step 3 Verify the remote host is exporting the mount point. The listing produced by this command should include the /cdrom mount point.
host# /usr/sbin/share
Step 4 On the client machine, verify the mount point on the remote host:
host# /usr/sbin/showmount -e <remote_server> | grep cdrom
where <remote_server> is the name of the remote host where the CD-ROM drive is mounted.
Step 5 On the client machine, mount the remotely installed CD-ROM device:
host# /usr/sbin/mount <remote_server>:/cdrom <local_mount_point>
where <local_mount_point> is the mount point on the client machine for the remotely mounted CD-ROM drive.
Step 1 When the following entry does not exist in the /etc/exports file, append it to the file. This allows the remote system to export the /cdrom mount point.
/cdrom -ro
Step 2 Export the /cdrom directory from the remote host:
host# /usr/sbin/exportfs /cdrom
Step 3 Verify the remote host is exporting the mount point. The listing produced by this command should include the /cdrom mount point.
host# /usr/sbin/exportfs
Step 4 On the client machine, verify the mount point on the remote host:
host# /usr/sbin/showmount -e <remote_server> | grep cdrom
where <remote_server> is the name of the remote host where the CD-ROM drive is mounted.
Step 5 On the client machine, mount the remotely installed CD-ROM device:
host# /usr/sbin/mount <remote_server>: /cdrom <local_mount_point>
where <local_mount_point> is the mount point on the client machine for the remotely mounted CD-ROM drive.
Step 1 When the following entry does not exist in the /etc/exports file, append it to the file. This allows the remote system to export the /cdrom mount point.
/cdrom -ro
Step 2 Export the /cdrom directory from the remote host:
host# /usr/sbin/exportfs /cdrom
Step 3 Verify the remote host is exporting the mount point. The listing produced by this command should include the /cdrom mount point.
host# /usr/sbin/exportfs
Step 4 On the client machine, verify the mount point on the remote host:
host# /usr/sbin/showmount -e <remote_server> | grep cdrom
where <remote_server> is the name of the remote host where the CD-ROM drive is mounted.
Step 5 On the client machine, mount the remotely installed CD-ROM device:
host# /usr/sbin/mount <remote_server>: /cdrom <local_mount_point>
where <local_mount_point> is the mount point on the client machine for the remotely mounted CD-ROM drive.
This section describes how to install the 4.2 version of the Cisco NSM software from the CD-ROM.
Step 1 Change to the directory where the CD-ROM drive is mounted.
host% cd /cdrom (Solaris: with volume management running, cd to the SERVICE_LEVEL_MANAGER directory under /cdrom)
Step 2 When you are currently logged in as root, log out and then log back in as yourself. You should not install the Cisco NSM software as root.
When a previous version of the Cisco NSM software is not already installed on the machine you are going to install this release, go to the "Installation" section. Otherwise, follow the directions listed below prior to going to the "Installation" section.
When a previously installed copy of the Enterprise/Solver or Cisco NSM software currently exists on your machine, it is advisable to install this version of the Cisco NSM software in a different location and/or:
1. save the router configuration files and current baselines to a location of your choice.
2. save the previous version's $ECSP_HOME/resources/scheduler/scheduler_file file and then append it to the $ECSP_HOME/resources/scheduler/scheduler_file file in the 4.2 Cisco NSM installation directory. For example:
3. edit your shell script file(s) removing any statements setting the ECSP environment variables and the path to the existing version's bin directory.
4. save the currently installed product using the "mv" command. For example, when the previously installed copy of the Enterprise/Solver or Cisco NSM software exists in the /home/apps/netsys directory, the following command moves the installed software to the /home/apps/netsys_BAK directory:
The Cisco NSM software installation script (INSTALL) is, by default, started in quick mode (described below.) To start the installation script in custom mode, use the -custom parameter. Custom mode prompts you for specific installation related values instead of using the default values described in section "Quick Mode Installation".
You can add the alias to your .cshrc or .aliases file as appropriate.
By default, the installation script (INSTALL) is run in quick mode (as opposed to custom mode.) When running in quick mode, you are prompted for a destination directory and whether you wish to add variables to your .cshrc or .profile file.
Running the installation script in quick mode makes the following assumptions:
1. The operating system, hostname, and hostid of the machine you are running the script on are used as defaults. Therefore, you must invoke the script on the machine you will be running the Cisco NSM software.
2. The ECSP_DATA environment variable is set to $HOME/netsys_data. This variable is used to specify the directory where the baselines you create are located. You can edit your .cshrc or .profile file to modify this environment variable.
3. The ECSP_HELPVIEWER environment variable is set to netscape. This variable is used to specify the HTML browser you wish to use for displaying Help information. You must specify the full path to the HTML browser program when it is not in your current PATH. You can edit your .cshrc or .profile file to modify this environment variable.
4. The ECSP_TMPDIR environment variable is set to $ECSP_DATA/tmp. This variable is used to specify the directory where temporary files are created. When the $ECSP_DATA/tmp directory does not have at least two megabytes of space available, Cisco NSM performance is greatly degraded. You can edit your .cshrc or .profile file to modify this default setting of this environment variable.
While running the script in either mode, keep the following in mind:
1. During Cisco NSM software installation, whenever you are prompted for the location of directories or files, you must specify absolute path names when you do not want to use the default values.
2. The Cisco NSM software is installed in a directory named netsys. The netsys directory is created either in the home directory of the user running the installation script (default) or in the directory you specified during the running of the Cisco NSM software installation script. For example, when you opt to install the Cisco NSM software in the /home/apps directory, the Cisco NSM software is actually installed in the /home/apps/netsys directory.
3. For your convenience, the required environment variables used by the Cisco NSM software are written into the following files under the netsys directory:
(a) .profile.ctk and profile.ctk - these files are in a format usable by Bourne and Korn shells.
(b) .cshrc.ctk and cshrc.ctk - these files are in a format usable by C shell.
You can either source these files just prior to running the Cisco NSM software, or you can have the installation script append them to a shell script file for you so they are automatically set for your environment.
4. The ECSP_HOME environment variable is set to the absolute path name of the netsys directory after you source one of the above mentioned files.
5. The Cisco NSM software uses SCCS as its version control software. The installation script expects the SCCS files to be located in /usr/bin (AIX and HP-UX 10.x), or /usr/ccs/bin (Solaris)and gives a warning when it is not found. When the SCCS files reside in a different location, you should change your PATH environment variable to ensure the SCCS files are accessible by the Cisco NSM software (in which case you can ignore any related warning messages.)
6. You must have read permission across all $ECSP_HOME directories and read/write permission in the $HOME/netsys_data, $ECSP_HOME/resources/license, $ECSP_HOME/data, and $ECSP_HOME/resources/scheduler directories.
7. You must have write permission in the directory pointed to by the ECSP_TMPDIR environment variable.
Step 3 Invoke the installation script from the command line as follows:
host% ./INSTALL
As necessary, provide the information prompted for by the installation script. When the installation script is complete, you must obtain and install a license, as described in the following section.
This section explains the procedure for obtaining and installing the license needed to use the Cisco NSM software. It assumes you have already read and followed the Cisco NSM software installation instructions, and the Cisco NSM software is ready to use with the exception of licensing.
By default, the licensing script (license.ctk) is run in quick mode (as opposed to custom mode.) When run in quick mode, you are only prompted for the Cisco NSM software's serial number, application key, and expiration date.
The Cisco NSM software incorporates Globetrotter FLEXlm (license management) software. FLEXlm has the following components which must be in place before the Cisco NSM software can be properly licensed:
This daemon (background process) communicates with the vendor daemon (described below.) It is linked to the Cisco NSM software and assures the applications are being used in a manner consistent with their licensing. This daemon should not be run as root.
This daemon is specific to the Cisco NSM software. The link between this daemon and the license manager daemon (lmgrd) allows the Cisco NSM software to run. This daemon should not be run as root.
The vendor daemon looks to this file for relevant licensing information per application, such as the host id, the number of simultaneous users, and the application license keys.
You must provide the following information to obtain a license key:
1. Your company's name and address.
2. The name, phone and FAX numbers, and email address of the person within your company requesting the Netsys Connectivity Service Manager, Netsys Performance Service Manager, and/or Netsys LAN Service Manager license.
3. The name of the dealer/distributor from whom the Cisco NSM software was obtained.
4. The host name of the machine running the lmgrd daemon. Type hostname at the command line prompt to receive the machine's host name.
5. The unique host ID of the machine running the lmgrd daemon. Type lmhostid at the command line prompt to receive the machine's host ID. This is not the machine's IP address.
6. The licensing version number of the Cisco NSM software. This number is provided at the end of the INSTALL installation script (or you can run the
$ECSP_HOME/bin/version -licenseversion command to obtain it).
7. The OS platform the Cisco NSM software is installed (that is, Solaris, HP-UX, or AIX).
Please complete the Request for Activation Key (Schedule A of the End-User License Agreement) and FAX it to Cisco Systems per the instructions on the form. Cisco Systems will return to you, via FAX or electronic mail, the information needed to install the license.
By default, the licensing script (license.ctk) is run in quick mode. To start the installation script in custom mode, use the -custom parameter. Custom mode prompts you for specific license related values instead of using the default values and assumptions described below.
Running the licensing script in quick mode makes the following assumptions:
1. The operating system, host name, and hostid of the machine you are running the script on are used as defaults. Therefore, you must invoke this script on the machine where you will be running the Cisco NSM software.
2. The license manager daemon (lmgrd) must run on the current machine.
3. The ECSP_HOME environment variable must be set prior to invoking the license.ctk script.
Step 1 Change directory to the $ECSP_HOME/bin directory and invoke the license.ctk script. Ensure the ECSP_HOME environment variable is set by sourcing the appropriate file described earlier after the installation process has completed. At the command line prompt specify:
host% cd $ECSP_HOME/bin
host% ./license.ctk
Step 2 The license.ctk script prompts you for the Cisco NSM software's serial number, an expiration date, and the Application key you were provided by Cisco Systems in response to the Request for Activation Key form(s) you returned. An Application key is a twenty digit, hexadecimal number (for example, A1B2 C3D4 E5F6 7890 1234).
Upon completion of the license.ctk script, the FLEXlm licensing software and files are in place. To use the Cisco NSM software, the lmgrd daemon (see the "Licensing Software Overview" section) must be running. When you start the Cisco NSM software via the ctk command, this daemon is automatically started, when it is not already running. To start this daemon manually, follow the instructions listed below for the appropriate Operating System.
Step 1 To invoke this daemon for the current session (without having to reboot), specify the following commands at the command line prompt:
host% cd $ECSP_HOME/resources/license
host% $ECSP_HOME/bin/solaris/lmgrd -c license.dat -l LOG
Step 2 To ensure the lmgrd daemon is started whenever the machine is rebooted, create the /etc/rc2.d/S99netsys file containing the following lines. <install_dir> is the absolute path of the directory where the Cisco NSM software was installed and <username> is a normal, non-privileged user.
ECSP_HOME=<install_dir>;export ECSP_HOME
cd $ECSP_HOME/resources/license
su <username> -c "umask 022; $ECSP_HOME/bin/solaris/lmgrd -c license.dat \
-l LOG"
Step 1 To invoke this daemon for the current session (without having to reboot), specify the following commands at the command line prompt:
host% cd $ECSP_HOME/resources/license
host% $ECSP_HOME/bin/hpux10/lmgrd -c license.dat -l LOG
Step 2 To ensure the lmgrd daemon is started whenever the machine is rebooted, create the /etc/rc.config.d/S99netsys file containing the following lines. <install_dir> is the absolute path of the directory where the Cisco NSM software was installed and <username> is a normal, non-privileged user.
ECSP_HOME=<install_dir>;export ECSP_HOME
cd $ECSP_HOME/resources/license
su <username> -c "umask 022; $ECSP_HOME/bin/hpux10/lmgrd -c license.dat \
-l LOG"
Step 1 To invoke this daemon for the current session (without having to reboot), specify the following commands at the command line prompt:
host% cd $ECSP_HOME/resources/license
host% $ECSP_HOME/bin/aix4/lmgrd -c license.dat -l LOG
Step 2 To ensure the lmgrd daemon is started whenever the machine is rebooted, add the following lines to your /etc/rc.tcpip file. <install_dir> is the absolute path of the directory where the Cisco NSM software was installed and <username> is a normal, non-privileged user.
ECSP_HOME=<install_dir>;export ECSP_HOME
cd $ECSP_HOME/resources/license
su <username> -c "umask 022; $ECSP_HOME/bin/aix4/lmgrd -c license.dat \
-l LOG"
To obtain the exact license version for the currently running Cisco NSM software, type the following at the command line prompt:
host% $ECSP_HOME/bin/version -licenseversion
An example of the output from this command is: "Licensing version: 4.0.1 (Internal v5.12.00)".
In the above example, the license version is 4.0.1. It is very important for you to obtain the exact license version and to provide it when obtaining your license, or the license keys you are subsequently provided, will not work.
FLEXlm also provides several useful utilities for checking the status of the licensing processes currently running.
Depending on the Operating System you are using, the utilities listed below are located in either the $ECSP_HOME/bin/solaris, $ECSP_HOME/bin/hpux10, or $ECSP_HOME/bin/aix4 directory.
This command allows you to monitor the status of network licensing activities. It shows which daemons are running and who is currently using a license. Invoke this command as follows:
host% lmstat -c $ECSP_HOME/resources/license/license.dat
This command allows you to diagnose problems during the license check-out process. When a failure occurred during license access, it provides the reason. It also displays extended connection diagnostics. Invoke this command as follows:
host% lmdiag -c $ECSP_HOME/resources/license/license.dat
This command allows you to shut down the lmgrd license daemon. You must shut down the lmgrd license daemon whenever you upgrade/install a new version of the Cisco NSM software. Invoke this command as follows:
host% lmdown -c $ECSP_HOME/resources/license/license.dat
Once you install the Cisco NSM software, you start the Netsys Service-Level Manager by specifying ctk at the command line prompt. For a complete list of the command line options, see Chapter 2 in the Netsys Connectivity Service Manager General Reference Guide.
When you invoke ctk without a valid license installed, the Cisco NSM software is started in Demo mode.
When you invoke ctk without the license manager daemon (lmgrd) running, the Cisco NSM software attempts to start this daemon for you.
Selecting Demo mode allows you to experiment with some of the functionality provided by the Cisco NSM software. Four demo networks are provided for this purpose.
The tutorial_baseline model contains thirteen router configuration files that are used as the basis for the tutorials provided in the Netsys Connectivity Service Manager User's Guide.
The perf.tutorial model (including pre-collected traffic data) contains router configuration files that are used as the basis for the tutorials provided in the Netsys Performance Service Manager User's Guide.
The demo_net model contains thirty seven router configuration files that make more extensive use of Cisco NSM software's functionality. The demo_net model uses the OSPF routing protocol, in addition to RIP and EIGRP. It also includes AppleTalk cable ranges, several Frame Relay links, Remote Source Route Bridging, and configuration file problems that demonstrate the increased range of integrity checks performed by the Cisco NSM software's Integrity Checks Report function.
The slm_and_vlan model showcases Service Level Manager and LAN switching aspects of the
4.x Cisco NSM software.
If you experience problems installing or using the Cisco NSM software or obtaining or installing the required license, please call Cisco Systems at 1-800-553-2447 or send email to tac@cisco.com.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
Posted: Mon Apr 12 17:23:16 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.