cc/td/doc/product/wanbu/9_1/nms
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Installing WAN Design Tools

Installing WAN Design Tools

This appendix provides instructions for installing the WAN Design Tools, the Network Modeling Tool (NMT), Configuration Extraction Tool (CET), Third-Party Interface (TPI) Conversion Plug-in, and SpreadSheet Interface (SSI) Conversion Plug-in. This appendix contains the following sections:


Note Check the Cisco WAN design Tools Release Notes for changes in the installation process.

System Requirements

NMT, CET, TPI, and SSI run on a Sun SPARC station running SunOS 4.1.4 , Solaris 2.5.1, or Solaris 2.6.1. NMT runs under many configurations, including SPARC IPX, LX, 5, 10, 20, and Ultra. Hardware requirements depend on the size of the model you are creating. A typical setup includes:

Installing the NMT

This section explains how to install the WAN Design Tools software and link it to your project directories. This procedure also installs any subapplications (CET, TPI, and SSI) that came with your copy of the NMT software. If you want to install only the subapplications, refer to the section "Installing the CET, TPI, or SSI Software" later in this chapter.

To run the NMT, you must first install the software (once for each release platform). Then, create an NMT working directory.

Load the NMT Software

The following procedure installs the software into a subdirectory under the NMT account you created. The installation process gives that subdirectory a name and a release number. For example, /usr/users/NMT/910.

Step 1 Log into the account that will own the NMT software. Go to the directory where the NMT releases are stored.

Step 2 Verify that you are in the correct directory by entering the following command:


Note This path with the release number is the path you will use when you create a working directory.

Step 3 If you are loading from a CD, see the release notes, or follow the instructions on the CD

If you are loading from a 3/4 tape, insert the tape and enter the following command:


<device> will be a UNIX device name, like dev/rst0


The last character is a 0 (rst0).


If you have a tar or compressed tar file, uncompress it if necessary, and then untar the file by entering the following command:


Step 4 Confirm that this step created a subdirectory in the NMT directory. The subdirectory has an NMT version number, for example, 910


Figure A-1: Example of NMT Directory Structure


Creating a Working Directory

This procedure is for the linking of the NMT software to working or project directories. Figure A-1 depicts the relationship between the NMT software, user, and project accounts. In the figure, a separate NMT account, is assumed to exist.

Step 1 If you are not already logged in, log in now.

Step 2 Create the working directory name:

mkdir project_name


You should periodically remove old files from the tmp directory


Step 3 Move to the subdirectory you just created:

Step 4 Make sure you are running in c shell. If you are not, enter the following command:

Step 5 Link the project directory to the NMT release. First, set the environment variable NMTHOME to the path of the release. For example:

setenvNMTHOME /usr/users/NMT/910.


Then execute the following command:


$NMTHOME/NMTLINK -a


The NMT files are linked or copied to the project_name directory. The -a option links other WAN Network Design Tools (Configuration Extraction Tool, Third Party Interface, and SpreadSheet Interface) to the project. If Cisco Strataview is not installed, you will see warnings from CET. If you do not specify -a, you will only link to NMT. You can later link SSI using SSI HOME and ssilink. Same for TPI and SSI


Start the NMT

This section describes how to run the NMT.

Step 1 If you are on a Cisco StrataView platform, while logged in as Cisco StrataView Plus and in the svplus directory, enter the following command to grant xwindows permission. (This can be done from the console window or an xterm window.)

You may want to add the xhost + command to the svplus.login file.


Step 2 Log in with your user name and enter your password. This should bring you to your user home directory, for example, /usr/users/my_name.

Step 3 Move to one of your project directories:

Step 4 Start NMT:

Installing the CET, TPI, or SSI Software

If you need to install or reinstall the Configuration Extraction Tool (CET), the Third Party Interface (TPI), or the SpreadSheet Interface (SSI), use this procedure. These applications are referred to as subapplications in this section.

The procedures in this section are for accessing, loading, and linking the applications to project directories.


Note You only need to do this if you did not use -a option with NMTlink.

Access a Directory

To install a WAN design tool subapplication, you must first go to or go to a working directory where you have run nmtlink..

Step 1 Set up a UNIX environment variable for CET, TPI, or SSI.

setenv [nmt_path]


nmt_path is the path to the version of the NMT software you are using.


Step 2 Link the project directory to the NMT release:

For CET: $CETHOME/cetlink


For TPI: $TPIHOME/tpilink


For SSI: $SSIHOME/ssilink


SSI PC Installation

To install SSI PC, do the following:

Step 1 Transfer the following files to your PC. Make sure you use binary mode:

Step 2 Copy the file SSI910 to your Excel 5.0 (or higher) installation. It can be either a Windows, Windows 95, or Macintosh environment.

Step 3 Copy the file to the xlstart subdirectory of the Excel product.

This Macro gives you the NMT_Load, NMT_Unload and NMT_PrettySheet commands.


Step 4 Copy tar.exe and SSIDOSKT.TAR to a DOS working directory.

Step 5 Enter the command 'tar xvf SSIDOSKT.TAR to un-archive the data.

Removing Applications

you can remove applications by running the following commands:

Troubleshoot NMT Installation

Symptom The command nmt fails, returns message:

xterm not found.

Probable Causes Unix is not configured for xterm.
Solution
Have a UNIX administrator provide xterm support for your account.

Symptom

Cannot write cnf files or reports.
Cannot update the map.

Probable Causes

No write permission.

Solution

Make sure your account has write permission to your working directory.

hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1998 © Cisco Systems Inc.