The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The following topics are covered under this chapter:
The AP 1532 series is an ultra low-profile outdoor access point. This AP has two models, an internal antenna model and an external antenna model.
1 | SN Label | 4 | PoE-In; WAN Port |
2 | Ground | 5 | LAN Port |
3 | DC Power 48 VDC |
1 | Console/Reset | 2 | Solar Shield Screw Holes |
1 | LED |
1 | Flexible Antenna Port (N Type) Connectors |
![]() Note | The Flexible Antenna Port Connectors are only present on the 1532E. |
Product ID | Freq. Band | Gain | Type | Required Quantity |
---|---|---|---|---|
AIR-ANT2547V-N | 2.4 / 5 GHz | 4 / 7 dBi | Omnidirectional | 2 |
AIR-ANT2547VG-N | 2.4 / 5 GHz | 4 / 7 dBi | Omnidirectional | 2 |
AIR-ANT2588P3M-N= | 2.4 / 5 GHz | 8 / 8 dBi | Directional 120x30° | 1 |
AIR-ANT2450V-N= | 2.4 GHz | 5 dBi | Omnidirectional | 2 |
AIR-ANT2480V-N= | 2.4 GHz | 8 dBi | Omnidirectional | 2 |
AIR-ANT2413P2M-N= | 2.4 GHz | 13 dBi | Directional 30x30° | 1 |
AIR-ANT5180V-N= | 5 GHz | 8 dBi | Omnidirectional | 2 |
AIR-ANT5114P2M-N= | 5 GHz | 14 dBi | Directional 30x30° | 1 |
Model | Configuration | Regulatory Domain | Switch Power | AIR-PWRINJ1500-2= | AIR-PWRINJ4= | AC/DC Power Adapter AIR-PWRADPT-1530= |
---|---|---|---|---|---|---|
1532I | 3x3:3 (2.4 GHz)
2x3:2 (5 GHz) |
A, D, K, N, Q, T, Z | UPoE | √ | √ | |
one Tx disabled*
2x3:2 (2.4 GHz) 2x3:2 (5 GHz) |
A, D, K, N, Q, T, Z | 802.3at PoE+ | N/A | √ | N/A | |
3x3:3 (2.4 GHz)
2x3:2 (5 GHz) |
C, E, F, H, M, R, S | 802.3at PoE+ | √ | √ | √ | |
1532E | 2x2:2 (2.4 GHz)
2x2:2 (5 GHz) |
all | 802.3at PoE+ | √ | √ | √ |
![]() Note | For more details please visit the 1532 Hardware Installation guide: http://www.cisco.com/en/US/docs/wireless/access_point/1530/installation/guide/1530hig.html |
There are two terms that are used when referring to Antenna Band Mode Configurations:
Please note that Antenna Band Mode is only available on the 1532E model, with external antennas; the 1532I has an internal antenna and does not require additional antennas.
![]() Note | Misconfiguring the Antenna Band Mode can strand a mesh AP, please make sure your physical antennas are properly configured before changing the Antenna Band Mode. A warning message will be displayed to confirm the changes. |
(Cisco Controller) >config ap antenna-band-mode <single|dual> <ap_name>
(Cisco Controller) >show ap config general <AP_NAME>
Antenna Band Mode ............................... Dual
AP#capwap ap ant-band-mode <dual/single>
One of the key features of the 1532 access point is the ability to “daisy chain” access points while they are operating as Mesh APs (MAPs). By “daisy chaining” MAPs, customers can either operate the access points as a serial backhaul, allowing different channels for uplink and downlink access thus improving backhaul bandwidth, or to extend universal access across a mesh network. Extending universal access allows a customer to connect a local mode or flexconnect mode 1532 access point to the Ethernet port of a MAP, thus extending the network to provide better client access. These features will be explained in greater detail in the following sections.
There are two roles of a daisy-chained access point, the Master AP and Slave AP. The Master AP must be configured as a Mesh AP (MAP), it is also recommended to set a preferred-parent and Bridge-group name. The Slave AP can either be configured as a Bridge Mode Root AP if used for serial backhaul or as a Local/Flexconnect Mode AP if used for extended universal access.
Ethernet Bridging must be enabled on the Master AP, which is configured as a MAP. If the Master AP is part of a multi-hop mesh network, all mesh hops must have Ethernet Bridging enabled including the RAP.
(Cisco Controller) >config ap bridging [enable/disable] <ap_name>
Daisy chaining should only be enabled on a Slave AP that is configured as a Bridge Mode Root Access Point, for all other daisy chaining configurations, daisy chaining does not need to be enabled.
(Cisco Controller) >config ap daisy-chaining [enable/disable] <ap_name>
(Cisco Controller) >show ap config general <ap_name>
Daisy Chaining .................................. Disabled
Daisy-chaining should only be enabled on a Slave AP that is configured as a Bridge Mode Root Access Point, for all other daisy chaining configurations, daisy chaining does not need to be enabled.
AP#capwap ap daisy-chaining <enable/disable>
The Master MAP must have Ethernet Bridging Enabled.
![]() Note | Only Bridge Mode MAPs should be set with a preferred parent. |
![]() Note | When the preferred parent is entered, no other mesh configurations can be submitted at the same time. You must apply the changes, wait 90 seconds, then other mesh changes can be made. |
![]() Note | To clear the Preferred Parent text box, the value "none" must be entered then submitted. |
(Cisco Controller) >config mesh parent preferred <ap_name> <PARENT_MAC_ADDRESS>
(Cisco Controller) >show ap config general <ap_name>
Mesh preferred parent ........................... 00:24:13:0f:92:00
![]() Note | BGN misconfigurations will cause network instability. |
Cisco Controller) >config ap bridgegroupname set MESH-BGN AP_NAME
AP#capwap ap autonomous Convert to Autonomous image. Proceed? (yes/[no]):
![]() Note | This command should only be issued once, during initial priming of the Access Point. |
AP#archive download-sw /force-reload /overwrite tftp://<tftp ip address>/<image name.tar> AP#archieve download-sw /force-reload /overwrite tftp://10.0.0.5/ap1g3-k9w7-tar
Note that the k9w7 denotes the autonomous image. The autonomous image can be found at cisco.com.
AP#archive download-sw /force-reload /overwrite tftp://<tftp ip address>/<image name.tar> AP#archieve download-sw /force-reload /overwrite tftp://10.0.0.5/ap1g3-k9w8-tar
Note that the k9w8 denotes the unified image. The unified image can be found at cisco.com.
Signal Level (dBm) | LED (Status) |
---|---|
>-44 | Constant green |
–47 to –44 | Blinking green fast |
–50 to –47 | Blinking green medium |
–53 to –50 | Constant amber |
–57 to –53 | Blinking amber fast |
–60 to –57 | Blinking amber medium |
–63 to –60 | Blinking amber slow |
–66 to –63 | Blinking red slow |
–69 to –66 | Blinking red medium |
–72 to –69 | Blinking red fast |
–75 to –72 | Constant red |
< –75 | Off |
The Range and Capacity Calculator is available on cisco.com
Deploying an outdoor mesh network requires careful planning and design. RF Nature: Not an Exact Science, Especially in Unlicensed Spectrum. There can be many other devices that can interfere with our mesh network. To optimize the deployment we can follow these recommendations:
Type | LED State | AP Action |
---|---|---|
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 Cisco IOS | ||
Initialization successful | ||
Association status | Chirping GREEN | Normal operating condition, joined to a controller, but no wireless client associated. |
GREEN | Normal operating condition, at least one wireless client association. | |
Operating status | Blinking AMBER | Software upgrade in progress. |
Cycling through GREEN, RED, and AMBER | Discovery/join process in progress. | |
Rapidly cycling through RED, GREEN, AMBER, and OFF | Access Point location command invoked | |
Blinking RED | Ethernet link not operational | |
Boot loader warnings | Blinking AMBER | Configuration recovery in progress (MODE button pushed for 2 to 3 seconds) |
RED | Ethernet failure or image recovery (MODE button pushed for 20 to 30 seconds) | |
Blinking GREEN | Image recovery in progress (MODE button released) | |
Boot loader errors | RED | DRAM memory test failure. |
Blinking RED and AMBER | FLASH file system failure. | |
Blinking RED and off | Environment variable failure. | |
Bad MAC address. | ||
Ethernet failure during image recovery. | ||
Boot environment failure. | ||
No Cisco image file. | ||
Boot failure. | ||
Cisco IOS errors | RED | Software failure; try disconnecting and reconnecting unit power. |
Cycling through RED, GREEN, AMBER, and OFF | General warning; insufficient inline power. |