Setting up a WISM2 to replace a WLC 4402

[ethutchinson]

We are replacing a WLC 4402 with a WISM2 we inherited from another department. The WLC 4402 has three interfaces. AP-manager (APs), Guest, and a secure for interior share access. I was successful in setting up the new AP-manager on the WISM2 with it's own VLAN and DHCP scope. I have also setup a new Guest wireless on the WISM2 with its own VLAN and DHCP scope that is completely separate from the production one on the WLC 4402. Our switching gear is HP procurve except the core which is HPE comware. The DHCP is done on a MS server 2016. I have a test Procurve switch setup off my core that has all the proper vlans for the WISM2. Everytime I try to get an IP address through DHCP for the new guest wireless it fails every time. In the DHCP logs I am finding entries with "BAD address". I thought maybe since my phone was on the production guest wireless previously it was rejecting me because it saw a duplicate MAC address (my phone) attaching to another scope. So I tried my notebook which has never used the production Guest wireless and the same result happens. I would think the Guest DHCP was being blocked somehow but the AP-manager DHCP scope for the WISM2 is working fine.

Any Ideas?

Software on the WISM2 is 8.0.120.0

[patoberli]

Yes you have to create those VLANs on all switches where this traffic should flow to/from. At a minimum the 6500. 

[ethutchinson]

patoberli and David,

Ok I can take care of that. I do find it curious/odd that VLAN id 15 which is listed as the ap-manager interface (hands out ip addresses to APs on the WISM2) is nowhere in sight when I do a sh vlan on the 6500. This interface is the only one of the three that actually works.

HMMMM

By the way thanks in advance for helping out my  HP based networking knowledge

[David Ritter]

I suspect that is because you have it set Native and not tagged.  Remember, the DHCP server hands out IP's to AP's. based upon local addressing,  the WISM would provide IP's to client devices if not doing DHCP passthru.

[ethutchinson]

David,

Once I created the vlans for guest and secure interfaces on the Core and I allowed them to work with the WISM

"wism module x controller 1 allowed_vlan (Vlan ids)

Everything came up. Thanks everyone for your help.