Problem trunk and tagged aruba 2930F switches + fiber + transceiver

[kkedzierski79]

Hello everyone
I'm sorry for my english
I am asking everyone for help in configuring VLAN communication
I have 6 switches and 3 of them are connected with fiber optics and additionally on each switch 3 VLANs.

Below is a description of my configuration that doesn't work properly. Please verify that this configuration is correct. Thank you very much for any help.

ip default gateway: 172.16.128.5

Switch (01)
trk1: port 16 (internet)
trk2: port 17
trk7: port 49 (transceiver connect fiber)
trk8: port 50 (transceiver connect fiber)

VLAN1 (default)
ports: 1-5 untagged
trk1-trk2, trk7-trk8 tagged lacp
ip address: 172.16.128.120 255.255.255.0

VLAN2
ports: 6-10 untagged
trk1-trk2, trk7-trk8 tagged lacp
ip address: 172.16.64.120 255.255.255.0

VLAN3
ports: 11-15 untagged
trk1-trk2, trk7-trk8 tagged lacp
ip address: 172.16.32.120 255.255.255.0

Fiber ports: 49-50 untagged
trk1-trk2, trk7-trk8 tagged lacp
-----------------

ip default gateway: 172.16.128.5

Switch (02)
trk2: port 18
trk3: port 19

VLAN1 (default)
ports: 1-5 untagged
trk2-trk3 tagged lacp
ip address: 172.16.128.121 255.255.255.0

VLAN2
ports: 6-10 untagged
trk2-trk3 tagged lacp
ip address: 172.16.64.121 255.255.255.0

VLAN3
ports: 11-15 untagged
trk2-trk3 tagged lacp
ip address: 172.16.32.121 255.255.255.0
-----------------

ip default gateway: 172.16.128.5

Switch (03)
trk3: port 20
trk4: port 21

VLAN1 (default)
ports: 1-5 untagged
trk3-trk4 tagged lacp
ip address: 172.16.128.122 255.255.255.0

VLAN2
ports: 6-10 untagged
trk3-trk4 tagged lacp
ip address: 172.16.64.122 255.255.255.0

VLAN3
ports: 11-15 untagged
trk3-trk4 tagged lacp
ip address: 172.16.32.122 255.255.255.0

-----------------

ip default gateway: 172.16.128.5

Switch (04)
trk7: port 25 (transceiver connect fiber)
trk9: port 22

VLAN1 (default)
ports: 1-5 untagged
trk7, trk9 tagged lacp
ip address: 172.16.128.123 255.255.255.0

VLAN2
ports: 6-10 untagged
trk7, trk9 tagged lacp
ip address: 172.16.64.123 255.255.255.0

VLAN3
ports: 11-15 untagged
trk7, trk9 tagged lacp
ip address: 172.16.32.123 255.255.255.0

Fiber (transeiver) ports: 25 untagged
trk7 tagged lacp

-----------------

ip default gateway: 172.16.128.5

Switch (05)
trk9: port 26

VLAN1 (default)
ports: 1-5 untagged
trk1-trk6 tagged lacp
ip address: 172.16.128.124 255.255.255.0

VLAN2
ports: 6-10 untagged
trk1-trk6 tagged lacp
ip address: 172.16.64.124 255.255.255.0

VLAN3
ports: 11-15 untagged
trk1-trk6 tagged lacp
ip address: 172.16.32.124 255.255.255.0

-----------------

ip default gateway: 172.16.128.5

Switch (06)
trk8: port 27 (transceiver connect fiber)

VLAN1 (default)
ports: 1-5 untagged
trk8 tagged lacp
ip address: 172.16.128.125 255.255.255.0

VLAN2
ports: 6-10 untagged
trk8 tagged lacp
ip address: 172.16.64.125 255.255.255.0

VLAN3
ports: 11-15 untagged
trk8 tagged lacp
ip address: 172.16.32.125 255.255.255.0

Fiber ports: 27 untagged
trk8 tagged lacp

I have connected them together (optical fiber)
Switch (01) - port: 49 (fiber) for Switch (04) - port: 25 (fiber) (transceiver)
Switch (01) - port: 50 (fiber) for Switch (06) - port: 27 (fiber) (transceiver)

Connection to each other over a Cat cable. 6
Switch (01) - trk2 (port: 17) to Switch (02) - trk2 (port: 18)
Switch (02) - trk3 (port: 19) to Switch (03) - trk3 (port: 20)

Switch (04) - trk9 (port: 22) to Switch (05) - trk9 (port: 23)

[parnassus · Accepted solution]

First of all please explain us why you created Port Trunks (Trk<id>) referencing just one physical port for each one?

Port Trunk = Link(s) Aggregation = to bond/aggregate/team two or more physical ports (up to 8 generally) to form a logical port (the various Trk<id> - trk1, trk2, trk3, etc - you listed) which can be used to uplink/downlink to a peer Switch or a Host (with teamed ports). You specified lacp...so your idea is to have (at least) two ports aggregated with LACP as link aggregation control protocol...so why each Port Trunk has just one port?

Here I suspect a confusion with Cisco's Trunk meaning...where Trunk = port that is able to carry multiple tagged VLANs.

If so...please re-think your actual design.

On HPE/HP/Aruba (as on Cisco) also a Port Trunk can carry multiple tagged VLANs...simply with interface ethernet trk1 tagged vlan <vlanid>...or, once into the <vlanid> context, with the simple command tagged <vlanid>.

First fix this part then we can start speaking about the above layer (IP Addressing, Routing, VLAN's SVI...).

Edit: trk<id> doesn't need to match between peer switches (Trk1 can connect to Trk100 and vice-versa...it shouldn't necessarily be Trk1 to Trk1 or TrkN to TrkN...it can be - it's really usual - TrkX to TrkY...what it is really important are that both Port Trunks have the same settings and uses the same type of ports and ports' speed)

[kkedzierski79]

---

@parnassus wrote:

First of all please explain us why you created Port Trunks (Trk<id>) referencing just one physical port for each one?

Port Trunk = Link(s) Aggregation = to bond/aggregate/team two or more physical ports (up to 8 generally) to form a logical port (the various Trk<id> - trk1, trk2, trk3, etc - you listed) which can be used to uplink/downlink to a peer Switch or a Host (with teamed ports). You specified lacp...so your idea is to have (at least) two ports aggregated with LACP as link aggregation control protocol...so why each Port Trunk has just one port?

Here I suspect a confusion with Cisco's Trunk meaning...where Trunk = port that is able to carry multiple tagged VLANs.

If so...please re-think your actual design.

On HPE/HP/Aruba (as on Cisco) also a Port Trunk can carry multiple tagged VLANs...simply with interface ethernet trk1 tagged vlan <vlanid>...or, once into the <vlanid> context, with the simple command tagged <vlanid>.

First fix this part then we can start speaking about the above layer (IP Addressing, Routing, VLAN's SVI...).

Edit: trk<id> doesn't need to match between peer switches (Trk1 can connect to Trk100 and vice-versa...it shouldn't necessarily be Trk1 to Trk1 or TrkN to TrkN...it can be - it's really usual - TrkX to TrkY...what it is really important are that both Port Trunks have the same settings and uses the same type of ports and ports' speed)

---

Hello Mr
From the very beginning I thank you for approaching my topic. You asked me a few questions that gave me a lot to think about and I will actually improve the pattern so that I can ask for a correct diagnosis. I will correct the scheme and insert it into the analysis after corrections.

[parnassus]

@Jenniifer, what? I'm not sure to understand your reply here...