Showing posts with label UCS. Show all posts
Showing posts with label UCS. Show all posts

Friday, March 28, 2014

After patching ESXi, Esxi disconnected from 1000V Cisco Switch (root cause is UUID all zero's)

Last week, I had patched 2 of  my ESXi that running on UCS. after I did patching,  I checked these 2 ESXi's standard and 1000V switch network configurations and port groups, everything was available and released system to production.

since my DRS in partially automated mode, This week, my colleague moved some servers to these ESXi and he found that VM's network connection failed.

I logged in to V center and found that  in Distributed 1000 V switch trust up-link and UN-trust unlink VLAN access has been changed to native VLAN 1 as below



then I have logged in to the 1000V switch and checked the VEM modules. I  found that one of the issue server UUID had changed all zero's and another server  VEM module was missing



Therefore i have logged in to both issue ESXI and checked Hardware UUID.  found as below that these two servers Hardware UUID is all Zero

So I assumed that Since the both system has all zero's in UUID, the 1000V is connected with first  system that I rebooted first ( eventhough all zero's, it's unique ID) and the second server was not connected because it has the same all zero's Unique ID and it's conflicted.

Solution: as I mentioned these EXI running on UCS, I rebooted these blade servers more than twice but the UUID was not changed from all zero's.  So I updated the BIOS version of both blade servers and The UUID has changed to the original and both ESXI system was connected to 1000V switch and network connection also established very well as usual.


Thursday, October 10, 2013

CISCO UCS balde / fabric / path down; reason waiting for flogi ALERT

Today I have patched my esxi server which is installed in UCS blade server and rebooted. after I reboot, I found in UCS Manager that there is two alarm was triggered as below but it supposed to be cleared automatically
Solution:

solution 1: once again I rebooted but this time the same alert triggered on fabric B. then I just found  the quick solution is need to just shutdown the server for 1 or 2 mins and power it on again. now there is no more error in the ucs manager, all alert was cleared automatically it self.

Easiest Solution:

check which server HBA having this issue and reset connectivity for that HBA. So that It will be soaked again and will get resolved



Cisco reason for the cause:

This is know issue in UCS. Bug no is CSCtn89396 and upgrade the UCS to latest Cisco suggested version