Depending on how your environment evolves, you may find that you need to modify how VSAN operates on the network. By virtue of VSAN's distributed nature, networking changes require careful planning to avoid the potential of causing a network partition and/or a VSAN production outage.
If you are making any significant change, such as modifying the IP subnet or VLAN, the new networking should be configured alongside the legacy networking, and then the legacy networking can be removed once the new configuration is enabled.
Even when taking all reasonable steps to avoid issues, networking changes could cause an outage if something goes wrong. Therefore, it is strongly recommended that significant network changes take place during a maintenance window.
In this recipe, we will demonstrate moving VSAN production to a new IP subnet. The same principle of standing up new networking before tearing down the original configuration applies to other similarly high-impact networking...