Guest

Preview Tool

Cisco Bug: CSCul67326 - 511-SIT: spio_ea crash seen while removing ip address

Last Modified

May 09, 2018

Products (1)

  • Cisco ASR 9000 Series Aggregation Services Routers

Known Affected Releases

5.1.1.BASE

Description (partial)

Symptom:
spio_ea process crash on the line card.
Once a crash has happened and the process has restarted, there is less that can be done from customer end to verify if this is the root cause.
The crash logs shall have the following string with a "non-zero and high value of the BadAddr":

LC/0/0/CPU0:Nov 27 01:54:26.304 : dumper[56]: %OS-DUMPER-4-SIGSEGV_INFO : Accessed BadAddr4b32170c. Signal code 1 - SEGV_MAPPER. Address not mapped. \

Though, this does not guarantee the same issue, but could give a hint regarding the same.

Conditions:
CFM sessions configured on physical (sub)interfaces on typhoon card.
  PTP sessions configured on physical/bundle (sub)interfaces
The trigger is too many occurence of one or more of following events. The events may occur over a long period of time, or over a short period as well if the 
number of CFM/PTP sessions are high. When the event count crosses over a consolidated count of 65K events (across all sessions), then this problem is likely to 
happen.
List of events:
> Configuration changes in CFM/PTP by user, which affects one or more sessions (more the sessions affected, more the events generated internally), like keep-alive 
interval changes, enabling/disabling any features on the sessions (like EFD) etc.
> State changes in the interfaces over which CFM/PTP is configured (interface going up/down, adding/removing from l2vpn etc.)
> State changes in the sessions themselves (example: Remote Defect Indication toggle etc.)
All such events (for any of the sessions) internally keep on adding up in a single counter. The issue can happen if this internal count crosses
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.