DCN Management

The Web LCT communicates with NEs, and manages and maintains network nodes through a DCN. In the DCN, the Web LCT and NEs are considered as nodes, which are connected by using the Ethernet or DCC physical channels. In practice, the Web LCT and NEs may be located at different floors of the same building, different buildings or different cities. Hence, Web LCT and NEs are connected through a DCN, which consists of switches and routers. The DCN between the NEs is referred to as an internal DCN.

Outband DCN Overview
The element management system (EMS) sets up communication with NEs through a data communication network (DCN), to manage and maintain these NEs.
HWECC Solution
ECC configuration is simple. By default, all Huawei equipment support the ECC protocol and the physical transmission channel is D1-D3 bytes. When the NE ID is set and fibers are connected, the ECC communication is established without any configurations. If you want to modify the ECC communication parameters, locally modify them. Do not remotely modify the parameters because ECC communication may be interrupted and cannot be recovered. If you have to remotely modify the parameters, start from the farthest end.
IP over DCC Solution
The IP over DCC communication transmits DCC data by the using IP data packets. The IP over DCC directly operates and maintains remote NEs by using standard TCP/IP protocol. In addition, it realizes the application functions, such as FTP, Telnet, and SNMP. As essential parts of the IP over DCC communication, the dynamic and static routing protocols are used to create route information.
OSI Over DCC Solution
The OSI protocol is a widely used communication protocol in a network. By using the OSI over DCC communication, a network that consists of equipment from multiple vendors transparently transmits management information at the network layer. Hence, the interconnection with the equipment that supports OSI protocol from the third party is realized.
Configuring Primary and Secondary GNEs
You can configure standby GNEs for NEs to avoid service interruption due to GNE failure. When a GNE for NEs fails, the GNE is automatically switched to a standby GNE, which then connects NEs to the Web LCT. Switching GNEs interrupts the communication transiently but does not affect services. You can configure up to three standby GNEs for an NE.

Parent topic: Managing NG WDM NEs