EasyManua.ls Logo

Alcatel-Lucent AOS-W 6.5.3.x - Page 522

Alcatel-Lucent AOS-W 6.5.3.x
1160 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
522| Access Points AOS-W 6.5.3.x| User Guide
The SetMeUp provisioning SSID is not showing up on the device
The SetMeUp-xx:xx:xx provisioning SSID used for manual AP upgrade only appears on a device if an AP fails
to upgrade to the AOS-W or Instant image during the switch and Instant discovery process.
APs can support up to 12 switch IP addresses for AOS-W image upgrade. During the switch discovery process,
the AP attempts to connect to each switch 10 times until it reaches one successfully. Each connection attempt
takes one minute. Depending on the number of switches that are located by the AP, it can take up to 120
minutes just to complete the switch discovery process.
Execute the show log provision command on the AP to track the progress of the switch discovery process.
The provisioning log displays the total number of switch IPv4 and IPv6 addresses that have been detected by
the AP, and the current stage of the discovery process.
The AP does not reboot after an upgrade failure
If an AP fails to upgrade to the AOS-W or Instant image during the switch and Instant discovery process, it
enters a 15 minute reboot period. After the AP is rebooted, it restarts the discovery process. However, there
are several conditions that can prevent the AP from completing the reboot:
n Keyboard input from the user.
n WebUI session connected to the AP (manual image upgrade).
n Pending image upgrade.
n Discovery of an AMP server.
n Discovery of a Central server.
Execute the show log provision command on the AP to determine why the AP has not rebooted. The
provisioning log displays one of the following messages:
n "Could not reboot- upgrade is pending"
n "Could not reboot- keyboard input"
n "Could not reboot- airwave is found"
n "Could not reboot- UI session"
n "Could not reboot- central is found
The operational state of an AP ethernet port goes down while using a PoE injector
Sometimes, while using a PoEinjector, the output of the show ap debug port status ap-name <ap-name>
command indicates that the operational state of an Ethernet port is down.
(host)#show ap debug port status ap-name test-ap-225
AP "test-ap-225" Port Status
-----------------------------
Port MAC Type Forward Mode Admin Oper Speed Duplex 802.3az PoE
---- --- ---- ------------ ----- ---- ----- ------ ------- ---
0 9c:1c:12:c0:ab:40 GE N/A enabled up 1 Gb/s full disabled N/A
1 9c:1c:12:c0:ab:41 GE tunnel enabled down N/A N/A N/A N/A
STP Portfast TX-Packets TX-Bytes RX-Packets RX-Bytes
--- -------- ---------- -------- ---------- --------
N/A N/A 69707 37468577 107570 11707191
N/A N/A 0 0 0 0
Execute the following command to verify if the AP is powered up using an 802.3af Power Sourcing Equipment.
(host) #show ap debug system-status ap-name <ap-name> | include POE
Power Supply : POE-AF

Table of Contents