Controllerless Networks

Reply
Highlighted
Occasional Contributor I

Clients getting disconnected regularly from AP 115

 

*********************************************************************************************************
 6/23/2020 19:41:13 PM    Target:     Command: show log system 
*********************************************************************************************************

Jun 23 22:37:59  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  /etc/setup_ip_swarm Ethernet 1
Jun 23 22:37:59  cli[2446]: <341166> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Get interface br0 ip: 192.168.0.11/255.255.255.0.
Jun 23 22:37:59  cli[2446]: <341185> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Retrieving ip address from br0, ip 192.168.0.11, mask 255.255.255.0.
Jun 23 22:37:59  cli[2446]: <341274> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Update election ip from br0, election ip 192.168.0.11/255.255.255.0.
Jun 23 22:37:59  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  build_my_ip_address: old ip and new ip same; skipping
Jun 23 22:37:59  cli[2446]: <341006> <CRIT> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Sending uplink_up msg to sapd
Jun 23 22:37:59  cli[2446]: <341006> <CRIT> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  trap uplink info.
Jun 23 22:37:59  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  last uplink is null, it's the first uplink, ignore this trap.
Jun 23 22:37:59  cli[2446]: <341264> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  disable uplink .
Jun 23 22:37:59  cli[2446]: <341167> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Uplink  type Dummy, state PROBE->DOWN.
Jun 23 22:37:59  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  disable dummy uplink
Jun 23 22:37:59  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  enable SSID[arb
Jun 23 22:38:02  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  recv non-3g setup_uplink finished from sapd
Jun 23 22:38:10  nanny[2397]: <303073> <ERRS> |AP ac:a3:1e:ca:b5:68@192.168.0.11 nanny|  Process /aruba/bin/ntpclient [pid 7659] died: got signal SIGTERM
Jun 23 22:38:10  nanny[2397]: <303079> <ERRS> |AP ac:a3:1e:ca:b5:68@192.168.0.11 nanny|  Restarted process /aruba/bin/ntpclient, new pid 9038
Jun 23 23:12:50  cli[2446]: <341271> <ERRS> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  ethernet uplink bond0 link down.
Jun 23 23:12:50  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  stopping DHCP on bond0
Jun 23 23:12:50  cli[2446]: <341185> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Retrieving ip address from br0, ip 192.168.0.11, mask 255.255.255.0.
Jun 23 23:12:50  cli[2446]: <341274> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Update election ip from br0, election ip 192.168.0.11/255.255.255.0.
Jun 23 23:12:50  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  build_my_ip_address: old ip and new ip same; skipping
Jun 23 23:12:50  cli[2446]: <341167> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Uplink bond0 type Ethernet, state UP->DOWN.
Jun 23 23:12:50  cli[2446]: <341263> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  enable uplink .
Jun 23 23:12:50  cli[2446]: <341167> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Uplink  type Dummy, state DOWN->PROBE.
Jun 23 23:12:50  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  enable dummy uplink
Jun 23 23:12:50  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  disable SSID[arb
Jun 23 23:12:53  cli[2446]: <341272> <ERRS> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  ethernet uplink bond0 link up.
Jun 23 23:12:53  cli[2446]: <341167> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Uplink bond0 type Ethernet, state DOWN->UP.
Jun 23 23:12:53  cli[2446]: <341166> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Get interface br0 ip: 192.168.0.11/255.255.255.0.
Jun 23 23:12:53  cli[2446]: <341005> <ERRS> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  wired reset detected, setup ip now
Jun 23 23:12:53  cli[2446]: <341181> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Uplink bond0, setup ip for uplink - Ethernet.
Jun 23 23:12:53  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  bring up dhcp client for ethernet uplink
Jun 23 23:12:54  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  /etc/setup_ip_swarm Ethernet 1


Jun 23 23:12:54  cli[2446]: <341166> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Get interface br0 ip: 192.168.0.11/255.255.255.0.
Jun 23 23:12:54  cli[2446]: <341185> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Retrieving ip address from br0, ip 192.168.0.11, mask 255.255.255.0.
Jun 23 23:12:54  cli[2446]: <341274> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Update election ip from br0, election ip 192.168.0.11/255.255.255.0.
Jun 23 23:12:54  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  build_my_ip_address: old ip and new ip same; skipping
Jun 23 23:12:54  cli[2446]: <341006> <CRIT> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Sending uplink_up msg to sapd
Jun 23 23:12:54  cli[2446]: <341006> <CRIT> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  trap uplink info.
Jun 23 23:12:54  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  last uplink is null, it's the first uplink, ignore this trap.
Jun 23 23:12:54  cli[2446]: <341264> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  disable uplink .
Jun 23 23:12:54  cli[2446]: <341167> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Uplink  type Dummy, state PROBE->DOWN.
Jun 23 23:12:54  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  disable dummy uplink
Jun 23 23:12:54  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  enable SSID[arb
Jun 23 23:12:57  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  recv non-3g setup_uplink finished from sapd
Jun 23 23:13:07  nanny[2397]: <303073> <ERRS> |AP ac:a3:1e:ca:b5:68@192.168.0.11 nanny|  Process /aruba/bin/ntpclient [pid 9038] died: got signal SIGTERM
Jun 23 23:13:07  nanny[2397]: <303079> <ERRS> |AP ac:a3:1e:ca:b5:68@192.168.0.11 nanny|  Restarted process /aruba/bin/ntpclient, new pid 12923
Jun 23 23:13:41  nanny[2397]: <303073> <ERRS> |AP ac:a3:1e:ca:b5:68@192.168.0.11 nanny|  Process /aruba/bin/radiusd-term [pid 12976] died: got signal SIGTERM
Jun 23 23:13:41  nanny[2397]: <303079> <ERRS> |AP ac:a3:1e:ca:b5:68@192.168.0.11 nanny|  Restarted process /aruba/bin/radiusd-term, new pid 13023
Jun 23 23:38:55  cli[2446]: <341271> <ERRS> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  ethernet uplink bond0 link down.
Jun 23 23:38:55  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  stopping DHCP on bond0
Jun 23 23:38:55  cli[2446]: <341185> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Retrieving ip address from br0, ip 192.168.0.11, mask 255.255.255.0.
Jun 23 23:38:55  cli[2446]: <341274> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Update election ip from br0, election ip 192.168.0.11/255.255.255.0.
Jun 23 23:38:55  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  build_my_ip_address: old ip and new ip same; skipping
Jun 23 23:38:55  cli[2446]: <341167> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Uplink bond0 type Ethernet, state UP->DOWN.
Jun 23 23:38:55  cli[2446]: <341263> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  enable uplink .
Jun 23 23:38:55  cli[2446]: <341167> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Uplink  type Dummy, state DOWN->PROBE.
Jun 23 23:38:55  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  enable dummy uplink
Jun 23 23:38:55  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  disable SSID[arb
Jun 23 23:38:58  cli[2446]: <341272> <ERRS> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  ethernet uplink bond0 link up.
Jun 23 23:38:58  cli[2446]: <341167> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Uplink bond0 type Ethernet, state DOWN->UP.
Jun 23 23:38:58  cli[2446]: <341166> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Get interface br0 ip: 192.168.0.11/255.255.255.0.
Jun 23 23:38:58  cli[2446]: <341005> <ERRS> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  wired reset detected, setup ip now
Jun 23 23:38:58  cli[2446]: <341181> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Uplink bond0, setup ip for uplink - Ethernet.


:38:59  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  /etc/setup_ip_swarm Ethernet 1
Jun 23 23:38:59  cli[2446]: <341166> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Get interface br0 ip: 192.168.0.11/255.255.255.0.
Jun 23 23:38:59  cli[2446]: <341185> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Retrieving ip address from br0, ip 192.168.0.11, mask 255.255.255.0.
Jun 23 23:38:59  cli[2446]: <341274> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Update election ip from br0, election ip 192.168.0.11/255.255.255.0.
Jun 23 23:38:59  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  build_my_ip_address: old ip and new ip same; skipping
Jun 23 23:38:59  cli[2446]: <341006> <CRIT> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Sending uplink_up msg to sapd
Jun 23 23:38:59  cli[2446]: <341006> <CRIT> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  trap uplink info.
Jun 23 23:38:59  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  last uplink is null, it's the first uplink, ignore this trap.
Jun 23 23:38:59  cli[2446]: <341264> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  disable uplink .
Jun 23 23:38:59  cli[2446]: <341167> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  Uplink  type Dummy, state PROBE->DOWN.
Jun 23 23:38:59  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  disable dummy uplink
Jun 23 23:38:59  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  enable SSID[arb
Jun 23 23:39:02  cli[2446]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli|  recv non-3g setup_uplink finished from sapd
Jun 23 23:39:10  nanny[2397]: <303073> <ERRS> |AP ac:a3:1e:ca:b5:68@192.168.0.11 nanny|  Process /aruba/bin/ntpclient [pid 12923] died: got signal SIGTERM
Jun 23 23:39:10  nanny[2397]: <303079> <ERRS> |AP ac:a3:1e:ca:b5:68@192.168.0.11 nanny|  Restarted process /aruba/bin/ntpclient, new pid 15836
 
 
Highlighted

Re: Clients getting disconnected regularly from AP 115

Looks like your AP Uplink connection is not stable.

Highlighted
Occasional Contributor I

Re: Clients getting disconnected regularly from AP 115

Sometimes i also get "Access point temporarily full". I dont think that is related.

 

is there something i can do to fix both the issues?

Highlighted

Re: Clients getting disconnected regularly from AP 115

How many Clients did you have connected on the AP?

 

Did you checked the Switch Port Counters like Port errors etc.?

If you see same issue on the switch I would suggest to exchange the Patch Cable.

 

Your Uplink Port is flapping.

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