cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
35974
Views
45
Helpful
23
Replies

CSCvj49423 - %SIF_MGR-1-FAULTY_CABLE:Switch 1 R0/0

John LaFrance
Level 1
Level 1

Cisco 3850-48F-L, Denali IOS 16.3.5b, uptime is 9 weeks, 6 days.

 

Seeing repeating log errors:

Sep 4 12:00:08: %SIF_MGR-1-FAULTY_CABLE:Switch 1 R0/0: sif_mgr: High hardware interrupt seen on switch 1
Sep 4 12:01:08: %SIF_MGR-1-FAULTY_CABLE:Switch 1 R0/0: sif_mgr: High hardware interrupt seen on switch 1
Sep 4 12:01:23: %SIF_MGR-1-FAULTY_CABLE:Switch 2 R0/0: sif_mgr: High hardware interrupt seen on switch 2
Sep 4 12:02:08: %SIF_MGR-1-FAULTY_CABLE:Switch 1 R0/0: sif_mgr: High hardware interrupt seen on switch 1

23 Replies 23

fdharmawan
Level 4
Level 4

Hi John,

 

Today I found the same log again. I replaced the cable and so far the switch works normally. Will monitor the condition for the next few days.

 

Do you have any spare stack cable? If so, try to replace the cable if the log still persists.

 

Cheers.

takhzar
Cisco Employee
Cisco Employee

Hi, 

Do we have any updates regarding the problem? I am experiencing the same problem with the firmware Version 16.3.6.

Sep 27 10:22:33.408 UTC: %SIF_MGR-1-FAULTY_CABLE:Switch 2 R0/0: sif_mgr: High hardware interrupt seen on switch 2
Sep 27 10:22:39.314 UTC: %SIF_MGR-1-FAULTY_CABLE:Switch 1 R0/0: sif_mgr: High hardware interrupt seen on switch 1
Sep 27 10:22:46.841 UTC: %SIF_MGR-1-FAULTY_CABLE:Switch 3 R0/0: sif_mgr: High hardware interrupt seen on switch 3
Sep 27 10:22:49.790 UTC: %SIF_MGR-1-FAULTY_CABLE:Switch 4 R0/0: sif_mgr: High hardware interrupt seen on switch 4

Cheers.


@takhzar wrote:

Do we have any updates regarding the problem? I am experiencing the same problem with the firmware Version 16.3.6.


Upgrade to the latest final 16.3.X release, 16.3.11 (20 August 2020) or the final 16.6.10 (25 August 2021).

@takhzar no change on this issue; I have not tried swapping out any suspect stack cables, and this switch is still operational on IOS 16.3.7 after 1 year, 7 weeks; no user impact, CPU averages 12-15% and no incrementing "changes to link" counters either.

AlexMarques
Level 1
Level 1

Hi Community

 

I had the similar problem with a C9300 in the stack and it occurred on the 4th stackswitch, on the last one. (IOS 17.3.4)

 

The solution for my problem was, with the command "sh switch stack-ports detail" I could see some CRC errors. So I replaced the stack module. Then I reset the counters and watched the whole thing. Since then I have no more problems.

jktan-1110
Level 1
Level 1

Dear Community,

 

I am observing same system messages on WS-C3650-24PS on IOS 16.6.6.

Error msg in switch logs: 

%SIF_MGR-1-FAULTY_CABLE: Switch 1 R0/0: sif_mgr: High hardware interrupt seen on switch 1

 

I have not found any solution yet, a reload was issued and the problem cleared itself only for first 30 minutes and then the messages appeared again in switch logs. I wonder if this could be a cosmetic bug as the switch is functioning well.

 

Please find below output from the switch: 

Switch#show switch detail
Switch/Stack Mac Address : b0aa.77b4.ab80 - Local Mac Address
Mac persistency wait time: 7 mins
H/W Current
Switch# Role Mac Address Priority Version State
-------------------------------------------------------------------------------------
*1 Active b0aa.77b4.ab80 15 V01 Ready
2 Standby 881d.fcb0.a280 13 V01 Ready

 

Stack Port Status Neighbors
Switch# Port 1 Port 2 Port 1 Port 2
--------------------------------------------------------
1 OK OK 2 2
2 OK OK 1 1

Switch#show switch stack-ports summary
Sw#/Port# Port Status Neighbor Cable Length Link OK Link Active Sync OK #Changes to LinkOK In Loopback
-------------------------------------------------------------------------------------------------------------------
1/1 OK 2 50cm Yes Yes Yes 1 No
1/2 OK 2 50cm Yes Yes Yes 1 No
2/1 OK 1 50cm Yes Yes Yes 1 No
2/2 OK 1 50cm Yes Yes Yes 1 No

I have also referred to C3K Troubleshooting Notes on CiscoLive: 
https://www.ciscolive.com/c/dam/r/ciscolive/us/docs/2019/pdf/BRKARC-3146.pdf
-Pg 35

However, this document doesn't provide any solution to the stack issue I am facing.

Welcome every member on Cisco Community to guide me on this. 

Thanks & Regards,

JK

RMA the stacking cables.

@Leo Laohoo Even though the stack ports status appeared to be good, I should still proceed with the RMA of stacking cables? Is there any other things I should try first before the RMA? Also, can advise if this is a cosmetic bug?

Eliminate all possibilities -- RMA the stacking cables.