Cisco – DCNM, why are you like this?

I thought it would be a good idea to upgrade the copy of Cisco DCNM installed on my laptop (in standalone mode) from 5.2(2) to 6.1(1) the other day. I ran the 32-bit installer and got an error about “Upgradation” being unsupported from this mode.


This probably should have set off alarm bells. But I hadn’t read the release notes, and wasn’t really paying attention. So I dutifully uninstalled 5.2(2) and had another go at it.


Sigh. I know that in production you wouldn’t be using a Windows 7 laptop to run this software. And I know that I should have carefully read the requirements before I attempted installation. If I had, I would have read this: “Cisco DCNM SAN Release 6.1(1a) and later releases do not support running the Cisco DCNM SAN client in standalone mode. If you were running the SAN client in standalone mode in Release 5.2(x), you should uninstall it and install Cisco DCNM SAN server Release 6.1(1a) or a later release. You cannot upgrade the standalone SAN client from DCNM Release 5.2(x) to Release 6.1(1a) or a later release”. But surely it could have popped up with this warning before telling me that I had to uninstall 5.2(2) first? DCNM developers have moved back to the top of my list. If they can’t code around my ignorance and laziness then I want no part of their product. And what the hell is “Upgradation” anyway?

EMC – PowerPath/VE on vSphere 4.1

Sometimes, and for what seems like no good reason, we have hosts in our vSphere clusters that seem to not have such a happy time with PowerPath/VE. I can tell you the symptoms, but can’t tell you the cause.

It should look like this.

The workaround we’ve come up with is to put the host into Maintenance Mode, uninstall PP/VE, and reinstall.

Here’s the commands you’ll need to run via the vMA. (BTW we still have issues with passthrough AD authentication on the ESXi boxes when using vMA – but I don’t care anymore).

login as: domain\adminuser
Using keyboard-interactive authentication.
Welcome to vMA
run ‘vma-help’ or see for more details.

[domain\adminuser@vMAhost ~]$ vifptarget -s vCenterhost

[domain\adminuser@vMAhost ~][vCenterhost]$ vihostupdate –server esxi.domain.internal –query
Enter username: root
Enter password:
———Bulletin ID———         —–Installed—–                 —————-Summary—————–
hp-nmi-driver-1.1.02                2010-11-27T03:20:56     HP NMI Sourcing Driver for VMware ESX/ESXi 4.1
hpq-esxi4.1uX-bundle-1.0a  2010-11-27T04:06:02     HP ESXi Bundle 1.0a
EMC-PP5.     2010-11-27T04:39:12       PowerPath 5.4.SP2 for ESX
ESXi410-201011401-BG            2010-12-15T00:45:41      Updates Firmware
VEM410-201010411-BG           2011-02-15T02:42:29      Cisco Nexus 1000V VEM
VEM410-201010112-BG           2011-02-15T02:42:29      Cisco Nexus 1000V  4.0(4)SV1(3b)
VEM410-201101108-BG           2011-02-15T03:57:07     Cisco Nexus 1000V  4.2(1)SV1(4)

[domain\adminuser@vMAhost ~][vCenterhost]$ vihostupdate –server esxi.domain.internal –remove –bulletin EMC-PP5.
Enter username: root
Enter password:
Error encountered:
   Message     – The update completed successfully, but the system needs to be rebooted for the changes to be effective.

[domain\adminuser@vMAhost ~][vCenterhost]$