+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 20
Wireless Networks Thread, Vlan on Procurve Switch in Technical; I am wanting to setup a VLAN on one network switch as per diagram attached. VLAN 999 has a dedicated ...
  1. #1

    Join Date
    Sep 2009
    Posts
    35
    Thank Post
    20
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Vlan on Procurve Switch

    I am wanting to setup a VLAN on one network switch as per diagram attached. VLAN 999 has a dedicated DHCP server. I have setup the wireless network so all traffic from the BYOD SSID is tagged 999.

    If I connect using a cable into VLAN 999 I can ping all devices in that VLAN. If I connect using a wireless device I canít ping.

    Can anyone help?
    Attached Images Attached Images

  2. #2
    Ergo's Avatar
    Join Date
    Sep 2012
    Location
    Nottingham
    Posts
    111
    Thank Post
    16
    Thanked 26 Times in 25 Posts
    Rep Power
    8
    Does the wireless controller have diagnostic tools from within it's interface such as Ping? If so can you ping from the wireless controller to something on VLAN 999?

    My assumption would be that the wireless system is not correctly tagging traffic onto VLAN 999 when connected to the Guest network. The switch configuration looks correct.

    Dave

  3. Thanks to Ergo from:

    rjones (6th December 2012)

  4. #3

    Join Date
    Feb 2008
    Location
    Wiltshire
    Posts
    878
    Thank Post
    274
    Thanked 139 Times in 112 Posts
    Blog Entries
    26
    Rep Power
    42
    Might want to TAG both the VLANs on the port that AP is plugged into rather than UNTAG? Had a similar issue when I was setting up VLANs for our BYOD.

    Pete

  5. 2 Thanks to FragglePete:

    Ergo (6th December 2012), rjones (6th December 2012)

  6. #4
    Ergo's Avatar
    Join Date
    Sep 2012
    Location
    Nottingham
    Posts
    111
    Thank Post
    16
    Thanked 26 Times in 25 Posts
    Rep Power
    8
    Quote Originally Posted by FragglePete View Post
    Might want to TAG both the VLANs on the port that AP is plugged into rather than UNTAG? Had a similar issue when I was setting up VLANs for our BYOD.
    Good point - will depend on how the wireless controller is configured with the SSID-VLAN associations.

    Dave

  7. #5

    Join Date
    Sep 2009
    Posts
    35
    Thank Post
    20
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Thank you for your reply. When I tag port 9 the AP does not provision or connect to the controller. I can also ping from the controller to an IP on Vlan 999.

  8. #6

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    15,826
    Thank Post
    875
    Thanked 1,675 Times in 1,458 Posts
    Blog Entries
    12
    Rep Power
    444
    If we have multiple vlans on our wireless controller we must make the switch port a trunk port. Have you tried this?

  9. Thanks to FN-GM from:

    rjones (6th December 2012)

  10. #7

    Join Date
    Sep 2009
    Posts
    35
    Thank Post
    20
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Do you mean make the port the controller is connected to a trunk?

  11. #8

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    15,826
    Thank Post
    875
    Thanked 1,675 Times in 1,458 Posts
    Blog Entries
    12
    Rep Power
    444
    Quote Originally Posted by rjones View Post
    Do you mean make the port the controller is connected to a trunk?
    yes

  12. #9
    nicholab's Avatar
    Join Date
    Nov 2006
    Location
    Birmingham
    Posts
    1,463
    Thank Post
    4
    Thanked 97 Times in 93 Posts
    Blog Entries
    1
    Rep Power
    50
    Some wireless system you need to make the port that the AP is connected to a trunk port as this is where traffic originates. Really you should see AP's as another switch so you trunk to these it also mean that you can protect the AP's web interface from access by clients.

  13. #10

    Ric_'s Avatar
    Join Date
    Jun 2005
    Location
    London
    Posts
    7,590
    Thank Post
    109
    Thanked 762 Times in 593 Posts
    Rep Power
    180
    I think that the missing factor is what wireless system you are using. They all do their provisioning differently and this is probably where it is falling down.

  14. #11

    AngryTechnician's Avatar
    Join Date
    Oct 2008
    Posts
    3,730
    Thank Post
    698
    Thanked 1,211 Times in 761 Posts
    Rep Power
    394
    Agree with @Ric_, I think this is going to be something specific to the wireless system. Your ProCurve setup looks fine and is the same as I have setup up our ProCurve for VLANs; all my Ruckus APs and the controller are on access ports, I have not had to make them a trunk port.

  15. #12
    nicholab's Avatar
    Join Date
    Nov 2006
    Location
    Birmingham
    Posts
    1,463
    Thank Post
    4
    Thanked 97 Times in 93 Posts
    Blog Entries
    1
    Rep Power
    50
    From that diagram it suggest that you are not keeping traffic form different SSID on different vlan's is this the case? If I was setting it up I would have each SSID on it own vlan only taking to others at the routing device on the network.

  16. #13

    Join Date
    May 2011
    Location
    Jus North of London, close but not too close
    Posts
    738
    Thank Post
    172
    Thanked 56 Times in 54 Posts
    Rep Power
    35
    Let us know what Wireless system you are having issues with. For example I setup Ruckus at last place as well. I tagged multiple SSID's for different vLANS. I did not however tag the ports that the Access points plugged into for vLAN1 the management/default vLAN which I left due to other issues. I had no issues connetcing to the Guest/BYOD networks unless the Access point was plugged into the wrong switch port.

  17. #14

    Join Date
    Sep 2009
    Posts
    35
    Thank Post
    20
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Thank you for your replies and help. We have the HP MSM760 controller.

  18. #15
    nicholab's Avatar
    Join Date
    Nov 2006
    Location
    Birmingham
    Posts
    1,463
    Thank Post
    4
    Thanked 97 Times in 93 Posts
    Blog Entries
    1
    Rep Power
    50
    I used a wireless system that consisted of the MSM760 and MSM422. The controller need to be in the same vlan as the AP's and that vlan needs DHCP (not the controller). I would configure the port with the AP's to be in untagged ports in the management vlan the same with the controller. You then need to decide which vlan you want to put traffic in form the different ssid's you go to the ssid in the MSM760 to do this. Also beware MSM422 had a tendency to end up in the wrong vlan's. You can tunnel guest traffic back to the controller if you which and then off load it on to the network from there this is where you may need to used a trunked port.

    In Summary I would expect the MSM AP to port to be

    Untagged managment
    Tagged SSID 1
    Tagged SSID 2

    Also to be clear I mean by trunking I mean 802.1Q Vlan Tagging.
    Last edited by nicholab; 7th December 2012 at 09:01 AM.

  19. Thanks to nicholab from:

    rjones (13th December 2012)

SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. Help with configuring DHCP with VLAN on procurve switch
    By chrisjako in forum Wired Networks
    Replies: 16
    Last Post: 3rd February 2012, 03:40 PM
  2. Routing between VLANs on HP ProCurve 4108GL Switch
    By robknowles in forum Wireless Networks
    Replies: 12
    Last Post: 1st June 2010, 08:12 AM
  3. VLANs on HP Switches
    By localzuk in forum Wireless Networks
    Replies: 3
    Last Post: 14th July 2009, 11:19 AM
  4. Changing port vLANs on an HP ProCurve switch
    By MrDylan in forum Hardware
    Replies: 6
    Last Post: 9th March 2006, 03:13 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •