Cisco 9200L 48P 4x-Critical process sif_mgr fault on rp_0_0 (rc=143)

[qinisani-qn]

Last reload reason : Critical process sif_mgr fault on rp_0_0 (rc=143) I got this error message after a switch stack rebooted yersterday. Any idea what could cause this?

Switch: Cisco 9200L 48P 4x
Firmware: 17.12.04

[balaji.bandi]

Looks for me Software Bug, contact tac for suggested version or possible Lower the stable version like 17.9.5

If you like to pursue the issue, check the below logs :

1. dir flash: core
2. dir crashinfo:
3. dir flash:tracelogs

[qinisani-qn]

Hi @balaji.bandi I have the crash log files but they are in .bin format can I send them to via email?

[balaji.bandi]

Logs always readble format and attach here. also check do you have constant any logs (show logging that give indication something wrong with stack cable ?)

[Leo Laohoo]

Is this switch a member of a stack?  If it is, has there been any history of stacking cable errors? 

If not, look at CSCwj16356.

[Diagor]

Hi Leo 

This switch in question is a member in a stack of 2 

it is switch 2 in the stack .

and this is a New Build so no prior stacking cable issues 

[Leo Laohoo]

Is IP Device Tracking (IPDT) turned on?

[qinisani-qn]

We have device-tracking attach-policy IPDT_POLICY enabled on all the access ports. This was done recently. Could this have an impact or result in the issue that we are witnessing? 

[Leo Laohoo]

SISF stands for Switch Integrated Security Feature and IP Device Tracking is the cornerstone.  

[qinisani-qn]

SISF stands for Switch Integrated Security Feature and IP Device Tracking is the cornerstone.  

Can you kindly expand on what you mean by this, does the above indicate that I need remove this configuration on the interfaces of our switches?
device-tracking attach-policy IPDT_POLICY

[Leo Laohoo]

Something in the IPDT settings caused the crash.  

[Rahul NIrmalkar]

Here are a few steps you can take to troubleshoot and resolve the issue
Look for any software bugs.
Confirm the reason for the stack reload.
Inspect for any errors in the stack cables.

[Leo Laohoo]

---

@Rahul NIrmalkar wrote:

Look for any software bugs.
Confirm the reason for the stack reload.
Inspect for any errors in the stack cables.

---

No one can deny this is not a ChatGPT-generated response.