localzuk 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. Yup. That'd be my thought. Then on both switches, tag the ports used as trunks on both vlans. In the case of 2 switches, gvrp over complicates things. I don't use GVRP across our 15 or so switches, there's no need. This would be my config: [color=#333333][i]ip default-gateway 192.168.3.200 [/i][/color][color=#333333][i]ip routing [/i][/color] [color=#333333][i]vlan 1 [/i][/color] [color=#333333][i]name "DEFAULT_VLAN" [/i][/color] [color=#333333][i]untagged A1-A22,B1-B3,D1-D6 [/i][/color]tagged X1 [color=#333333][i]ip address 192.168.3.38 255.255.248.0 [/i][/color] [color=#333333][i]exit [/i][/color] [color=#333333][i]vlan 2 [/i][/color] [color=#333333][i]name "RUCKUS" [/i][/color]tagged X1 [color=#333333][i]ip address 172.10.0.20 255.255.248.0 [/i][/color] [color=#333333][i]ip helper-address 192.168.3.59 [/i][/color] [color=#333333][i]exit[/i][/color] [color=#333333][i]ip default-gateway 192.168.3.38 [/i][/color] [color=#333333][i]vlan 1 [/i][/color] [color=#333333][i]name "DEFAULT_VLAN" [/i][/color] [color=#333333][i]untagged P,Q[/i][/color][color=#333333][/color]tagged A [color=#333333][i]ip address 192.168.3.54 255.255.248.0[/i][/color] [color=#333333][i]exit [/i][/color] [color=#333333][i]vlan 2 [/i][/color] [color=#333333][i]name "RUCKUS" [/i][/color] [color=#333333][i]untagged Y,Z [/i][/color]tagged A [color=#333333][i]ip helper-address 192.168.3.59 [/i][/color] [color=#333333][i]exit [/i][/color] [color=#333333][i]gvrp [/i][/color]With X1 being the trunk port, P,Q being ports on VLAN1, Y,Z on VLAN2 and A being the trunk port on the edge switch.
BassTech Posted January 23, 2014 Author Posted January 23, 2014 I've now disabled routing on the edge switch completely, and re-configured the main switch for routing. On the edge switch, it's port 27 that connects back to the main, so I set that port as trunked (Trk1) and tagged it for VLAN1 & VLAN2, the problem is that as soon as I do that, all the clients coming off the edge switch lose connection, untill I untag VLAN1 on Trk1 again :/
LukeTitmus Posted January 23, 2014 Posted January 23, 2014 What is your full DCHP scope? Is your address range 172.10.0.xx/24 or whatever the subnet needs to be for the amount of address you need Personally I would have 172.10.0.1 as my Default gateway and then start the client addresses at 172.10.0.20, just seems logical and you have some space for extra things you may need on that range
localzuk Posted January 23, 2014 Posted January 23, 2014 What do you mean you set it as trunked? The term 'trunk' is just a general term for a link with HP switches (unlike with Cisco switches where it has a specific meaning in the config). By trunked, I merely mean you've tagged both vlan 1 and 2 on that port on both ends of the switch. So port 27 should be tagged vlan 1 and tagged vlan 2. Then whatever the port on the core switch should be tagged with both too.
localzuk Posted January 24, 2014 Posted January 24, 2014 Oh, also Trunk does have a meaning in HP but it isn't the one we're working with here (Trunking is joining ports together in the HP world).
BassTech Posted January 24, 2014 Author Posted January 24, 2014 Oh, also Trunk does have a meaning in HP but it isn't the one we're working with here (Trunking is joining ports together in the HP world). ahh, HP and their terminology! That makes a lot more sense now, I've been using the HP trunking features! So, I need to TAG (not untag) VLAN1 + VLAN2 on port 27 on the edge switch (which is a fiber connection back to the main) and then on the main TAG VLAN1 + VLAN2 on the port that the edge switch comes off. Yesterday when I tagged VLAN1 + VLAN2 on port 27 on the edge switch, all the clients on VLAN1 lost connection to the servers for some reason. @LukeTitmus our range is 172.10.0.xx/24 we're just testing at the minute, but it will all be logical when it goes live
localzuk Posted January 24, 2014 Posted January 24, 2014 ahh, HP and their terminology! That makes a lot more sense now, I've been using the HP trunking features! So, I need to TAG (not untag) VLAN1 + VLAN2 on port 27 on the edge switch (which is a fiber connection back to the main) and then on the main TAG VLAN1 + VLAN2 on the port that the edge switch comes off. Indeed. Yesterday when I tagged VLAN1 + VLAN2 on port 27 on the edge switch, all the clients on VLAN1 lost connection to the servers for some reason. If one end wasn't tagged, it'd do this.
BassTech Posted January 24, 2014 Author Posted January 24, 2014 Ok, thanks for the help so far, will do some more tinkering today and post results
sonofsanta Posted January 24, 2014 Posted January 24, 2014 Tagging and untagging is a weird and illogical naming convention that confuses easily (to the point I've just had to double check my own switches to make sure I'm not leading you astray), so for clarity: Every port must be untagged with at least one VLAN. This is the VLAN that the device belongs to, and a port can only be untagged with one VLAN. So for a wireless point that you want on VLAN 2, you have to untag the relevant port on the switch with VLAN 2. Ports that connect between switches should be untagged to VLAN1 (for the sake of simplicity). If you removed any untagging on your switch connections yesterday, that's why connections were dropped. Tagging is only used on the ports that switches use to connect to each other. It basically says "I'm not part of this VLAN, but I'll pass the traffic along". So if you have devices on VLAN2 on your edge switch, the port that connects upstream must also be tagged with VLAN2 (as well as the equivalent port on the other switch). You don't need to tag the port with the VLAN it's already untagged with, so if the switch port is untagged to VLAN1 you don't need to tag that port with VLAN1 as well. If you're setting up a new VLAN and traffic can't seem to get anywhere, odds are it's this bit you've forgotten (based on my experience of being me, anyway). In summary, for your current setup: the ports between your switches should be untagged with VLAN1 and tagged with VLAN2. The port you are using for your VLAN2 device should be untagged with VLAN2. 1
localzuk Posted January 24, 2014 Posted January 24, 2014 (edited) The ports between switches should not be untagged between switches as far as I was told at uni. All 'switch to switch' links are tagged. Switch to end device links are untagged. So, as I said before port 27 on the edge should be tagged vlan 1 and vlan 2 and the other end should also be tagged vlan 1 and 2, with only the end device ports using the 'untagged' part. That is the setup I've used here, and was used in the school I was at previously (set up by Northgate IS), and pretty much every other network I've seen also. EDIT: This does seem like a personal choice though to be honest, but it has to be uniform between switches - you can't have vlan 1 tagged one end and untagged the other. It has to be matched. Edited January 24, 2014 by localzuk
sonofsanta Posted January 24, 2014 Posted January 24, 2014 I wish I could remember enough from my CCNA course at Uni to say, but it was a long time ago and I struggled to remember it all back then in the first place Might be a difference between the ProCurve and Comware switches - my switch to switch connections are all untagged VLAN1, set to hybrid mode, though I know for a fact the latter is preference, and was the way the SwitchShop bloke preferred when he was setting/training us up. Works for me, anyway, might be worth a go if all else fails!
DMcCoy Posted January 24, 2014 Posted January 24, 2014 Every port must be untagged with at least one VLAN. Tagging is only used on the ports that switches use to connect to each other. It basically says "I'm not part of this VLAN, but I'll pass the traffic along". So if you have devices on VLAN2 on your edge switch, the port that connects upstream must also be tagged with VLAN2 (as well as the equivalent port on the other switch). [/b]. You can have ports which are only tagged (I usually do vlan 1 between switches as tagged, remote end first!) You can have untagged and tagged (for lldp for phones as an example) and use untagged and multiple tagged vlans for a machine with a vlan aware card if you need to You will also have multiple tagged to things like VM hosts etc.
BassTech Posted January 29, 2014 Author Posted January 29, 2014 (edited) I've managed to tag port 27 on VLAN1 + VLAN2 on our test switch, and also tagged VLAN1 + VLAN2 on the main switch (port B2). On our test workstation (that comes off the test switch) I have untagged this port on VLAN2, and set the default gateway server as 172.10.0.20... But still no IP, and can't ping 172.10.0.20 - Now I'm really stumped as to why it can't get an IP. Edited January 29, 2014 by BassTech
BassTech Posted January 29, 2014 Author Posted January 29, 2014 Post the configs again? Yep Main (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 ip routing 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 tagged B2 exit vlan 2 name "RUCKUS" ip address 172.10.0.20 255.255.248.0 ip helper-address 192.168.3.59 tagged B2 exit interface A7-A20 monitor exit Test (2626): ; 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-26,28 ip address 192.168.3.54 255.255.248.0 tagged 17,27 no untagged 2 exit vlan 2 name "RUCKUS" untagged 2,17 no ip address tagged 27 exit
localzuk Posted January 29, 2014 Posted January 29, 2014 You have your DHCP server helper address set as 192.168.3.59 - is this your DHCP server address? You say you set the DHCP server as 172.10.0.20? This is the IP address of VLAN 2 on the core switch, so you can't use it again. 1
BassTech Posted January 29, 2014 Author Posted January 29, 2014 Yes, 192.168.3.59 is our DHCP server. On the workstation, I set the default gateway to 172.10.0.20 (Sorry, I put DHCP instead of default gateway above - typo)
DMcCoy Posted January 29, 2014 Posted January 29, 2014 You must *disable* routing on the 2626 And the dhcp server has 192.168.3.38 as it's gateway? 1
BassTech Posted January 29, 2014 Author Posted January 29, 2014 Disabled routing on the 2626 now (thought I already did it), went to check the default gateway on DHCP server and it was set as 192.168.3.200 - changed that to 192.168.3.38 and it picked up an IP address immediately! [borat voice]: Great Success! Thanks to all for the help - would've really struggled without edugeek Now to configure and connect squid ready for BYOD..... Lee 1
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