The VMWare demo version of the Management Gateway Appliance currently only has one NIC and any attempt to add second NIC fails to add using the web interface.
It is common to create a demo environment in VMWare where there are two virtual networks that do not have access to each other. The Core Server resides on only one network and the VMWare demo version of the Management Gateway Appliance resides on both virtual networks. A virtual machine with an agent can then be added to the network that the Core Server does not reside on. This allows for the simulation of a device being on a separate unattached network, allowing use of the Management Gateway.
Enabling the Ability to Configure a Second Interface
To enable the ability to configure a second interface, follow these steps:
Log into the Management Gateway.
Press Alt-F2 to switch to a different screen.
Note: To switch back to the main screen press Alt-F1. The windows manager that the Gateway uses is Fluxbox.
Right-click anywhere on the desktop to get the Fluxbox menu to appear. It will display some options as follows:
Choose xterm. This opens an xterm command prompt.
Change directories to /etc/sysconfig/newtork-devices.
Create a directory called ifconfig.eth1.
sudo mkdir ifconfig.eth1
Configure the directory ownership and permissions.
sudo chown root:webedit ifconfig.eth1 sudo chmod 775 ifconfig.eth1
The second network card is now configurable using the normal method on the administration web page of the VMWare demo version of the Management Gateway Appliance.
Note: If adding a second network card, it may be necessary to add additional routes. For information on adding persistent static routes to the Management Gateway, see the following article: Cloud Services Appliance 4.2 - How To Add a Persistent Static Route