Wired Intelligent Edge

Hello,

I'm new here and I would need some help,

I have in total 4 Aruba 2930M switches, they are setup in a star with one switch serving as central switch,

I have one vlan for Dante, one for other protocols, and one management vlan.

From this central switch there is one fiber trunk which works fine, the other 2 switches are trunked by copper, in the copper trunk switches it's not possible to ping from one device to another,

this is the running config:

SwitchStage# sh run

Running configuration:

; JL320A Configuration Editor; Created on release #WC.16.07.0003
; Ver #14:01.4f.f8.1d.9b.3f.bf.bb.ef.7c.59.fc.6b.fb.9f.fc.ff.ff.37.ef:02

hostname "SwitchStage"
module 1 type jl320a
trunk 22-24 trk1 lacp
snmp-server community "public" unrestricted
oobm
ip address dhcp-bootp
exit
vlan 1
name "MGMTVLAN"
no untagged 1-20
untagged 21
tagged Trk1
ip address 192.168.10.1 255.255.255.0
ipv6 enable
ipv6 address dhcp full
exit
vlan 2
name "DANTE"
untagged 1-12
tagged Trk1
no ip address
exit
vlan 3
name "OTHER"
untagged 13-20
tagged Trk1
no ip address
exit
spanning-tree Trk1 priority 4
no tftp server
no autorun
no dhcp config-file-update
no dhcp image-file-update

this is the lldp info

SwitchStage# show lldp info remote-device

LLDP Remote Devices Information

LocalPort | ChassisId PortId PortDescr SysName
--------- + ------------------ ------------------ --------- ------------------
9 | 3821c7-5d4480 10 10 SwitchPA
12 | 3821c7-5de680 12 12 SwitchKoker
20 | 3821c7-5de680 20 20 SwitchKoker
24 | 8030e0-eba480 48 48 SwitchKleineZaal

As a workaround I have now patched directly one port in the Dante vlan to a Dante port on another switch, this is working ok..

Could you please advice on how to just get all trunks up and running for all vlan, in a star configuration..

Thanks!

On the interface between 2 switches, make sure to TAG all vlan's on that interface, example: the interface to switchpa:

interface 9

tagged vlan 1,2,3

Do the same on switchpa interface that uplinks to the "core" switch.

Hi! you must be a little more clear about your topology. You wrote you have a Star, that's OK...so who is at the center? SwitchStage?

I ask because reading the LLDP:

SwitchStage# show lldp info remote-device

LLDP Remote Devices Information

LocalPort | ChassisId PortId PortDescr SysName
--------- + ------------------ ------------------ --------- ------------------
9  | 3821c7-5d4480 10 10 SwitchPA
12 | 3821c7-5de680 12 12 SwitchKoker
20 | 3821c7-5de680 20 20 SwitchKoker
24 | 8030e0-eba480 48 48 SwitchKleineZaal

it seems ports 12 and 20 are uplinked to the same switch "SwitchKoker" (respectively on ports 12 and 20 too)and port 24 (part of an aggregated group made of three ports - 22 to 24) is connected to switch "SwitchKleineZaal" (port 48)...where one expect to see at least three ports (part of Trk1) to three ports (part of TrkX) to the peer switch...but it's not...so why you defined a Trk1?

Suppose you have 1 central Switch and 3 periferic ones...then suppose you have single link downlinks from the central Switch to periferic ones...to transport VLANs between all of them you need to define the very same VLAN id on all involved four switches and configure uplink/downlink ports to be tagged members of those VLAN ids (I suppose you will not use VLAN 1) and untagged members of a VLAN id use to manage switches "VLAN for Switch Management" (at least I do so).

Then if you need to route those VLANs you can easily enable IPv4 Routing on the central Switch and assign IP addresses to VLAN you want to route...periferic switches just need an IP Address on VLAN dedicated to their management (the one which have untagged uplink/downlink member ports) and configure on each of them IP Default Gateway pointing to that VLAN IP Address (that's only for management purposes...since other VLANs are transported Layer 2 to the core one).

No more, no less.

Hi, thx for picking this up, 

Indeed SwitchStage is the central switch,

the ports 12 and 20 which are now connected are only a temporary workaround, the idea is to use the ports 22, 23 en 24, who are members of Trk1

Each swich has an ip address in vlan 1, but no ip address in vlan 2 and vlan 3, as I understand I should give in the central switch a gateway address to the vlan 2 and 3, and this is not necesary on the other switches? 

So for example I give vlan 2 ip 192.168.0.1 and vlan 3 ip 192.168.1.1?

Also I will tag the vlans on the Trk1 member ports of all switches

---

@davy111 wrote:

 

the idea is to use the ports 22, 23 en 24, who are members of Trk1

---

That's the wrong part.

If the schema is correct port 22, 23 and 24 are uplinked to three different switches...so you must not use the logical interface Trk1 which represent a ports aggregation of three ports...here the trunk word doesn't mean "to carry multiple VLANs"...I suspect you misunderstood the concept.

You are going to have instead three differnet (single link) uplinks...one departing form 22 to Switch PA, another from port 24 to Switch Zaal and the last one departing from port 23 to Switch Koker...simple.

No (HP/Aruba) Trunks here...I don't see any aggregation here.

Instead ports 22, 23 and 24 shall be configured as tagged members of VLAN you want to transport from/to the Core Switch Stage...and leave them untagged member of the VLAN dedicated to Switch Management (it's actually VLAN 1 and there you have Switch Stage as Gateway on .10.1 and each other Switch has its own IP - .10.4, .10.3 and .10.2 in that very same range).

You can assing VLAN IP addresses on all VLAN on all Switches but it's not necessary IF your reference is the Switch Stage at core position (I presume it has IP Routing enabled and all the others have it disabled).

Hope you understood the picture...  

Hi, just to let you know I have not been able to visit this site (Leietheatre, Deinze, Belgium) until now, normally tomorrow I go there, I'll let you know the results.. regards, Davy

Hello,

With you suggestions I've indeed got the result I wanted now, many thanks!

This is now my center switch config:

SwitchStage# sh run

Running configuration:

; JL320A Configuration Editor; Created on release #WC.16.07.0003
; Ver #14:01.4f.f8.1d.9b.3f.bf.bb.ef.7c.59.fc.6b.fb.9f.fc.ff.ff.37.ef:02

hostname "SwitchStage"
module 1 type jl320a
ip routing
snmp-server community "public" unrestricted
oobm
ip address dhcp-bootp
exit
vlan 1
name "MGMTVLAN"
no untagged 1-20,22-24
untagged 21
ip address 192.168.10.1 255.255.255.0
ipv6 enable
ipv6 address dhcp full
exit
vlan 2
name "DANTE"
untagged 1-12
tagged 22-24
no ip address
exit
vlan 3
name "OTHER"
untagged 13-20
tagged 22-24
no ip address
exit
no tftp server
no autorun
no dhcp config-file-update
no dhcp image-file-update

--- 

config of one of the 'outside switches':

SwitchKoker# sh run

Running configuration:

; JL320A Configuration Editor; Created on release #WC.16.07.0003
; Ver #14:01.4f.f8.1d.9b.3f.bf.bb.ef.7c.59.fc.6b.fb.9f.fc.ff.ff.37.ef:02

hostname "SwitchKoker"
module 1 type jl320a
qos type-of-service diff-services
snmp-server community "public" unrestricted
oobm
ip address dhcp-bootp
exit
vlan 1
name "MGMTVLAN"
no untagged 1-20
tagged 21-24
ip address 192.168.10.2 255.255.255.0
ipv6 enable
ipv6 address dhcp full
exit
vlan 2
name "DANTE"
untagged 1-12
tagged 22-24
no ip address
exit
vlan 3
name "OTHER"
untagged 13-20
tagged 22-24
no ip address
exit
no tftp server
no autorun
no dhcp config-file-update
no dhcp image-file-update

All Dante devices are shown in the Dante controller so seems fine now,

A next question of my boss is now to set up DHCP on the center switch throughout the Dante vlan, is this possible on this switch model?

Thx again!

---

@davy111 wrote: A next question of my boss is now to set up DHCP on the center switch throughout the Dante vlan, is this possible on this switch model?

---

Hi, Yes, it's possible...I think your question would be perfectly and completely answered by reading this guide