Those two link in lag mc 100 supposed to work as a redundant link (two different way of fiber). If one link fails, another should work. We were doing some test, and it's failed.
And also, TAC advice was to upgrade to newet version, we did it, but it didn't help. My version is 10.10.1030.
M.
Original Message:
Sent: Mar 25, 2023 04:15 AM
From: ninjawatcher
Subject: Aruba CX 8320 lag multi-chassis
Hi,
we seen something similar with an MC lag.
if one of the links is removed after a while we start to see pings dropped for a few seconds then come back this repeated continuously until the second link was brought up again or it was changed to. Lag rather than multi chassis.
we guessed that with the second link gone the switch was still trying to send traffic down the second link even though it was gone.
we were advised to upgrade our switch software, I can't remember what to now unfortunately.
my question would be why are you removing a link from the multi chassis lag?
Original Message:
Sent: Mar 24, 2023 06:26 AM
From: Davide Poletto
Subject: Aruba CX 8320 lag multi-chassis
Hi! can you better explain this sentence (regarding, I believe, how your ESXi and Firewalls are connected to VSX pairs) "Lately we disconnected secondary link, from those which are aggregated"? a simple drawing would help to start.
Original Message:
Sent: Mar 23, 2023 12:45 PM
From: mbrodzin
Subject: Aruba CX 8320 lag multi-chassis
Hi All,
My infrastructure consists of 3x VSX pairs of 8320 switches connected together via 40G links. Two of VSX pairs are connected via 2x 40G links aggregated in lag multichassis (two VSX pairs in DC1 and DC2, third VSX pair is in office).
To those two pairs of VSX switches (in DC1 and DC2) are connected esxi hosts and firewalls, all via 10G links. All L3 is on firewall, switches works only in L2.
Lately we disconnected secondary link, from those which are aggregated. Some time passed and strange things begin to happening in one of our vlans. Lost pings, even inside this vlan. We connected this link againg and everything went back to normal.
Created a TAC case, upgraded to newer firmware, 10.10.1030 and tested it againg. Same thing starts to happening.
Did anybody have similar issue?
Regards
M.