Glossary N

NE

It is the network element, including the hardware unit and the software running on it. Usually, one NE has at least SCC (System Control & Communication Unit) board which responsible for the management and monitoring of the NE. The host software runs on the SCC board.

NE database

There are three types of database on NE SCC board as following:(1) DRDB: a dynamic database in a dynamic RAM, powered by battery; (2) SDB: a static database in a power-down RAM; (3) FDB0, FDB0: permanently saved databases in a Flash ROM. In efficient operation, the NE configuration data is saved in DRDB and SDB at the same time. Backing up an NE database means backing up the NE configuration data from SDB to FDB0 and FDB1. When an NE is restarted after power-down, the NE database is restored in the following procedures: As the SDB data is lost due to power-down, the main control restores the data first from DRDB. If the data in DRDB is also lost due to the exhaustion of the battery, the data is restored from FDB0 or FDB1.

NE ID

In a network, each NE corresponds to a unique identifier, i. e. the NE ID. ECC communication among NEs is performed through the identification of NE IDs. The NM uses NE ID, in an interface or a database, to identify various NEs in a network. In the OptiX transmission equipment, it is specified that the NE ID is a 24-bit binary digit, i. e. three bytes. The DIP switch on the SCC board of the NE constitutes the lower 16 bits of the NE ID. The higher 8 bits of the NE ID is the extended ID (default value: 9), which is also called the sub-network number. The extended ID is usually used to identify different sub-networks. For example: The ID of an NE is: 0x0009001e.

NE layer data on NM

It is the NE configuration data saved in the NM database. Consistency between the data on the NM side and that on the NE side is the precondition of efficient running of the transmission equipment. If there is any data on the NE side, the Web LCT can save such data in the NE layer on the NM side through the upload function, thus forming the NE layer data on the NM side. If there is no data on the NE side, the Web LCT can send the NE layer data on the NM side through the upload function, thus forming the data on the NE side. Meanwhile, the NE layer data on the NM side is one of the important data sources of the network layer data on the NM side.

Network entity

Network entity refers to the universal basic devices used to describe the functions and structure of the transmission network, which considerably facilitates the description of the network. The network entities include transmission object and sub-network.

Network layer data on NM

It is the network configuration data saved in the NM database and is the data source for the network function of the Web LCT. The network layer data on the NM side includes three parts: fiber connection data, protection sub-network and SDH NNI data and trail information.

NNI

NNI is the abbreviation for Network Node Interface. It identifies the interface between the ATM network nodes.

Number of routes calculating

Usually,the Web LCT can work out multiple trails which comply with the requirements according to the route restriction. The user can select one of them. The number selected here is the maximum number of optional routes which is worked out by the Web LCT .