Technical data

270 Meru System Director Configuration Guide © 2012 Meru Networks, Inc.
Enterprise Mesh Troubleshooting
2. Associate with the ESSID. The ESSID is beaconing, but hidden (the hidden-bit is
set in beacons) so do this:
a.
Open Network Connections (Network Places -> View Network Connections)
b. Open View the available networks from the Intel(R) PRo/Wireless
Connection.
c. Change the order of preferred Networks from the left panel under Related
tasks
d. Click Add a preferred network and supply the parameters SSID mcow-aabbcc
where aabbcc are the last 3 bytes of the AP’s MAC address (which is the Serial
Number in the show ap output).
Accessing Wireless AP via Console-over-Wireless Example
 Your Enterprise Mesh interface (wds1-31) is 00:12:F2:aa:bb:cc
 Your CoW ESSID is “mcow-aabbcc”
— Network Authentication is Open
— Data Encryption is WEP
— Uncheck The key is provided for me automatically
— Network key is mC0w!
— Key Index is 3
— Click OK twice
 Disable and enable your interface and based on order you connect to the ESS. Note
that it shows “limited or no connectivity” because you don't get (or need) any IP
address.
:
3. Connect to the AP with wcoe.exe as follows:
— wcoe -p -d 00:12:F2:c0:ec:0e (you must use this command, as shown)
— Select your Centrino interface
— Pressing Enter gives you login prompt from the AP
— To Escape out of the terminal program use Ctrl-Break
— You can login as user admin with the default password admin
— Use the command wbsclient display flash, which is the command to do the
same as wbs display flash from serial console.
:
4. Use the Enterprise Mesh CLI commands to display and configure Enterprise Mesh
parameters:
Note:
This works only if the AP is in discovery loop or has not yet loaded any
ESS profiles after booting up.
Note:
wcoe is L2-based connectivity only, which does not use any IP addresses.
If the node reboots in its discovery loop, as it occasionally does, you may
be disconnected. Wait and reconnect after a short period of time.