Deployment Guide
131
E
XAMPLE
4: C
ONNECTING
H
IVE
AP
S
TO
H
IVE
M
ANAGER
Check that the HiveAPs have made a CAPWAP connection with HiveManager:
Click Monitor > Access Points > HiveAPs.
The page displays the three HiveAPs that you put on the network. If you see the three HiveAPs, refer to
Figure 5 on page 132
. If you do not see them, check the following:
•
Do the HiveAPs 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 booting up. If the PWR status LED on a HiveAP 320 or 340 is pulsing green, it is still
loading the HiveOS firmware. The Power LED on the HiveAP 20 indicates that it is loading firmware by
glowing steady amber. If the PWR status LED is dark, the device does not have power. If a HiveAP 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 HiveAP is powered from an AC outlet, make sure that the power
cable is firmly attached to the power connector, the AC/DC power adaptor, and the outlet.
•
Are the two portals—HiveAP1 and HiveAP2—connected to the Ethernet network?
When the devices are properly connected, the ETH0 status LED on the HiveAP 300 series device pulses
green to indicate a 1000 Mbps link or amber for a 10/100 Mbps link. On the HiveAP 20, the LAN status
LED blinks green to indicate that the link is up and active. If the ETH0 or LAN LED is dark, make sure
that both ends of the Ethernet cable are fully seated in the HiveAP and switch ports. If the ETH0 or LAN
status LED is still dark, try a different cable.
•
Did the HiveAPs receive network settings from a DHCP server? At a minimum, each HiveAP needs to
receive an IP address, netmask, and default gateway in the same subnet as HiveManager. To check their
settings, make a physical or virtual console connection to the HiveAPs,
1
and do the following:
To check the IP address, netmask, and default gateway of the mgt0 interface on a HiveAP, enter
show interface mgt0
, and look at the settings displayed in the output.
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 (HiveAP3) has successfully formed a link with
a portal using the default hive "hive0", enter
show hive hive0 neighbor
and check the Hstate
column. If at least one other HiveAP is listed as a neighbor and its hive state is Auth, the mesh point
has successfully formed a link and can access the network. If the hive state is anything else, it
might still be in the process of forming a link. The following are the various hive states:
Disv (Discover) - Another HiveAP has been discovered, but there is a mismatch with its hive ID.
Neibor (Neighbor) - Another HiveAP has been discovered whose hive ID matches, but it has not
yet been authenticated.
CandPr (Candidate Peer) - The hive ID on a discovered HiveAP matches, and it can accept more
neighbors.
AssocPd (Association Pending) - A HiveAP is on the same backhaul channel, and an association
process in progress.
Assocd (Associated) - A HiveAP has associated with the local HiveAP and can now start the
authentication process.
Auth (Authenticated) - The HiveAP has been authenticated and can now exchange data traffic.
You can also check the presence of hive neighbors by viewing the entries listed in the Supplicant
column for the wifi1.1 interface in the output of the
show auth
command.
1. To make a physical console connection, connect a console cable to the HiveAP as explained in several of the HiveAP platform
chapters. A virtual access console is an SSID that the HiveAP 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 “<hostname>_ac”. Form a
wireless association with the HiveAP through this SSID, check the IP address of the default gateway that the HiveAP assigns to
your wireless client, and then make an SSH or Telnet connection to the HiveAP 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 and password: admin, aerohive. For HiveAPs 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 HiveAP. For a list of country codes, see
"Appendix A Country Codes" on page 213
.
Содержание access point
Страница 1: ...Aerohive Deployment Guide ...
Страница 7: ...HiveAP Compliance Information 6 Aerohive ...
Страница 13: ...Contents 12 Aerohive ...
Страница 37: ...Chapter 2 The HiveAP 20 ag Platform 36 Aerohive ...
Страница 71: ...Chapter 4 The HiveAP 340 Platform 70 Aerohive ...
Страница 81: ...Chapter 5 The HiveAP 320 Platform 80 Aerohive ...
Страница 105: ...Chapter 8 The High Capacity HiveManager Platform 104 Aerohive ...
Страница 123: ...Chapter 10 Using HiveManager 122 Aerohive ...
Страница 209: ...Chapter 14 Deployment Examples CLI 208 Aerohive ...
Страница 217: ...Appenidix A Country Codes 216 Aerohive ...