Principles for setting node IDs

5

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.

Other related questions:
Division principles of OceanStor 9000's pool nodes
Division principles of OceanStor 9000's pool nodes: - All nodes in a node pool must be of the same type. - In V100R001C01 and V100R001C20, a node pool contains 3 to 20 nodes. - In V100R001C30, if a node pool consists of P12, P25, P36, or C36 nodes, the node pool can contain 3 to 20 nodes. If a node pool consists of C72 nodes, the node pool can contain 2 to 10 nodes. - After deployment, nodes in a node pool cannot be modified. - If you want to modify a node, you must delete the node from its original pool first, and then add the node to a new pool.

Division principles of pool nodes for OceanStor 9000 V100R001C30
Division principles of pool nodes for OceanStor 9000 V100R001C30: - All nodes in a node pool must be of the same type. - If a node pool consists of P12, P25, P36, and C36 nodes, the node pool can contain 3 to 20 nodes. If a node pool consists of C72 nodes, the node pool can contain 2 to 10 nodes. - After deployment, nodes in a node pool cannot be modified. - If you want to modify a node, you must delete the node from its original pool first, and then add the node to a new pool.

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.

Division principles of pool nodes for OceanStor 9000 V100R001C01 and V100R001C20
Division principles of pool nodes for OceanStor 9000 V100R001C01 and V100R001C20: - All nodes in a node pool must be of the same type. - A node pool contains 3 to 20 nodes. - After deployment, nodes in a node pool cannot be modified. - If you want to modify a node, you must delete the node from its original pool first, and then add the node to a new pool.

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