WLAN Cloud Services How to configure an Access Point-Sensor

Cloud Adoption How-To Guide
WLAN Cloud Services
How to configure an Access Point-Sensor
WLAN Cloud Services – How to configure an Access Point-Sensor
Prerequisite Requirements
The instructions contained in this document assume the following prerequisites:
1)
Configuration of the Motorola WLAN Controller with:
a)
Matching firmware (WiNG 5.2 or greater) contained on the Access Point.
b)
A profile to configure the Access Point to a completed state once adopted.
2)
Access Point is set to the factory default configuration.
3)
UDP port 24576 is allowed to pass traffic from the Access Point to the WLAN Controller.
Default Configuration
Access Points running WiNG 5.x firmware include the following factory default configuration:
1)
No regulatory, regional or contact information.
2)
A default username admin and password motorola.
3)
HTTPS and SSHv2 management interfaces are enabled.
4)
A DHCP client enabled on VLAN 1.
5)
A zero configuration IPv4 address assigned to VLAN 1.
Initial Login
Using an SSH terminal emulation tool such as PuTTy, connect to the dynamic or zero configuration
IP address assigned to the Access Point:
1)
Login using the default username/password:
ap6521-E3CE9A login: admin
Password: motorola
System is currently using the factory default login credentials.
Please change the default password to protect from unauthorized access.
2)
When prompted enter a new password:
Enter new password: Motorola
Confirm new password: Motorola
Zero Configuration IPv4 Addressing
New Access Points running WiNG 5.X firmware are automatically assigned a link-local zero
configuration IPv4 address which can be used to connect to the Access Point using a standard web
browser or SSHv2 client when a DHCP server is un-available.
Page 1
WLAN Cloud Services – How to configure an Access Point-Sensor
The link-local zero configuration IPv4 address uses the 169.254.0.0/16 range as described in RFC
3927 which is combined with the last two octets of the Access Point’s base Ethernet MAC address to
determine the zero configuration address assigned to the Access Points.
To connect to an Access Point using the zero configuration IPv4 address:
1)
Obtain the Access Point’s base Ethernet MAC address (example 5C-0E-8B-E3-CE-9A)
2)
Convert the last two octets of the Access Points base Ethernet MAC address from HEX to
Decimal (example 5C-0E-8B-E3-CE-9A):
Hex
Decimal
CE
206
9A
154
3)
Add the values to the zero configuration block to determine the zero configuration link-local
address (example 169.254.206.154/16).
4)
Change the IP address of the PC to be in the same subnet as the zero configuration link-local
address (example 169.254.206.155).
Optional IP Address Assignment Change
Use the following to change the IP address on the VLAN. The Access Point can be accessed with
either a private IPv4 address in the 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16 ranges as described
in RFC 1918, a dynamic IP address from a DHCP server, or the Zero Configuration IPv4 address in
the 169.254.0.0/16 range as described in RFC 3927.
1)
Enable the Privileged Exec mode:
ap6521-E3CE9A>enable
2)
Access the Access Point’s device configuration:
ap6521-E3CE9A#configure self
Enter configuration commands, one per line.
3)
End with CNTL/Z.
Create a virtual IP interface for VLAN 1:
ap6521-E3CE9A(config-device-5C-0E-8B-E3-CE-9A)#interface vlan1
4)
Define one of the following IP address assignments:
Private IPv4 Address:
ap6521-E3CE9A(config-device-5C-0E-8B-E3-CE-9A-if-vlan1)#ip address 10.0.0.0/8
DHCP Address:
Page 2
WLAN Cloud Services – How to configure an Access Point-Sensor
ap6521-E3CE9A(config-device-5C-0E-8B-E3-CE-9A-if-vlan1)#ip address dhcp
Zero Configuration Ipv4 Address:
ap6521-E3CE9A(config-device-5C-0E-8B-E3-CE-9A-if-vlan1)#ip address zeroconf
5)
Commit and save the changes:
ap6521-E3CE9A(config-device-5C-0E-8B-E3-CE-9A-if-vlan1)#commit
ap6521-E3CE9A(config-device-5C-0E-8B-E3-CE-9A-if-vlan1)#write memory
ap6521-E3CE9A(config-device-5C-0E-8B-E3-CE-9A-if-vlan1)#end
Basic Configuration Procedure
Define the Controller Host entries to adopt the Access Point to the Primary WLAN Controller
(example WLAN IP address 64.233.160.23). A fail-over Secondary WLAN controller can also be
defined (example WLAN IP address 64.233.160.24).
1)
Enable the Privileged Exec mode:
ap6521-E3CE9A>enable
2)
Access the Access Points device configuration:
ap6521-E3CE9A#configure self
Enter configuration commands, one per line.
3)
End with CNTL/Z.
Configure LAN and WAN controllers to prevent adoption to local controllers on the same
VLAN as the Access Point:
Disable adoption on the VLAN interface:
ap6521-E3CE9A(config-device-5C-0E-8B-E3-CE-9A)#no mint mlcp vlan
Enable adoption over the IP network:
ap6521-E3CE9A(config-device-5C-0E-8B-E3-CE-9A)#mint mlcp ip
!
4)
Caution – LAN adoption must be disabled before plugging the Access Point into a WLAN controller
when a Motorola WLAN controller is used as a DHCP server on the local LAN.
Define the primary and optionally a secondary host controller:
ap6521-E3CE9A(config-device-5C-0E-8B-E3-CE-9A)#controller host 64.22.87.174 level 2
ap6521-E3CE9A(config-device-5C-0E-8B-E3-CE-9A)#controller host 64.22.87.175 level 2
Page 3
WLAN Cloud Services – How to configure an Access Point-Sensor

Note – A secondary controller is used as a fail-over and should have the same configuration files as
the primary controller.
5)
Commit and save the changes:
ap6521-E3CE9A(config-device-5C-0E-8B-E3-CE-9A)#commit
ap6521-E3CE9A(config-device-5C-0E-8B-E3-CE-9A)#write memory
ap6521-E3CE9A(config-device-5C-0E-8B-E3-CE-9A)#end
Verification
Use the following procedures to verify the Access Point and WLAN Controller adoption and
communication:
1)
Verify the controller adoption type, system name, MAC address, mint address and time:
ap6521-E3CE9A(config-device-5C-0E-8B-E3-CE-9A)#show adoption status
Adopted by:
Type
System Name
MAC address
MiNT address
Time
2)
:
:
:
:
:
NX9000
nx9000-noc
00-0C-29-E2-FD-76
12.E2.FD.76
0 days 00:11:03 ago
Verify the Access Point communicated correctly with the WLAN Controller:
ap6521-E3CE9A(config-device-5C-0E-8B-E3-CE-9A)#show mint mlcp history
2013-03-09 16:14:23:MLCP VLAN disabled
2013-03-09 16:14:23:DNS resolution completed, starting MLCP
2013-03-09 16:14:23:Start mlcp ip discover
2013-03-09 16:14:23:Sending MLCP_DISCOVER to IP 64.22.87.174, UDP port 0
2013-03-09 16:14:24:Received 0 hostnames through option 191
2013-03-09 16:14:28:Sending MLCP_DISCOVER to IP 64.22.87.174, UDP port 0
2013-03-09 16:14:33:Sending MLCP_DISCOVER to IP 64.22.87.174, UDP port 0
2013-03-09 16:14:33:Received offer from 64.22.87.174:24576 preferred=0 capacity =
10236 (force:1, level 2)
2013-03-09 16:14:38:Sending MLCP_REQUEST to 64.22.87.174:24576
2013-03-09 16:14:38:MLCP created level 2 force:1 IP link to 64.22.87.174:24576
Post Adoption
After adoption the Access Point will automatically:
1)
Upgrade to the latest firmware.
2)
Pull Configuration for:
Page 4
WLAN Cloud Services – How to configure an Access Point-Sensor
a)
Radio 1 – WLAN with Radio Share.
b)
Radio 2 (on dual radio Access Point) – Sensor
Use the following procedure to verify ADSP communication on the Access Point:
1)
Verify the sensor-server host, port and status:
ap6521-E3CE9A(config-device-5C-0E-8B-E3-CE-9A-if-vlan1)#show wireless sensor-server
-------------------------------------------------------------------------------#
SENSOR SERVER HOST
PORT
STATUS
-------------------------------------------------------------------------------1
64.22.87.174
443
online
2
0
no server defined
3
0
no server defined
--------------------------------------------------------------------------------
Page 5
WLAN Cloud Services – How to configure an Access Point-Sensor
MOTOROLA, MOTO, MOTOROLA SOLUTIONS and the Stylized M Logo are trademarks or registered
trademarks of Motorola Trademark Holdings, LLC and are used under license. All other trademarks are the
property of their respective owners.
© 2013 Motorola Solutions, Inc. All rights reserved
Page 6