Well you are configuring two separate protocols in this case - and the terminology/syntax between aos-s (2930) and aos-cx (6000) is different for each.
So if the goal is to configure redundant Layer-2 Links between two switches:
You will want first want to configure link aggregation - two physical interfaces grouped together
AOS-S = trunk 1-2 trk1 lacp - This would initial a trunk using 802.3ad dynamic standard on Switch Ports 1 and 2
AOS-CX = interface lag 1 ~ lacp mode active & interface 1/1/1 ~ lag 100 & interface 1/1/2 ~ lag 100
Then you can VLANs to those link aggs - for multiple VLANS
AOS-S = interface Trk1 ~ untagged vlan 1 ~ tagged vlan 1,11,21
AOS-CX = interface lag 1 ~ vlan trunk native 1 ~ vlan trunk allowed 1,11,21
------------------------------
If my post was useful, please Accept Solution and Give Kudos.
------------------------------
Zak Chalupka
Principal Engineer - HPE Aruba
ACDX | ACMP | ACSP | ACCP
wifizak@hpe.com------------------------------
Ideas expressed here are solely my own and not necessarily that of HPE Aruba.
------------------------------
Original Message:
Sent: Mar 27, 2024 11:46 AM
From: Liran Waiss
Subject: how to configure trunk in two situations
- trunk between 2530 to 2930
using trk1, trk2 etc
or with
untag on the the default vlan and tag on the vlans
what is the difference ?
and also if i have on one of the switches above 2 different trunks to to different switch's,
i need to user the trk1, trk2 etc or again only untag on the defualt and tag the vlans i want to pass ?
2. trunk between 2930 to 6000/8320
in this situation only the 2930 have a trk1, trk2 etc,
the 6000/8320 don't have this trk1, trk2,
i can only see i can create lag or make the port nativ untag and allowed the vlans
so which way is the right one.
thanks,
liran