MSM 710

[Ian Power]

Hi I need to setup a Managed Wireless network and I have selected to use the MSM710 as I used to use Colubris in the past. The question I have is as follows.

5 of my Access points are going to be accross a Wireless bridge. If both sides of the wireless bridge (building A & Building B) are one flat network using the 1 IP address range, will the AP's in the remote site access the WLAN Controller for centralised management and roaming control?

[cenk sasmaztin]

yes it is possible

http://www.hp.com/rnd/support/manuals/mscseries.htm

reading management and configuration guide

[stevephillips79]

hi,
i dont know more about it but Quickstart introduces the MSM710 Controller, formerly MSC-5100, and shows you how to get started using it.




___________________________________________

Want to get-on Google's first page and loads of traffic to your website? Hire a SEO Specialist from Ocean Groups [url=http://oceangroups.org/] seo specialist [/url]

[Troy Jollimore]

I have a similar setup. On a flat network the wireless bridge should be a non-issue since it passes all traffic. It's only when you start to segment into subnets or otherwise control packets that you'll need to be more careful with configuration.

I'd be interested in your progress, as I'm just starting this thing up myself.

[Troy Jollimore]

Just an update. I set up the LAN port on my MSM710 controller as 192.168.0.1, which intimates that WLAN devices will use that same subnet and use that IP address as their gateway. I then set the Internet port up as 192.168.1.182, which is the same as the rest of my site LAN. The LAN's gateway is then set up as the default route. The MSM710 is only set up with one VSC so far, providing DHCP on the Client Tunnels only. This will give WLAN devices access to the Internet, as well as to the rest of the network via direct IP access, or if you have DNS or Host Entries set up.

That's it in it's simplest on a network with no VLANs or other routing. One con is that the APs each take an address from my existing DHCP server on the .1.x subnet. This can easily be overcome with the proper use of VLANs and routing, however. That'll probably be your next step with the network in any case.