Guest

Preview Tool

Cisco Bug: CSCur35982 - LISP xTR doesn't register eid prefix if the prefix is unreachable

Last Modified

Feb 15, 2018

Products (8)

  • Cisco Nexus 7000 Series Switches
  • Cisco Nexus 7000 10-Slot Switch
  • Cisco Nexus 7000 4-Slot Switch
  • Cisco Nexus 7700 6-Slot Switch
  • Cisco Nexus 7000 18-Slot Switch
  • Cisco Nexus 7700 18-Slot Switch
  • Cisco Nexus 7700 10-Slot Switch
  • Cisco Nexus 7000 9-Slot Switch

Known Affected Releases

6.2(10)

Description (partial)

Symptom:
LISP xTR doesn't register eid prefix, even though more specific prefixes exist in the routing table. We should be registering the prefixes. which have more specific prefixes reachable as well.

Conditions:
See example:

R2# show ip lisp database
LISP ETR IP Mapping Database for VRF "default" (iid 0), global LSBs:
0x00000001

EID-prefix: 10.2.0.0/16, instance-id: 0, LSBs: 0x00000001, no-route
  Locator: 20.0.2.2, priority: 10, weight: 100
           Uptime: 00:04:32, state: up, local
R2# show ip route 10.2.0.0
IP Route Table for VRF "default"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]

10.2.0.0/24, ubest/mbest: 2/0
    *via 20.1.2.1, Eth2/1, [110/20], 00:10:01, ospf-1, type-2
    *via 20.1.2.3, Eth2/1, [110/20], 00:10:01, ospf-1, type-2
R2#

In this case 10.2.0.0/16 should still be registered to the mapping-system, even though no 10.2.0.0/16 route exists in the rib.
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.