How to setup VLANs on 1810G-24

[doujind]

Hello.
Can someone please help with setting up VLANs on my Procurve 1810G-24, firmware P.1.6.
This is an example what I would like to achive:
Eg.:
1 VLAN, subnet 1, port 2.
2 VLAN, subnet 2, ports 13,15,17,19.
3 VLAN, subnet 3, ports 14,16,18.
Port 1 connects up to DHCP server, that's why I need all three VLANs can see Port 1 and connect it.

I did everything as was shown in thread (http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1267165843985+28353475&threadId=1400651), but it doesn't work.
Thanks for your replays!

[Mohammed Faiz]

Hi,

You haven't said where your router is connected and on which VLAN.
Your router is what will forward the DHCP request packets from the clients on VLANs 2 and 3 to the DHCP server (using the "ip helper-address" option)

[doujind]

I have no router, only Procurve 1810G-24.
Several interfaces with the ip-addresses of three subnets were set up on the network card at dhcp-server. Now without VLAN-s all works. But I want to organize VLAN-s.

[Mohammed Faiz]

So your server supports VLAN tagging and you've assigned the same VLAN IDs to the server as you have on the switch?
If so the only thing you're missing is tagging all the client VLANs on the port that the DHCP server is connected to.

[doujind]

In the server installed network card HP NC110T PCI Express Gigabit.
Server model HP ProLiant ML110 G6.

config /etc/network/interfaces


auto lo
iface lo inet loopback

auto eth0.2
iface eth0.2 inet static
address 192.168.10.1
netmask 255.255.255.192
network 192.168.10.0
broadcast 192.168.10.63
vlan_raw_device eth0

auto eth0.3
iface eth0.3 inet static
address 192.168.10.65
netmask 255.255.255.192
network 192.168.10.64
broadcast 192.168.10.127
vlan_raw_device eth0

auto eth0.4
iface eth0.4 inet static
address 192.168.10.129
netmask 255.255.255.192
network 192.168.10.128
broadcast 192.168.10.191
vlan_raw_device eth0

auto eth0.5
iface eth0.5 inet static
address 192.168.10.193
netmask 255.255.255.192
network 192.168.10.192
broadcast 192.168.10.255
vlan_raw_device eth0

What do you mean, saying your phrase "tagging all the client VLANs on the port that the DHCP server is connected to"?

[Mohammed Faiz]

Ok, I'm not 100% on creating virtual interfaces on linux servers but the problem appears to be that you have setup IPs on the server that are in different subnets but all on the same VLAN (vlan_raw_device eth0).
Once you've fixed that then you need to tag all the client vlans onto the port that the DHCP server is connected to.

> What do you mean, saying your phrase
> "tagging all the client VLANs on the port
> that the DHCP server is connected to"?

What switch is your DHCP server connected to?
You want to tag VLANs 2 and 3 (from your example) onto that port if you want it to be able to see subnets 2 and 3.

I have to point out this isn't the recommended method of doing this. What you want is a switch that can perform routing which would hold the gateway IP addresses for each of the other subnets. All you would need to do then is add ip helper-addresses onto the vlans (that point to your DHCP server) on that switch and make sure your routing is correct and then you'd be done.

[doujind]

Please, can you describe, how to add ip helper-addresses onto the vlan on my switch and how to organize routing.

[Mohammed Faiz]

The 1810G switches don't do routing and hence you can't add ip helper-addresses to them.
I know you said you don't have a router but how is your traffic routed to the internet?

[doujind]

My traffic routed to the internet through proxy server ML110 G6 which has the ip-addresses of each subnet on the network card.

[Mohammed Faiz]

In that case I would recommend using a switch that can do basic routing instead of the 1810G. Something like the 2610 series.