Controllerless Networks

Reply
Contributor I

Unusual Behavior with 2 IAP-225s and Orange LEDs

Hello All -

 

So all has been great one the 1 IAP-225 I had connected to my switch and it was in a master role.  This afternoon I added a second IAP-225 to the same switch and since that time I've had some rather odd behavior.

 

The 2 IAPs will alternate which one becomes the master.  The LEDs on the right of the device (2.4GHz and 5 Ghz) become steady orange (from steady green) when it no longer is the master.  The IAPs are running on an PoE+ switch.

 

Any ideas what's occuring here and how I can troubleshoot further?

 

Thanks

Guru Elite

Re: Unusual Behavior with 2 IAP-225s and Orange LEDs

What version of instant?
What POE switch?
Have you seen both APS from a single AP?

*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.3 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Contributor I

Re: Unusual Behavior with 2 IAP-225s and Orange LEDs

 

6.4.2.6-4.1.1.10_51810 for the version

UniFi Edge Switch 250 (The only POE/POE+ devices on here are the two IAPs)

Not sure I follow the third item.

 

 

 

Guru Elite

Re: Unusual Behavior with 2 IAP-225s and Orange LEDs

If both access points are in a cluster, you should be able to see both access points from the VC or virtual controller. If you never saw that, they never formed a cluster. Did they form a cluster?

*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.3 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Contributor I

Re: Unusual Behavior with 2 IAP-225s and Orange LEDs

Yes, both APs are listed in the GUI - "2 Access Points" column has both IAPs populated with their MAC addresses.

Guru Elite

Re: Unusual Behavior with 2 IAP-225s and Orange LEDs

Shoe log system on the command line should say why access points are no longer the VC.

*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.3 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Contributor I

Re: Unusual Behavior with 2 IAP-225s and Orange LEDs

Thanks - interesting (part in bold)

 

DSTAIRS-PPC# show log system

 

Dec  3 18:08:00  syslog: <341005> <ERRS> |AP DSTAIRS-PPC: |  terminal access is enabled but dropbear is not running, starting

Dec  3 18:08:02  nanny[2390]: <303022> <WARN> |AP DSTAIRS-PPC: |  Reboot Reason: AP rebooted Thu Dec 3 18:06:51 UTC 2015; Current uplink down, no useable uplink 

Dec  3 18:08:15  cli[2466]: <341317> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  Regulatory table file init at version 1.0_51685, build Sep 14,2015.

Dec  3 18:08:21  cli[2466]: <341004> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  Extended ssid enabled

Dec  3 18:08:21  cli[2466]: <341207> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  AP support up to 16 SSID.

Dec  3 18:08:22  cli[2466]: <341172> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  Find enet0 name eth0.

Dec  3 18:08:22  cli[2466]: <341004> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  cli starting, clearing any dpimgr

Dec  3 18:08:22  cli[2466]: <341004> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  cli_choose_eth_uplink:eth current uplink set to DHCP

Dec  3 18:08:22  cli[2466]: <341169> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  Add uplink Ethernet 0.

Dec  3 18:08:22  cli[2466]: <341167> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  Uplink eth0 type Ethernet, state INIT->LOAD.

Dec  3 18:08:22  cli[2466]: <341169> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  Add uplink Wifi-sta 6.

Dec  3 18:08:22  cli[2466]: <341169> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  Add uplink 3G/4G 7.

Dec  3 18:08:22  cli[2466]: <341167> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  Uplink  type Dummy, state INIT->LOAD.

Dec  3 18:08:22  cli[2466]: <341004> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  receive sapd hello for process recovery

Dec  3 18:08:23  cli[2466]: <341174> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  No current uplink, pick the highest one - Ethernet eth0.

Dec  3 18:08:23  cli[2466]: <341263> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  enable uplink eth0.

Dec  3 18:08:23  cli[2466]: <341167> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  Uplink eth0 type Ethernet, state LOAD->PROBE.

Dec  3 18:08:23  cli[2466]: <341265> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  enable ethernet uplink eth0.

Dec  3 18:08:23  cli[2466]: <341004> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  the ethernet uplink inuse in first time, get ip address.

Dec  3 18:08:23  cli[2466]: <341167> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  Uplink eth0 type Ethernet, state PROBE->UP.

Dec  3 18:08:23  cli[2466]: <341185> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  Retrieving ip address from br0, ip 192.168.0.83, mask 255.255.255.0.

Dec  3 18:08:23  cli[2466]: <341274> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  Update election ip from br0, election ip 192.168.0.83/255.255.255.0.

Dec  3 18:08:23  cli[2466]: <341004> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  build_my_ip_address: old ip and new ip same; skipping

Dec  3 18:08:23  cli[2466]: <341006> <CRIT> |AP DSTAIRS-PPC@192.168.0.83 cli|  Sending uplink_up msg to sapd

Dec  3 18:08:23  cli[2466]: <341006> <CRIT> |AP DSTAIRS-PPC@192.168.0.83 cli|  trap uplink info.

Dec  3 18:08:23  cli[2466]: <341004> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  last uplink is null, it's the first uplink, ignore this trap.

Dec  3 18:08:23  cli[2466]: <341173> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  Current uplink set to Ethernet, state UP.

Dec  3 18:08:23  cli[2466]: <341135> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  Master Changed - new 127.0.0.1 old 0.0.0.0 current swarm state 0.

Dec  3 18:08:24  cli[2466]: <341135> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  Master Changed - new 127.0.0.1 old 0.0.0.0 current swarm state 1.

Dec  3 18:08:28  cli[2466]: <341004> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  Swarm State Change from Found to Image-ok

Dec  3 18:08:33  cli[2466]: <341194> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  Loading configuration, func swarm_timer_handler, line 8650.

Dec  3 18:08:35  cli[2466]: <341004> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  launching dpimgr now.

Dec  3 18:08:35  cli[2466]: <341004> <WARN> |AP DSTAIRS-PPC@192.168.0.83 cli|  cli_dpimgr_stop: dpimgr pid= 0 is reset now

 

Re: Unusual Behavior with 2 IAP-225s and Orange LEDs

Make sure the patch cable on the IAP225 is not on E1 , it should be on E0
Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Contributor I

Re: Unusual Behavior with 2 IAP-225s and Orange LEDs

Thanks will check that out.

Contributor I

Re: Unusual Behavior with 2 IAP-225s and Orange LEDs

Does a IAP typically reboot if a link is lost or restored in a cluster?

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: