|
|
This chapter describes how to use the Configuration Extraction Tool (CET) and contains the following sections:
The CET extracts data from the Informix database used by the Cisco Wan Manager (CWM), formerly called StrataView Plus.(SV+). The CET then formats the data into a standard .cnf file that can be read by the NMT. CET works with all Cisco Wan Manager releases numbered 9.2 and all SV+ releases numbered 7.0 or greater. For instructions on installing the CET, see the appendix "Installing WAN Design Tools."
The current CET release includes a number of enhancements:
A configuration file generated by the CET consists of data extracted from your network. Where that data is not available, NMT default values are used. Table 5-1 lists the tables and fields that are based on data extracted by the CET. For a complete description of configuration fields, see the appendix, "Configuration Tables and Fields." This appendix also lists the fields supported by the CET.
| Table | Field | Data based on | Notes |
|---|---|---|---|
Sites | Site | Actual node name |
|
|
|
|
|
| NodeType | Actual node type | IGX not recognized until Release 8.2. |
| SwRel | Actual data. | Software release of the switch(es) at this site.. If blank, then use the global value defined in the Model Settings. |
| Fdr | Actual data | Flagged if tiered network IGX or IPX. Only applicable after Release 8.0. |
| PC | Actual processor card. | Default value used until switch Release 9.1. |
| Domain | Actual domain number or name | Beginning with Cisco Wan Manager 9.0, CWM network name is used. Prior to 9.0, network ID is used. |
| JN | Not used by NMT | Flagged if you are using Structured Network Junction Node. |
| IGX | Derived from actual data. | Not available until switch release 8.1. |
| TF | Derived from actual data. | Not available until switch release 8.1. |
| Map V, Map H | Actual CWM or SV+ map coordinates, if any. | Only available if CWM or SV+ map has been configured. |
Links | Site 1, Site 2 | Actual node name |
|
| Hub 1 ID, Hub 2 ID | Actual slot, port, and virtual trunk (if any) identifier |
|
| Trunk type | Actual interface type | Y1 trunks shown as T1, and T2 trunks shown as T3. Until switch release 9.1, broadband trunks were determined heuristically, based on port speed and card type. |
| Trunk capacity | Line load calculation for narrowband trunks; Interface type for broadband trunks, in which case capacity is fixed |
|
| Trunk card | Actual card type |
|
| VT Rate | Actual rate |
|
| Keep | Count of links with the given characteristics | Since slot, port are included, this field is always set to 1. |
| Reserve | Actual statistical reserve | Defaults applied to links between BPX switches and tiered network feeders. |
| Receive rate | Actual receive rates |
|
| Comment | Actual user comment, if any. | Not available until sv+ release 9.0. |
Voice Traffic |
|
| Cisco 3810 feeder voice traffic not supported.. |
| Hub 1 ID, Hub 2 ID | Actual slot, port identifier |
|
| Qty | Count of identical connections | Since slot and port are included, this field is always set to 1. |
| Type | Connection bandwidth requirements | Derived heuristically prior to switch release 8.5. T connections shown as P; FastPAD CELP8 and CELP48 conns shown as ATC16. |
| COS | Actual class of service | Defaults used prior to switch release 8.5. |
| % utilization | Actual percent utilization | Defaults used prior to switch release 8.5. |
| Bc | Actual back card; number of lines based on actual front card | Until switch release 9.1, field was determined heuristically, based on the observed ports used. |
| Fdr 1 ID, Fdr 2 ID | Actual slot port on feeder node | Cisco 3810 feeders are not supported. |
| Preferred Route, Actual Route | Actual current route and preferred route, if any. | Available starting with switch release 7.2. Specific Trunk not available until switch release 8.4. |
| Comment | Actual user comment | Not available prior to switch release 7.2, nor for SV+ release 8.4. |
Data Traffic |
|
| Cisco 3810 feeder data traffic not supported. |
| Site 1, Site 2 | Actual node names | Master node unavailable until release 8.1, assumed to be Site 1. |
| Hub 1 ID, Hub 2 ID | Actual slot, port identifier |
|
| Qty | Count of identical connections | Since slot and port are included, this field is always set to 1. |
| Type | Connections bandwidth requirements | Derived heuristically. Modifier F not available until Release 8.1; nx64, nx56 shown as the resulting product starting with switch release 9.1. |
| COS | Actual class of service | Defaults used prior to switch release 8.5. |
| % utilization | Actual percent utilization | Defaults used prior to switch release 8.5. |
| Cd | Actual encoding format | Defaults used until switch release 7.2. |
| DFM | Actual connection requirement | Default used until switch release 7.2. |
| Bc | Actual back card; number of lines based on actual front card | Heuristic, based on observed number of ports used until switch release 9.1. |
| Fdr 1 ID, Fdr 2 ID | Actual slot, port or feeder node | Cisco 3810 feeders not supported. |
| Preferred Route, Actual Route | Actual current route and preferred route, if any. | Available starting with switch release 7.2. Specific Trunk not available until switch release 8.4. |
| Comment | Actual user comment | Not available prior to switch release 7.2, nor for SV+ release 8.4. |
Bursty Traffic |
|
| MC3810 and FastPad not supported. ATM traffic on ALM card not supported. |
| Site 1, Site 2 | Actual node name | Master node unavailable until 8.1; assumed to be Site 1 |
| Hub 1 ID, Hub 2 ID | Actual slot, port identifiers |
|
| Qty | Actual quantity of identical connections | Since slot, port, dlci (a VP1, VC1) are included, quantity is always set at 1. |
| Type | Actual connection type | Until switch release 8.2, heuristic analysis determined whether ATM connections were ABR, CBR, or VBR. |
| MIR (MCR) both ends | Actual minimum information rate or minimum call rate |
|
| PIR (PCR) both ends | Actual peak information rate or peak call rate |
|
| BackCard | Actual back card; number of lines based on front card | SL back cards are shown as SM; number of lines on FRM back card is determined heuristically based on ports used and port speeds. Until switch release 9.1, heuristic was based on ports used, connection type, and port speeds. |
| FrontCard | Actual front card. | Only filled in for FRSM-HS cards. |
| Fdr 1 ID, Fdr 2 ID | Actual slot, port identifiers on the feeder node | FastPAD and Cisco 3810 feeders not supported |
| Fdr BC | Actual back card | Only MGX 8220 feeders supported |
| % Utilization (both ends) | Actual percent utilization |
|
| Ad | Actual connection restrictions | Defaults used until switch release 8.1 (8.2 for ATM). |
| COS | Actual class of service | Defaults used until switch release 8.1 (8.2 for ATM) |
| CMAX (both ends) | Actual Cmax values |
|
| QIR | Actual quiescent information rate | Not used by NMT. |
| CIR | Actual committed information rate | Not used by NMT. |
| Endpoint Address | Actual DLCI or VPI.VCI of conn ends. | Not used by NMT. |
| Routing Address | Actual VPI.VCI of routing segment. | Not used by NMT. |
| Index | Actual SV+ connection index | Not used by NMT. |
| Preferred Route, Actual Route | Actual current route and preferred route, if any | Not available until switch release 7.2. Specific Trunk not available until switch release 8.1. Current route not available for SV+ release 8.1 or 8.2. |
| Comment | Actual user comment | Not available prior to switch release 7.2, nor for SV+ release 8.4. |
Access Ports | Site | Actual node name |
|
| Hub ID | Actual slot and port at the hub node |
|
| Feeder ID | Actual slot and port at the feeder |
|
| Speed | Actual port speed | MC3810 and FastPAD not supported. |
Feeders | Site | Actual hub node name |
|
| Hub ID | Actual hub slot and port to which the feeder is connected |
|
| Name | Actual feeder node name | MC3810 not supported until switch release 9.1. |
| Type | Actual feeder type | MC3810 not supported until switch release 9.1. |
| Speed | Actual clock speed of the port to which the feeder is connected | MC3810 not supported until switch release 9.1. |
The following procedure explains how to extract data from Cisco Wan Manager and generate an NMT-compatible .cnf file. The process is illustrated in Figure 5-1.
CET Schematic Overview
Take the following steps to run the CET:
Step 1 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 flat files from the SQL database and writes them in the sub-directory ntwk_name. If the command fails or generates warning messages, view the file ntwk-name/svp2cet.con for a log of SQL extraction.
To extract the configuration from Cisco Wan Manager, enter the following command:
svp2cet <netw_name> [<swt_rev>]
netw_name is the 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 is the switch software revision you are using. You may need to use this option only if the Cisco Wan Manager release is more recent than the switch software release.
Step 3 Enter the following command to format the above extracted data into a .cnf file named ntwk_name.cnf, which you can read into NMT. If the command fails or generates warning messages, view the file ntwk-name/cet2nmt.con for a summary of the data analysis problems:
cet2nmt <netw_name> {<nmt-ver>}
netw_name is the name of the directory you created.
nmt_ver identifies the NMT release you are using. Normally you should not need to use this option, since you will be using the current NMT release.
There are several other CET commands that may help you more effectively use the software:
To obtain help about any of the CET commands, enter the command followed by -h, for example, cet2hmt -h.
Occasionally, CET will execute successfully, but the resulting extract will be incomplete. The table below lists some common CET extraction problems and what can be done 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: 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.
|
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 | Informix Error 82 (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: ls-1 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 |
| ||||||||||||||||||
Symptom | Informix Error 217 (Column [name of column] not found in any table in the query) | ||||||||||||||||||
Probable Causes | Cisco Wan Manager 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 doesn't 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. /tmp is not writable. | ||||||||||||||||||
Solution | Check that /tmp is writable. Enter the ls-ld/tmp command. If the output begins with drw-rw-rw, you can write to /tmp, and the problem is with the database. With the help of the TAC, get the user's Informix database size increased. |
If CET fails during the cet2nmt command, look at the end of the cet2nmt.con file. The table below lists common problems and what to do about them.
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 | Contact Network Modeling for help. |
Posted: Fri Dec 3 18:36:44 PST 1999
Copyright 1989-1999©Cisco Systems Inc.