Shameless link alert! ALERRTTTT!
This is a really, really good reference architecture paper – I think most of us within the space can setup and configure components such as workspace/Identity manager and Appvolumes, but not everyone gets the opportunity to really go to town across multiple sites with a view to building it up from the bottom – so this is where this paper comes in really handy. There’s everything you need for those situations where you’d have go hunting for the further information and also helps for getting buy in as to what exactly is needed as defined by a whitepaper. There are other configurations as solutions for multi site architecture (I know, I’ve done a few myself), but with this, you know exactly what you put in and what you’ll get out.
Horizon 7 Multi-site architecture
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.
||Impact if not running
||Relevant log file
||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
||The aced process provides RSA SecurID authentication functionality for BIG-IP APM’s access policy engine.
||RSA SecurID authentication fails
||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
||The antserver process allows Secure Web Gateway (SWG) to dynamically filter web content.
||No dynamic web content filtering
||The dnscached process provides DNS cache functionality to BIG-IP APM subsystems.
||BIG-IP APM DNS performance is impaired
||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
||The eca process provides the client-side NT Lan Manager (NTLM) authentication mechanism.
||BIG-IP APM is unable to authenticate using NTLM
||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.
||The nlad process establishes communication channels to the Domain Controller (DC) for NTLM authentication.
||No NTLM communication to backend DC
||The omapd process provides the IF-MAP server implementation for SWG and AFM user identification.
||No user identification for SWG
||The rba process provides support for client-side Kerberos authentication.
||No Kerberos authentication
||The rewrite process rewrites links in web content for Portal Access.
||Portal Access web links are not rewritten
||The samlidpd process interacts with the mcpd process to automate SAML IdP connector creation.
||SAML IdP connector creation fails
||The urldb process categorizes incoming URLs for SWG.
||No SWG URL categorization
||The urldbmgrd process downloads and indexes the URL categorization database for use by the urldb process.
||URL categorization for SWG is impaired
||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
||The websso process provides Single Sign-On (SSO) functionality for the BIG-IP APM system.
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
The vmworld 2017 HOL just popped up ! Get ’em while they’re hot!
VMworld 2017 HOL
I always find this document to be really helpful when deploying not only View, but when other components start getting involved:
vRealize Operations for Horizon
VMware Horizon Client
VMware Identity Manager
VMware Unified Access Gateway
VMware App Volumes
VMware User Environment Manager
VMware vCenter Server
And you either need a checklist of ports or need to precisely and politely inform the Network team/Firewall admin that you need some ports opening up.
Me: Can you not just open all the ports I just told you from that IP?
FW Bloke: No, I need some documentation to prove those are the ports I need to change for my change request.
Me: But…I sent you it weeks ago?
FW Bloke: I know, but I didn’t make the change so need to raise a new CR.
Me: So… Just add the document I sent across…Please?
FW Bloke: I can’t, I need a new one.
Me:… I hate you.
FW Bloke: I don’t care.
Horizon 7 Network Ports
Ah, Barcelona, one of the busiest cities I’ve been to where it’s nigh on impossible to get a taxi late at night!
I didn’t go early enough to hit the Partner sessions (On a weekend? Really?!) as I landed on the Monday, but I spent more time this year with customers and colleagues. As soon as I started building my sessions, I realised all the interesting ones were full! I have to admit though, last year held a lot more interest for me – this year it seemed a bit scraping the barrel, in the sense of, much less new and innovative solutions were in place.
There were a few familiar faces missing from the stalls, some ‘interesting’ gimmicks… That even for a hardened freebie hunter/blagger (Modern Hunter/Gather), was a little disconcerting! I only came away with this little bloke and a blue LED bouncy ball that someone just shoved into my hand.
Wolverine in a sports jacket! The Lego Build a Mini-fig probably put the most smiles on peoples faces all week!
*Tap tap tap tap*
*Tap tap tap tap*
Yes…You are typing the correct password. When setting up the UAG, there’s a minimum password complexity…It just doesn’t tell you that you met it or not… Honestly it’s up there with the firewall changes for VROPS they don’t tell you about, plus calling Domains ‘Realms’…
Anyway! Easily fixed – Root password on the console screen should be fine and do the following:
echo ‘adminPassword=P@ssw0rd’ > /opt/vmware/gateway/conf/firstboot.properties
chown gateway /opt/vmware/gateway/conf/firstboot.properties
supervisorctl restart admin
Lo and Behold! You can access the WebUI again…
One of my colleagues wrote a UAG Firewall rules generator which is worth a look!
I actually wrote some documentation on this for my team, when I encountered the issue. Then I lost it. Hence setting up a website to store everything I come across, on!
This issue came about myself after I upgraded the version of VROPS I had installed and I couldn’t for the life of me understand why the agent simply refused to connect. So after much messing around, I found the following vmware KB:
VMware vRealize Operations Manager for Horizon 6.2 Broker Agent fails to pair with the Horizon adapter (2140844)
Yep, they decided to leave out the necessary ports allowed through the firewall on the appliance. Thanks vmware!
If you aren’t comfortable using VI – which for the uninitiated, can be a nightmare, you can take a copy of the file (download it/FTP it off etc) and make the changes, then re-upload it.
Don’t forget the restart the firewall service – also when I rebooted the VROPs server once, it lost the settings, so rookie mistake or something more…sinister… Not sure, don’t care, just had to do this again! 😉