Using NAT address translation to avoid multiple site visits for transport equipment deployment

Question:
During the deployment of transport equipment, site supervisors often fail to correctly configure IP address or the subnet mask of the equipment according to the original plan, resulting in the remote NMS failing to log in the equipment normally. When sites are far away, a second site visit consumes much time and labor.
Analysis:
None
Root cause:
None
Answer:
Transport equipment usually connects to the centralized NMS through external DCN networks. You can use SSH to log in the router of the DCN network from the remote NMS server, and configure NAT on the router to translate the address of the NMS server to one that is in the same network segment as the local transport equipment. After the translation, the NMS server will be able to connect to the equipment normally, and reconfigure the communication parameters to the planned ones. Finally, you can log in the router and delete the NAT translation commands, and the network will become normal.
A(U2000) - A (router)----DCN----B (router) - B (router)
For example, the IP address of the U2000 NMS server of site A is 192.168.1.2/255.255.255.240. The planned IP address of the newly deployed OSN 8800 equipment is 192.168.1.4/255.255.255.240 when communicating with the U2000 through external DCN networks. The site supervisor only set the equipment ID to 9-20, but left the IP address as the default 129.9.0.20/255.255.0.0. For U2000 at site A to communicate normally with the OSN 8800 equipment of site B, NAT must be performed on the router of site B, mapping 192.168.1.2 to 129.9.0.22. When the OSN 8800 is loaded on the U2000 and its communication parameters are reconfigured to the planned ones, the original DCN settings can be restored.

Scroll to top