Hello Gabriel,
are you so kind to post the output of commands listed below?
VLAN status for aggregated interface trk1 (made of 1/22+2/22):
show vlan port trk1 detail
VLAN status for aggregated interface trk2 (made of 1/21+2/21):
show vlan port trk2 detail
As far as I can understand from your Aruba 2930F VSF configuration both aggregated interfaces (trk1 and trk2) were ONLY set to be untagged members of VLAN id 1 (default)...there isn't any reference to other VLAN ids thus your statement:
@neok wrote: And finally I setup the vlans that coul be passed through trunks:interface trk1 tagged vlan 10,20,30,40
However, I can't get my vlan up.
seems wrong...there is no tagging on trk1 (and both checks above shall confirm). Redo commands:
interface ethernet trk1 tagged vlan 10,20,30,40
interface ethernet trk2 tagged vlan 10,20,30,40
and then re-check VLAN status for both aggregated trunks (trk1 and trk2)...you should discover that trk1 and trk2 are now tagged members of VLAN ids 10, 20, 30 and 40 (other than being untagged members of VLAN id 1).
I don't understand WHY you tag single interfaces in this way:
1/1-1/20 untagged on VLAN 1
2/1-2/20 untagged on VLAN 1
and, concurrently:
1/1 and 2/1 tagged only on VLAN 10
1/2 and 2/2 tagged only on VLAN 20
1/3 and 2/3 tagged only on VLAN 30
1/4 and 2/4 tagged only on VLAN 40
1/5 and 2/5 tagged only on VLAN 50
1/6 and 2/6 tagged only on VLAN 60
1/7 and 2/7 tagged only on VLAN 70
1/8 and 2/8 tagged only on VLAN 80
1/9 and 2/9 tagged only on VLAN 90
1/10 and 2/10 tagged only on VLAN 100
1/11 and 2/11 tagged only on VLAN 110
1/12 and 2/12 tagged only on VLAN 120
1/13 and 2/13 tagged only on VLAN 130
1/14 and 2/14 tagged only on VLAN 140
1/15 and 2/15 tagged only on VLAN 150
1/16 and 2/16 tagged only on VLAN 160
1/17 and 2/17 tagged only on VLAN 170
1/18 and 2/18 tagged only on VLAN 180
1/19 and 2/19 tagged only on VLAN 190
1/20 and 2/20 tagged only on VLAN 200
what's the final purpose? why this pattern? who is connected to each pair (e.g. on 1/1 and 1/2)?