Wired Intelligent Edge

Hello All,

I'm seeing, what I believe to be an odd behavior, but wanted to see if anyone could help explain. We have a pair of 8325s in a VSX Pair. Port 1/1/7 on each member is part of a multi-chassis lag (lag7)

When both links are up, everything works as you would expect. The weirdness I am seeing, is if I administratively shut one of the ports. (For example, if I shut 1/1/7 on the VSX Primary, but leave 1/1/7 on the secondary online and available), I still see MAC-Address learnt on the port

What I see, is the VSX Primary is still showing MAC-Addresses on LAG7.

That seems strange to me because the physical link is down, I would have expected it to show all the MAC-Address to then come from the ISL?. This issue still occurs even if I physically disconnect the module/fiber.

I do have a case open for this and am going to test in our lab, but just curious if this is an expected behavior.

Thanks all,
Chris

Hello All,

I'm seeing, what I believe to be an odd behavior, but wanted to see if anyone could help explain. We have a pair of 8325s in a VSX Pair. Port 1/1/7 on each member is part of a multi-chassis lag (lag7)

When both links are up, everything works as you would expect. The weirdness I am seeing, is if I administratively shut one of the ports. (For example, if I shut 1/1/7 on the VSX Primary, but leave 1/1/7 on the secondary online and available), I still see MAC-Address learnt on the port

What I see, is the VSX Primary is still showing MAC-Addresses on LAG7.

That seems strange to me because the physical link is down, I would have expected it to show all the MAC-Address to then come from the ISL?. This issue still occurs even if I physically disconnect the module/fiber.

I do have a case open for this and am going to test in our lab, but just curious if this is an expected behavior.

Thanks all,
Chris

Hello All,

I'm seeing, what I believe to be an odd behavior, but wanted to see if anyone could help explain. We have a pair of 8325s in a VSX Pair. Port 1/1/7 on each member is part of a multi-chassis lag (lag7)

When both links are up, everything works as you would expect. The weirdness I am seeing, is if I administratively shut one of the ports. (For example, if I shut 1/1/7 on the VSX Primary, but leave 1/1/7 on the secondary online and available), I still see MAC-Address learnt on the port

What I see, is the VSX Primary is still showing MAC-Addresses on LAG7.

That seems strange to me because the physical link is down, I would have expected it to show all the MAC-Address to then come from the ISL?. This issue still occurs even if I physically disconnect the module/fiber.

I do have a case open for this and am going to test in our lab, but just curious if this is an expected behavior.

Thanks all,
Chris

Hello All,

I'm seeing, what I believe to be an odd behavior, but wanted to see if anyone could help explain. We have a pair of 8325s in a VSX Pair. Port 1/1/7 on each member is part of a multi-chassis lag (lag7)

When both links are up, everything works as you would expect. The weirdness I am seeing, is if I administratively shut one of the ports. (For example, if I shut 1/1/7 on the VSX Primary, but leave 1/1/7 on the secondary online and available), I still see MAC-Address learnt on the port

What I see, is the VSX Primary is still showing MAC-Addresses on LAG7.

That seems strange to me because the physical link is down, I would have expected it to show all the MAC-Address to then come from the ISL?. This issue still occurs even if I physically disconnect the module/fiber.

I do have a case open for this and am going to test in our lab, but just curious if this is an expected behavior.

Thanks all,
Chris

In https://www.arubanetworks.com/techdocs/AOS-CX/10.10/PDF/vsx.pdf

you find:

VSX has similar benefits as Virtual Switching Framework (VSF), however, VSX also offers better high
availability required in core and data center environments. VSX binds two AOS-CX switches of the same
model type to operate as one device for layer 2. VSX also operates as independent nodes for layer 3.

show mac-address-table 

and

show mac-address-table vsx-peer

should show the same table if they are in sync.

Hello All,

I'm seeing, what I believe to be an odd behavior, but wanted to see if anyone could help explain. We have a pair of 8325s in a VSX Pair. Port 1/1/7 on each member is part of a multi-chassis lag (lag7)

When both links are up, everything works as you would expect. The weirdness I am seeing, is if I administratively shut one of the ports. (For example, if I shut 1/1/7 on the VSX Primary, but leave 1/1/7 on the secondary online and available), I still see MAC-Address learnt on the port

What I see, is the VSX Primary is still showing MAC-Addresses on LAG7.

That seems strange to me because the physical link is down, I would have expected it to show all the MAC-Address to then come from the ISL?. This issue still occurs even if I physically disconnect the module/fiber.

I do have a case open for this and am going to test in our lab, but just curious if this is an expected behavior.

Thanks all,
Chris

Thanks Everyone,

I wish there was a diagnostic tool to view the forwarding table (looks like maybe 10.11 has that?) regardless, I confirmed on a few different VSX setups we have this is intended behavior.

Was seeing some strange issues downstream and wanted to verify.

Thanks again, everyone

In https://www.arubanetworks.com/techdocs/AOS-CX/10.10/PDF/vsx.pdf

you find:

VSX has similar benefits as Virtual Switching Framework (VSF), however, VSX also offers better high
availability required in core and data center environments. VSX binds two AOS-CX switches of the same
model type to operate as one device for layer 2. VSX also operates as independent nodes for layer 3.

show mac-address-table 

and

show mac-address-table vsx-peer

should show the same table if they are in sync.

Hello All,

I'm seeing, what I believe to be an odd behavior, but wanted to see if anyone could help explain. We have a pair of 8325s in a VSX Pair. Port 1/1/7 on each member is part of a multi-chassis lag (lag7)

When both links are up, everything works as you would expect. The weirdness I am seeing, is if I administratively shut one of the ports. (For example, if I shut 1/1/7 on the VSX Primary, but leave 1/1/7 on the secondary online and available), I still see MAC-Address learnt on the port

What I see, is the VSX Primary is still showing MAC-Addresses on LAG7.

That seems strange to me because the physical link is down, I would have expected it to show all the MAC-Address to then come from the ISL?. This issue still occurs even if I physically disconnect the module/fiber.

I do have a case open for this and am going to test in our lab, but just curious if this is an expected behavior.

Thanks all,
Chris