scripts files _ types

Script Files

When you upgrade the U2000, you can upgrade the configuration data with zero data loss by importing and exporting the scripts. Script files that contain the basic data are required for importing and exporting scripts.

Script File Type

Table 1 lists the types of the script files in the .txt format that the U2000 provides and the contents of the data.

Table 1 Script files the U2000 provides

Script File Type Naming Rule Contained Data Whether the Import or Export Feature Is Supported

Network-wide Configuration File None This file is a script set, including all the information in NE Configuration File, NE Port Naming File, NE List File and Network Layer Information File in case of importing/exporting. Before exporting, the networkwide data should be configured, including:

� Fiber connection: Includes the source/sink port, name and additional information of the fiber.

� Protection subnet: Includes basic attributes of the protection subnet, the NE and link information.

� Trail: Includes the basic attributes of the trail, additional information, the source/sink port and the physical route, and supports exporting of VC12, VC3, VC4 and VC4 service circuit.

� Wavelength: Includes the basic attributes of the wavelength, additional information, the source/sink port, and the physical route.

This file can be imported and exported.

NE Port Naming File NEPort_extension ID-basic ID_NE name_coding format.txt,such of NEPort_9-1_NE1.txt

This file contains the naming information about every port on the NE.


NE Configuration File NEData_extension ID-basic ID_NE name_coding format.txt,for example, nedata_9-1_NE1.txt

This file contains the configuration information that is similar to the command lines. This configuration script contains all data needed when NE can run normally as follows:

� NE attributes: including attributes, NE user and password, NE communication settings, its subnet, coordinate in view and DCN attributes

� Installation slots: including slot position and board type.

� Protection relation: including protection groups and their protection relation.

� Service configuration: including SDH traffic (including binding traffic) and SNC traffic.

� Clock configuration: including clock priority table, invalid condition of clock source, 2M phase-locked clock source, clock subnet, restoration conditions of clock source, SSM output conditions and clock source level.

� Overhead configuration: including public overhead, advanced overhead, auxiliary overhead, conference call, F1 data port pass-through, broadcast data port, communication port, data port, ring-out route and number of subnet connected with optical port.

� Environment controlling: including PMU settings, EMU settings, and CAU settings.

� Board configuration: including SDH interface, PDH interface, WDM interface, ATM interface and optical amplification board interface.

� Traffic configuration: including TDA traffic, TDA feed selection and TDA clock source settings.

� Equipment protection: including 1+1 protection, 1:N equipment protection, OLP channel protection, WDM channel protection, wavelength protection group and 1:N channel protection.

� Equipment maintenance: including fan settings and board temperature threshold.

� Board information: including slot number, type, BIOS version, board software version, FPGA version, Flash version. Board information only supports exporting.


NE List File NWNeList_U2000 name_coding format.txt This file contains information about NEs, U2000, and their physical location. When the NE list file is imported or exported, the NE port naming file and the NE configuration file are imported or exported in sequence according to the NE list file.


of 3Script Files

In addition, the U2000 provides the script files in the .xml format for the network planning and design, containing the network-wide configuration file, NE configuration file, network layer information file, and ASON information file. The ASON information file can be imported and exported, but other types of script files in the .xml format can be exported only.

NOTE:

� The default coding format in a script file is UTF-8. To change the coding format of the script file, you can change encoding configuration item in the installation path of the NMS/server/cbb/trans/core/conf/xml/script/script_enum.xml configuration file.

� By default, the name of a script file contains the NE name. To exclude the NE name from a script file name, you can change the scriptname configuration item in the installation path of the NMS/server/cbb/trans/core/conf/xml/script/script_enum.xml configuration file.

Main Usage

The main usage of the script files is as follows:

� Realizing the upgrade of the configuration data with zero loss during the U2000 upgrade. This is an important method for the U2000 upgrade. This is the main usage of the script files.

� After the network data is modified, restoring the customized information of the U2000, such as the trail name, fiber name, port name and the customer information.

� By modifying the script files, realizing the division and combination of the U2000 data and realizing the import of the desired data only, such as the NE list (with no configuration data), fiber connection, protection subnet, or trail.

� Supporting the simplified implementation of the project design.

NM Computer Information File NMInfo_U2000 name_coding format.txt This file contains the configuration information about the U2000 server. The configuration information is as follows:

� Hardware information such as the operating system name and its version, operating system patch version, physical memory, CPU count and frequency

� Network information such as the host name and IP address

� Database information such as the database name and its version

This file can be exported but cannot be imported.

NOTE:

It can be used to import third-party software such as MDS.

Service Actualization Script NWSvcData_U2000 name_coding format.txt

This file provides service actualization data scripts for the transport service actualization system. The service actualization data scripts are as follows:

� NE attributes � Board installation � Board protection � Protection relationship � Service configuration � Protection subnets � Trail configuration


Network Layer Information File NWCfg_U2000 name_coding format.txt This file contains information on the network layer configuration, including the following:

� Fiber cable connections � Protection subnets � Trail configuration


Network Modeling and Design Information File

None It is an interactive file for MDS, where the ASON information is added on the basis of the Networkwide Configuration File, including: It starts to support exporting of Network Modeling and Design Information File from T2000 V200R003C01, and does not support the importing function. The exported content is Networkwide Configuration Information + ASON Node Route Calculation Policy + ASON Node Resource Reservation (importing it to the NWMDCfg.txt file). It starts to support importing of Network Modeling and Design Information File from T2000 V200R005C01. The exported content is Networkwide Configuration Information + ASON Node Route Calculation Policy + ASON Node Resource Reservation + ASON Service Group Information (importing it to the NWMDCfg.txt file).To be compatible with the earlier version and reserve the NWMDCfg.txt file, the actual content should be consistent with that in the NWCfg_NM Name.txt.


CEAS NEData_extension ID-basic ID_NE name_coding format.txt,for example, nedata_9-1_NE1.txt

This file provides scripts for the operation that is performed on multiple NEs in batches.


Network Basic Configuration Information File

None The network basic configuration information file is the whole set of the following script files. When the network basic configuration information file is exported, the network layer information file does not contain network-layer path information, NE port naming file, NE configuration file, NE list file, and NM computer information file are exported. When the network basic configuration information file is imported, the NE configuration file and the NE port naming file are imported in sequence according to the NEs contained in the NE list file. The network layer information file is also imported.


of 3Script Files

Compatibility

� The scripts exported from the U2000 of an earlier version can be imported to the U2000 of a later version. But an error may occur if the scripts exported from the U2000 of a later version is imported to the U2000 of an earlier version. The U2000 of an earlier version does not support the features and functions that are added and the parameters that are modified in the U2000 of a later version. After the scripts are imported, an error message is displayed. But this does not affect the import of other information.

� The scripts generated on Windows and on UNIX are compatible.

� T2000 scripts can be imported to the U2000.

Application

During the network adjustment, such as adding or deleting a node in the network, if the fiber connection is deleted, the protection subnet and trail carried on the fiber are deleted from the network layer of the U2000. After the network adjustment, if the source and sink ports of the trail are not changed, you can find the trail again by performing the trail search. But the original customized information of the trail, such as the trail name, customized information of the trail, and remarks, cannot be restored through the search.

To restore the customized information of the trail, you need:

1. Before the network adjustment, export the network layer information file.

2. After the network adjustment, import the network layer information file.

NOTE:

� When the source and sink ports of the trail are not changed after the network adjustment, you can use the scripts to restore the customized information. Otherwise, you need restore the customized information manually.

� When the network layer information file is imported after the network adjustment, errors may be displayed for part of the data, because certain objects, such as NEs, boards, and ports, are changed. This does not affect the restoration of the customized information.

Parent topic: Backing Up and Restoring the U2000 Network Configuration Data by Using Scripts

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

of 3Script Files

scripts files _ types

Documents