03-13-2019 07:45 AM
Is there a reason to explain why, after the VSX upgrade from 10.01.0030 to 10.02.0010, the VSX ISL Keepalive dedicated interface gained the ipv6 address link-local enablement automagically?
Discovered that on a diff between running configurations taken pre-/post-ArubaOS-CX upgrade.
Solved! Go to Solution.
03-13-2019 07:54 AM
Yes, there is one. I think it is documented in release note, but quick explanation.
in 10.2, IPV6 is disabled by default on interfaces. It was enabled in 10.1.
To keep feature consistency (IPv6 still enabled) between 10.1 and 10.2,
ipv6 address link-local is inserted in the configuration to maintain IPv6 enabled. If you don't need v6, you "simply" have to remove ipv6 address link-local from your interface configuration.
Re: ArubaOS-CX VSX: ipv6 address link-local enabled on VSX ISL Keepalive interface on AOS-CX 10.02
03-13-2019 08:08 AM
Just for reference, on ArubaOS-CX 10.02.0001 and 10.02.0010 Release Notes documents the most similar item I was able to find related to the ipv6 address link-local feature (provided that we're speaking of VSX ISL and so about VSX in general) is this one:
"VSX active-forwarding only works when the L3 interface is IPv4. Enabling it on an interface that has dual-stack or IPv6 may result in traffic losses."
listed among Feature Caveats. Are you referring to that one?