Table Of Contents
Using the Configuration Extraction Tool
Fields Addressed by CET
Using the CET
Other CET Commands
AIX Platform Support
Troubleshooting CET
Remote CET Extracts
Troubleshooting
Using the Configuration Extraction Tool
This chapter describes how to use the Configuration Extraction Tool (CET), which extracts data from the Informix database that the CWM uses. The CET then formats the data into a standard CNF file that the NMT can read. The CET works with CWM 9.2 or later and is included in the UNIX installation of the NMT.
For instructions on installing the CET, see "Installing the WAN Modeling Tools."
In this chapter, see these sections:
•
Fields Addressed by CET
•Using the CET
•Other CET Commands
•Troubleshooting CET
•Remote CET Extracts
Fields Addressed by CET
A configuration file generated by the CET consists of data extracted from your network. The source is the CWM Informix database. When that data is not available, the NMT default values are used. For descriptions of the fields that are extracted from the CWM data, see "Configuration Tables and Fields."
The CET provides the added functionality of translating all coded value fields in Informix into easy-to-use strings. For some fields, the CET checks second data sources if problems exist with the CWM collection process. For CWM 9.1 or earlier, the CET fills in some fields heuristically.
Using the CET
To extract data from CWM and generate an NMT-compatible CNF file, perform the following steps.
Step 1 For the best data consistency, make sure the network is not running any administration activities that add or delete network elements. Also, make sure you are in the correct working directory, and that the CET has been installed there.
Step 2 The svp2cet command extracts selected data from the SQL database and writes them in the subdirectory netw_name. If the command fails or generates warning messages, view the <ntwk-name>/svp2cet.con file for a log of SQL extraction.
To extract the configuration from CWM, enter this command:
svp2cet <netw_name> [options]
where,
•netw_name = Name of the directory that the command creates. The directory contains data files that are used as inputs for the command shown in the next step, which builds a .cnf file. You will use this directory name again in the next step.
•swt_rev = Switch software revision you are using. You may need to use this option only if the CWM release is more recent than the switch software release.
It may take a long time for the extraction process to run. There is no on-screen indication that the process is running. A message appears announcing when the process is complete or another message appears if the process fails. If the process fails, delete the netw_name directory before running the command again.
Step 3 Enter the following command to format the above extracted data into a .cnf file named netw_name.cnf, which you can read into NMT. If the command fails or generates warning messages, view the file netw-name/cet2nmt.con for a summary of the data analysis problems:
cet2nmt <The cet2nmt > [ options]
netw_name is the name of the directory you created.
The cet2nmt has an option to extract a single domain or several domains from the CWM DB. If your CWM is monitoring multiple AutoRoute networks, or multiple PNNI peer groups, you may extract a single or multiple domains using the -network option. The syntax is as follows:
cet2nmt <netw_name> -network <domain_name>
Multiple domain names can also be specified, as shown in the following example:
cet2nmt <netw_name> -network <domain_name1> [,<domain_name2>]...
The cet2nmt has an option to create the .cnf file with different then netw_name plan name. That option can be very usefull when user creates several plans with dufferent options. The syntax is as follows:
cet2nmt <netw_name> -o <myplan>
In this case the utility produces the myplan.cnf file.
Step 4 This step is optional.
If manual corrections are required on the output CNF file, you can make them once, and then automatically make them again with the 'adj2nmt' command. The command only updates fields that are missing from CWM or are not that reliable. The site names, and slot port information is used to match links and connections. Messages are generated for every change.
adj2nmt <in-file> <reference-file> <out-file> {[options]}
in-file is the most recent extraction file.
reference-file is the extraction with the manual changes applied
out-file in the input file with the same parameters changed on the output file.
Options:
•-add—Add links and connections that are in the reference file but missing from the input file.
•-diffrep—Write no output file, but generate a report about the differences of the two files.
Note The field update functionality and the topology compare functionality can now be called directly from the NMT menu under Files/Read 2nd CNF.
This process is illustrated in Figure 5-1.
Figure 5-1 CET Schematic Overview
Other CET Commands
There are several other CET commands that may help you more effectively use the software:
•svp_dmp. Use this command to if the CET generates a defective CNF file. This command should be run immediately after you run the svp2cet command. This command dumps the data from CWM tables into a series of DMP files. These files can be analyzed by your Cisco customer support representative. Enter this command as in the following example:
where nwt_name = Name of the network
•svp_rev—Use this command to find out the CWM revision level.
•swt_rev—Use this command to find out the software revision level of your switches.
•adj2nmt—Use this command to recreate manual changes on previous extractions to current extractions.
•sniffcnf< ntwk_name>—Use this command to obtain an on-screen summary of the network topology. This is useful for a high-level check that the data extraction was successful.
The following CET installation commands are not required to run unless the NMT was installed as a standalone:
•cetlink— Use this command to copy the necessary CET files to your project directory. You can invoke it by running the command $CETHOME/cetlink
•cetrel—Use this command to remove the CET software from your project directory.
To obtain help about any of the CET commands, enter the command followed by -h, such as cet2nmt -h.
AIX Platform Support
If you have the CWM installed on an AIX platform, run the svp2cet command on that platform and run the rest of the process on a support UNIX platform. Install the NMT on both the CWM AIX platform and a standard platform. After running the svp2cet command, copy the entire subdirectory with the plan name you entered to your working directory on the standard platform. Then, run the cet2nmt command to complete the extraction process.
To move the entire sub directory, use the UNIX tar command, then transfer the tar command in binary mode and untar it on the standard platform.
Troubleshooting CET
Occasionally, CET will execute successfully, but the resulting extract will be incomplete. If CET fails during the svp2cet command, look at the earliest error in the svp2cet.con file. The table below lists some common problems, and what to do about them.
Symptom
|
Links are missing
|
Probable causes
|
Incomplete data in SV+ database.
|
Solution
|
View the file named "maybe_links.sv." This file contains possible links based on incomplete data. If the missing links are in this file, add them to the "links.svp" file, and rerun cet2nmt.
|
Symptom
|
Connections are missing.
|
Probable causes
|
Incomplete data in SV+ database.
|
Solution
|
CWM 9.2 or later: View the files that begin with the word extra. These contain connection segments that are in the data base, but which were not collected because they were not part of an end-to-end connection.
SV+ 7.0 - SV+ 9.1: View the files maybe.voice.svp, maybe_data.svp, maybe_frame.svp, and maybe_atm.svp.
If you find the connections, try rerunning svp2cet and cet2nmt.
If this doesn't succeed, contact WAN Manager support.
|
Symptom
|
Informix Error 862 (cannot open file for run)
|
Probable causes
|
cetlink has not been run.
User is executing CET from a subdirectory
CET installation did not execute properly.
|
Solution
|
Make sure this directory contains cetbin:
if cetbin is not there, run cetlink
See if all required subdirectories and programs are in cetbin. If they are not there, you must reinstall CET.
|
Symptom
|
Informix Error 529 (Cannot attach to shared memory)
Informix Error 123 (ISAM error: No shared memory)
|
Probable causes
|
Informix DB is not on line.
|
Solution
|
Become the Superuser INFORMIX
Type cd
Type tbmonitor, or bin/tbmonitor
In tbmonitor, select mode. This will confirm that the database is off-line.
Select start-up. The database is brought from off-line to quiescent.
Select on-line. This brings the database on-line
Select exit to exit mode.
Select exit to exit tb monitor
Exit informix
|
Symptom
|
Informix Error 217 (Column [name of column] not found in any table in the query)
|
Probable causes
|
CWM release and the Informix Database are incompatible. In other words, a new sv+ has been installed, but is not in use
|
Solution
|
Use the swt_rev option on the svp2cet command.
|
Symptom
|
Informix Error 564 (cannot sort rows) and/or
Informix Error 407 (Error number 0 received from sql_exec process)
The above error(s) are also combined with a unix error: /:write failed, file system is full
|
Probable causes
|
There is not enough empty space in the /tmp partition, where informix does its sorting work
|
Solution
|
If there are files called textnnn.0, then space can be recovered by closing the shell tools.
If this still does not work, space can be cleared by copying info and files to other partitions (then erasing them from /tmp)
|
Symptom
|
Informix Error 229 (Cannot open or create a temporary file) and/or
Informix Error 162 (ISAM error: BLOB space does not exist)
|
Probable causes
|
The Informix database is full or almost full, or the temporary space directory is not writable or full
|
Solution
|
Check that the directory defined by the DBTEMP environment variable is writable by this account. If DBTEMP is not defined, check the /tmp directory. The problem could also be that there is no more free disk space in the temporary directory.
If you have error 162, have TAC increase the user's Informix database size.
|
Symptom
|
REXX Error 48: Failure in System Service
|
Probable causes
|
Not enough memory available. This usually refers to swap-space. (To see how much swap space is available, use the pstat -s or swap -s command. To see how much memory is available, use the dmesg | grep avail mem command
|
Solution
|
Close all other applications that use a lot of memory, such as Sun's file manager or Netscape.
|
Symptom
|
REXX Error 41: Bad Arithmetic Conversion
|
Probable causes
|
The input data contained a blank rather than a digit.
|
Solution
|
No workaround. Contact Network Modeling for help.
|
Symptom
|
The following error message is displayed:
DB not found.
Console file from the svp2cet command shows some queries and then SQL error 802.
|
Probable causes
|
The CWM is a newer version than the NMT and has tables or fields that the NMT does not recognize.
|
Solution
|
Upgrade the NMT to a later version that supports that CWM version.
|
Symptom
|
The cet2nmt command displays the following error:
REXX: Service not available
|
Probable causes
|
The command ran out of memory.
|
Solution
|
Reconfigure your system to use more swap space on disk.
|
Symptom
|
The %UTIL values extracted are bad.
|
Probable causes
|
You are using CWM 9.2.09 and do not have patch 10 applied.
|
Solution
|
Apply patch 10 to CWM.
|
Symptom
|
The CET installation says that CWM is not installed, and you know that it is installed.
|
Probable causes
|
The NMT version is too old for the CWM version, or the CWM is installed in a non standard way with a different database name.
|
Solution
|
Upgrade NMT to a later version that supports that version of CWM.
|
Remote CET Extracts
If you wish to obtain a CET extract from a CWM or SV+ Informix database located on another workstation, you may not need to install NMT or CET on the remote platform. You may be able to issue the svp2cet command on your workstation and return the data from the remote platform to your workstation.
A remote CET extract is possible only in the following circumstances:
•You must know the hostname of the remote host. You may need to know the IP address of the remote host.
•Your local host workstation must be able to access the remote host. That is, you must be able to successfully ping the remote host, either by hostname or by IP address, from your local host.
•Informix 7.2 or later must be installed on both your local host and the remote host. (If the CWM is installed on either host, you have met the requirement for that host.
•You must know the password to the svplus user ID at the remote host.
You cannot obtain a remote CET extract from a PC.
To configure the workstations for remote data extraction, follow these steps:
Step 1 Set the environment variable INFORMIXSERVER to the hostname of the remote host. That is, issue the following Unix command: setenv INFORMIXSERVER <remotehostname>
Step 2 Setup your local host with an Informix sqlhosts entry for the remote host.
a. Edit your /usr/users/informix72/etc/sqlhosts file.
b. Add a new entry of the following form (filling in the blanks): <remotehostname> ontlitcp <remotehostaddr> informix_istar
where remotehostaddr = IP address of the remote host; but, if you can ping the remote host by name, you can alternatively use the hostname of the remote host. Whichever you choose, use the same remotehostaddr in the two steps below.
Step 3 Setup your local host for "friendly" ftp access to the remote host's svplus userid.
a. Edit (or create) the .netrc file in your home directory.
b. Add a new entry of the following form (filling in the blanks): machine <remotehostaddr> login svplus password <password>.
<password> is the password to the svplus account at the remote host. Therefore, your .netrc file should not allow others to read it. You can use the Unix command, chmod 600 ~/.netrc
Step 4 Setup the svplus userid on the remote host to allow remote shell access from your local host:
a. Remotely log on to the remote host as user svplus:
rlogin <remotehostaddr> -l svplus
b. Edit (or create) the .rhosts file in the svplus home directory.
c. Add a new entry of the following form:
<localhostname> <yourlocaluserID>
<localhostname> must be the official name of your host, not one of its nicknames. If you do not know it, execute the command, "who am i", after you have logged on to the remote host. Your official host name will appear within parentheses ().
To check whether your setup is correct, run the svp-rev and swt-rev commands. If both commands work correctly, your setup is correct.
Troubleshooting
Symptom
|
A command returns Informix error 23101:
Unable to load locale categories.
|
Probable causes
|
The INFORMIXDIR environment variable is not set correctly
|
Solution
|
Either issue the command, unsetenv INFORMIXDIR, or the command, setenv INFORMIXDIR /usr/users/informix.
|
Symptom
|
A command returns Informix error 930:
Cannot connect to database server <remotehostname>
|
Probable causes
|
Either Informix is not installed on the remote host, or the INFORMIXSERVER environment variable has been set incorrectly.
|
Solution
|
If Informix is installed, perform Step 1 of the setup procedure.
|
Symptom
|
A command returns Informix error 25596:
The INFORMIXSERVER value is not listed in the sqlhosts file or the Registry.
|
Probable causes
|
Informix sqlhosts file has not been updated.
|
Solution
|
Perform Step 2 in the setup procedure.
|
Symptom
|
A command returns Informix error 951:
Incorrect password or user <yourlocaluserID> is not known on the database server.
|
Probable causes
|
The local host doesn't have "friendly" access to the remote host.
|
Solution
|
Perform Step 2 of the setup procedure, making sure that the <remotehostaddr> used is the same as that used in the sqlhosts file of Step 3 the setup procedure.
|
Symptom
|
A command returns the message:
Cisco Wan Manager (StrataView Plus) on host <hostname> is either not installed or not accessible
|
Probable causes
|
The remote host does not allow remote shell access.
|
Solution
|
Perform Step 4 the setup procedure.
|
Symptom
|
Command returns Informix error 908
|
Probable causes
|
The remote CWM site is not up and running.
|
Solution
|
Verify the remote CWM site is running and can be pinged from your site.
|
Feedback
