This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Extreme Networks
- Community List
- Switching & Routing
- ExtremeSwitching (EXOS/Switch Engine)
- Re: 1x DHCP Server 2019 - multiple VLANs - what am...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
1x DHCP Server 2019 - multiple VLANs - what am I doing wrong?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
10-06-2020 06:20 AM
I’m having an Extreme Networks x460 Switch and 2 VLANs. On VLAN 11 there’s a Windows Server 2019 located which has 2 scopes (for the different vlans)
VLAN 11 IP Switch: 192.168.11.253/24
IP DHCP Server: 192.168.11.1
VLAN 193 IP Switch: 192.168.193.253/24
I’m able to ping the DCHP Server from the Switch
I did a config bootprelay add 192.168.11.1 vr VR-Default
Also enable bootprelay VLAN VLAN11
and enable bootprelay VLAN VLAN193
and last but not least: enable ipforwarding vlan11
and enable ipforwarding vlan193
When I connect a client to VLAN 193 I’m not getting an IP Adress.
The DHCP Server has a Scope for: 192.168.11.100-110 and a Scope for: 192.168.193.100-110
Solved! Go to Solution.
2 ACCEPTED SOLUTIONS
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
10-06-2020 08:15 AM
I found the error and it’s working now - thank you!!
The problem was the getting back to the VLAN . The Problem was more firewall related then switch related. Best Regards, Frank PS: Wireshark did the trick
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
10-06-2020 02:34 PM
15 REPLIES 15
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
10-06-2020 07:54 AM
so the offer can’t reach 192.168.193.253 - ipforwarding is enabled von both vlan. Do I need anything else? like a iproute
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
10-06-2020 07:47 AM
ok, it seems like, the offer is not getting back. I see a DHCP Discover from 192.168.198.253 to 192.168.11.1 and afterwards I see the DHCP Offer from 192.168.11.1 to 192.168.193.253.
and nothing more… Filter in Wireshark is DHCP
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
10-06-2020 07:19 AM
Hi Stefan,
was mich wundert ist: DHCP Relay Agent Information Option: Disabled on virtual Router VR-Default
Ich werde mal Wireshark aktivieren und schauen, ob am Server was ankommt.
lg,
Frank
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
10-06-2020 07:11 AM
Servus Frank,
in the “show bootprelay” output we can see that the switch relays the DHCP-Discover. The question is where the packet is going and why it doesn’t come back. 🙂
Easiest thing would be to start a wireshark on the windows server and look if the packets are received from the server. The problem could be anything (DHCP-Scope problem, routing problem, static route on the DHCP-Server and so on...)
Best regards
Stefan
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
10-06-2020 06:37 AM
but I did a conf bootprelay add 192.168.11.1 vr VR-Default. Is there anything else I need to do to get the relay working?
