Loop(Green -> Blue -> Red): LED party mode?

[Gioacchino]

Hello,

EWC with 2x 9120 with 17.3.6.

I have access to the GUI and theo APs are in active standby (this would be another question, since I never asked for redundancy).

I see the APs are registered and I can push config like SSID or controlling whether the LED are active or not.

However, both of the APs have their leds in a loop with the sequence specified in the subject.

I read about the "party mode" that you can enable via ap name <AP name> led flash start duration X, but this is not the case because when enabling it I can see the frequence increases, when disabling the frequency decreases.

Any clue/hint?

TIA, Gioacchino

[marce1000 · Accepted solution]

 - It could be a POE issue and or due to insufficient power  , attach  a console to one of the APs and reboot , watch the console messages. If this is not possible due to remoteness of the AP then also reboot it and just after boot issue the command show logging ; watch for anomalies (too).

                >..since I never asked for redundancy
  - The EWC AP's use VRRP as a kind of default active standby mechanism

  Appendix : Review the configuration of the EWC AP(s) with the CLI command show tech wireless ; have the output analyzed with 
                                           https://cway.cisco.com/wireless-config-analyzer/

 M.

[Gioacchino]

Thanks @marce1000 , as tothe VRRP, I guess this is limited to two devices. What's "annoying", for somebody who doesn't know very well the Cisco wireless AP solution, is that when in stby mode you don't have access to the console. Hence you cannot issue wireless ewc-ap ap shell username <AP username> and get the AP console. Are there any other ways? Sorry for discussing a second topic within a different thread.

Gio

[marce1000]

   >...Hence you cannot issue wireless ewc-ap ap shell username <AP username> and get the AP console. Are there any other ways?
    Not that I know off , now the idea is that the mode of the APs (CAPWAP or EWC) should be configured before production or standalone for instance (without network connected) , 

 M.

[Gioacchino]

Thanks Marce1000,

waybe by swapping standby and active, we should get access to the AP shell previuously not available. What would you think?
If this might do the trick, would you know how to swap roles (active - stby) on the EWC?

TIA

[marce1000]

         >... maybe by swapping standby and active, we should get access to the AP shell previously not available. 
 - I was thinking along the same lines , or perhaps simply powering down the current active if the access to the cisco shell on the current standby is only needed for a short period in time (e.g.)

 M.

[Gioacchino · Accepted solution]

Eventually I discovered that they were connected to an old 2960 that supplied just 15.4W per port and hence they were not sufficient for the 9120.

https://www.cisco.com/c/en/us/td/docs/wireless/access_point/9115ax/quick/guide/ap9115ax-getstart.html#pgfId-69305

Weird that the blinking sequence for insufficient power is the same as the "party mode" (just the frequency is lower). If you enter a room and see that sequence you may be puzzled

[Rich R]

The LED colours and sequences have different meaning on each AP model so it's always best to check the documentation.  In this case it's quite clearly stated the meaning of what you saw at:
https://www.cisco.com/c/en/us/td/docs/wireless/access_point/9120ax/quick/guide/ap9120ax-getstart.html#pgfId-98295

Access point operating system errors

Cycling through Red-Off-Green-Off-Blue-Off

General warning; insufficient inline power