Cisco AIR-AP1131G-E-K9 Hardware Installation Guide - Page 102

using DHCP Option 43., Step 1 - poe

Get Cisco AIR-AP1131G-E-K9 PDF manuals and user guides View all Cisco AIR-AP1131G-E-K9 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 102 highlights

Appendix E Priming Lightweight Access Points Prior to Deployment Before deploying your lightweight access points to their final locations, follow these steps to prime your access points: Step 1 In a Layer 3 environment, ensure a DHCP server (typically on your switch) is enabled on the same subnet as your lightweight access points. The access points receives its IP address and controller information using DHCP Option 43. The lightweight access point must be able to find the IP address of the controller. This can be accomplished using DHCP, DNS, OTAP, 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 "Using DHCP Option 43" section on page 6-2 for more information. Note For a Layer 3 access point on a different subnet than the controller, ensure the route to the controller has destination UDP ports 12222 and 12223 open for LWAPP communications. Ensure that the routes to the primary, secondary, and tertiary controllers allow IP packet fragments. Step 2 Step 3 Step 4 Ensure that your controller is connected to a switch trunk port. Configure the controller in LWAPP Layer 3 mode and ensure its DS Port is connected to the switch. Use the CLI, web-browser interface, or Cisco WCS procedures as described in the appropriate controller guide. a. In multi-controller environments, You can set one controller's DS port to Master (you can use the config network master-base disable CLI command or you can use the controller GUI) so that new lightweight access points always associate with it. You can use the show network config CLI command to determine if the controller DS port is the master. All lightweight access points associate to the master controller. From one location, you can configure lightweight access point settings such as primary, secondary, and tertiary controllers. This allows you to redistribute your lightweight access points to other controllers on the network. You can also use a Cisco WCS server to control, configure, and redistribute all your lightweight access points from a single location. Apply power to the access points: a. Connect your lightweight access points to untagged access ports on your POE capable switch. You can optionally use power modules or power injectors to power your access points. b. After you power up the lightweight access point, it begins a power-up sequence that you can check by observing the access point LEDs. All LEDs blink sequentially back and forth, indicating that the access point is trying to find a controller. Note If the access point remains in this mode for more than 5 minutes, the access point is unable to find the master controller. Check the connection between the access point and the controller and ensure they are on the same subnet. c. If the lightweight access point shuts down (all LEDs off), check to ensure that sufficient power is available. d. When the lightweight access point associates with the controller, if the access point code version differs from the controller code version, the access point downloads the operating system code from the controller. All the access point LEDs blink simultaneously during the download. Cisco Aironet 1100 Series Access Point Hardware Installation Guide E-2 OL-4309-07

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
E-2
Cisco Aironet 1100 Series Access Point Hardware Installation Guide
OL-4309-07
Appendix E
Priming Lightweight Access Points Prior to Deployment
Before deploying your lightweight access points to their final locations, follow these steps to prime your
access points:
Step 1
In a Layer 3 environment, ensure a DHCP server (typically on your switch) is enabled on the same subnet
as your lightweight access points. The access points receives its IP address and controller information
using DHCP Option 43.
The lightweight access point must be able to find the IP address of the controller. This can be
accomplished using DHCP, DNS, OTAP, 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
“Using DHCP Option 43” section on page 6-2
for more information.
Note
For a Layer 3 access point on a different subnet than the controller, ensure the route to the
controller has destination UDP ports 12222 and 12223 open for LWAPP communications.
Ensure that the routes to the primary, secondary, and tertiary controllers allow IP packet
fragments.
Step 2
Ensure that your controller is connected to a switch trunk port.
Step 3
Configure the controller in LWAPP Layer 3 mode and ensure its DS Port is connected to the switch. Use
the CLI, web-browser interface, or Cisco WCS procedures as described in the appropriate controller
guide.
a.
In multi-controller environments, You can set one controller’s DS port to
Master
(you can use the
config network master-base disable
CLI command or you can use the controller GUI
)
so that new
lightweight access points always associate with it. You can use the
show network config
CLI
command to determine if the controller DS port is the master.
All lightweight access points associate to the master controller. From one location, you can
configure lightweight access point settings such as primary, secondary, and tertiary controllers. This
allows you to redistribute your lightweight access points to other controllers on the network.
You can also use a Cisco WCS server to control, configure, and redistribute all your lightweight
access points from a single location.
Step 4
Apply power to the access points:
a.
Connect your lightweight access points to untagged access ports on your POE capable switch. You
can optionally use power modules or power injectors to power your access points.
b.
After you power up the lightweight access point, it begins a power-up sequence that you can check
by observing the access point LEDs. All LEDs blink sequentially back and forth, indicating that the
access point is trying to find a controller.
Note
If the access point remains in this mode for more than 5 minutes, the access point is unable to
find the master controller. Check the connection between the access point and the controller and
ensure they are on the same subnet.
c.
If the lightweight access point shuts down (all LEDs off), check to ensure that sufficient power is
available.
d.
When the lightweight access point associates with the controller, if the access point code version
differs from the controller code version, the access point downloads the operating system code from
the controller. All the access point LEDs blink simultaneously during the download.