Config-sync over Management Interface in f5

Config-sync over management interface – while not a best practice – can be a handy thing to have, whether that is because of a lack of interfaces, switch capacity or other reason.

This has cropped up for me in a refresh / migration project where interfaces were changed out for fibre and didn’t come up immediately. This allowed us to sync the machines and configure failover before attending to the interface issue ..

Best practices for f5 High Availability configuration can be found here.

The management interface will not show up by default under the config-sync tab:

Only traffic interfaces available by default.
Only traffic interfaces available by default.

this has to be enabled using the following commands:

tmsh modify sys db configsync.allowmanagement value enable
tmsh save sys config
Enter commands on the CLI
Enter commands on the CLI

Refresh the page and we can now choose to run the management interface:

Management interface now available
Management interface now available

vSphere Client Download – Direct Links

vSphere Client Download

I think everyone knows what a pain it can be to try and download the vSphere client – we therefore present the vSphere Client download links for ALL client versions to date! Although VMWare are steering people towards using the vCenter webui client which brings more functionality, 95% of standard day-to-day administration can be comfortably done with the standalone client.

Also, scroll to the bottom of the page for an overview of the vSphere client and how it works.

vSphere v6.0

vSphere v5.5

vSphere v5.1

vSphere v5.0

vSphere v4.1

It appears that VMware have removed the vsphere 4.1 client installer files, thank you Joe for letting me know! Please bear with me while I source these and link to them, in the meantime you can find them using the filemare ftp search engine. As these are not direct from VMware, please make sure you have scan these for virus / malware should you choose to download them.

  • 4.1 : VMware-viclient-all-4.1.0-258902.exe – file removed by VMware. You may be able to find it using the filemare ftp search engine.
  • Update 1 : VMware-viclient-all-4.1.0-345043.exe – file removed by VMware. You may be able to find it using the filemare ftp search engine.
  • Update 2 : VMware-viclient-all-4.1.0-491557.exe – file removed by VMware. You may be able to find it using the filemare ftp search engine.
  • Update 3a :VMware-viclient-all-4.1.0-925676.exe – file removed by VMware. You may be able to find it using the filemare ftp search engine.

Installation on Windows 8:

If you are having issues installing the client on Windows 8, click here for details.

What is the vSphere 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.

iRule Event Order for HTTP Requests and TCP Connections

iRule Event Order

There is an excellent article on DevCentral regarding iRule order but this focuses on TCP, the event order for an HTTP request is different as you can see below:

Event Order – HTTP Request

1. RULE_INIT
2. CLIENT_ACCEPTED
3. CLIENTSSL_HANDSHAKE
4. CLIENTSSL_CLIENTCERT
5. CLIENT_DATA
6. HTTP_REQUEST | CACHE_REQUEST
7. HTTP_CLASS_FAILED | HTTP_CLASS_SELECTED
8. STREAM_MATCHED
9. HTTP_REQUEST_DATA
10. CLIENT_DATA | HTTP_REQUEST_DATA
11. LB_SELECTED | LB_FAILED
12. STREAM_MATCHED
13. SERVER_CONNECTED (Here is where the backend server is reached)
14. SERVER_SSL_HANDSHAKE
15. HTTP_REQUEST_SEND
16. SERVER_DATA (CACHE_RESPONSE | HTTP_RESPONSE)
17. HTTP_RESPONSE_DATA

Event Order – TCP Connection

1. RULE_INIT
2. CLIENT_ACCEPTED
3. CLIENT_DATA
4. STREAM_MATCHED
5. LB_FAILED | LB_SELECTED
6. SERVER_CONNECTED
7. SERVER_DATA