Controllerless Networks

Reply
Occasional Contributor II

Can't get two IAP-175s to see each other

Hello,

 

I have two IAP-175s running the latest firmware and as far as I can tell are both "factory defaults" -- as in I clicked "Clear Configuration" for them both.

My problem here is that I can't get these IAPs to see each other on the network. I have both hooked into my LAN via ethernet cable, both are getting IP addresses in the same subnet, I can log into each of them from my laptop by going to their respective IP addresses... But each acts like it can't see the other one and reports only itself as an Access Point, making it of course impossible to setup a mesh which is what i'm trying to do here (a simple mesh, where IAP #1 is hard-line connected to the network and IAP #2 is providing network access via the mesh). 

I am banging my head against the wall trying to figure out what i'm not doing right here, all the instructions I find make it sound like both devices should just "show up", but it's not happening.

 

John


Accepted Solutions
Highlighted
Guru Elite

Re: Can't get two IAP-175s to see each other

Make sure that they both have the correct time (at least the right day).  If can get into the GUI of both, go to Mainenence> Clear Configuration and reboot both and see if they can find each other.

 

EDIT:  Make sure both have access to the internet, so they can get the time via NTP.  Reset them both using the procedure above and reboot and see if they see each other.  "show swarm" and "show log system" should give you some clues about what is going on.


*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.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
ArubaOS Consolidated Release Notes
Aruba VIA ASE Solution - Configure VIA VPN

View solution in original post

Highlighted
Occasional Contributor II

Re: Can't get two IAP-175s to see each other

Maybe like I previously said I used the wrong reset procedure but this time following your instructions they found each other! I also think part of my problem might have been I had a static IP assigned and the DNS address was incorrect. Either way, they at least can see each other thank you!

View solution in original post


All Replies
Highlighted
MVP Guru

Re: Can't get two IAP-175s to see each other

Do you have the 'allowed-aps' enabled? Do you have any output when you complete '#show warm'? Can they both reach the same default gateway?

 


ACMP, ACSA, ACDX #985
If my post addresses your query, give kudos:)
Highlighted
Occasional Contributor II

Re: Can't get two IAP-175s to see each other

When I execute # show swarm state on my IAPs here is what I get

 

d8:c7:c8:c8:03:dd# show swarm state

AP Swarm State           :swarm_config_sync_complete
mesh auto eth0 bridging  :no
mesh ldart State     :suspending
Config in flash       :yes
factory SSID in flash :no
extended-ssid configured :no
extended-ssid active     :no
Config load cnt       :1
VC Channel index      :1
IDS Client Gateway Detect :yes
Config Init success cnt for heartbeat   :0
Config Init success cnt for register    :0
Config Init skipping cnt for heartbeat  :0
Config Init skipping cnt for register   :0
Config Init last success reason   :N/A
Config Init last success time     :N/A

 

d8:c7:c8:c8:03:e0# show swarm state

AP Swarm State           :swarm_config_sync_complete
mesh auto eth0 bridging  :no
mesh ldart State     :suspending
Config in flash       :yes
factory SSID in flash :no
extended-ssid configured :no
extended-ssid active     :no
Config load cnt       :1
VC Channel index      :1
IDS Client Gateway Detect :yes
Config Init success cnt for heartbeat   :0
Config Init success cnt for register    :0
Config Init skipping cnt for heartbeat  :0
Config Init skipping cnt for register   :0
Config Init last success reason   :N/A
Config Init last success time     :N/A
d8:c7:c8:c8:03:e0# show tech-support
show clock

 

I don't believe i have allowed-aps enabled (I'm not sure what setting you are referring to here tho, I assume it's a white-list of APs?).

They are both receving their IP addresses on the network from the same DHCP server, same subnet, same gateway, etc.

 

 

Highlighted
Occasional Contributor II

Re: Can't get two IAP-175s to see each other

Is there anyone else who can help here? I'm really struggling with what could be going wrong here.

Highlighted
Guru Elite

Re: Can't get two IAP-175s to see each other

Type "show log system" on the CLI of each Instant AP to see what could be wrong...


*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.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
ArubaOS Consolidated Release Notes
Aruba VIA ASE Solution - Configure VIA VPN
Highlighted
Occasional Contributor II

Re: Can't get two IAP-175s to see each other

When I do that the only thing I see is this log entry (repeated many times)

 

Mar 1 12:13:32 cli[1783]: <341005> <ERRS> |AP d8:c7:c8:c8:03:dd@192.168.1.2 cli| terminal access is enabled but dropbear is not running, starting

 

The date is wrong, although I have a proper NTP server setup and timezone is correct. There are no other log entries!

 

Thoughts??

Highlighted
Guru Elite

Re: Can't get two IAP-175s to see each other

What version of Instant is this?  Did it ever work?


*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.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
ArubaOS Consolidated Release Notes
Aruba VIA ASE Solution - Configure VIA VPN
Highlighted
Occasional Contributor II

Re: Can't get two IAP-175s to see each other

Here's my version

 

Aruba Operating System Software.
ArubaOS (MODEL: 175P), Version 6.4.4.8-4.2.4.9
Website: http://www.arubanetworks.com
Copyright (c) 2002-2017, Aruba Networks, an HP company.
Compiled on 2017-10-03 at 06:27:17 PDT (build 61734) by p4build
FIPS Mode :disabled

 

Yes so the story behind these IAPs is they used to be all setup and working in a mesh years ago. They have since been taken down and have been in storage for quite some time. Having a use for them again I brought them out to create a wireless bridge to an offsite location but I can't get them to see each other.

Highlighted
Occasional Contributor II

Re: Can't get two IAP-175s to see each other

Here is the log for the other IAP (I just rebooted it)

Jan 16 13:39:44  syslog: <341005> <ERRS> |AP d8:c7:c8:c8:03:e0: |  open core directory failed
Jan 16 13:39:44  syslog: <341005> <ERRS> |AP d8:c7:c8:c8:03:e0: |  terminal access is enabled but dropbear is not running, starting
Jan 16 13:39:44  syslog: <341005> <ERRS> |AP d8:c7:c8:c8:03:e0: |  telnetd is missing, restarting
Jan 16 13:39:47  nanny[2025]: <303022> <WARN> |AP d8:c7:c8:c8:03:e0: |  Reboot Reason:
Jan 16 13:39:58  cli[2055]: <341317> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Regulatory table file init at version 1.0_61527, build Sep 20,2017.
Jan 16 13:40:05  cli[2055]: <341207> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  AP support up to 6 SSID.
Jan 16 13:40:06  cli[2055]: <341172> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Find enet0 name bond0.
Jan 16 13:40:06  cli[2055]: <341004> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  cli_choose_eth_uplink:eth current uplink set to DHCP
Jan 16 13:40:06  cli[2055]: <341169> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Add uplink Ethernet 0.
Jan 16 13:40:06  cli[2055]: <341167> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Uplink bond0 type Ethernet, state INIT->LOAD.
Jan 16 13:40:06  cli[2055]: <341169> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Add uplink Wifi-sta 6.
Jan 16 13:40:06  cli[2055]: <341169> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Add uplink 3G/4G 7.
Jan 16 13:40:06  cli[2055]: <341167> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Uplink  type Dummy, state INIT->LOAD.
Jan 16 13:40:06  cli[2055]: <341004> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  CLI to PAPI port 15233 communication code 1
Jan 16 13:40:06  cli[2055]: <341004> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  receive sapd hello for process recovery
Jan 16 13:40:07  nanny[2025]: <303074> <ERRS> |AP d8:c7:c8:c8:03:e0@192.168.1.140 nanny|  Process /aruba/bin/radiusd [pid 2098] died: exited with 0x1
Jan 16 13:40:07  nanny[2025]: <303079> <ERRS> |AP d8:c7:c8:c8:03:e0@192.168.1.140 nanny|  Restarted process /aruba/bin/radiusd, new pid 2203
Jan 16 13:40:07  cli[2055]: <341174> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  No current uplink, pick the highest one - Ethernet bond0.
Jan 16 13:40:07  cli[2055]: <341263> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  enable uplink bond0.
Jan 16 13:40:07  cli[2055]: <341167> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Uplink bond0 type Ethernet, state LOAD->PROBE.
Jan 16 13:40:07  cli[2055]: <341265> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  enable ethernet uplink bond0.
Jan 16 13:40:07  cli[2055]: <341004> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  the ethernet uplink inuse in first time, get ip address.
Jan 16 13:40:07  cli[2055]: <341167> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Uplink bond0 type Ethernet, state PROBE->UP.
Jan 16 13:40:07  cli[2055]: <341185> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Retrieving ip address from br0, ip 192.168.1.140, mask 255.255.0.0.
Jan 16 13:40:07  cli[2055]: <341274> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Update election ip from br0, election ip 192.168.1.140/255.255.0.0.
Jan 16 13:40:07  cli[2055]: <341004> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  build_my_ip_address: old ip and new ip same; skipping
Jan 16 13:40:07  cli[2055]: <341006> <CRIT> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Sending uplink_up msg to sapd
Jan 16 13:40:07  cli[2055]: <341006> <CRIT> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  trap uplink info.
Jan 16 13:40:07  cli[2055]: <341004> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  last uplink is null, it's the first uplink, ignore this trap.
Jan 16 13:40:07  cli[2055]: <341173> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Current uplink set to Ethernet, state UP.
Jan 16 13:40:07  cli[2055]: <341135> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Master Changed - new 127.0.0.1 old 0.0.0.0 current swarm state 0.
Jan 16 13:40:08  cli[2055]: <341135> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Master Changed - new 127.0.0.1 old 0.0.0.0 current swarm state 1.

Jan 16 13:40:11  cli[2055]: <341004> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  CLI to PAPI port 8504 communication code 1
Jan 16 13:40:11  cli[2055]: <341004> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Swarm State Change from Found to Image-ok
Jan 16 13:40:16  cli[2055]: <341194> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Loading configuration, func swarm_timer_handler, line 10301.
Jan 16 13:40:16  cli[2055]: <341101> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Execute command-configure terminal.
Jan 16 13:40:18  nanny[2025]: <303074> <ERRS> |AP d8:c7:c8:c8:03:e0@192.168.1.140 nanny|  Process /aruba/bin/radiusd [pid 2203] died: exited with 0x1
Jan 16 13:40:18  nanny[2025]: <303079> <ERRS> |AP d8:c7:c8:c8:03:e0@192.168.1.140 nanny|  Restarted process /aruba/bin/radiusd, new pid 2359
Jan 16 13:40:19  cli[2055]: <341004> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  Swarm State Change from Image-ok to Complete
Jan 16 13:40:30  cli[2055]: <341131> <WARN> |AP d8:c7:c8:c8:03:e0@192.168.1.140 cli|  AP sends meshd parameters 724fde1d011e928863086437f711295fa17f5b2650d6fbc07b-724fde1d011e92886-0-0.
Jan 16 13:40:36  nanny[2025]: <303073> <ERRS> |AP d8:c7:c8:c8:03:e0@192.168.1.140 nanny|  Process /usr/sbin/dhcp-helper [pid 2358] died: got signal SIGTERM
Jan 16 13:40:36  nanny[2025]: <303079> <ERRS> |AP d8:c7:c8:c8:03:e0@192.168.1.140 nanny|  Restarted process /usr/sbin/dhcp-helper, new pid 2465
Jan 16 13:40:36  nanny[2025]: <303074> <ERRS> |AP d8:c7:c8:c8:03:e0@192.168.1.140 nanny|  Process /aruba/bin/radiusd [pid 2359] died: exited with 0x1
Jan 16 13:40:36  nanny[2025]: <303079> <ERRS> |AP d8:c7:c8:c8:03:e0@192.168.1.140 nanny|  Restarted process /aruba/bin/radiusd, new pid 2466
Highlighted
Guru Elite

Re: Can't get two IAP-175s to see each other

Did you perform a factory reset on both Iaps?  That is what I would do, if I were facing so many issues.  There is not enough information to determine what is wrong, unfortunately.


*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.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
ArubaOS Consolidated Release Notes
Aruba VIA ASE Solution - Configure VIA VPN
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: