Differences between the primary NE and gateway NE on an ASON network

18

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.

Other related questions:
Whether multiple primary NEs that function similar to gateway NEs can be created in an ASON domain
Only one primary NE and one secondary NE can be created in an ASON domain. The U2000 server needs to establish a connection with either the primary or secondary NE. The NE that establishes a connection with the U2000 is called the gateway NE and implements communication between the ASON network and the U2000 server. In normal cases, you are advised to configure the primary NE as the communication NE. When the primary NE fails, the secondary NE becomes the communication NE. If both the primary and secondary NEs fail, the system automatically selects an ASON NE as the communication NE.

Relationship between optical NEs and electrical NEs on an ASON network
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.

Relationship between the node ID of an ASON NE and an NE ID
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 relationship between ASON NE'S NODE ID and ne's id
Ne's NODEID is different to ne's ip address ,and uniqueness in network and so the only.NODEID, ne's id and ne's ip address is independent of each other.

Whether multiple primary NEs can be managed like GNEs in an ASON domain
You can set only one primary NE and one secondary NE in an ASON domain. The NMS only needs to communicate with one NE on an ASON network. This NE is called the communication NE. It is the NE that represents the ASON network to communicate with the NMS. Usually, the communication NE is the primary NE. When the primary NE fails, the secondary NE becomes the communication NE. If both the primary and secondary NEs fail, the system automatically selects an ASON NE as the communication NE.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top