APM-9600 fails to boot on XOS 10.0 with a VAP type xslinux_v6_64
Article ID: 167809
Updated On:
Products
XOS
Issue/Introduction
This article summarizes an APM-9600 boot failure scenario on XOS 10.0 with a VAP type xslinux_v6_64 VAP
2. The APM is part of a VAP group configured with the operating system type xslinux_v6_64
3. The APM boots normally as a Standby VAP (not part of a VAP group)
Symptoms:
1. The APM fails to boot permanently with the following output on the console port:
1. The APM fails to boot permanently with the following output on the console port:
DEBUG - LINK [1] - Link Up.
.............
DEBUG - HELLO [1] - Received.
DEBUG - Backplane MAC Address : 0003d2000204.
DEBUG - LINK [1] - Link Up.
DEBUG - BOOTP [1] - Sending Request.
DEBUG - BOOTP [2] - Sending Request.
DEBUG - BOOTP [1] - Reply C 00000000, Y 01010266 S 01010214 G 00000000
DEBUG - TFTP [1] - Sending RRQ [01010214][/fw_1/boot/bzImage.nb2smp].
DEBUG - TFTP [1] - First block received.
....................................................................................................................................................................................................................................................................................................................................................
DEBUG - TFTP [1] - Last block received, transfer size 3490576 bytes.
DEBUG - STATS [1] - Receive.
Frames 6853 Errors 0 Fragments 0 ICMP 0
Bcast 1 Mcast 33 ARP 1 UDP 6819
DEBUG - LINK [1] - Link Up.
...............
DEBUG - HELLO [1] - Received.
DEBUG - Backplane MAC Address : 0003d2000204.
INFO - Loading network image.
WARNING - Unable to boot from network.
2. The APM is part of a VAP group configured with the operating system type xslinux_v6_64
Cause
The APM must run the latest firmware to support the VAP kernel xslinux_v6_64. Here is an example output from /crossbeam/bin/revs_check that shows the missing firmware revision:
Slot 4, PartNo 005682, Serial P339N000: Bootstrap rev 1.8.0.0, requires rev 1.8.0.2 (ap9600_fpga_0207_flash0005)
Slot 4, PartNo 005682, Serial P339N000: Bootloader rev 1.8.0.4, requires rev 1.8.0.6 (ap9600_fpga_0207_flash0005)
Slot 4, PartNo 005682, Serial P339N000: Diag rev 0.5.0.4, requires rev 0.5.0.5 (ap9600_fpga_0207_flash0005)
Resolution
To perform firmware upgrade, the APM must boot as a part of a VAP group. You can temporarily use a VAP group of the type xslinux_v5_64 to perform the firmware upgrade.
1. Create a new "xslinux_v5_64" VAP group or convert the existing "v6_64" VAP group into "v5_64".
2. As necessary, modify "available-ap-list" and "max-load-count" to ensure the APM boots the "v5_64" image.
3. Upgrade firmware on the APM module (see XOS Configuration Guide for details).
4. Verify that APM boots the "v6_64" image properly after the upgrade.
NOTE: There is no application qualified to run on "v6" kernel as of May 2014.
1. Create a new "xslinux_v5_64" VAP group or convert the existing "v6_64" VAP group into "v5_64".
2. As necessary, modify "available-ap-list" and "max-load-count" to ensure the APM boots the "v5_64" image.
3. Upgrade firmware on the APM module (see XOS Configuration Guide for details).
4. Verify that APM boots the "v6_64" image properly after the upgrade.
NOTE: There is no application qualified to run on "v6" kernel as of May 2014.
Workaround
N/AFeedback
Powered by
