Hi,
In IAP-225, we are seeing WAP is taking long time for boot-up and initialization. The WAP is taking approx 3 minutes just for boot-up and approx 2 minutes for it to stabilize.
In our testing, we have observed that, we can establish SSH/Serial session with WAP approx 3 minutes however running certain commands immediately after the login does not work. The command gets stuck in its execution(so the session in hung state) for sometime before giving up.
However, approximately after 5 minutes, it seems WAP is stable and the above mentioned issue is not seen.
The command having this issue is “show image” which displays the current software version.
Question: Is there any way to speed up the boot-up time and overall initialization of the WAP?
As we can see below, the message on the console indicates, the WAP took close to 3 minutes before allowing the serial connection.
User: admin
System uptime is 173 seconds and CLI is not ready yet, please try again later.
User: admin
System uptime is 175 seconds and CLI is not ready yet, please try again later.
User: admin
Password:
show tech-support and show tech-support supplemental are the two most useful outputs to collect for any kind of troubleshooting session.
84:d4:7e:c6:da:e4#show image <-- Running the command immediately after login causes the session in hung state for a while.
84:d4:7e:c6:da:e4#
After 5 minutes, it executed successfully.
84:d4:7e:c6:da:e4# show image
CLI's management authentication settings have been changed. Your login credentials are now being re-checked...
Your credentials are still valid, command will now execute.
Primary Partition :0
Primary Partition Build Time :2017-12-20 04:29:04 UTC
Primary Partition Build Version :6.5.4.4_62887 (Digitally Signed - Production Build)
Backup Partition :1
Backup Partition Build Time :2016-09-12 03:25:40 PDT
Backup Partition Build Version :6.5.0.0_56428 (Digitally Signed - Production Build)
AP Images Classes
-----------------
Class
-----
Centaurus
84:d4:7e:c6:da:e4#
SNMP Log:
Between, 3 and 5 minutes, even the SNMP commands does not fetch any results.
[root@192.168.10.1: ]# snmpget -c public -v2c192.168.10.2 AI-AP-MIB::aiVirtualControllerVersion.0
AI-AP-MIB::aiVirtualControllerVersion.0 = No Such Instance currently exists at this OID
[root@192.168.10.1: ]#
After 5 minutes:
--------------------
[root@192.168.10.1: ]# snmpget -c public -v2c192.168.10.2 AI-AP-MIB::aiVirtualControllerVersion.0
AI-AP-MIB::aiVirtualControllerVersion.0 = STRING: 6.5.4.4-6.5.4.4_62887
[root@192.168.10.1: ]#
Console logs for more details:
----------------------------------------
Launching NTP Client on 192.168.10.1
[ 74.861247] wl 0000:01:00.0: enabling device (0000 -> 0002)
[ 75.657797] aruba_usb_power_control:1136 en:1 status:0
[ 75.719386] aruba_enable_usb_block:556 Enabled USB
[ 75.776699] aruba_usb_power_control:1144 Enable USB power control for 224/225
[ 75.028817] wifi0: AP type AP-225, radio 0, max_bssids 16[ 75.862179] ardmore_usb_power_control:1055 enabled the USB interface
[ 75.938253] Enabling eth1 due to power change [power profile 1]
[ 76.011408] wl 0001:03:00.0: enabling device (0000 -> 0002)
[ 76.343690] wifi1: AP type AP-225, radio 1, max_bssids 16
ardmore: Insmod BT modules
[ 77.048802] usbcore: registered new interface driver usbserial
[ 77.133560] USB Serial support registered for generic
[ 77.200892] usbcore: registered new interface driver usbserial_generic
[ 77.279180] usbserial: USB Serial Driver core
[ 77.373531] usbcore: registered new interface driver cdc_acm
[ 77.441333] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
Clearing P1020 PCIe Error Status
AP rebooted Wed Feb 7 20:19:28 UTC 2018; CLI cmd at uptime 0D 23H 58M 9S: reload
shutting down watchdog process (nanny will restart it)...
<<<<< Welcome to the Access Point >>>>>
Completed SW FIPS KAT test
User: [ 98.692863] 1: no user entry for192.168.10.2 (84:d4:7e:c6:da:e4)
[ 107.083899] i am master now
[ 107.117301] (20:21:56) !!! Init ---> Master
[ 107.167357] asap_send_elected_master: sent successfully
[ 107.698322] 1: no user entry for 192.168.10.2 (84:d4:7e:c6:da:e4)
User: admin
System uptime is 168 seconds and CLI is not ready yet, please try again later.
User: admin
System uptime is 171 seconds and CLI is not ready yet, please try again later.
User: admin
Thanks,
Shiva