Tools

Channel Area

Service Product Area

Forum Affairs

Relationship between the node ID of an ASON NE and an NE ID

19

Relationship between the node ID of an ASON NE and an NE ID:
The node ID of an NE must be different from the IP address of an NE and must be unique on the entire network. The node ID is independent of the NE ID and NE IP address.

The ID of an OTN NE is unique in the entire network. When the NE is configured as the gateway NE, the NE uses the IP address for TCP/IP communication with the NMS. For other communications between NEs, the device uses the DCC communication with other devices, and the ID is the only identifier.

When the optical and electrical NEs of an ASON NE are not split, the OTU or FIU boards on the ASON NE can function as edge points, and the related TE links can be automatically created when the boards are created.
When the optical and electrical NEs are split, the multiplexer/demultiplexer or other optical-layer boards can function as the edge points of the optical NEs.
When the fiber connections between the optical ports on the multiplexer/demultiplexer boards and those on the OTU boards are created, the intra-NE links that carry OCh signals are automatically created.

The primary NE is responsible for communication between the ASON network and U2000 server. It transmits information on the ASON control plane and reports ASON events to the U2000 server. An ASON domain can have only one primary NE and one secondary NE.
A gateway NE is connected with the U2000 server using the TCP/IP protocol. Generally, an NE that is connected to the U2000 server through a LAN or WAN is a gateway NE. Multiple gateway NEs can be connected to the U2000 server.
Generally, you can configure the primary or secondary NE as the gateway NE on an ASON network to leverage ECC bandwidth resources.