Configuration Extraction Tool

This chapter describes how to use the Configuration Extraction Tool (CET) and contains the following sections:

• Fields Addressed by CET

• Using the CET

• Other CET Commands

The CET extracts data from a StrataView Plus Informix database and formats the data into a standard .cnf file that can be read by the NMT. CET works with all StrataView Plus releases numbered 7.0 or greater. For instructions on installing the CET, see the appendix "Installing WAN Design Tools."

Fields Addressed by CET

A configuration file generated by the CET consists of data extracted from your network and, where that data is not available, NMT default values. 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 fields supported by the CET.

Table  5-1: Configuration Fields Revised by the CET

Table	Field Revised by CET	Data based on	Notes
Sites	Site	Actual node name
	Type	Actual node type	IGX not recognized until Release 8.2.
	Size	Largest slot found for IGX and IPX	Derived heuristically.
	Fdr	Actual data	Flagged if tiered network IGX or IPX. Only applicable after Release 8.0.
	HEP	Actual processor card type	Default value used until switch Release 8.4.
	Domain	Actual domain number
	JN	Not used by NMT	Flagged if you are using Structured Network Junction Node.
Links	Site 1, Site 2	Actual node name
	Hub 1 ID, Hub 2 ID	Actual slot, port, and virtual trunk (if any) identifier
	Type	Actual interface type	Y1 trunks shown as T1, and T2 trunks shown as T3. Until switch Release 8.4, broadband trunks were determined heuristically, based on port speed and card type.
	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 and tiered network feeders.
	Receive rate	Actual receive rates
Voice	Site 1, Site 2	Actual node name	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	Connection bandwidth requirements	Derived heuristically. T connections shown as P; FastPAD CELP8 and CELP48 conns shown as ATC16.
	Bc	Actual back card; number of lines based on actual front card	Until switch Release 8.4, field was determined heuristically, based on the observed ports used.
	Fdr 1 ID, Fdr 2 ID	Actual slot port on feeder node	Cisco 3800 feeders are not supported.
	Site B - I	Actual preferred route, if any	Available starting with switch Release 7.2.
Data	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 8.4.
	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 8.4.
	Fdr 1 ID, Fdr 2 ID	Actual slot, port or feeder node	Cisco 3800 feeders not supported.
	Site B --- I	Actual preferred route, if any	Not available until switch Release 7.2.
Bursty	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 (both ends)	Actual minimum information rate or minimum call rate
	PIR (both ends)	Actual peak information rate or peak call rate
	BC	Actual back card; number of lines based on front card	MM back cards are shown as SM; number of lines on BRM back card is determined heuristically based on ports used and port speeds. Until switch Release 8.4, heuristic was based on ports used, connection type, and port speeds.
	Fdr 1 ID, Fdr 2 ID	Actual slot, port identifiers on the feeder node	FastPAD and Cisco 3800 feeders not supported
	Fdr BC	Actual back card	Only AXIS 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.
	DLCI or VPI	Actual DLCI or VPI	Not used by NMT.
	VCI	Actual VCI	Not used by NMT.
	Index	Actual SV+ connection index	Not used by NMT.
	Site B---I	Actual preferred route, if any	Not available until switch Release 7.2.
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	Cisco 3800 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	Cisco 3800 not supported.
	Type	Actual feeder type	Cisco 3800 not supported. Cage size uses the default.
	Speed	Actual clock speed of the port to which the feeder is connected

Using the CET

The following procedure explains how to extract data from StrataView Plus and generate an NMT-compatible .cnf file. The process is illustrated in Figure 5-1.

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.

---

Note If you run StrataView Plus on the IBM AIX platform (which is not supported by NMT), you can still run the command svp2cet. You then need to tar the network directory, move it to your NMT platform, and untar it before running the cet2nmt command.

---

Figure 5-1: CET Schematic Overview

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 StrataView Plus, 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 have to use this option if the StrataView Plus release is more recent than the switch software release.

swt_rev is the StrataView Plus switch revision you are using. Do not use this option unless you are using an NMT release that is more recent than the switch software release. On rare occasions, this may be the case during demonstrations and labs.

---

Note 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 ntwk_name directory before running the command gain.

---

Step 3 The following command reads the extracted files and writes a .cnf file in your working directory. If the command fails or generates warning messages, view the file ntwk-name/cet2nmt.con for a summary of the data analysis problems.

Enter the following command to format the above extracted data into a .cnf file named ntwk_name.cnf, which you can read into NMT:

cet2nmt netw_name [nmt_ver]

netw_name is the name of the directory created in the previous step.

nmt_ver is the NMT release you are using. If you are using the latest NMT release, you do not have to enter it.

Other CET Commands

There are several other CET commands that may help you more effectively use the software:

• cetlink. This command copies the necessary CET files to your project directory. You can invoke it by running the command $CETHOME/cetlink or the command

~NMT/nmt_ver/cetlink

nmt_ver is the NMT release you are using.

• cetrel. This command removes the CET software from your project directory.

• svp_dmp. If the CET generates a defective .cnf file, run this command. This command should be run immediately after you run the svp2cet command. This command dumps the data from StrataView Plus tables into a series of .dmp files. These files can be analyzed by your Cisco customer support representative.

To use the command, enter the following command:

svp_dmp netw_name

nwt_name is the name of the network.

• svp_rev. Use this command to find out the Strataview Plus revision level.

• swt_rev. Use this command to find out the software revision level of your switches.

• sniffcnf ntwk_name gives an on-screen summary of the network topology. This is useful for a high-level check that the data extraction was successful.

To obtain help about any of the CET commands, enter the command followed by -h, for example, cet2hmt -h.