1 / 79

Adopting access points

Adopting access points. Versions of the AP7131/AP7131N older than 4.1.1.0 have incompatibilities with the WiNG 5.x codebase which causes the AP to lock up.

breck
Download Presentation

Adopting access points

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Adopting access points

  2. Versions of the AP7131/AP7131N older than 4.1.1.0 have incompatibilities with the WiNG 5.x codebase which causes the AP to lock up. • Administrators need to upgrade their 4.x Access Points to the latest version of AP firmware (4.1.1.0) and at that point upgrade their controllers to 5.x. • If the user upgrades an AP7131/AP7131N running a version of code older than 4.1.1.0 using the AP migration image, there is a possibility of the AP getting “stuck” on coming up with 5.x. • If this occurs, the following error message is seen on the console after bootup: ***cpu not running at correct speed. Expected(500Mhz) current> Speed(600MHz)*** To work-around this issue, the administrators need to type the following command after the error message: • ‘achipfix_cpu_speed’

  3. Adopting access points • Controller running 5.2 code can adopt the following models of access points: • 7131, 650, 6511, 300 • 5181 model access points cannot be adopted by controllers running 5.2 code • Non-Brocade access points (i.e. Motorola access points) cannot be adopted

  4. Adopting access points • Definitions • Layer 2 adoption – AP and controller on the same Layer 2 or BC/MC domain. AP get adopted by the controller using a simple Layer 2 adoption handshake between them. • Layer 3 adoption – AP needs to know the IP address or fully qualified hostname of the controller in order to get adopted by that controller.

  5. Adopting access points • All access point models support both Layer 2 and Layer 3 adoption by controllers. • Gotcha: The only exception to the statement above is 7131 access point models running 4.x code. • 7131 access point models running 5.2 code supports both Layer 2 and Layer 3 adoption (just like all of the other access point models) • 7131 access point models running 4.x code only support Layer 3 adoption (even if the AP and controller are connected to the same Layer 2 BC/MC domain). No Layer 2 adoption of 7131 access point models running 4.x code.

  6. Adopting access points • So let’s look at this scenario where you have a 7131 access point running 4.x code that’s in factory default config or fresh out-of-the-box and you want to adopt it with a controller running 5.2 code

  7. Adopting access points • Download the image file BR7131-5.2.0.0-069R.bin from the Brocade tech support website. • Note: You will notice that there are three similar looking files: • BR7131-5.2.0.0-069R.bin • BR71XX-5.2.0.0-069R.img • BR7131-5.2.0.0-069R-04010300010R.img • The one you want for this step is the first file: BR7131-5.2.0.0-069R.bin • Copy BR7131-5.2.0.0-069R.bin to a USB memory device • Connect your USB memory device to the controller

  8. Adopting access points • In case it’s too hard to read, that long CLI command in the middle is: legacy-auto-update br71xx image flash:/BR7131-5.2.0.0-069R.bin Important!

  9. Adopting access points • Same as previous step but using the web GUI

  10. Adopting access points • Remember, 7131 access point running 4.x only support Layer 3 adoption by controllers! • This is true even if the AP and controller are connected to the same Layer 2 MC/BR domain! • Therefore, these 7131 access point must be: • Assigned an IP address, and • Told which controller it needs to be adopted by • There are many ways to do this. But I’m going to show you two of the easiest ways.

  11. Adopting access points • The first way is to configure these settings directly on each and every 7131 access point that’s running 4.x code. • This is quick and easy if you only have one or two 7131 access points to configure. It is not quick and easy if you have one or two hundred 7131 access points to configure. • Connect to the 7131 AP console port • Exactly same console port settings as the controllers • Just simply power up your access point and connect the GE1/POE port to your network.

  12. Adopting access points Factory default admin password is admin123 admin123

  13. Don’t Know The Admin Password? • For 7131 Access Point version 4.x • Restore the factory default admin password • This only restores the factory default admin password • To restore the factory default config boot> reset config Power cycle 7131. Wait 16 seconds. You have six seconds to press the Esc key.

  14. Adopting access points admin>summary BR7131 firmware version : 4.1.4.0-002R country code : us ap-mode : independent serial number : BJR2441F097 model : BR7131 WLAN 1: WLAN name : WLAN1 ESS ID : 101 Radio Band(s) : VLAN : <none> Security Policy : Default QoS Policy : Default Rate Limiting : disabled LAN1 Name: LAN1 LAN1 Mode: enable LAN1 IP: 10.120.61.36 LAN1 Mask: 255.255.252.0 LAN1 DHCP Mode: client LAN2 Name: LAN2 LAN2 Mode: disable LAN2 IP: 192.168.1.1 LAN2 Mask: 255.255.255.0 LAN2 DHCP Mode: client WAN Interface IP Address Network Mask Default Gateway DHCP Client ------------------------------------------------------------------------------ enable 0.0.0.0 255.0.0.0 0.0.0.0 disable DHCP client enabled in factory default configuration

  15. Adopting access points Don’t forget the exec in front of the ping Ctrl-C to stop pinging

  16. Adopting access points • But if you need to upgrade dozens or hundreds or thousands of factory default, fresh out-of-the box 7131 access points, then this method of manually configuring the controller’s IP address on each and every one of them is simply not feasible. • This is where you use DHCP options to configure these 7131 access points, instead of manually configuring each access point. • To do this, you need a DHCP server that support DHCP options. • Strongly recommended: If there is already an existing DHCP server running on the network that the access point are going to be connected to, then this should be the DHCP server that you configure the DHCP options on. This is the quickest, easiest way to assign these DHCP options to the access points. • Otherwise, if the above recommendation is not possible, luckily there’s a DHCP server that comes for free, built into each and every controller that we can configure to assign these DHCP options to the access points.

  17. Adopting access points

  18. Adopting access points • Now, there are many DHCP servers out there that support DHCP options. You are free to use whatever DHCP server you want, as long as it support DHCP options. • In this example, I’m going to configure a freeware DHCP server software called: DHCP Server • If you are interested, you can download this freeware DHCP server software here: • http://www.dhcpserver.de/dhcpsrv.htm • You can do the same with pretty much any other DHCP server that support DHCP options • But your DHCP server must support DHCP options. If it doesn’t support DHCP options, then this method won’t work for you

  19. Adopting access points • Helpful tip: • Before going ahead with a massive batch upgrade of 7131 access points running 4.x using DHCP options, try performing one access point upgrade manually, using the CLI commands directly on the AP. • If you cannot get the access point to upgrade using the manual method, then I can guarantee you that it will not work using DHCP options • Get it to work first with one access point manually, and then if you’re successful, go ahead with using DHCP options

  20. Adopting access points • And finally, if for some reason, you don’t have a DHCP server that support DHCP options, then you can always use the built-in DHCP server that comes for free in the controller! • Warning! Adding a DHCP server to a network that already has a DHCP server in it can result in nasty consequences! Proceed with caution!

More Related