OPERATIONAL DEFECT DATABASE
...
...
A Csco switch may experience a crash within SISF: UNIX-EXT-SIGNAL: Segmentation fault(11), Process = SISF Main Thread
SISF is used implicitly by DHCP snooping via the DT-PROGRAMMATIC or WL-DEV-TRACK-DHCP policy. Having DHCP snooping enabled for multiple VLANs were one of the known trigger conditions to hitting this issue.
User can check if device-tracking is enabled on trunk port, in which case, a large number of bindings could be learnt from the neighbour switch and increase CPU and memory utilization. To disable learning device-tracking bindings from trunk port, follow below. config t device-tracking policy DT_trunk_policy trusted port device-role switch interface device-tracking attach-policy DT_trunk_policy
The root cause of CSCvg26012 is that many internal events were hooked onto the same policy (no matter what the policy name is). When we tries to process an event, searching this event from an internal cache takes time, the more entries in the table and incoming control packets (ARP/ND), the longer the searching takes, which eventually causes CPU hog and high memory.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
