Guest

Preview Tool

Cisco Bug: CSCvu69077 - Old LISP mobility commands not removed after changing the critical IP address pools

Last Modified

Oct 11, 2020

Products (1)

  • Cisco DNA Center

Known Affected Releases

DNAC1.3.3.5

Description (partial)

Symptom:
When the Voice/Data critical IP address pools attached to the virtual network (VN) on the "Host Onboarding" page are changed, and added back with a custom authentication policy name, the previous corresponding LISP mobility statement may not be deconfigured by Cisco DNA Center on the edge device.


Example - 
!
interface Vlan2047
<snip>
 vrf forwarding VN1
 ip address x.x.x.x 255.255.255.0
<snip>
 lisp mobility X_X_X_X-VN1-IPV4     <===  Old statement
 lisp mobility CRITICAL-DATA1-VN1-IPV4     <=== Old statement
 lisp mobility CRITICAL-DATA2-VN1-IPV4     <=== Current Data Critical VLAN authentication Policy (CRITICAL-DATA2)

Conditions:
This has been seen only when using a custom "Authentication Policy" when adding a critical IP address pool to a  VN, and this previous configuration being left behind does not happen every time.
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.