Guest

Preview Tool

Cisco Bug: CSCuj08205 - oneP: next hop EC is 0 after async update

Last Modified

May 10, 2018

Products (1)

  • Cisco ASR 9000 Series Aggregation Services Routers

Known Affected Releases

5.1.0.BASE

Description (partial)

Symptom:
A call to onep_routing_l3_ucast_next_hop_get_ec  to get the next hop EC after an async operation unexpectedly returns 0.

Conditions:
After a route operation, the expected error codes returned by onep_routing_l3_ucast_next_hop_get_ec are:
1 - ROUTING_ROUTE_EC_SUCCESS
4 - ROUTING_ROUTE_EC_FAILURE

After a call to the async API, the next_hop_ec is returned as 0 instead of 1 or 4
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.