These considerations apply to modifying networks:
- You cannot change the names of the S Series Node networks.
- You can modify all properties of the access network and management network except their names. To modify a subnet, change the applicable gateway address, subnet mask, or prefix length.
- When you modify the access network, communication with the S Series Node is briefly disrupted. However, the S Series Node does not reboot.
- When you modify the management network, the S Series Node reboots. Enabling or disabling management-network monitoring does not cause a reboot.
- You can change the physical or virtual IP address of the server module that's servicing the change request. If the IP address you change is the one the request is using and you're making the change in the HCP S Series Management Console, the Console session immediately ends.
- You can change the subnet for the server interconnect network, but you cannot change the fourth octet of the server-module IP addresses on that network.
- When you change the subnet for the server interconnect network, both S Series Node server modules automatically reboot. Until the reboot is complete, no communication can occur between the S Series Node and other devices.
- Multiple S Series Nodes can have the same server interconnect network subnet and the same server interconnect network IP addresses for their server modules. This configuration is possible because the server interconnect network on any given S Series Node is isolated from the server interconnect network on every other S Series Node.
- When you correctly change the configuration of a network, the HCP S Series Management Console displays a success message. However, this message is displayed before the change is fully implemented. To ensure that the change succeeded, check the S Series Node event log. If you do not see the following message, the change succeeded:
Network configuration change could not be applied