Technical data

Installing and Configuring an Enterprise Mesh System
© 2012 Meru Networks, Inc. Wireless Backbones With Enterprise Mesh 267
Each Enterprise Mesh node has a forwarding address that contains the destination
for the next hop, which provides the basic forwarding mechanism. As a packet
moves towards the root of the Enterprise Mesh tree, the wds-table records the
route that will be used when the packet is returned.
To ensure that the topology and dataplane-encryption in each AP is correct, issue
the following command for each AP:
show ap 1
...
AP Role : gateway
Parent AP ID : 0
Dataplane-Encryption : off
...
show ap 2
...
AP Role : wireless
Parent AP ID : 1
Dataplane-Encryption : off
...
show ap 3
...
AP Role : wireless
Parent AP ID : 2
Dataplane-Encryption : off
...
show ap 4
AP Role : wireless
Parent AP ID : 3
Dataplane-Encryption : off
Determine from this output that:
— Each AP displays the correct role. In our example, AP1 has the gateway role,
and the remaining three APs are wireless.
— Each wireless AP has two interface identifiers, the first is Ethernet and second
is wireless.
— Each AP has its parent AP ID pointing to the correct AP. In our example, the
gateway AP (AP-1) has no parent. The first wireless AP (AP-2) has the parent
AP ID for the gateway (AP-1), and the second wireless AP (AP-3) has a parent
AP ID of the first wireless AP (AP-2). The final AP has AP3 for a parent AP ID.
Phase 3: Remove the Cables and Deploy the APs
Phase 3 consists of removing the cables, deploying the APs in their final location, and
turning them on. They will then be picked up by the controller as wireless APs.
To deploy the APs, follow these steps:
1. Determine that the first level of wireless APs are provisioned and connected, with
parent APs showing the correct entries.
2. Ensure that each AP has a power source; if you are using PoE, you need to provide
a power supply for wireless nodes or leaf nodes before Step 7.