|
|
This chapter describes how to use the Third-Party Interface (TPI) Conversion Plug-in, and contains the following sections:
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.
Before using TPI, make sure that it is set up in a directory that has an NMT environment. For more information, see the section "Link the Application to the Project Directory" in the appendix "Installing WAN Design Tools."
This section describes how to translate between NMT and WANDL network design formats on your Sun workstation.
Take the following steps to set up a project directory:
Step 1 On a platform that has both the NMT and WANDL installed, and from a directory you have write access to, create a project directory:
mkdir project_name
Step 2 Change to that directory.
cd project_name
Step 3 Link the current version of NMT to your project directory. Use the -a option to link all other NMT subprograms, including TPI, if you wish, and skip step 5.
~NMT/nmt_ver/nmtlink -a
nmt_ver is the NMT release number expressed without periods--for example 840.
If NMT has not been installed under an NMT account, use the $NMTHOME environment variable (see the appendix "Installing WAN Design Tools").
/nmt_ver/tpilink
Step 4 Start the NMT to confirm that it is properly linked to your working directory.
./nmt
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]
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.
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]
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 494 HQ Cupertino 408 777 CUP Atlanta 404 850 ATL Chesterfield 314 537 CHES Frankfurt 999 999 FRNK DE Tokyo 999 999 TOKYO JP Fleet 999 999 FLEET UK Rotterdam 999 999 RTRDM NL Milano 999 999 MILAN Col_Polanco 999 999 MEX Queensland 999 999 QUEEN AU No_Sydney 999 999 SYDNEY Seoul 999 999 SEOUL Hong_Kong 999 999 HK Ottawa 999 999 OTT Paris 999 999 PARIS
|
|