Question : Why does AP-275 comes up with an Inactive (I) flag where as other APs are up using the same AP configuration?
Environment Information : AP-275
Aruba OS 6.4+
Aruba Controller 7200, 6000 (M3), 3000 or 600 Series Controllers
Symptoms : AP 275 is coming up with I Flag where as other APs like AP-135/AP-125 using the same AP-Group are working fine
Cause : POE requirement for AP-275 is different from other APs
Resolution : AP-275 requires a minimum of 802.3at power (POE+) for it to function properly. With 802.3af power, the AP will come up with Inactive flag (I) and the radios and E1 port will still be disabled.
In one case, we have seen a Cisco 3850 POE switch (WS-C3850-48P) capable of POE+ was unable to power up the AP-275 fully. This was because the power module required for enabling POE+ per port was not in place.
Max Power supplied is 15.4W even though the POE switch is capable of upto 30W. We know that AP-275 requires a minimum of 802.3at (POE+) and upto a max power of 30W.
The resolution is to installed the required power supplies on the POE switch so that it can provide the POE+ power it is capable of.
Reference link for detailed specs for this POE switch:
Answer : If other APs are working fine using the same ap-group, then we must ensure the AP-275 is able to stably heartbeat (GRE) with the Controller and find out whether the AP is rebootstarpping or rebooting often. If GRE is blocked or GRE heartbeat packets droppedo n that path, the AP will continually bootstrap. It will appear to be active for the 8 seconds (by default) required for the AP to decide that the GRE tunnel is not there. The AP will appear as inactive ("I" flag) briefly between the times the AP reboots and the time the Controller configures the virtual APs. Commands used to verify GRE heartbeats and number of AP reboots/rebootstraps:
# show datapath session table <AP IP>
# show ap debug counters ap-name <AP>
In one instance, we have observed the AP-275 to be up continually with "I" flag and the AP is neither rebootstrapping or rebooting.
(Aruba) (config) #show ap database | include ap-group1
As seen above, the PAPI and GRE tunnels seem to be active. The AP-Debug log and System log shows the AP is provisioned and configured fine and all profiles are applied correctly and we see no anomaly.
(Aruba) (config) #show log system all | include Aruba-AP-275
The issue is related to the amount of power supplied to the AP and this is evident from the following output:
(Aruba) (config) #show ap debug system-status ap-name Aruba-AP275