Question: How can we quickly identify the issue before and after the units have been installed?
Product and Software: This article applies to all ArubaOS versions that were released before October 15, 2007.
Over time, it is very common for customer add access points before they upgrade. Customers will first notice an issue when the APs are active with the default CLI channel assignments. If the APs are all deployed in a common area, the interference level for the default channels will be high and clients will experience connectivity issues. Channel 1 and channel 36 will have reports of client issues.
1) Enter the 'show version' command to display the compiled date. Make sure the compile date is after October 15, 2007.
(SanLeandro2400) #show version
Aruba Operating System Software.
ArubaOS (MODEL: Aruba2400), Version 220.127.116.11
Copyright (c) 2002-2007, Aruba Networks, Inc.
Compiled on 2008-07-02 at 13:16:09 PDT (build 18875) by p4build
ROM: System Bootstrap, Version CPBoot 1.0.8 (Oct 13 2003 - 14:41:30)
Switch uptime is 15 days 7 hours 48 minutes 34 seconds
Reboot Cause: User reboot.
Processor (revision 16.20 (pvr 8081 1014)) with 256M bytes of memory.
32K bytes of non-volatile configuration memory.
256M bytes of Supervisor Card System flash (model=CF 256MB).
2) If the OUI portion of the MAC is address is "00:1A:1E", you must upgrade before adding AP to your network.
3) In release 2.5.4.x, enter the 'show ap registered location 0.0.0' command to display the MAC address of the APs. Look for BSSIDs with the "00:1A:1E" prefix.
4) In release 3.x, enter the 'show ap bss-table' command to display the MAC address of the APs. Look for BSSIDs with the "00:1A:1E" prefix.