MSM765 SSIDs and VLANs

[niftybit]

We have a HP MSM765 Integrated Controller

 

Software version: 5.7.3.0-13117

 

This is mounted in slot C of an E5412zl switch.

 

Amongst the SSIDs on the controller is one called ‘DSHS Visitor’ which uses VLAN 240 and WPA/WPA2. This was set up by a managed service engineer years ago and works perfectly.

 

When I try to make an exact copy for a new one called ‘DSHS Public’ with VLAN 250 clients are unable to get a DHCP IP address.

 

The VSC bindings are set up the same, if I change the binding for ‘DSHS Public’ to use the VLAN 240 profile, it words – but obviously gives out the wrong IP range.

 

The DHCP ranges are set up on our domain controllers the same, and if accessed via ethernet cable addresses are picked up from DHCP.

 

I feel I’m missing something simple, I’ve followed many guides but never find a solution.

 

Any suggestions of what to try next would be very appreciated.

 

Roger.

[RedwayNetworks_Michael]

Ive sent this one across to my engineers for us. I will let you know what they come back with

[RedwayNetworks_Michael]

We have a HP MSM765 Integrated Controller

 

Software version: 5.7.3.0-13117

 

This is mounted in slot C of an E5412zl switch.

 

Amongst the SSIDs on the controller is one called ‘DSHS Visitor’ which uses VLAN 240 and WPA/WPA2. This was set up by a managed service engineer years ago and works perfectly.

 

When I try to make an exact copy for a new one called ‘DSHS Public’ with VLAN 250 clients are unable to get a DHCP IP address.

 

The VSC bindings are set up the same, if I change the binding for ‘DSHS Public’ to use the VLAN 240 profile, it words – but obviously gives out the wrong IP range.

 

The DHCP ranges are set up on our domain controllers the same, and if accessed via ethernet cable addresses are picked up from DHCP.

 

I feel I’m missing something simple, I’ve followed many guides but never find a solution.

 

Any suggestions of what to try next would be very appreciated.

 

Roger.

Please see below response from the engineers, please do feel free to reach out if you still have issues

 

Engineer comment

In addition to configuring the wireless network to use the 250, you also need to configure the wired network to use VLAN250.

 

I would check the relevant switch ports (such as ports going to the controller, APs & switch uplinks). Depending on the traffic flow not all of these ports need to be tagged, but as a general rule if you have a port tagged to use VLAN240, you would likely need it to also tag VLAN250.

[RedwayNetworks_Michael]

Also - make sure DHCP is accounted for on the new VLAN.

 

This may mean that DHCP relay (sometimes known as "ip helper") needs to be configured on the layer 3 interface for VLAN 250 and also a corresponding sope is configured on the DHCP server.

[Davit2005]

Similar to a lot of other wireless environments every switch port would need to be tagged for each AP where the SSID is broadcast.

 

Aruba Campus APs where you have a controller or mobility masters and controllers the APs form a tunnel back to the controllers so might be no need to tag the individual ports where the APs are connected to for all the different vlans/ssids.

 

The MSM765 is old, I had the pleasure (or not) of working with it 7 years back. I have not got the documentation I created for setting up a SSID on the MSM765 though, I only did one, lol.

[niftybit]

Hi,

Tagging the VLAN from the controller to the APs was the missing part. Using HP Airwave, I had convinced myself that VLAN 240 was on hardly on any switches, this wasn't entirely true - it was on some of them, which was in turn the exact areas that DSHS Visitor was in use. To further muddy things, one area had DSHS Visitor but it didn't have VLAN 240 set as it's egress VLAN, so worked but not in the correct way by giving out addresses in another VLAN.

I've added VLAN 250 to key switches and ports, so now IPs are being given out correctly as they should.

Huge thanks for the help received here.