Technical data

Installing and Configuring an Enterprise Mesh System
© 2012 Meru Networks, Inc. Wireless Backbones With Enterprise Mesh 265
Connectivity Layer : L2
Dataplane Encryption : off
AP Role : access
Parent MAC Address : 00:00:00:00:00:00
Parent AP ID : 0
Link Probing Duration : 120
AP Model : OAP180
AP Label : ATS5
Sensor AP ID : 0
Hardware Revision :
Power Supply Type : 802.3-af
AP Indoor/Outdoor type : Indoor
Note the output values for the AP Role, Parent AP ID, and Dataplane Encryption
parameters. Initially all new APs have the default values shown above.
2. Change the AP Role to a gateway and enable encryption for security, then reboot
the AP:
Default(config)# ap 1
Default(config-ap)# role gateway
Default(config-ap)# dataplane-encryption on
Default(config-ap)# end
Default)# reload ap 1
(Note that Parent AP configuration is not required for a gateway.)
3. Configure the wireless AP that will become AP 2 and that will consider the
gateway its parent, then reboot the AP:
Default(config)# ap 2
Default(config-ap)# role wireless
Default(config-ap)# parent-ap 1
Default(config-ap)# dataplane-encryption on
Default(config-ap)# end
Default)# reload ap 2
The role wireless is used for all Enterprise Mesh APs that are not a gateway AP.
The parent-ap ID identifies the parent AP for connection, AP 1 (the gateway) in
this example.
4. Configure the third AP, which refers to AP 2 as its parent, as follows:
Default# configure terminal
Default(config)# ap 3
Default(config-ap)# role wireless
Default(config-ap)# parent-ap 2
Default(config-ap)# dataplane-encryption on
Default(config-ap)# end
Default)# reload ap 3
5. Configure the last AP, the leaf, as follows:
Default# configure terminal
Default(config)# ap 4
Default (config)# role wireless