I have heard a lot on Infoblox issues with Citrix and had the chance to meet some of the Infoblox team today for lunch and a meeting. My first question, and Kevin Dralle’s, whom I work with, was about the apparent incompatibility of InfoBlox and Citrix, especially with PVS. Please comment if you think this doesn’t work or has issues.
Some of the issue have been described elsewhere (I know Jarian Gibson has wrote and tweeted a few things on this also)
With Infoblox there is a CTX but it’s a bit mysterious on details
So what is going on with InfoBlox, anytime we have had customer with InfoBlox on and Citrix we cringe or opt for perhaps a dual NIC, isolated PVS VLAN (using Microsoft DHCP). In any case here is what happens.
InfoBlox assigns the device a UID based on MAC but also on some of the device characteristics. So when we boot off PVS, we bring up the bin file which acts as the OS at the time of PXE boot. We have a static MAC but since after the bin file pulls the TFTP image then brings up a windows OS, the UID changes, which infoblox assumes you’ll need another IP address. Obviously there are use cases for this but for PVS this is an issue as you’ll get two IP addresses.
One fix has been to use reservations but this defeats the whole purpose of using an appliance or solution to manage this all. Furthermore, when or if you get into automation and orchestration, you’ve got one more component to worry about when increasing the scope.
You do need to be on the 6.6 or higher release for this option but it is worth it if you have this issue or are an InfoBlox shop and want to rollout PVS without trying something uncommon to deployments (using BDM has a lot less collateral out there than PXE boot does).
Below are the two areas from the Grid and Member layers where you can set this (courtesy of InfoBlox!).