In the past it has been a massive pain to download the vSphere client. Although the web UI has become far less clunky and much more streamlined – we still present the vSphere Client download links for ALL client versions to date! A fair chunk of standard day-to-day administration can be comfortably done with the standalone client.
The vSphere Client is the principal interface for administering vCenter Server and ESXi; vSphere client download links are all listed above – make sure you have downloaded the correct version for your ESXi release! There’s no problem having more than one installed – the launcher, i.e. the login window you see when you open the client, will connect to your ESXi server and choose the correct version to carry on with – or prompt you to download another version!
The vSphere Client user interface is configured based on the server to which it is connected:
When the server is a vCenter Server system, the vSphere Client displays all the options available to the vSphere environment, according to the licensing configuration and the user permissions
When the server is an ESXi host, the vSphere Client displays only the options appropriate to single host management.
When you first log in to the vSphere Client, it displays a Home page with icons that you select to access vSphere Client functions. When you log out of the vSphere Client, the client application retains the view that was displayed when it closed, and returns you to that view when you next log in.
You perform many management tasks from the Inventory view, which consists of a single window containing a menu bar, a navigation bar, a toolbar, a status bar, a panel section, and pop-up menus.
This article walks through how to configure an f5 default gateway for your internal (or external!) machines.
Often, SNAT automap, a SNAT address or SNAT pool is used to essentially “hide NAT” the incoming packet behind the BigIP which will mean that the server will reply directly back to it; this doesn’t work or isn’t wanted for some environments though.
If the packet is passed through the f5 and still contains its original (internet routable) client source IP then the back-end server will send its reply to the default gateway and if this *isn’t* the BigIP then we will have asymmetric routing which is never pleasant at the best of times. This is therefore an example scenario where using the f5 as a default gateway would be convenient.
This is actually a “Forwarding (IP)” Virtual Server which will listen on all Self IPs but you can (and most certainly should) lock this down on a VLAN basis for security.
Name your virtual server, in this case “s_gateway”
Specify a source address – this is optional but if you leave it blank it will default to 0.0.0.0/0 meaning it will accept connections from ALL IP addresses whether internal or external. As this is a MAJOR SECURITY RISK you should lock it down to the subnets you want to accept connections from, in this case we have used “10.5.5.0/24” – connections from all other address ranges will be silently dropped
Destination – you can lock this down to a specific network but for a default gateway we want to allow everything so this is “0.0.0.0/0”
Set ports to “*” to accept connections to any port.
Unless you only wat to allow TCP & UDP, drop the Protocol menu down and choose “All Protocols”
Select the VLANs you want to enable this on (optional)
Enable SNAT Automap – this essentially hides connections behind the BigIP -you could also use a SNAT pool or address