Large number of NE IP was not automatically changed accordingly to NE ID.
This phenomenon is happen after a case of upgrading a number of RTN in the warehouse, which involve using FTP method which is not recommended. We only notice it after deploying mass NE in region and
adding to the NMS.
Create an excel with the formula in it to convert NE ID to IP.
Request the sub contractor during commissioning of the RTN, check after input the NE ID, is the IP display are accordingly to the NE ID or not. If not, manually set the IP accordingly the excel.
1. Login randomly to the NE and check the management IP. Notice that a large numbers of NE the IP was not changed. Even changing the NE ID, the IP does not change automatically.
2. Read through manuals and it actually specifies that if the IP has been manually set, this will cause the “IP changes accordingly to NE ID” fail to function.
Default subnet: 188.8.131.52
Subnet mask: 255.255.0.0
The initial IP address of an NE is not manually set. It varies along with the change of the NE ID. If the IP address of the NE is already set manually, the NE IP address does not vary with the NE ID. In this case, the
NE IP address and the NE ID need to be set separately.
The relation between the initial IP address and the basic ID of an NE is as follows: If the initial IP address is 129.9.c.d, the basic ID satisfies the ID/256 formula. "c" and "d" in the initial IP address are the quotient
and remainder of the formula respectively. For example, when the basic ID is 0x6101 (the basic ID in decimal is 24833), the quotient of the 24832/256 formula is 97, and the remainder of the formula is 1. In this
case, the IP address is 184.108.40.206.
3. The cause was during the upgrade in warehouse earlier, the engineer use FTP method and connects RTN using switch. Then he login and change the management IP and perform mass upgrading of few
IP doesn’t change accordingly was due during the process of upgrading the NE. I recommend don’t manually set the IP because this management IP is important for management purposes. If it is set manually,
there is a risk that conflicts will happen and also the IP planning for it is unnecessary. The IP conflict will cause management issues on current and future functionality.