If anyone out there knows of anyone using HP Blade Chassis and Virtual Connect modules, you may want to send this to them:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02720395&lang=en&cc=us&taskId=101&prodSeriesId=1844065&prodTypeId=329290 The wrong DNS lookup to the device could result in a DoS, the entire VC goes dark (or both do if you have redundant VCs). If you happen to use 10.x.x.x range internal hosts, then chances are you've already seen this problem. The firmware update to fix this is still pending. Doing anything to fix it takes the VC module off-line and requires a reset. Right now, remove any configured EBIPA DNS servers in the OA. Via the OA CLI (fair warning, causes a VC reset): remove EBIPA SERVER DNS <your DNS server> Some very special developer dreamed up this problem. I'll spare you the details. Some crafty googling of c7000 VC ethernet DNS issues will find them. -Ryan PS - If you happen to have any older DL3** G4s lying around, and you use hpacucli to monitor a RAID array - update your HP utils to the latest version. Trust me, you will regret it if you don't. /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
