This article is intended for administrators wishing to solve the error message when registering the Plugin VM with vCenter "Device "eth0" does not exist".
Note: Although the error is shown the registration can seem successful but there is no plugin displayed in vCenter thought it can be visible in Administration>Client Plugins
Resolution/Information
Edit the netplan config file to update the device from the currently allocated name to eth0. As the register script is looking for a device that has this name.
Description of Problem
When running the register plugin command the following error: "Device "eth0" does not exist" is thrown and despite what looks a successful deployment there is no visible plugin in the vCenter or Datacenter object in Inventory View in vCenter.
sudo /opt/stormagic/SvSAN/bin/configure_plugin.sh -o register -v <vcenter fqdn> -u <username> -p -
Steps to Resolve:
Step 1
Unregister the plugin from vCenter using the following syntax (adjust where necessary).
sudo /opt/stormagic/SvSAN/bin/configure_plugin.sh -o unregister -v <vCenter fqdn> -u <user name> -p -
Step 2
Now edit the .yaml file to change the name of the interface to eth0.First make a backup of the current config using the following syntax:
cp /etc/netplan/01-netplan-ansible.yaml /etc/netplan/01-netplan-ansible-bk.yaml
Step 3
Edit the exiting .yaml file and update the set command:
sudo nano /etc/netplan/01-netplan-ansible.yaml
Change the value in "set-name" to eth0. In this example it was ens192 - updated this to eth0 and saved changes.
Step 4
Apply changes with the following command
sudo netplan apply
Step 5
Register the plugin VM once more with vCenter using the same command as before:
sudo /opt/stormagic/SvSAN/bin/configure_plugin.sh -o register -v <vcenter fqdn> -u <username> -p -
Verify that the command has completed without warnings and that the plugin has been successfully registered in vCenter.
For further troubleshooting of the plugin VM see these articles:
Troubleshooting Issues with PluginVM deployment for SvSAN
SvSAN Plugin VM and Edge Control Orchestrator networking - View/Modify
See Also
Comments
0 comments
Article is closed for comments.