In most of the small and medium-sized enterprises (SMEs), we don’t have IT department and sometimes hire third-party for installation and setup. This post provides a checklist for things need to be aware while setting up Cisco Aironet 2800 access points.
- Installation – Put a padlock or cable tie to secure the AP on the mounting bracket to avoid AP falling from the ceiling due to vibration or earthquake.
- Install Ethernet and serial console cable to the AP if the AP is hard to access, such as a high ceiling. I have encountered some bugs that require the serial console to recover the AP.
- Separate management traffic and user traffic with VLAN. Management traffic should be untagged and user traffic should be tagged.
- Setup TFTP server and configure TFTP path on the controller. When you add more APs on later days, this allows new APs to update their firmware by their own if they’re shipped with a different firmware version. This makes adding new APs plug-and-play without extra configuration.
- Do NOT include firmware file name on TFTP path. Provide the path to the directory only. During the firmware update, APs will use platform type (e.g., ap3g3) as the file name.
- Don’t update individual AP. Update at the controller.
- Use TAC recommended software version to avoid headaches.
- Make sure you have the login to download AP software from Cisco.
- When contacting Cisco for support, use WebEx to save your time. On Ubuntu Linux, keyboard control is not supported on WebEx but it allows Cisco support staff to see your screen. They can tell you what command you need to issue on the console.
- If an AP does not join the controller (WLC or ME), it is possible that it’s been configured in bridge mode. New AP should not have this problem, but an AP sent by Cisco after RMA may have this issue.