Filter
Top Products
Wireless mobility
Wireless mobility scenario
One MSM7xx service controller such as the MSM710 Mobility Controller or MSM710
Access Controller with a user-installed Mobility license.
Two APs such as the MSM310.
A PBX / VoIP server.
A voice-capable wireless client such as a Wi-Fi phone.
Multiple subnets connected by router. This scenario uses three subnets: 192.168.1.0,
192.168.2.0, and 192.168.3.0.
A DHCP scope defined for each subnet.
A. Configure the network
1. Using appropriate router and DHCP server configuration (beyond the scope of this guide)
construct a three-subnet network as illustrated above with the service controller (LAN
port) on subnet 192.168.1.0, one MSM310 on subnet 192.168.2.0 and another on subnet
192.168.3.0.
B. Pre-configure the service controller
The service controller LAN port defaults to IP address 192.168.1.1. You will likely need to
change this address to an available address on subnet 192.168.1.0. Before connecting the
service controller to your network, pre-configure its IP address as follows:
1. Reset the service controller to its factory defaults. In its management tool, select Service
Controller >> Maintenance > Config file management. For additional information
see Appendix C: Resetting to factory defaults.
2. Set your computer IP address to a value in the range 192.168.1.2 to 192.168.1.254.
3. Disconnect any cable from the service controller Internet port and connect the service
controller LAN port to your computer.
4. In a Web browser, open page: https://192.168.1.1.
5. Select Service Controller >> Network > Ports > LAN port and under Addressing,
set an available Static IP address (192.168.1.10 in this scenario) and Mask. After
selecting Save, you will lose connection with the management tool. This is expected
behavior.
C. Connect the service controller to the network
1. Connect the service controller LAN port to the network on which it will reside (subnet
192.168.1.0).
2. Configure the LAN port on your computer for Automatic IP address assignment by DHCP
and connect it to the same 192.168.1.0 subnet.
3. In a Web browser open page https://<IP address of the service controller>
(192.168.1.10 in this scenario). Confirm that the management tool opens. This is
sufficient to prove that the service controller is reachable on the network via its LAN
port.
11-4