FYI, ran into an issue tonight working with VVOLs.
I had just upgraded my PureStorage array to Purity 5 GA release and wanted to jump into VVOLs on my lab.
Customers will not be able to use vvols unless they manually install FNIC driver 220.127.116.11 or higher.
VVOLs are not supported on any VICs with the drivers installed from the current Cisco-branded v6.5 and 6.5U1 ESXi ISOs.
This is Cisco bug CSCux64473 Specific cause is because included driver did not support “Secondary LUN IDs”.
If a customer tries, their Protocol Endpoint will just never show up.
Symptom: UCS server with VIC adapter does not support VMware Virtual Volume feature
Conditions: When attempting to access Virtual Volume from UCS servers installed with VIC card.
Workaround: Virtual volume is not supported on any the VIC cards / FNIC drv ( Their but report isn’t totally true, I tested 18.104.22.168 driver and it worked great!)
- Latest driver release does work:
Now, after updating the driver and rebooting my servers, VVOLs is working awesome!
PureStorage does VVOLS right!