{"id":174,"date":"2014-02-28T13:42:45","date_gmt":"2014-02-28T18:42:45","guid":{"rendered":"http:\/\/ybontap.tynsoe.org\/wordpress\/?p=174"},"modified":"2014-02-28T13:42:45","modified_gmt":"2014-02-28T18:42:45","slug":"network-va-fusion","status":"publish","type":"post","link":"https:\/\/ybontap.tynsoe.org\/?p=174","title":{"rendered":"Configuring Network for NetApp Virtual Appliances in Fusion"},"content":{"rendered":"

NetApp Virtual Appliances like OnCommand Unified Manager 6 or OnCommand Performance Manager 1 are normally deployed within VMware ESX hypervisors. It can work on other hypervisors as well but it requires additional steps to workaround an error that occurs when you try to set the IP address to something else than DHCP. The purpose of this article is to explain how to make IP configuration available when you setup the virtual appliance in a lab-on-laptop<\/a> lab, or anywhere else that is not a ESX server.<\/p>\n

<\/p>\n

When you try to change the IP address, either in the web UI or in the VM console, you will get an \u00ab\u00a0unknown error\u00a0\u00bb while trying to apply the settings.<\/p>\n

This is caused by the way the configuration scripts handles errors while restarting the different services. \u00a0For some reason, applying network settings restarts VMware tools, and with it, the HGFS service that is not available by default on a VMware Fusion VM which reports the error. It makes the configuration script roll back to previous setting.<\/p>\n

To prevent that issue, you must restart the virtual appliance, bypass normal boot, and edit vmware-tools init script manually.<\/p>\n

Boot the virtual appliance directly in a shell<\/h1>\n

Boot the VA, and you should see a boot selection screen like this one :<\/p>\n

\"Standard<\/a>

Standard boot screen for a NetApp Virtual Appliance<\/p><\/div>\n

Type the \u00ab\u00a0e<\/strong>\u00a0\u00bb letter before the countdown expires.<\/p>\n

Then you need to edit the boot argument on the line that starts with \u00ab\u00a0linux<\/strong>\u00a0\u00bb to make it look like this :<\/p>\n

\"Boot<\/a>

Boot arguments screen for a NetApp VA<\/p><\/div>\n

Basically, you remove \u00ab\u00a0quiet<\/strong>\u00a0\u00bb and \u00ab\u00a0console=tty2<\/strong>\u00a0\u00bb arguments, and add \u00ab\u00a0init=\/bin\/sh<\/strong>\u00a0\u00bb<\/p>\n

If you do that correctly, you should get to the following screen after typing \u00ab\u00a0Ctrl-x<\/strong>\u00a0\u00bb to boot<\/p>\n

\"This<\/a>

This is the shell prompt you should get<\/p><\/div>\n

Modifying the vmware tools script<\/h1>\n

For now, the filesystem is mounted read-only, you need to remount it with \u00ab\u00a0rw\u00a0\u00bb option :<\/p>\n

# mount -o remount,rw \/<\/pre>\n
Then edit the following file :<\/p>\n
# vi \/etc\/init.d\/vmware-tools<\/pre>\n