10-23-2012 10:30 AM - edited 03-01-2019 10:42 AM
We recently enabled smtp callhome for our ucs pod a few days ago. Since then, we've received more than a dozen email bursts about power supply failures in each of the four Cisco Nexus 2232TP FEXs in our pod. In each case, we get a "Recovered" email within a minute or two, and we're not seeing power supply failure emails for any other devices within the UCS pod.
Here's a sample email burst from this morning, showing the subject lines within my email inbox:
System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:01:27 GMT-00:00 Recovered : Power supply 2 in fex 6 operability: inoperable
System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:01:27 GMT-00:00 Recovered : Power supply 2 in fex 6 operability: inoperable
System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:01:27 GMT-00:00 Recovered : Power supply 2 in fex 6 operability: inoperable
System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:01:27 GMT-00:00 Recovered : Power supply 2 in fex 6 power: error
System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:01:27 GMT-00:00 Recovered : Power supply 2 in fex 6 power: error
System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:01:27 GMT-00:00 Recovered : Power supply 2 in fex 6 power: error
System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:00:58 GMT-00:00 Power supply 2 in fex 6 operability: inoperable
System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:00:58 GMT-00:00 Power supply 2 in fex 6 operability: inoperable
System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:00:58 GMT-00:00 Power supply 2 in fex 6 operability: inoperable
System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:00:58 GMT-00:00 Power supply 2 in fex 6 power: error
System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:00:58 GMT-00:00 Power supply 2 in fex 6 power: error
If we were seeing this from just one fex, I'd suspect a hardware issue. If any of the other UCS devices (rackmount/blade servers, fabric interconnects, etc) reported similar issues, I'd suspect a power feed problem within the DC.
But this has me baffled. If it helps, the UCS pod is running firmware 2.0.3c
Cheers,
Paul
Solved! Go to Solution.
10-25-2012 07:38 AM
Thanks Paul,
It is known ( cosmetic ) issue with power supply model.
The above is resolved in recent version of Nexus 5K switch software. New defect to port the fix to UCSM has been submitted today
It will take a while to get published on web site.
Even though they are cosmetic, I would suggest you open a TAC SR with UCSM, FEX tech support and above bug IDs so that we can track the resolution.
HTH
Padma
10-24-2012 10:36 PM
Hello Paul,
can you please share following output
scope fex
show psu detail
connect nxos
show logging | egrep -i 'power|gpio'
Padma
10-25-2012 07:26 AM
10-25-2012 07:38 AM
Thanks Paul,
It is known ( cosmetic ) issue with power supply model.
The above is resolved in recent version of Nexus 5K switch software. New defect to port the fix to UCSM has been submitted today
It will take a while to get published on web site.
Even though they are cosmetic, I would suggest you open a TAC SR with UCSM, FEX tech support and above bug IDs so that we can track the resolution.
HTH
Padma
10-25-2012 12:27 PM
Thanks for the reply, and it's a bit of a relief that this is a known issue. I'll open a TAC SR as you suggest.
Cheers,
Paul
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide