Principles for setting node IDs

A node ID is independent of an NE ID and NE IP address. On an ASON network, each ASON NE is identified using a unique node ID.
Node IDs can be planned according to the following rules in practice:
Preferentially use the following network segment: 172.16.0.0 to 172.31.255.255. In this network segment, a total of 1,048,574 IP addresses are available (except 72.16.0.0 and 172.31.255.255).
If the addresses in the preceding network segment conflict with the addresses in the management plane network segment or DCN network addresses, preferentially use the following network segment: 10.0.0.0 and 10.255.255.255. In this network segment, a total of 16,777,214 IP addresses are available (except 10.0.0.0 and 10.255.255.255).
If a network segment conflict still exists, use the following network segment: 192.168.0.0 to 192.168.255.255. In this network segment, a total of 65,534 IP addresses are available (except 192.168.0.0 and 192.168.255.255).
If the preceding network segments cannot satisfy user requirements, formulate a plan with Huawei.
The following provides the node ID characteristics and configuration requirements:
No duplicate node ID is allowed in the same ASON domain.
The node ID and NE IP address of an NE cannot be in the same network segment.
A node ID is independent of an NE ID and NE IP address.
Node IDs and IP addresses must be in the same format, but a node ID cannot be 0.0.0.0, 1.2.3.4, or 255.255.255.255.
When both ASON services and packet services are configured, the LSR IDs of packet services must be consistent with the node IDs of ASON services.
Node IDs must be configured before ASON is enabled. Otherwise, a warm reset is automatically performed on the NE.

Scroll to top