Black Box LWN602A User Manual page 85

Smartpath enterprise wireless system
Hide thumbs Also See for LWN602A:
Table of Contents

Advertisement

Check that the SmartPath APs have made a CAPWAP connection with SmartPath EMS:
Click "Monitor > Access Points > SmartPath APs."
The page displays the three SmartPath APs that you put on the network. If you see the three SmartPath APs, refer to Figure 8-6.
If you do not see them, check the following:
• Do the SmartPath APs have power?
Check the PWR (Power) status LED on the top of the devices. If it is glowing steady green, it has power and has finished boot-
ing up. If the PWR status LED on a SmartPath AP (LWN602HA) is pulsing green, it is still loading the SmartPathOS firmware. If
the PWR status LED is dark, the device does not have power. If a SmartPath AP is getting power through PoE from the switch
or from a power injector, make sure that the PSE is configured and cabled correctly. If a SmartPath AP is powered from an AC
outlet, make sure that the power cable is firmly attached to the power connector, the AC/DC power adapter, and the outlet.
• Are the two portals—SmartPath AP1 and SmartPath AP2—connected to the Ethernet network?
When the devices are properly connected, the ETH0 status LED on the SmartPath AP (LWN602HA) pulses green to indicate a
1000-Mbps link or amber for a 10-/100-Mbps link. If the ETH0 is dark, make sure that both ends of the Ethernet cable are
fully seated in the SmartPath AP and switch ports. If the ETH0 status LED is still dark, try a different cable.
• Did the SmartPath APs receive network settings from a DHCP server? At a minimum, each SmartPath AP needs to receive an IP
address, netmask, and default gateway in the same subnet as SmartPath EMS. To check their settings, make a physical or virtual
console connection to the SmartPath APs,* and do the following:
To check the IP address, netmask, and default gateway of the mgt0 interface on a SmartPath AP, enter show interface mgt0,
and look at the settings displayed in the output.
* To make a physical console connection, connect a console cable to the SmartPath AP as explained in Chapter 5 (the SmartPath
AP platform chapter). A virtual access console is an SSID that the SmartPath AP automatically makes available for administrative
access when it does not yet have a configuration and cannot reach its default gateway. By default, the SSID name is "<host-
name>_ac". Form a wireless association with the SmartPath AP through this SSID, check the IP address of the default gateway
that the SmartPath AP assigns to your wireless client, and then make an SSH or Telnet connection to the SmartPath AP at that IP
address. When you first connect, the Initial CLI Configuration Wizard appears. Because you do need to configure all the settings
presented in the wizard, enter N to cancel it. When prompted to log in, enter the default admin name: BB-(last six digits of MAC
address) (for example, BB-123456) and password: blackbox. For SmartPath APs set with "world" as the region code, enter the
boot-param country-code number command. For number, enter the country code for the location where you intend to deploy the
SmartPath AP. For a list of country codes, see Appendix: Country Codes.
A mesh point must first establish a wireless link to a portal over their backhaul interfaces before it can contact a DHCP server.
To see that the mesh point (SmartPath AP3) has successfully formed a link with a portal using the default cluster "cluster0",
enter show cluster cluster0 neighbor and check the Cstate column. If at least one other SmartPath AP is listed as a neighbor
and its cluster state is Auth, the mesh point has successfully formed a link and can access the network. If the cluster state is
anything else, it might still be in the process of forming a link. The following are the various cluster states:
Disv (Discover)—Another SmartPath AP has been discovered, but there is a mismatch with its cluster ID.
Neibor (Neighbor)—Another SmartPath AP has been discovered whose cluster ID matches, but it has not yet been
authenticated.
CandPr (Candidate Peer)—The cluster ID on a discovered SmartPath AP matches, and it can accept more neighbors.
AssocPd (Association Pending)—A SmartPath AP is on the same backhaul channel, and an association process in
progress.
Assocd (Associated) —A SmartPath AP has associated with the local SmartPath AP and can now start the authentication
process.
Chapter 8: Basic Configuration Examples
724-746-5500 | blackbox.com
Page 85

Advertisement

Table of Contents
loading

This manual is also suitable for:

Lwn602aeLwn602haLwn602hae

Table of Contents