VC network changes with powered on blades

[chuckk281]

Bob had a customer question:

***************

Customer has 2 identical enclosures with BL460G7 blades and VC. Same firmware on all components and same OS/apps on the blades.

He’s trying to add the same network to each enclosure and associate the new network to the appropriate blades.

On one enclosure he’s able to do this just fine, and the new network shows up in the OS.

On the other enclosure he can add the network, but can’t associate it to the blades. He gets the message, “server power state is incompatible with the current operation”.

Any idea why two identical environments would get different results?

***************

Info from Dave:

*************

The servers need to be powered off for VC to assign the profile.

VC profile interrogates the blade at POST and configures the additional NICs accordingly, is FCoE, iSCSI or Ethernet…

*************

Any other comments or questions?