Third-Party Interface

This chapter describes how to use the Third-Party Interface (TPI) Conversion Plug-in, and contains the following sections:

• Translating Between NMT and WANDL Formats

• Special Location Files

TPI translates NMT .cnf files to and from WANDL files. Figure 6-1 provides a high-level illustration of this process. If the design begins in NMT, all parameter values are preserved during the return from the WANDL design. If the design begins in WANDL, the tpi2nmt command assumes defaults and NMT catches unsupported settings. For information on the fields translated by TPI, refer to the appendix "Configuration Tables and Fields."

The WANDL design tool bbdsgn can further optimize the network transmission requirements and costs. For more information on WANDL design tools, contact customer service.

Translating Between NMT and WANDL Formats

This section describes how to translate between NMT and WANDL network design formats on your Sun workstation.

Figure 6-1: TPI Schematic Overview

Converting NMT Configuration Files into WANDL Files

This procedure explains how to convert NMT configuration (.cnf) files into files that can be read by WANDL software.

Step 1 Start the NMT and verify that you have a readable configuration file.

Step 2 Run the TPI command that creates a directory that holds a set of WANDL network design files and specify the extension for these files:

nmt2tpi infile [-NT][-NA][-NIMA][-NIM][-id input_dir]-il loc_filename[-of
WANDL_ext_name][-D][-H]


• infile is the name of any .cnf file in the current directory. This name is used as the name of the destination directory for the files extracted from the .cnf file.These files are readable by the WANDL bbdsgn program.

• -NT--The program should not preserve the NMT parameters.

• -NA--The link avoid media field in the .cnf file will not be translated into WANDL link avoid specifications.

• -NIMA--The version of WANDL you are using does not support IMATM trunks. This option converts all such trunks to T1/E1.

• -NIM--The program should not display informational messages, only warnings, error, and those messages that may require user action.

• -id input_dir --Specify a different directory than the current directory as the source of the .cnf file.

• -il loc_filename--Specify a specific filename for an .loc file.

• -of WANDL_ext_name--Specify a specific WANDL file extension plan name.

• -D--Display steps and debugging information.

• -H--Display help.

Step 3 You can start the WANDL design session with the nmt2tpi output files by using the following commands:

cd dir_name

bbdsgn spec.extension

dir_name is the name of the .cnf file specified in the previous step.

spec.extension is the WANDL specification file, specifying a set of files to be run together.

Converting WANDL Files into NMT .cnf Files

This procedure is for the conversion of WANDL files into files that can be read by the NMT. This procedure processes files specified in the WANDL specification file.

Step 1 Return to the parent directory.

cd ..

Step 2 Convert the WANDL files into an NMT .cnf format by entering

tpi2nmt WANDL_directory [-BPXT3 card][-NA][-NIM][-od output_directory]
[-if cnf][-of cnf][-D][-H]


• WANDL_directory-- The name of the directory containing the WANDL data files (as well as the extension used by the WANDL data files, typically the network name). This name is assigned to the output .cnf file and .loc file. The .loc file has system coordinates. For more information on .loc files, see the section "Special Location Files" later in this chapter.

• -BPXT3 card --The BPX card should provide for T3 links. Choices are BXM (default) and BNI. This setting applies only to links not created by NMT. NMT value will override this option.

• NOUXM - New links will not use the uxm card

• -NA--The program should not translate link avoid information.

• -NIM--The program should not display informational messages, only warnings, errors, and those messages that may require user action.

• -od output_directory --Specify a directory different from the default as the destination of the .cnf file.

• -if cnf --Specify a specific WANDL file extension name for input.

• -of cnf --Specify a specific name for the .cnf output.

• -D--Display steps and debugging information.

• -H--Display help.

Special Location Files

When converting files for use in WANDL, you may wish to create files from which WANDL can derive site locations.

An .loc file contains geographic location information. For sites within the United States you can specify the location by entering the NPA and NXX of the multiplexer site. (The NPA is the area code, and the NXX is the exchange prefix within the US.) For sites outside the US, you should set NPA and NXX to 999.

To create an .loc file, create a text file Each entry should appear in the following order: NMT site name, area code, exchange prefix, WANDL location name, and country. The completed file should resemble this:

San_Jose 408 49HQ	SA	163241N	113233E	419237	48492
Cupertino 408 777 CUP	SA	19241N	344762E	234761	23476
San_Jose 408 49HQ	SA	173581N	278723E	411235	11923
Atlanta 404 850 ATL	SA	163341N	132121E	321437	48492
Chesterfield 314 537 CHES	SA	169941N	444433E	419232	23476
Frankfurt 999 999 FRNK DE	SA	159419N	313243E	222562	48492
Tokyo 999 999 TOKYO JP	SA	122241N	154323E	419217	11923
Fleet 999 999 FLEET UK	SA	164651N	254333E	119237	48492
Rotterdam 999 999 RTRDM NL	SA	154341N	214563E	222562	23476
Milano 999 999 MILAN	SA	177741N	313989E	119237	48492
Col_Polanco 999 999 MEX	SA	153341N	313443E	419237	18322
Queensland 999 999 QUEEN AU	SA	178241N	413533E	519237	48492
No_Sydney 999 999 SYDNEY	SA	163241N	113433E	219237	119237
Seoul 999 999 SEOUL	SA	163241N	213343E	483927	48492
Hong_Kong 999 999 HK	SA	163241N	113233E	129372	26731
Ottawa 999 999 OTT	SA	161241N	113653E	267318	48492
Paris 999 999 PARIS	SA	154241N	314233E	212562	11923

The map2tpi command creates and updates teh Loc files with the map locations in config/node.config.

The tpi2map commmandloads the Loc V&H or map locations back into confignode.config.