Cisco Aironet 1815m Manual
Cisco
Adgangspunkt
Aironet 1815m
Læs nedenfor 📖 manual på dansk for Cisco Aironet 1815m (40 sider) i kategorien Adgangspunkt. Denne guide var nyttig for 22 personer og blev bedømt med 4.5 stjerner i gennemsnit af 2 brugere
Side 1/40
G ETTING S GTARTED UIDE
Cisco Aironet 1815m Access Point
3
1 About this Guide
This guide provides instructions on how to install and configure the Cisco Aironet 1815m Access
Point. This guide also provides mounting instructions and limited troubleshooting procedures.
The Cisco Aironet 1815m Access Point is referred to as the access point, or abbreviated as AP in this
document.
2 About the Access Point
The Cisco Aironet 1815m access point is an 802.11 a/b/g/n/ac (Wave 2) access point, with internal
antennas only. The access point can be mounted on a wall or a ceiling, and supports 2x2:2 SS
MU-MIMO applications.
Access Point Model Numbers and Regulatory Domains
The Cisco Aironet 1815m access point model has the model number format AIR-AP1815M-x-K9,
where the ‘x’ placeholder represents the regulatory domain. The ‘x’ can be any one of the supported
regulatory domains listed at:
http://www.cisco.com/go/aironet/compliance
8
Figure 1 Access Point Status LED and Ports Location
Tip The Cisco Aironet 1815m access point looks visually similar to the 1815i AP. However, the
Cisco logo on the 1815m has a deep blue color, unlike the grey colored logo on the 1815i.
1
Status LED.
For more information, see the “Access Point Status LED” section on page 18
2
Security screw hole location, where the security screw locks the AP to its mounting bracket,
AIR-AP-BRACKET-8
3Location of the console port, the PoE port, and the Mode button.
354952
1
2
3
9
Figure 2 Access Point Ports and Mode Button
Figure 3 AIR-AP-BRACKET-8
1RJ45 console port
2PoE-In port (Ethernet Uplink port)
3Mode button.
For information on how to use the Mode button, see “Using the Mode Button” section on
page 20.
354953
1 2 3
354954
10
6 Preparing the AP for Installation
Before you mount and deploy your access point, we recommend that you perform a site survey (or use
the site planning tool) to determine the best location to install your access point.
You should have the following information about your wireless network available:
• Access point locations.
• Access point mounting options: on a wall or a ceiling only.
Note You can mount the access point above a suspended ceiling but you must purchase
additional mounting hardware: See “Mounting the Access Point” section on page 14 for
additional information.
• Powered by 802.3af, through PoE from a network device or a PoE power injector or hub (usually
located in a wiring closet).
Note Access points mounted in a building’s environmental airspace must be powered using PoE
to comply with safety regulations.
Cisco recommends that you make a site map showing access point locations so that you can record the
device MAC addresses from each location and return them to the person who is planning or managing
your wireless network.
7 Installation Overview
Installing the access point involves these operations:
Step 1 Performing a Pre-Installation Configuration, page 11 (optional)
Step 2 Mounting the Access Point, page 14
Step 3 Powering the Access Point, page 14
Step 4 Configuring and Deploying the Access Point, page 15
12
Step 1 Make sure that the Cisco wireless LAN controller DS port is connected to the network. Use
the CLI, web-browser interface, or Cisco Prime Infrastructure procedures as described in the
appropriate Cisco wireless LAN controller guide.
a. Make sure that access points have Layer 3 connectivity to the Cisco wireless LAN controller
Management and AP-Manager Interface.
b. Configure the switch to which your access point is to attach. See the Cisco Wireless LAN
Controller Configuration Guide for the release you are using, for additional information.
c. Set the Cisco wireless LAN controller as the master so that new access points always join with
it.
d. Make sure DHCP is enabled on the network. The access point must receive its IP address
through DHCP.
e. CAPWAP UDP ports must not be blocked in the network.
f. The access point must be able to find the IP address of the controller. This can be
accomplished using DHCP, DNS, or IP subnet broadcast. This guide describes the DHCP
method to convey the controller IP address. For other methods, refer to the product
documentation. See also the “Configuring DHCP Option 43” section on page 23 for more
information.
Note The access point requires a Gigabit Ethernet (GbE) link to prevent the Ethernet port from
becoming a bottleneck for traffic because wireless traffic speeds exceed transmit speeds
of a 10/100 Ethernet port.
Step 2 Apply power to the access point. See “Powering the Access Point” section on page 14.
a. As the access point attempts to connect to the controller, the LED cycles through a green, red,
and amber sequence, which can take up to 5 minutes.
Note If the access point remains in this mode for more than five minutes, the access point is
unable to find the Master Cisco wireless LAN controller. Check the connection between
the access point and the Cisco wireless LAN controller and be sure that they are on the
same subnet.
b. If the access point shuts down, check the power source.
c. After the access point finds the Cisco wireless LAN controller, it attempts to download the
new operating system code if the access point code version differs from the Cisco wireless
LAN controller code version. While this is happening, the Status LED blinks amber.
13
d. If the operating system download is successful, the access point reboots.
Step 3 Configure the access point if required. Use the controller CLI, controller GUI, or Cisco Prime
Infrastructure to customize the access-point-specific 802.11ac network settings.
Step 4 If the pre-installation configuration is successful, the Status LED is green indicating normal
operation. Disconnect the access point and mount it at the location at which you intend to
deploy it on the wireless network.
Step 5 If your access point does not indicate normal operation, turn it off and repeat the
pre-installation configuration.
Note When you are installing a Layer 3 access point on a different subnet than the Cisco
wireless LAN controller, be sure that a DHCP server is reachabl
e from the subnet on
which you will be installing the access point, and that the subnet has a route back to
the Cisco wireless LAN controller. Also be sure that the route back to the Cisco
wireless LAN controller has destination UDP ports 5246 and 5247 open for CAPWAP
communications. Ensure that the route back to the primary, secondary, and tertiary
wireless LAN controller allows IP packet fragments. Finally, be sure that if address
translation is used, that the access point and the Cisco wireless LAN controller have
a static 1-to-1 NAT to an outside address. (Port Address Translation is not
supported.)
17
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 “Checking the Access Point LED”
section on page 18).
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 chirping green if no clients are associated or
green 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
“Configuring DHCP Option 43” section on page 23 for additional information.
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.
18
12 Checking the Access Point LED
Access Point Status LED
Note It is expected that there will be small variations in the LED color intensity and hue from unit
to unit. This is within the normal range of the LED manufacturer’s specifications and is not a
defect.
The access point status LED indicates various conditions which are described in Table 2.
Table 2 LED Status Indications
Message
Type
LED State Message
Meaning
Boot loader status
sequence
Blinking Green DRAM memory test in progress
DRAM memory test OK
Board initialization in progress
Initializing FLASH file system
FLASH memory test OK
Initializing Ethernet
Ethernet OK
Starting the Cisco AP-OS operating system of the
AP
Initialization successful
Association status Chirping Green Normal operating condition, but no wireless
client associated
Green Normal operating condition with at least one
wireless client association
Operating status Blinking Amber Software upgrade is in progress.
Cycling through Green,
Red, and Amber
Discovery/join process is in progress.
Rapidly cycling
through Red, Green,
Amber, and off.
Access point location command invoked from
controller web interface.
Blinking Red Ethernet link is not operational.
20
13 Miscellaneous Usage and Configuration Guidelines
Using the Mode Button
Using the Mode button (see Figure 2) you can:
• Reset the AP to it’s default factory-shipped configuration.
• Clear the AP internal storage, including all configuration files and the regulatory domain
configuration.
To use the mode button, press, and keep pressed, the mode button on the access point during the AP
boot cycle. Wait until the AP status LED changes to Amber. During this, the AP console shows a
seconds counter, counting the number of seconds the mode button is pressed. Then:
• To reset the AP to default factory-shipped configuration, keep the mode button pressed for less
than 20 seconds. The AP configuration files are cleared.
This resets all configuration settings to factory defaults, including passwords, encryption keys, the
IP address, and the SSID. However, the regulatory domain provisioning is not reset.
• To clear the AP internal storage, including all configuration files and the regulatory domain
configuration, keep the mode button pressed for more than 20 seconds, but less than 60 seconds.
The AP status LED changes from Amber to Red, and all the files in the AP storage directory are
cleared.
If you keep the mode button pressed for more than 60 seconds, the mode button is assumed faulty and
no changes are made.
21
Troubleshooting the Access Point to
Cisco Controller
Join Process
Note Ensure that your controller is running the latest Cisco Wireless Controller Software Release
as specified in the access point’s data sheet.
Access points can fail to join a controller for many reasons: a RADIUS auth
orization is pending;
self-signed certificates are not enabled on the controller; the access point’s and controller’s regulatory
domains don’t match, and so on.
Controller software enables you to configure the access points to send all CAPWAP-related errors to
a syslog server. You do not need to enable any debug commands on the controller because all of the
CAPWAP error messages can be viewed from the syslog server itself.
The state of the access point is not maintained on the controller until it receives a CAPWAP join
request from the access point. Therefore, it can be difficult to determine why the CAPWAP discovery
request from a certain access point was rejected. In order to
troubleshoot such joining problems
without enabling CAPWAP debug commands on the controller, the controller collects information for
all access points that send a discovery message to it and maintains information for any access points
that have successfully joined it.
The controller collects all join-related information for each access point that sends a CAPWAP
discovery request to the controller. Collection begins with the first discovery message received from
the access point and ends with the last configuration payload sent from the controller to the access
point.
You can view join-related information for up to three times the maximum number of access points
supported by the platform for the 2500 series controllers and the Controller Network Module within
the Cisco 28/37/38xx Series Integrated Services Routers.
Note The maximum number of access points varies for the Cisco WiSM2, depending on which
controller software release is being used.
When the controller is maintaining join-related information for the maximum number of access points,
it does not collect information for any more access points.
An access point sends all syslog messages to IP address 255.255.255.255 by default when any of the
following conditions are met:
• An access point running software release 8.0.x.x or later has been newly deployed.
22
• An existing access point running software release 8.0.x.x or later has been reset after clearing the
configuration.
If any of these conditions are met and the access point has not yet joined a controller, you can also
configure a DHCP server to return a syslog server IP address to the access point using option 7 on the
server. The access point then starts sending all syslog messages to this IP address.
When the access point joins a controller for the first time, the controller sends the global syslog server
IP address (the default is 255.255.255.255) to the access point. After that, the access point sends all
syslog messages to this IP address until it is overridden by one of the following scenarios:
• The access point is still connected to the same controller, and the global syslog server IP address
configuration on the controller has been changed using the config ap syslog host global
syslog_server_IP_address command. In this case, the controller
sends the new global syslog server
IP address to the access point.
• The access point is still connected to the same controller, and a specific syslog server IP address
has been configured for the access point on the controller using the config ap syslog host specific
Cisco_AP syslog_server_IP_address command. In this case, the controller sends the new specific
syslog server IP address to the access point.
• The access point is disconnected from the controller and joins another controller. In this case, the
new controller sends its global syslog server IP address to the access point.
• Whenever a new syslog server IP address overrides the existing syslog server IP address, the old
address is erased from persistent storage, and the new address is stored in its place. The access
point also starts sending all syslog messages to the new IP address provided the access point can
reach the syslog server IP address.
You can configure the syslog server for access points and view th
e access point join information only
from the controller CLI.
Important Information for Controller-based Deployments
Keep these guidelines in mind when you use 1815m series access points:
• The access point can only communicate with Cisco wireless LAN 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.
• 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.
• 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.
23
Configuring DHCP Option 43
You can use DHCP Option 43 to provide a list of controller IP addresses to the access points, enabling
them to find and join a controller.
The following is a DHCP Option 43 configuration example on a Windows 2003 Enterprise DHCP
server for use with Cisco Aironet lightweight access points. For other DHCP server implementations,
consult product documentation for configuring DHCP Option 43. In Option 43, you should use the
IP address of the controller management interface.
The 1815m series access point uses the type-length-value (TLV) format for DHCP Option 43. DHCP
servers must be programmed to return the option based on the access point’s DHCP Vendor Class
Identifier (VCI) string (DHCP Option 43). The VCI string for the 1815m access point is:
Cisco AP c1815m
The format of the TLV block is listed below:
• Type: 0xf1 (decimal 241)
• Length: Number of controller IP addresses * 4
• Value: List of WLC management interfaces
To configure DHCP Option 43 in the embedded Cisco DHCP server, follow these steps:
Step 1 Enter configuration mode at the CLI.
Step 2 Create the DHCP pool, including the necessary parameters such as default router and name
server. A DHCP scope example is as follows:
ip dhcp pool <pool name>
network <IP Network> <Netmask>
default-router <Default router>
dns-server <DNS Server>
Where:
<pool name> is the name of the DHCP pool, such as AP1815M
<IP Network> is the network IP address where the controller resides, such as
10.0.15.1
<Netmask> is the subnet mask, such as 255.255.255.0
<Default router> is the IP address of the default router, such as 10.0.0.1
<DNS Server> is the IP address of the DNS server, such as 10.0.10.2
Step 3 Add the option 43 line using the following syntax:
28
Statement 371—Power Cable and AC Adapter
English Translation
When installing the product, please use the provided or designated connection cables/power cables/AC
adaptors. Using any other cables/adaptors could cause a malfunction or a fire. Electrical Appliance and
Material Safety Law prohibits the use of UL-certified cables (that have the “UL” shown on the code)
for any other electrical devices than products designated by CISCO. The use of cables that are certified
by Electrical Appliance and Material Safety Law (that have “PSE” shown on the code) is not limited
to CISCO-designated products.
Produkt Specifikationer
| Mærke: | Cisco |
| Kategori: | Adgangspunkt |
| Model: | Aironet 1815m |
Har du brug for hjælp?
Hvis du har brug for hjælp til Cisco Aironet 1815m stil et spørgsmål nedenfor, og andre brugere vil svare dig
Adgangspunkt Cisco Manualer
15 Januar 2025
13 Januar 2025
9 Oktober 2024
7 Oktober 2024
27 September 2024
19 September 2024
1 September 2024
9 August 2024
8 August 2024
7 August 2024
Adgangspunkt Manualer
- Adgangspunkt Bosch
- Adgangspunkt Aruba
- Adgangspunkt Netis
- Adgangspunkt Moog
- Adgangspunkt TP-Link
- Adgangspunkt HP
- Adgangspunkt D-Link
- Adgangspunkt Asus
- Adgangspunkt AVM
- Adgangspunkt Planet
- Adgangspunkt Belkin
- Adgangspunkt Edimax
- Adgangspunkt Black Box
- Adgangspunkt DataVideo
- Adgangspunkt TRENDnet
- Adgangspunkt Honeywell
- Adgangspunkt Buffalo
- Adgangspunkt Linksys
- Adgangspunkt Huawei
- Adgangspunkt Netgear
- Adgangspunkt Totolink
- Adgangspunkt Digitus
- Adgangspunkt Zebra
- Adgangspunkt Techly
- Adgangspunkt Dell
- Adgangspunkt Alcatel-Lucent
- Adgangspunkt LevelOne
- Adgangspunkt ZyXEL
- Adgangspunkt Fortinet
- Adgangspunkt Tenda
- Adgangspunkt LigoWave
- Adgangspunkt EQ3
- Adgangspunkt Ubiquiti Networks
- Adgangspunkt EnGenius
- Adgangspunkt Devolo
- Adgangspunkt Grandstream
- Adgangspunkt Renkforce
- Adgangspunkt Mikrotik
- Adgangspunkt Eminent
- Adgangspunkt Hercules
- Adgangspunkt V7
- Adgangspunkt Amer Networks
- Adgangspunkt Mercku
- Adgangspunkt EQ-3
- Adgangspunkt Vimar
- Adgangspunkt Dahua Technology
- Adgangspunkt Speco Technologies
- Adgangspunkt StarTech.com
- Adgangspunkt Draytek
- Adgangspunkt Crestron
- Adgangspunkt Lindy
- Adgangspunkt Lancom
- Adgangspunkt Sitecom
- Adgangspunkt AMX
- Adgangspunkt Homematic IP
- Adgangspunkt Intellinet
- Adgangspunkt Kingston
- Adgangspunkt Steren
- Adgangspunkt Media-Tech
- Adgangspunkt Moxa
- Adgangspunkt Allnet
- Adgangspunkt Allied Telesis
- Adgangspunkt Airlive
- Adgangspunkt Macally
- Adgangspunkt Hawking Technologies
- Adgangspunkt INCA
- Adgangspunkt Advantech
- Adgangspunkt Silex
- Adgangspunkt SMC
- Adgangspunkt Cambium Networks
- Adgangspunkt CradlePoint
- Adgangspunkt FlyingVoice
- Adgangspunkt Extreme Networks
- Adgangspunkt Aerohive
- Adgangspunkt Bountiful
- Adgangspunkt WatchGuard
- Adgangspunkt NUVO
- Adgangspunkt Cudy
- Adgangspunkt IP-COM
- Adgangspunkt Mach Power
- Adgangspunkt Syscom
- Adgangspunkt Meru
- Adgangspunkt Amped Wireless
- Adgangspunkt 3Com
- Adgangspunkt Ruckus Wireless
- Adgangspunkt Bintec-elmeg
- Adgangspunkt Brocade
- Adgangspunkt ICC
- Adgangspunkt Insteon
- Adgangspunkt Juniper
- Adgangspunkt Comtrend
- Adgangspunkt Premiertek
- Adgangspunkt Atlantis Land
- Adgangspunkt Mojo
- Adgangspunkt Luxul
- Adgangspunkt Peplink
Nyeste Adgangspunkt Manualer
20 Marts 2025
13 Januar 2025
13 Januar 2025
12 Januar 2025
30 December 2025
26 December 2024
23 December 2024
23 December 2024
16 December 2024
15 December 2024