f5 have the marketing reputation as the de facto load balancer for Horizon View. In my own experience of using the virtual appliance with View 6.2.2 (and using it for other services) I have to say I wouldn’t want to touch one or recommend one again.
Aside from the many woes that I’ve experienced and at the expense of everyones precious time, I saw a new issue the other day that could help anyone else troubleshooting View/f5 issues.
After a host appliance went down and then everything was resolved, none of the View connections that were being brokered by the f5 would work. Traffic would flow through to Security Servers and UAGs, Connection servers were accessible internally, but any connections that were reliant on the f5 (via the view Iapp), were terminating with ‘network error’, then ‘authentication error’. TCP dumps showed traffic, everything was up and there was also the possibility of storage and/or networking issues due the host failure.
Everything else seemed fine. The quik view/ihealth of the f5 looked fine and everything else worked. After engaging f5 support, they suggested that they’d seen this before and noticed that for a few seconds, the f5 had gone from Active to Standby and back again. He simply suggested restarting VDI APM daemon.
Voila! Connections working again!
What was most annoying that nowhere said the service hadn’t started, or got stuck, it was only because f5 had seen the issue before that they pointed us towards that.
So, emergency over and I’m sharing the various services/daemons in case you encounter a similar issue.
|Daemon||Description||Impact if not running||Relevant log file|
|acctd||The RADIUS accounting daemon used by BIG-IP APM to send RADIUS accounting start and stop messages to external RADIUS servers.||RADIUS accounting messages are not sent to external RADIUS servers||/var/log/apm|
|aced||The aced process provides RSA SecurID authentication functionality for BIG-IP APM’s access policy engine.||RSA SecurID authentication fails||/var/log/apm|
|apmd||The apmd process executes access policy for a user session; this includes Authentication, Authorization, hosting Accounting, and Audit. It also provides an MPI interface, as well as support for access control protocol.||No access policy enforcement for user session or any MPI-reliant processes, such as rewrite and websso||/var/log/apm|
|antserver||The antserver process allows Secure Web Gateway (SWG) to dynamically filter web content.||No dynamic web content filtering||/var/log/apm|
|dnscached||The dnscached process provides DNS cache functionality to BIG-IP APM subsystems.||BIG-IP APM DNS performance is impaired||/var/log/apm|
|eam||The eam process provides external access management for 3rd party identity integration, such as Oracle Access Manager (OAM) single sign-on (SSO).||OAM SSO authentication fails||/var/log/apm|
|eca||The eca process provides the client-side NT Lan Manager (NTLM) authentication mechanism.||BIG-IP APM is unable to authenticate using NTLM||/var/log/apm|
|mdmsyncmgr||The mdmsyncmgr process fetch MDM-managed endpoint list from MDM servers and stores it in local MySQL database.||BIG-IP APM is unable to fetch MDM-managed endpoint list.||/var/log/apm|
|nlad||The nlad process establishes communication channels to the Domain Controller (DC) for NTLM authentication.||No NTLM communication to backend DC||/var/log/apm|
|omapd||The omapd process provides the IF-MAP server implementation for SWG and AFM user identification.||No user identification for SWG||/var/log/omapd|
|rba||The rba process provides support for client-side Kerberos authentication.||No Kerberos authentication||/var/log/apm|
|rewrite||The rewrite process rewrites links in web content for Portal Access.||Portal Access web links are not rewritten||/var/log/rewrite|
|samlidpd||The samlidpd process interacts with the mcpd process to automate SAML IdP connector creation.||SAML IdP connector creation fails||/var/log/saml_automation.log|
|urldb||The urldb process categorizes incoming URLs for SWG.||No SWG URL categorization||/var/log/apm, /var/log/urldb-trace.log|
|urldbmgrd||The urldbmgrd process downloads and indexes the URL categorization database for use by the urldb process.||URL categorization for SWG is impaired||/var/log/apm, /var/log/urldbmgr-trace.log|
|vdi||The vdi process handles communication for XML-based clients and back-end systems such as Citrix and VMware View.||Citrix integration and RDP access fails||/var/log/apm|
|websso||The websso process provides Single Sign-On (SSO) functionality for the BIG-IP APM system.||SSO fails||/var/log/apm|
You can manage the services by using the TMSH utility – get putty’ed in (or similar) and follow this through:
- Log in to the tmsh utility by typing the following command:tmsh
- To stop, start, or restart a BIG-IP APM process, use the following syntax:<action> /sys service <process>
In this command syntax, note the following:
- <action> is the action to be performed, such as stop, start, or restart
- <process> is the name of the BIG-IP APM process
For example, to restart the eam process, type the following command:
restart /sys service eam