!Trunk link to Northfield House interface tengigabitethernet 1/1/2 switchport mode trunk switchport trunk allowed vlan add 10,11,12 exit
!Create static LAG to Wharfside Core switches interface tengigabitethernet 1/0/19-24 channel-group 1 mode on
!Static LAG to Wharfside Core switches interface port-channel 1 switchport mode trunk switchport trunk allowed vlan add 10,12 tagged exit
!Routing ip route 192.168.20.0 255.255.255.0 192.168.172.254 ip route 192.168.22.0 255.255.255.0 192.168.172.254 ip route default 192.168.1.1
Am I on the right track? It's hard to test as I would have to remove the current switch from the network because of the VLAN interface address and routing, plus nobody seems to go home here!
Thanks for the suggestions Daniel. I only included those lines to replicate the AVAYA config as closely as possible.
You're correct, there will be no handsets connected directly to this switch but it will be handling L3 routing for the CISCO core switch (on the other end of the LAG) as the IP handsets are in a different VLAN to the PBX, which is in the corp data vlan.
Thanks for the link, I will take a look and take the plunge and try swapping the switches (outside of office hours!).
We have now had the opportunity to test the configuration by swapping the switch out and we had some strange results:
Plugging a client into a port belonging to VLAN 10 can ping addresses through the port-channel 1 but couldn't ping addresses on VLAN 12.
Clients plugged into VLAN 10 couldn't ping through the the routed interface to VLAN 20 but the from the switch console I could ping VLAN20.
There are two ports assigned into the channel group. Although these were configured as a static LAG we noticed that 1 interface kept dropping and then coming back up.
Looking at internet forums I think we can try the following:
Adding "ip routing" to enable routing - even though static routes are defined do you have to manually enable routing?
I had IP addresses assigned to each vlan interface, just missed the ip routing command! We have another test this weekend.
If I have two different vlans on the same port can I traverse the vlan or do I need to add a static route? The port-channel has vlan 10 (data) and vlan 12 (VOIP) allowed on it. The VOIP handsets need to communicate with the PBX, which is on vlan 10.
With the current AVAYA switches it is enough that the vlans are directly connected, you don't need to specify a route. Is this the case with Dell?
mattstanding
7 Posts
2703
0
Posted February 24th, 2017 03:00
Hi Daniel,
Thanks for the advice - it's been a great help. I have matured the proposed config a little more and have this:
!Corporate data vlan
vlan 10
name VLAN_CORP
interface address 192.168.1.6 255.255.255.0
interface range tengigabitethernet 1/0/1-12
switchport mode access
switchport access vlan 10
switchport access pvid 10
exit
!Public nework vlan
vlan 11
name VLAN_PUBLIC
interface tengigabitethernet 1/0/13-16
switchport mode access
switchport mode vlan 11
switchport access pvid 11
exit
!VOIP vlan
vlan 12
name VLAN_VOICE
interface address 192.168.12.254 255.255.255.0
exit
!Transport vlan to Wharfside Suites
vlan 172
name VLAN_TRANSPORT
interface address 192.168.172.253 255.255.255.0
interface tengigabitethernet 1/1/1
switchport mode trunk
switchport trunk allowed vlan add 11,13,172 tagged
exit
!Trunk link to Northfield House
interface tengigabitethernet 1/1/2
switchport mode trunk
switchport trunk allowed vlan add 10,11,12
exit
!Create static LAG to Wharfside Core switches
interface tengigabitethernet 1/0/19-24
channel-group 1 mode on
!Static LAG to Wharfside Core switches
interface port-channel 1
switchport mode trunk
switchport trunk allowed vlan add 10,12 tagged
exit
!Routing
ip route 192.168.20.0 255.255.255.0 192.168.172.254
ip route 192.168.22.0 255.255.255.0 192.168.172.254
ip route default 192.168.1.1
Am I on the right track? It's hard to test as I would have to remove the current switch from the network because of the VLAN interface address and routing, plus nobody seems to go home here!
Thanks in advance,
Matt