cancel
Showing results for 
Search instead for 
Did you mean: 

Vlan configuration issues

Vlan configuration issues

Jaren_Boone
New Contributor II
I'm working on extreme summit x450 with exos 15.3.1.4. I am playing around with vlans and am having some issues. Here is my vlan configuration:

configure vlan default delete ports all
configure vr VR-Default delete ports 1:1-48, 2:1-48, 3:1-24
configure vr VR-Default add ports 1:1-48, 2:1-48, 3:1-24
configure vlan default delete ports 1:1-48, 2:1-48, 3:1-24
create vlan "Data"
configure vlan Data tag 1
configure vlan Default tag 3000
create vlan "test"
configure vlan test tag 10
create vlan "Voice"
configure vlan Voice tag 100
configure vlan Data add ports 1:3-48, 2:1-48, 3:1-3, 3:5-24 untagged
configure vlan test add ports 1:48 tagged
configure vlan test add ports 3:4 untagged
configure vlan Voice add ports 1:3-48, 2:1-48 tagged
configure vlan Voice add ports 1:1-2 untagged
configure vlan Voice ipaddress 192.168.112.3 255.255.255.0
enable ipforwarding vlan Voice
configure vlan Data ipaddress 172.24.112.27 255.255.254.0
enable ipforwarding vlan Data
configure vlan test ipaddress 172.24.108.3 255.255.254.0
enable ipforwarding vlan test
configure ports 1:48 monitor vlan test
configure ports 3:4 monitor vlan test

At the other end of port 3:4 is a fortigate router with 172.24.108.1/23. We have a dhcp server at 172.24.112.18. If I ping 172.24.108.1 from 172.24.108.3 it works. If I ping 172.24.112.18 from 172.24.108.3 it fails. I can ping it from 172.24.112.27 and it works correctly. I'm not sure where else to look to try and get this working. Ultimately I want to have DHCP handing out 172.24.108 addresses.

14 REPLIES 14

Am I adding that route to the dhcp server on the switch?

There is no routing issue on the switch but on the rest of the network.

You'd do 2 things....
- add a route to the DHCP server if that is possible = 172.24.107.0/23 via 172.24.112.27
- configure DHCP relay on the switch or the the DHCP requests from the clients will never reach the DHCP server because the server is in a different subnet

Sorry, I just realized I mistyped in the previous response. The gateway I gave it was 108.1, not 107.1. And the gateway in the dhcp offer is the 108.1 gateway.

Hi Jaren,

The gateway offered in the dhcp offer needs to be in the same network as the offered IP address. So, make sure that the gateway IP set in the DHCP scope is in the 108 network instead of the 112.

Thanks
Brad

When I put a system on the test vlan and assign it a static ip address on the 172.24.108 network and give the system a default gateway of 172.24.107.1, it works fine getting to all of the resources on the 112 network. But when I try to get a dchp address it fails because it doesn't know how to get to the 112 network so it has to be a routing issue on the switch right? I just can't for the life me figure out how to fix it. Assuming my logic in that it's a routing issue is correct

GTM-P2G8KFN