Precautions for DCN subnet division


Take the following precautions during DCN subnet division:
Ensure that the number of NEs in a DCN subnet is within the recommended range.
Disable the DCC and GCC channels between DCN subnets.
Before dividing a DCN into subnets, plan an external DCN for connecting to gateway NEs in each subnet.
Ensure that DCN subnet division must not compromise the existing DCN route restoration (protection) capability.
Group separated optical and electrical NEs at the same site in the same DCN subnet.

Other related questions:
Reasons for communication interruptions between a device and DCN after a WDM hub is connected to a DCN
Question: The communication between a BWS 1600G device and DCN is interrupted after the hub of the BWS 1600G device is connected to the DCN using two network cables. The BWS 1600G device uses three subracks, and the ETH indicator on the system control board is steady on. After a computer is connected to the hub, the computer crashes, causing an NE login failure. Analysis: Other ports on the switches in the DCN work properly. Disconnect the network cable from the faulty NE, and then connect the network cable to a normal port. The issue is replicated, the fault is not caused by the switches. Set the IP address of the computer to the same as that of the device. Test the two network cables connected to the hub respectively. No abnormality occurs, indicating that the fault is not caused by the network cables and IP address configuration. Check and find that the hub is connected to the DCN using two network cables. This indicates that a loop is formed in the DCN. In this case, the computer is connected to the hub using a network cable, and the CPU usage reaches 99%. As a result, the computer crashes, the indicator of the network interface card (NIC) is steady on, and the ETH indicator of the system control board on the WDM device is also steady on. This indicates that the DCN receives a large volume of data send by itself. As a result, the communication between the NE and DCN is interrupted. Remove one network cable between the hub and DCN. The computer works normally again. In addition, reset the system control board, and then the NE can be logged in to normally. Root cause: The main reasons for DCN network interruptions are as follows: 1. Issues of switches in the DCNs 2. Issues of network cables 3. Issues of IP configurations 4. Issues of the hub Answer: Remove one network cable between the hub and DCN, and then reset the system control board. Suggestion and conclusion: None

Division of dual planes
The network of FusionInsight HD is divided into two planes, the service plane and management plane. The two planes are deployed in physical isolation mode to ensure network security.

Adjusting OceanStor 9000's subnet division
Procedure for adjusting OceanStor 9000's subnet division: 1. Log in to DeviceManager. 2. Create a subnet. a. Choose Settings > Cluster Settings > InfoEqualizer > Subnet Management. b. Click Create. In the Create Subnet dialog box, enter the required information and click OK. c. In the Success dialog box that is displayed, click OK. In the subnet list, you can view the newly created subnets.

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