-
Notifications
You must be signed in to change notification settings - Fork 43
Description
(use upvote 👍 for attentions)
Validation Type
[ ] - Fault
[ ] - Config
[X] - Bug
[ ] - Other
What needs to be validated
[CSCvu25176] IP address conflict between vPC VIP and Spine Anycast IPV6 address
Newly created vPC VIP was assigned the same ip address as the already assigned anycast IPV6 address for the spines, ipv6expg-default. This was causing the traffic to be intercepted and processed by the spine instead of forwarded to the leafs.
Why it needs to be validated
Its possible that this issue may not be visible in steady state if the leaf pair does not have any active VPC port channels.
The pre upgrade script can help bring this to customer attention
Check the output of these two moquery and it should match.
COLO-C220M4-APIC01# moquery -d "client-[uni/fabric/ipv6protp-default/ipv6expg-default]" | grep ^ip
ip : 10.202.112.66/32
COLO-C220M4-APIC01# moquery -d "uni/fabric/ipv6protp-default/ipv6expg-default" | grep ^virtualIp
virtualIp : 10.202.112.66/32
If different then raise a warning to follow the workaround listed under CSCvu25176