Technical FAQs

Ask a Question

Changing the private IP of StruxureWare Central but leaving it in the same subnet may cause issues with gateway given to DHCP devices.

Issue:

Changing the private IP of StruxureWare Central but leaving it in the same subnet may cause issues with gateway given to DHCP devices.

Product Line:

InfraStruxure Central
StruxureWare Central
StruxureWare Data Center Expert

Environment:

All versions

Cause:

DHCP issues.

Resolution:

If you change the private side IP of StruxureWare / InfraStruxure Central but keep it in the same segment, the default gateway provided to the DHCP devices does not get properly updated.

For example, if you change the private IP of the Central from 192.168.1.1 to 192.168.1.20, the DHCP server's configuration does not update properly. Any devices that are on the private side of the Central or are added to it will still get a 192.168.1.1 gateway. This will cause issues when launching to devices or if the devices are set up to e-mail or send traps to systems outside of the private network.

To avoid this issue, change more than the last octet of the private side IP of the Central.

If this issue has already occurred and you want to keep the current configuration, we suggest you disconnect the private side network connection so that any changes do not effect devices. Once disconnected, change the subnet mask. This will force the DHCP config to change and update the gateway. Once the system reboots as it will for any network change, put the subnet mask back to it's original config. After the system reboots again, you can reconnect the private network and all the devices should eventually get the new gateway settings.
Was this helpful?
What can we do to improve the information ?