c240m4 will not see san boot paths after firmware upgrade

[Dragomir]

i got a c240 m4 server that after upgrading the firmware to 3.1(2e) will not see the boot from san path and now will not boot into the OS.

any idea?

[Kirk J]

Greetings.

Please confirm that your vHBA initiator WWPNs didn't get reset or changed.

The 'access denied' usually indicates a lun masking type issue.

Are these using a vic 1227?

Please check the output of your upstream FC switch (assuming cisco):

#show zoneset active vsan xx 

This may require some troubleshooting with TAC.

Thanks,

Kirk...

[Dragomir]

this looks like a problem after upgrading the firmware on the c240

I am looking at this bug

https://quickview.cloudapps.cisco.com/quickview/bug/CSCuv34051

anyone having these issues?

I got the esxi server back up, reordered the nics back to what it used to be. then rebooted and it got reorder again.

[Wes Austin]

Hello,

This is actually a hypervisor specific issue and has no dependency on UCS. This could occur on any vendor's server platform.

Here is the VMware KB:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2019871

We have customers who follow the workaround listed in the bug or as a pro-active step in order to avoid the problem before adding or removing interfaces, choose to manually order and place the vNICs instead of letting the system place it automatically.

This can be done from the Service profile -> Network -> Modify vNIC/vHBA placement -> Specify Manually (for Select Placement)

For existing configuration, place the vNICs manually according to the current order that they are placed to avoid triggering any re-ordering

HTH,

Wes

[Kirk J]

As to the SAN boot issue, how did you resolve that?

As far as vnic naming/ordering issues go, here is the VMware KB article: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2019871

Thanks,

Kirk...

[Wes Austin]

Tony,

The zoning needs to be investigated, as we are not being assigned an FCID and have no results in the nameserver query response.

-Wes