Loading...
Loading...
Router crashed over long run.
Long soak run of interface flap, clear IGP , clear ip route
No workaround.
Root Cause: The fid_handle stored in label_data is already freed, we are crashing on trying to access a freed fwd_handle. In this case as the label_data has a freed fwd_handle, someone else has freed this handle already. Fix Description: Existing code we are checking that the allocated label is real label then assigning label_data->asic_fwd_handle to fwd_handle. As per the bug id CSCup25290 if the label is real label it must be set is_my_fwd_handle to true. From the logs have found that the label is real label and is_my_fwd_handle is false. So to prevent the router from crashing in current implementation we have added check if is_my_fwd_handle is false and the allocated label is real label assigning NULL to the fwd_handle. Fix Limitations: I added error messages, if a label_data is trying to free the fwd_handle that does not belong to it (boolean my_fwd_handle is false). I could hit these error messages in two cases: 1. pw_bind, when we delete the old fwd_handle. 2. pw_unbind, we are delete the label_data. This particular label was a real label, the reason why this was holding a fwd_handle, that does not belong to it is unknown. I checked the setup when these error messages were seen, and there was no functional impact. We have to investigate why the atom real label, is holding a fwd_handle, that does not belong to it. And, if this would have any other impact.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.