Your SlideShare is downloading. ×
0
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Iuwne10 S02 L03
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Iuwne10 S02 L03

370

Published on

Published in: Technology, News & Politics
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
370
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
67
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Basic Cisco WLAN Installation Discovering and Associating with a Controller
  • 2. LWAPP Modes Lightweight Access Point Protocol
  • 3. Layer 3 Lightweight AP Protocol (LWAPP) <ul><ul><li>Layer 3 LWAPP is in a UDP/IP frame </li></ul></ul><ul><ul><li>Cisco WLAN controller and AP can be connected to the same VLAN/subnetwork or connected to a different VLAN/subnetwork </li></ul></ul><ul><ul><li>Requires Cisco AP to obtain an IP address using DHCP </li></ul></ul><ul><ul><li>Control traffic is encrypted, data is not </li></ul></ul>
  • 4. Controller > General
  • 5. Access Point Association Sequence
  • 6. AP LWAPP Discover and Join Overview <ul><ul><li>AP issues a DHCP DISCOVER to obtain address </li></ul></ul><ul><ul><li>AP attempts Layer 2 controller discovery </li></ul></ul><ul><ul><li>AP attempts Layer 3 controller discovery </li></ul></ul><ul><ul><ul><li>LWAPP discovery broadcast on local subnet </li></ul></ul></ul><ul><ul><ul><li>Over-the-Air provisioning (OTAP) </li></ul></ul></ul><ul><ul><ul><li>Local stored controller IP address from prior successful join process </li></ul></ul></ul><ul><ul><ul><li>DHCP option 43 </li></ul></ul></ul><ul><ul><ul><li>DNS resolution of CISCO-LWAPP-CONTROLLER </li></ul></ul></ul><ul><ul><li>After AP discover controllers, it selects and joins one via primary, secondary, tertiary, or master configuration of controllers </li></ul></ul>
  • 7. AP LWAPP Discovery <ul><ul><li>AP obtains an IP address </li></ul></ul><ul><ul><ul><li>Statically defined </li></ul></ul></ul><ul><ul><ul><li>DHCP discover </li></ul></ul></ul><ul><ul><li>AP tries to connect to a controller using Layer 2 then Layer 3 LWAPP (LWAPP only models), or Layer 3 LWAPP (Cisco IOS-based models) </li></ul></ul><ul><ul><li>Layer 3 LWAPP discovery order: </li></ul></ul><ul><ul><ul><li>Subnetwork broadcast mode </li></ul></ul></ul><ul><ul><ul><ul><li>Connect Cisco AP directly to, or same subnet as, a Cisco controller to learn Cisco controller IP address </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Cisco AP will send a subnetwork broadcast </li></ul></ul></ul></ul>
  • 8. AP LWAPP Discovery (Cont.) <ul><ul><li>Over-the-air provisioning (OTAP) </li></ul></ul><ul><ul><ul><li>Connect Cisco AP in range of another already connected AP </li></ul></ul></ul><ul><ul><ul><li>Configure the controller to allow OTAP </li></ul></ul></ul><ul><ul><ul><li>Cisco AP will receive information about controllers from its neighboring APs </li></ul></ul></ul><ul><ul><li>AP priming </li></ul></ul><ul><ul><ul><li>Connect Cisco AP directly, or same subnet as a Cisco controller to learn Cisco controller mobility group IP addresses </li></ul></ul></ul><ul><ul><ul><li>Move Cisco AP to a remote network and have it use DHCP for a local and gateway address </li></ul></ul></ul><ul><ul><ul><li>Cisco AP will send a subnetwork broadcast discovery request to the primary controller and all controllers in the learned mobility group </li></ul></ul></ul>
  • 9. LWAPP Layer 3 Discovery <ul><ul><li>DHCP vendor option mode </li></ul></ul><ul><ul><ul><li>Place Cisco AP on remote network and have it use DHCP for a local and gateway address </li></ul></ul></ul><ul><ul><ul><li>Use DHCP extension to learn a Cisco controller management interface IP address from extension Option 43 </li></ul></ul></ul><ul><ul><li>DNS/DHCP vendor option mode </li></ul></ul><ul><ul><ul><li>Place Cisco AP on remote network and have it use DHCP for a local and gateway address </li></ul></ul></ul><ul><ul><ul><li>Use DHCP extension to learn a DNS IP address </li></ul></ul></ul><ul><ul><ul><li>Cisco AP will then make an address resolution call using the hostname CISCO-LWAPP-CONTROLLER, which should be configured to return the management interface IP address of available controllers </li></ul></ul></ul>
  • 10. Access Point Join Order <ul><ul><li>Response from primary, then secondary, and finally tertiary configured controller </li></ul></ul><ul><ul><li>If no configured controller, response from a master controller </li></ul></ul><ul><ul><li>If no master controller response, response from the least loaded controller </li></ul></ul><ul><ul><li>Least loaded AP-Manager interface or least loaded controller </li></ul></ul>
  • 11. Access Point Join Phase Without Master
  • 12. Access Point Join Phase Without Master (Cont.)
  • 13. Access Point Join Phase Without Master (Cont.)
  • 14. Access Point Join Phase Without Master (Cont.)
  • 15. Access Point Join Phase Without Master (Cont.)
  • 16. Access Point Join Phase With Master
  • 17. Access Point Join Phase With Master (Cont.)
  • 18. Access Point Join Phase With Master (Cont.)
  • 19. Access Point Join Phase With Master (Cont.)
  • 20. Access Point Join Phase With Master (Cont.)
  • 21. Primary Controller Name
  • 22. Controller > Advanced > Master Controller Mode Master controller configuration should only be used for provisioning APs to associate them to a particular controller and then to assign a primary controller.
  • 23. AP LWAPP Join Messages <ul><li>LWAPP join request </li></ul><ul><ul><li>Includes type of controller and MAC address of controller </li></ul></ul><ul><ul><li>Includes AP hardware and software version </li></ul></ul><ul><ul><li>Includes the name of the AP issuing the join request </li></ul></ul><ul><ul><li>Indicates the number and type of radios present in AP </li></ul></ul><ul><ul><li>Includes a certificate payload for establishing a secure connection </li></ul></ul><ul><ul><li>Includes a session payload to setup the session value </li></ul></ul><ul><ul><li>Includes a test payload to test the ability of the network to support jumbo frames </li></ul></ul><ul><li>LWAPP join reply </li></ul><ul><ul><li>Includes a result code </li></ul></ul><ul><ul><li>Includes controller’s certificate payload response </li></ul></ul><ul><ul><li>Includes a test payload to test the network’s ability to support jumbo frames </li></ul></ul>
  • 24. AP States
  • 25. LWAPP Configuration Phase <ul><li>The LWAPP configure request: </li></ul><ul><ul><li>Wants the controller to provide configuration data </li></ul></ul><ul><ul><li>Provides the controller with a list of configurable parameters and the current values </li></ul></ul><ul><li>The LWAPP configure response: </li></ul><ul><ul><li>Provides configuration values for the AP </li></ul></ul><ul><ul><li>Allows the controller to override requested configuration elements from the AP. </li></ul></ul><ul><ul><li>Includes configure command packets. </li></ul></ul><ul><ul><li>Causes the AP: </li></ul></ul><ul><ul><ul><li>To evaluate each configuration element </li></ul></ul></ul><ul><ul><ul><li>To begin implementing the configuration elements </li></ul></ul></ul>
  • 26. Design: AP Redundancy <ul><li>AP redundancy </li></ul><ul><ul><li>RF “self-healing” allows system to compensate dynamically for lost APs </li></ul></ul><ul><ul><li>System must be designed to support self-healing </li></ul></ul><ul><ul><li>Distance between APs determines redundancy limits </li></ul></ul>
  • 27. Controller Redundancy
  • 28. Controller Redundancy Designs — N + 1
  • 29. Controller Redundancy Designs — N + N
  • 30. Controller Redundancy Designs — N + N + 1
  • 31. Summary <ul><ul><li>LWAPP can operate at Layer 2, using Ethernet or Layer 3, using IP. </li></ul></ul><ul><ul><li>An LWAPP AP will try to discover as many controllers as possible, using Layer 2 or Layer 3 methods. </li></ul></ul><ul><ul><li>It will then choose to join the best controller, based on configuration or network elements. </li></ul></ul><ul><ul><li>Once associated to a controller, it will receive its configuration using a secure connection. </li></ul></ul><ul><ul><li>A good design should plan for AP redundancy but also controller redundancy. </li></ul></ul>
  • 32.  

×