Cisco Cisco Aironet 2600e Access Point 설치 가이드
12
8
Mounting the Access Point
Cisco Aironet 2600 series access points can be mounted in several configurations, including on a suspended ceiling, on a hard
ceiling or wall, on an electrical or network box, and above a suspended ceiling. Click this URL to browse to complete access
point mounting instructions:
ceiling or wall, on an electrical or network box, and above a suspended ceiling. Click this URL to browse to complete access
point mounting instructions:
9
Deploying the Access Point on the Wireless Network
After you have mounted the access point, follow these steps to deploy it on the wireless network:
Step 1
Connect and power up the access point.
Step 2
Observe the access point LED (for LED descriptions, see
a.
When you power up the access point, it begins a power-up sequence that you can verify by observing the access point
LED. If the power-up sequence is successful, the discovery and join process begins. During this process, the LED blinks
sequentially green, red, and off. When the access point has joined a controller, the LED is green if no clients are associated
or blue if one or more clients are associated.
LED. If the power-up sequence is successful, the discovery and join process begins. During this process, the LED blinks
sequentially green, red, and off. When the access point has joined a controller, the LED is green if no clients are associated
or blue if one or more clients are associated.
b.
If the LED is not on, the access point is most likely not receiving power.
c.
If the LED blinks sequentially for more than 5 minutes, the access point is unable to find its primary, secondary, and
tertiary Cisco wireless LAN controller. Check the connection between the access point and the Cisco wireless LAN
controller, and be sure the access point and the Cisco wireless LAN controller are either on the same subnet or that the
access point has a route back to its primary, secondary, and tertiary Cisco wireless LAN controller. Also, if the access
point is not on the same subnet as the Cisco wireless LAN controller, be sure that there is a properly configured DHCP
server on the same subnet as the access point. See the
tertiary Cisco wireless LAN controller. Check the connection between the access point and the Cisco wireless LAN
controller, and be sure the access point and the Cisco wireless LAN controller are either on the same subnet or that the
access point has a route back to its primary, secondary, and tertiary Cisco wireless LAN controller. Also, if the access
point is not on the same subnet as the Cisco wireless LAN controller, be sure that there is a properly configured DHCP
server on the same subnet as the access point. See the
Step 3
Reconfigure the Cisco wireless LAN controller so that it is not the Master.
Note
A Master Cisco wireless LAN controller should be used only for configuring access points and not in a working
network.
network.
10
Troubleshooting
If you experience difficulty getting your access point installed and running, look for a solution to your problem in this guide or
in additional access point documentation. These, and other documents, are available on Cisco.com.
in additional access point documentation. These, and other documents, are available on Cisco.com.
Guidelines for Using Cisco Aironet Lightweight Access Points
Keep these guidelines in mind when you use 2600 series lightweight access points:
•
The access point can only communicate with Cisco wireless LAN controllers, such as 2500 series, 5500 series, and WiSM
controllers.
controllers.
•
The access point does not support Wireless Domain Services (WDS) and cannot communicate with WDS devices. However,
the controller provides functionality equivalent to WDS when the access point joins it.
the controller provides functionality equivalent to WDS when the access point joins it.
•
CAPWAP does not support Layer 2. The access point must get an IP address and discover the controller using Layer 3,
DHCP, DNS, or IP subnet broadcast.
DHCP, DNS, or IP subnet broadcast.
•
The access point console port is enabled for monitoring and debug purposes. All configuration commands are disabled when
the access point is connected to a controller.
the access point is connected to a controller.