Jump to content

Recommended Posts

Posted (edited)

I'm looking at VLAN-ing our network in the near future, so spending a bit of time getting my head around things and working out the best step forward. Advice on here has been great in understanding stuff, however....

 

I'm playing with a test network using a HP Procurve 2610 Switch, a couple of spare laptops and an old machine running Windows 2008R2. The main core switch is a HP Procurve 5406zl which I'm not going to play with just yet, I'm giving myself a bit of a primer first before I start bashing away at that!

 

First step I thought would be to see if I can create a few port based vlans on the switch and get the DHCP Relay working, then move on from there.

 

Can't for the life of me get it working. I've got four VLANS in total on the switch, DEFAULT (1) ,5 , 10 and 20. I've got the server in VLAN-5 on 192.168.0.10, and setup three scopes in DHCP for 192.168.0.x, 192.168.10.x and 192.168.20.x for now. Nothing sitting in the Default (1) presently.

 

Config is as follows:

 


Startup configuration:

; J9088A Configuration Editor; Created on release #R.11.54

hostname "ProCurve Switch 2610-48"
ip routing
snmp-server community "public" Unrestricted
vlan 1

  name "DEFAULT_VLAN"

  untagged 1-12,49-52
  ip address 10.43.48.120 255.255.252.0
  no untagged 13-48
  exit
vlan 5
  name "VLAN5"
  untagged 13-24
  ip address 192.168.0.5 255.255.255.0
  exit
vlan 10
  name "VLAN10"
  untagged 25-36
  ip address 192.168.10.1 255.255.255.0
  ip helper-address 192.168.0.10
  exit
vlan 20
  name "VLAN20"
  untagged 37-48
  ip address 192.168.20.1 255.255.255.0
  ip helper-address 192.168.0.10
  exit

 

IP Addresses are just not being dished out on the 10 and 20 VLANS, but obviously fine on the VLAN where the DHCP is sitting.

 

What am I missing here?

 

Many thanks

 

Pete

Edited by FragglePete
Bad Grammar!
Posted
Will the 2610 do the routing? Does the DHCP server have the address of the switch doing the routing as the default gateway? Your config looks correct but I see no mention of what is doing the routing which I suspect the 5406 is for as I have one of them.
  • Thanks 1
Posted

Hi,

 

I think on your default VLAN you may have the tagging done incorrectly, i.e. you said no untagged 13-48 well these ports are later untagged i.e. connected to stations i'm presumming. Also vlan 20 and vlan 1 shares some ports so that could be confusion it as well.

 

Ideally if the port is connecting to servers, printers, and other end user devices then it should be set to untagged i.e. statically mapped to a particular vlan. If they are connected to other switch then it should be tagged because tagged ports will allow to carry traffic from multiple vlan on that link/port.

 

Ash.

  • Thanks 1
Posted (edited)
Sorry Layer 3 the network layer of the OSI mode this is where routers operate. Have you set the default gateway on the server to the switch? I would also use the same address in each subnet for the router normally the last address. Edited by nicholab
  • Thanks 1
Posted

Thanks for all the replies! I know its only a L2 Edge, but all the docs say it does dhcp-relay and stuff. I'll look again and have another play, might just have to work on the main core instead!!! :D

 

Pete

Posted
Thanks for all the replies! I know its only a L2 Edge, but all the docs say it does dhcp-relay and stuff. I'll look again and have another play, might just have to work on the main core instead!!! :D

 

Pete

 

Don't think you would be able to enable "ip routing" if the switch did not support it.

Posted
Don't think you would be able to enable "ip routing" if the switch did not support it.

 

Indeed - IP Routing is an option on the IP Configuration menu screen, and it is switched on.

 

Just looking back at the other posts, in particular "Have you set the default gateway on the server to the switch?" and the answer to that one is "No!" Will have another play in the morning.

 

Pete

Posted

Well, there you go. That was the problem!

 

The DHCP Server had its Gateway Address set to the actual gateway, not the IP address of the Switch. So, changed the Gateway address to 192.168.0.5 and as if by magic IP addresses being handed within the different scopes! Superb!

 

Thanks ChrisH for that one!

 

Pete

Posted

Ok. Nicholab, thank you as well!!!!

 

You just answered my other question that started rattling around in my head about the 'proper' Gateway. Thanks for clearing that one up for me. Getting my head round this now so the mist is starting to clear.

 

Again, thank you, thank you, thank you! ;-)

 

Pete

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...