BassTech Posted January 20, 2014 Posted January 20, 2014 Hi, We have 2 VLANs set up here: 1 (DEFAULT_VLAN) 2 (RUCKUS) I am using our HP ProCurve 2610-24 to test it (which comes off our main switch, a HP ProCurve 4108GL), and have 'untagged' ports 2 and 17 on VLAN2 which are what x2 test computers are plugged into. I've set up a scope of 172.10.0.0/21 on our DHCP server, just for VLAN2 to use. I used these command to configure the switch: #Config #VLAN 02 #Name "RUCKUS" #ip address 172.10.0.1 255.255.248.0 #ip helper-address 192.168.3.59 But the clients still won't automatically get a 172.10.x.x address from DHCP. I'm sure I've missed something/set something wrong but can't figure out what! Any help welcome.
localzuk Posted January 20, 2014 Posted January 20, 2014 Do you have ip routing enabled? Only thing I can think of off the top of my head.
Davit2005 Posted January 20, 2014 Posted January 20, 2014 I think there was a certain issue with HP 4104GL & 4108GL on certain firmware where ip routing/trunking was concerned. firmware version revision 51 I think rings a bell. We had a 4104GL at last place but I managed to get our firewall to provide DHCP for guest and BYOD vLANS only to overcome the issue.
sonofsanta Posted January 20, 2014 Posted January 20, 2014 Just to test, connect something to port 2 or 17 with a static address in the desired range and see if you can ping your DHCP server (or anything else on VLAN 1). If not, it may be your routing, as @localzuk says. If you can, the problem is probably with your DHCP server.
BassTech Posted January 20, 2014 Author Posted January 20, 2014 ip routing is enabled Good point re the 4100s - will look at updating the firmware on it as I don't think it's been updated since day 1! Do i need to configure the 4108GL in any way? I've created VLAN2 on it, as well as enable GVRP mode (which HP says automatically tags the correct ports)..
localzuk Posted January 20, 2014 Posted January 20, 2014 Can you post your config for the 4108GL and the 2610? I don't use GVRP here, as I manually tag the trunk ports and define VLAN data on each switch instead.
BassTech Posted January 20, 2014 Author Posted January 20, 2014 @sonofsanta - We can ping our DHCP (192.168.3.59), but only if we set our default gateway to 172.10.0.10 (Our squid server, using it as transparrant proxy for BYOD) If we set the default gateway as 192.168.3.200 which is our CISCO firewall then no reply to the ping. @localzuk - I will get them and post here
localzuk Posted January 20, 2014 Posted January 20, 2014 The gateway should be the IP address of the 4108GL on that particular VLAN. Then the 4108GL should have its default gateway set to your preferred default gateway.
sonofsanta Posted January 21, 2014 Posted January 21, 2014 Again, as @localzuk says, your default gateway for your VLAN has to be in that VLAN, because you go through your default gateway to get to other IP ranges, so if your gateway is on another IP range... chicken and egg When you set the VLAN up on the switch you assign it an IP, use that IP as the default gateway and then the switch will do the routing (assuming it's layer 3, not familiar with the ProCurve models).
Davit2005 Posted January 21, 2014 Posted January 21, 2014 ip routing is enabled Good point re the 4100s - will look at updating the firmware on it as I don't think it's been updated since day 1! Do i need to configure the 4108GL in any way? I've created VLAN2 on it, as well as enable GVRP mode (which HP says automatically tags the correct ports).. I actually think after a certain Firmware they changed something regarding Trunking and IP Routing see the following HP release HP Support document - HP Support Center
BassTech Posted January 21, 2014 Author Posted January 21, 2014 Ok, been playing around with it this morning.. Main switch (4108GL) - The default gateway is set to 192.168.3.200 on here. The VLAN2 IP address is set to 172.10.0.20 255.255.248.0. Test switch (2626-24) - The default gateway on here is set to 172.10.0.20. The VLAN2 IP address is set to 172.10.0.9. On the test client, I've put 172.10.0.9 as the default gateway, but it still only gets a 169 address :/ It works if I give it a static 172.10.x.x address, but still not getting it automatically
sonofsanta Posted January 21, 2014 Posted January 21, 2014 (edited) So with the static address, can you ping the DHCP server / can the DHCP server ping you? The only place you need to change the default gateway is on the device, and on the scope options for the VLAN address range on your DHCP server. This gateway should be the IP you gave the VLAN interface. The switches themselves should stay on whatever they were before. Another check: can you ping the VLAN interface IP (i.e. the address you want to use as the default gateway on this VLAN) from the DHCP server? Examples of what I'm talking about using made up addresses. Our internet router is IP 192.168.0.2. Our core switch is IP 192.168.0.10. Its default gateway is the internet router, i.e. 192.168.0.2. The cab switch in our office is IP 192.168.0.13. Its default gateway is the core switch, i.e. 192.168.0.10, as the core switch does all the routing between VLANs (not actually true, but we'll pretend it is for now). A server on VLAN1 would have the core switch as its default gateway. On the cab switch I've set up VLAN5, range 192.168.5.10-192.168.5.255. The IP for the VLAN interface is 192.168.5.1. Any device on this range, when given its IP address (e.g. 192.168.5.10) and its subnet (255.255.255.0) will have a default gateway of 192.168.5.1. This can be done statically, or set up as an option on the scope in the DHCP server. Edited January 21, 2014 by sonofsanta
themightymrp Posted January 21, 2014 Posted January 21, 2014 Your main switch has an IP address (for vlan2) of 172.10.0.20. This is the IP address which should be the default gateway for your PC's, not 172.10.0.9
localzuk Posted January 21, 2014 Posted January 21, 2014 The 2626-24 shouldn't have an IP for VLAN2 - it isn't doing any routing. It should just have the VLAN defined. So, it should be: Core Switch: Default IP - 192.168.3.200 VLAN1 - Has its own IP VLAN2 - 172.10.0.20 The 'trunk' port going to the 2626-24 should be tagged with both vlan 1 and 2 Edge Switch: Default IP: VLAN1 IP of core switch Trunk port tagged with vlan 1 and 2 VLAN 1 and 2 merely defined, no IP etc... Edge ports - untagged 1 or 2 The clients should then send their request for an IP on their own VLAN, which the switch will broadcast across the trunk where the core will recognise the VLAN and direct it to the ip helper address, where the DHCP server (which should have a DHCP scope that matches the IP address defined for VLAN2 on the core) will reply with an IP. The DHCP scope should define the gateway address for VLAN2 as being 172.10.0.20, as this is the device doing the internal routing.
BassTech Posted January 21, 2014 Author Posted January 21, 2014 So, now it's set up as: Core switch Default gateway: 192.168.3.200 VLAN1 IP: 192.168.3.38 VLAN2 IP: 172.10.0.20 Edge switch Default gateway: 192.168.3.38 VLAN1 IP: 192.168.3.54 VLAN2 IP: Test computer Default gateway: 172.10.0.20 DCHP Server 172 range > Scope options > Router: 172.10.0.20 Still, no automatic IP When on the test computer, I can ping 172.10.0.20 and get a reply. I try and ping the DHCP server on 192.168.3.59, request timed out. Also get request timed out if I try and ping 172.10.0.20 from the DHCP server. Which makes me thing it's a routing issue on our core switch!
localzuk Posted January 21, 2014 Posted January 21, 2014 That does sound like a routing issue now, yes. That config sounds right.
BassTech Posted January 21, 2014 Author Posted January 21, 2014 I'll have to double check the routing settings on our core switch, it should be: #config #vlan 02 #name "RUCKUS" #ip address 172.10.0.1 255.255.248.0 #ip helper-address 192.168.3.59 #exit Which is what I did last week :S
sonofsanta Posted January 21, 2014 Posted January 21, 2014 Your VLAN IP address is set to 172.10.0.1 there - try using that as your default gateway instead.
BassTech Posted January 22, 2014 Author Posted January 22, 2014 (edited) Ah, I see where I went wrong now! I want to go and try it, but have "misplaced" our serial cable, so had to order a new one in. We have every type of cable EXCEPT a female to female serial Edited January 22, 2014 by BassTech
BassTech Posted January 23, 2014 Author Posted January 23, 2014 I ran this on the main switch today: #config #vlan 02 #name "RUCKUS" #ip address 172.10.0.20 255.255.248.0 #ip helper-address 192.168.3.59 #exit But still no automatic IP address... When I did #ip address 172.10.0.20 255.255.248.0, the switch replied with "The IP address 172.10.0.20/21 already exists."
localzuk Posted January 23, 2014 Posted January 23, 2014 Ok, can you post the full config for the 2 switches?
BassTech Posted January 23, 2014 Author Posted January 23, 2014 Sure: Main switch (4108gl) ; J4865A Configuration Editor; Created on release #G.07.53 hostname "HP ProCurve Switch 4108GL" cdp run mirror-port A1 module 2 type J4864A module 1 type J4908A module 4 type J4893A ip default-gateway 192.168.3.200 snmp-server community "public" Unrestricted snmp-server host 192.168.3.51 "public" snmp-server host 192.168.0.194 "public" vlan 1 name "DEFAULT_VLAN" untagged A1-A22,B1-B3,D1-D6 ip address 192.168.3.38 255.255.248.0 exit vlan 2 name "RUCKUS" ip address 172.10.0.20 255.255.248.0 ip helper-address 192.168.3.59 exit interface A7-A20 monitor exit gvrp Test switch (2626-24) ; J9085A Configuration Editor; Created on release #R.11.07 hostname "ProCurve Switch 2610-24" snmp-server location "Foden house middle foor" ip default-gateway 192.168.3.38 ip routing snmp-server community "public" Unrestricted snmp-server host 192.168.0.194 "public" vlan 1 name "DEFAULT_VLAN" untagged 1,3-16,18-28 ip address 192.168.3.54 255.255.248.0 tagged 2,17 exit vlan 2 name "RUCKUS" untagged 2,17 ip address 172.10.0.20 255.255.248.0 ip helper-address 192.168.3.59 exit gvrp
DMcCoy Posted January 23, 2014 Posted January 23, 2014 turn off gvrp, turn off routing on the test switch, turn on routing on the core switch.
DPrince Posted January 23, 2014 Posted January 23, 2014 My understanding is that your Main Switch (4108) should have the gateway address for each vlan listed, as you've done. Your edge switch just has the ip address of the switch itself, configured under the vlan the management will be done under (so if you have a management vlan, your switch ip should be configured under that vlan). You don't need routing on your edge switch.
sonofsanta Posted January 23, 2014 Posted January 23, 2014 (edited) That's why your main switch is whining about the IP being in use - your edge switch already has it. If you're routing at your core, i.e. this VLAN will span multiple switches, set the interface with IP up there. Your edge switch then needs to know nothing beyond the fact that the VLAN exists, so that you can tag/untag ports. I'm on COMWARE5 switches here, but as an example, this is my printer VLAN routed from core: Core switchinterface Vlan-interface192 description Printers_VLAN ip address 192.168.192.1 255.255.255.0 dhcp select relay dhcp relay server-select 1 Edge switchvlan 192 description Printers_VLAN My routing is done statically (still older switches on the network that need it) so the edge switch has a default route set up to push any traffic it's not sure of up to the core. The 192 traffic meets that definition, so it's sent up to the core that routes it appropriately. Edited January 23, 2014 by sonofsanta
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now