cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
810
Views
0
Helpful
4
Replies
Highlighted

Odd power supply fault callhome emails on Cisco 2232 FEXs?

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

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Thanks Paul,

It is known ( cosmetic ) issue with power supply model. 

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtz84683

The above is resolved in recent version of Nexus 5K switch software. New defect to port the fix to UCSM has been submitted today

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCuc87547

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

View solution in original post

4 REPLIES 4
Highlighted
Cisco Employee

Hello Paul,

can you please share following output

scope fex

show psu detail

connect nxos

show logging | egrep -i 'power|gpio'

Padma

Highlighted

Padma,

Thanks for the reply. I've attached the requested information, and let me know if I can provide any additional details.

Cheers,

Paul

Highlighted

Thanks Paul,

It is known ( cosmetic ) issue with power supply model. 

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtz84683

The above is resolved in recent version of Nexus 5K switch software. New defect to port the fix to UCSM has been submitted today

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCuc87547

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

View solution in original post

Highlighted

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

Content for Community-Ad