Unable to reconfigure FSVM network
Article ID: 326701
Updated On:
Products
VMware vSAN
Issue/Introduction
Explain how to reconfigure file services network.
Symptoms:
Symptoms:
- When vSAN File Service is enabled and configured on a particular network, it does not allow changing the network interface.
- Configure > vSAN > Services > Edit File Service > Networking allows only changes to netmask and gateway but not the network interface.
- The admin cannot move the file share services to a different network.
Environment
VMware vSAN 7.0.x
Cause
EAM doesn't support reconfiguring the network of existing agent VMs deployed by OVF.
Resolution
Ensure to follow Configure File Services and have the network planned as described before proceeding with enabling vSAN File Services to ensure the networking is configured per best practices from the start.
Workaround:
However, if you need to make a change to the network use the below steps.
For environments 7.0U3c and newer:
1) Ensure you have a backup of all the data on the file shares
2) Disable vSAN File Services
3) Re-enable vSAN File Services ensuring you're using the required network per best practice
For environments below 7.0U3c follow one of the below action plans:
Upgrade your environment to 7.0U3c or higher, preferably the latest version available, then follow the above steps to change the network config.
If you can't upgrade then follow the below steps:
1) Ensure you have a backup of all the data on the file shares
2) Disable vSAN File Services
3) Open a case with vSAN support so we can run a script to completely remove the vSAN File Service configuration
5) Restore the data from backups back to the file shares
Workaround:
However, if you need to make a change to the network use the below steps.
For environments 7.0U3c and newer:
1) Ensure you have a backup of all the data on the file shares
2) Disable vSAN File Services
3) Re-enable vSAN File Services ensuring you're using the required network per best practice
For environments below 7.0U3c follow one of the below action plans:
Upgrade your environment to 7.0U3c or higher, preferably the latest version available, then follow the above steps to change the network config.
If you can't upgrade then follow the below steps:
1) Ensure you have a backup of all the data on the file shares
2) Disable vSAN File Services
3) Open a case with vSAN support so we can run a script to completely remove the vSAN File Service configuration
Note: Running this script will wipe out the file shares resulting in the data on these shares being wiped as well so it's critical to have backups of the data.
4) Re-enable vSAN File Services ensuring you're using the required network per best practice5) Restore the data from backups back to the file shares
Additional Information
Impact/Risks:
The only way to change the networking, other than the netmask and gateway, is to do a complete redeploy of vSAN File Services.
The only way to change the networking, other than the netmask and gateway, is to do a complete redeploy of vSAN File Services.
Feedback
Yes
No
Powered by
