Cisco ACI 4.2(7l) & L3out Cat9500 17.3.4 -Leaf switches crashed on PIM

[Nilay Patel]

C9500-48Y4C - 17.3.4 (L3-out connected to ACI) 

Cisco ACI 4.2(7l) Controller | n9000-14.2(7l) (No change made on ACI)

on Cat 9500 command entered

ip pim bidir-enable

no ip multicast-routing

ip multicast-routing

Leaf Switches were crashed: any idea (switch core crash file generated - services name "PIM" Process 23122)

[Robert Burns · Accepted solution]

Could be a bug - but not sure as you didn't detail the leaf model.   For these type of issues, best to open a TAC case so they can decode the dump.  Other than that, we'd be guessing/shooting in the dark.
As I like shooting in the dark, could possibly be CSCwb39899. Need the dump signature to confirm though.

Robert

[Nilay Patel · Accepted solution]

Thanks a lot!

exact same issue as you shared but we are running 14.2(7l)

module-1# show logging onboard internal reset-reason

Last log in OBFL was written at time Sat Oct 29 17:37:45 2022

Reset Reason for this card:
Image Version : 14.2(7l)
Reset Reason (LCM): Unknown (0) at time Fri Oct 28 18:34:37 2022
Reset Reason (SW): Reset triggered due to HA policy of Reset (16) at time Fri Oct 28 18:27:42 2022
Service (Additional Info): pim hap reset
Reset Reason (HW): Reset triggered due to HA policy of Reset (16) at time Fri Oct 28 18:34:37 2022
Reset Cause (HW): 0x01 at time Fri Oct 28 18:34:37 2022
Reset internal (HW): 0x00 at time Fri Oct 28 18:34:37 2022

Last log in OBFL was written at time Fri Oct 28 17:48:45 2022

Reset Reason for this card:
Image Version : 14.2(7l)
Reset Reason (LCM): Unknown (0) at time Fri Jul 8 14:50:39 2022
Reset Reason (SW): Reset Requested by CLI command reload (9) at time Fri Jul 8 14:43:43 2022
Service (Additional Info): PolicyElem Ch reload
Reset Reason (HW): Reset Requested by CLI command reload (9) at time Fri Jul 8 14:50:39 2022
Reset Cause (HW): 0x01 at time Fri Jul 8 14:50:39 2022
Reset internal (HW): 0x00 at time Fri Jul 8 14:50:39 2022

[Robert Burns · Accepted solution]

Then you're likely affected.  This bug wasn't fixed until 14.2(7u) - or the listed 15.2(x) versions in the bug note.

Robert