01-25-2017 11:17 PM - edited 03-08-2019 09:04 AM
Hi Everyone,
I have a WS-C2960XR-48FPS-I switch with 15.2(2)E5 software version and it keeps showing this alarm.
The switch is in stack.Anybody had experience this? Appreciate anybody could help me.
Jan 26 08:08:35.490 KWT: %PLATFORM_ENV-1-FRU_PS_ACCESS: FRU Power Supply is not responding (HO1-5TH-2960-XR-3)
Jan 26 08:08:40.495 KWT: %PLATFORM_ENV-1-FRU_PS_ACCESS: FRU Power Supply is not responding (HO1-5TH-2960-XR-3)
Jan 26 08:08:45.493 KWT: %PLATFORM_ENV-1-FRU_PS_ACCESS: FRU Power Supply is not responding (HO1-5TH-2960-XR-3)
Jan 26 08:08:50.495 KWT: %PLATFORM_ENV-1-FRU_PS_ACCESS: FRU Power Supply is not responding (HO1-5TH-2960-XR-3)
Jan 26 08:08:55.493 KWT: %PLATFORM_ENV-1-FRU_PS_ACCESS: FRU Power Supply is not responding (HO1-5TH-2960-XR-3)
Jan 26 08:09:00.498 KWT: %PLATFORM_ENV-1-FRU_PS_ACCESS: FRU Power Supply is not responding (HO1-5TH-2960-XR-3)
01-26-2017 12:27 AM
Hi
it could be this bug below , when you look at the power supplys are they up and working ?
Product: |
(1)
|
Known Affected Releases: |
(3)
|
Known Fixed Releases: |
(9)
|
Support Cases: |
(206)
|
01-28-2017 01:30 AM
Thank Mark Malone for the information. Appreciate it.
The switch is up even it keeps on showing this alarm.
01-29-2017 08:47 AM
you will need to change the software version to fix it or just leave it as its cosmetic if upgrading is not an option , if its flooding your syslog use logging discriminator to drop it
01-29-2017 09:33 PM
Again I thank you. we are going to upgrade the switch to the latest software version
(c2960x-universalk9-mz.152-2.E6)... Appreciate a lot.
06-28-2017 05:35 AM
I tried now Release 15.2(2)E6 and 15.2(4)E4. No success. Problem doesn't disappear.
06-29-2017 07:03 AM
Seems we have to wait till there is a fix for the following software bug: CSCve04418
From our environment I have seen the following:
Unfortunately no way to force bootldr upgrade.
02-21-2018 09:26 AM
06-21-2017 08:45 AM
We are facing the same issue with Catalyst WS-C2960XR-24PS-I. The affected switches are running 15.2(2)E5.
In any case we actually shouldn't have the issue anymore with 15.2(2)E5 :-(.
Any experience from others from which release this issue is solved? Next try for us would be 15.2(2)E6.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: