Have you configured both (Static) LAGs before manually connecting both Switches with those Cat.6 Ethernet cable pairs?
IF so, disconnect them, then, on each Switch, configure the LAG to use LACP (Dynamic) or No Protocol (Statico) and redo the VLAN Tagging against that BAGG (BAGG port type should be set to Trunk, then you can set the BAGG port VLAN Tagged for the VLANs you need to be tagged)...once all is done connect both Switches as you did before. The BAGG (Static or Dynamic) should go up in few seconds.
Better to use LACP (Dynamic) if you are working with very similar (if not equals) Switches.
Better to start with necessary ports (LAG members ports) in their default configuration so you know yet the settings are corrects on both Switches for all involved ports.
I'm not an HPE Employee
Could you please draw and post a simple diagram of the Network Topology you're trying to configure?
An image is better than hundreds words.
Maybe I'm missing (or I misunderstood) something about what you wrote in relation of your Trunks...since you have 5 Switches I hope you haven't done any network loop (I mean: is it your Switches topology a Star, a Daisy Chain or what?).
From each Switch you should have only one Trunk (a LAG or just a single Link, doesn't matter) to any other Switch of your network...no loops, no rings (no other links or LAGs coming back directly from the same Switch or indirectly through other Switches).
I'm not an HPE Employee
Network Topology is clear but, at first sight, its trunking isn't...IMHO a network diagram will be better than hundreds words.
I'm not an HPE Employee
Well, in HP/HPE jargon the "Link Aggregation" is also known as "Port Trunking"...that is the CISCO EtherChannel. CISCO calls Trunk what is VLAN 802.1Q Tagging...so there is some confusion when we speak about "Trunk"...read, as example, here and here.
When you need to carry more than a VLAN on the same link (no matter which type of link), in HP world, you need to change the VLAN Port Type (of a Physical Port <- like your case OR of a Logical Port <- like the case of a LAG) from "Access Type" to "Trunk Type"...that's the confusion of terms (Trunk/Trunk) IMHO.
In the HP/HPE world there are basically three VLAN Port Types (that you can associate with a Physical/Logical port):
- Access
- Trunk ----> a VLAN Port Type set to "Trunk" is able to (A) Carry multiple VLANs on a single physical link, (B) tag VLAN(s) with IEEE 802.1Q and (C) leave the native VLAN Untagged <-- Which is what you want.
- Hybrid
Differences are explained in this document.
So basically you can have an Aggregated Physical Ports uplink (a LAG) <-- it's not your case...or you can have just a Single Physical Port uplink <-- that's your case...OK...both uplinks are able to carry multiple VLAN(s) if their VLAN Port Types are set to "Trunk Type":
- Aggregated Physical Ports uplink (a LAG) -> set (as example) LACP or Static -> go to the BAGG Logical Port and set the VLAN Port Type as "Trunk Type" to assign/permit that link to carry more VLAN(s).
- Single Physical Port uplink -> set the VLAN Port Type as "Trunk Type" to assign/permit that link to carry more VLAN(s).
It's just a matter of terms.
I'm not an HPE Employee
Focusing on the uplinks only I think you should consider to set each uplink port as VLAN Tagged for all VLAN(s) you want be permitted on that uplink and so permitted between that Switches' pair (do that considering your chain of three - or more - Switches and how the VLAN(s) are distributed/used on those ones).
So a scenario could be (here I used the uplinking schema: Switch "N" port 1 to 2 of the next Switch "N+1" in the chain):
Switch 1 Switch 2 Switch 3
port 1 <-- uplink --> port 2 / port 1 <-- uplink --> port 2
| | | |
| | | |
VLAN Tagged X VLAN Tagged X VLAN Tagged X
VLAN Tagged Y VLAN Tagged Y VLAN Tagged Y
I'm not an HPE Employee