Hello Adam, in a similar scenario if I were you I would switch from a non-Protocol (Trunk) Port Trunk to a LACP driven Port Trunk, on both ends this means:
trunk C12,C13 trk4 lacp <- HP ProCurve 5308 side
trunk 1/48,3/48 trk2 lacp <- VSF Aruba 2930F side
and here
show lacp and
show trunk commands are your friends.
To perform the change (from trunk mode to lacp mode) you should destroy the <Trk-Id> logical interfaces on both ends so plan it accordingly (expect some disruption).
Also check VLAN memberships of both <Trk-Id> logical interfaces to see if they match each others: use the
show vlan ports ethernet <trkX> details command (VLANs membership's patterns should match in a trk4
versus trk2 comparison).
Verify settings of C12, C13, 1/48 and 3/48 interfaces in order to see if they "match" (especially Speed and Duplex mode, say all 1Gbps and all Full-Duplex Auto-Negotiation); if you're going to change trunk mode to lacp mode on those Port Trunks do start from physical interfaces in their default state (clear statistic counters, reset VLAN membership to VLAN 1 default untagged)...in other terms, if you have doubts, try to start from scratch, it's not mandatory nor essential...but it could help...you can also just reconfigure them (with cabling disconnected)...it's just a way to do things
step-by-step starting from a known operational state.
I would also check the VSF status of your three Aruba 2930F Switches (since you're terminating the physical links coming from the standalone HP ProCurve 5308xl C12 and C13 ports, respectively into VSF Member 1 port 48 and VSF Member 3 port 48...the good health of VSF plays a role here).
A well formed Port Trunk (Link Aggregation) should have no issue with Spanning Tree since (M|R)STP, once enabled, will see the aggregation as one interface (so no blocking action will occur on Port Trunk member interfaces).
Eventually you can do few customizations on Trunk ports (as example, set the point-to-point mac option to true on both the logical Trk4 and Trk2 interfaces <- this because the link is between two peer switches).
Hope you're moving from a standalone HP ProCurve 5308xl to a VSF of Aruba 5400R zl2...or, at least, to a single Aruba 5400R zl2 with two Management Modules (with NonStop Redundancy enabled)...if you are forced to use the HP ProCurve 5308xl for longer than expected then a good thing would be to use Trk4 member ports from different modules (if you can)...so if a module in which there is one member port fails, the Trk4 will survive.
------------------------------
Davide Poletto
------------------------------
Original Message:
Sent: Sep 24, 2021 07:36 PM
From: Adam Forsyth
Subject: Trunk configuration of an uplink between switches
I have a 5308 switch acting as a building router (I know it's super old, and have plans to upgrade it with a 5406R in a few weeks, but doing it in 2 parts is how this network upgrade ended up working out). It's connected to a VSF of 3 2930F switches with a trunk of 2 1000BT connections.
On the 5308 the trunk is configured like this:
trunk C12-C13 Trk4 Trunk
On the 2930F side the trunk is configured like this:
trunk 1/48,3/48 trk2 trunk
This should match and work properly, right? I do it all the time in lots of different places on our network, and it works just fine. I ask because this configuration had been working fine for a few weeks, but yesterday I got reports that users on the network in this building were having difficulty. I started looking into it and found that we were having packet loss of 60% or more, and when pinging different things ping was reporting duplicates being received.
So, I started suspecting a network loop (despite the fact that spanning tree is configured and should eliminate a loop should a user create one). I finally figured out the loop was the connection between these two switches. If I disconnected one of the links, the network would recover and everything would start working fine again. If I reconnected it, performance would degrade and I'd start seeing the duplicate ping packets again.
For now I've left the uplink with one connection of the trunk unplugged, and it continues to work fine. Does anyone have an idea of what's going wrong in this situation?
------------------------------
Adam Forsyth
------------------------------