1 Switch went offline other didn't why?

Simple configuration details
2x S8 POE Switches. Call them Switch 1 (1.2m) and Switch 2 (1.2m)
2x AP6-Pro, call them AP 1 (2.0g) and AP 2 (2.0g)
Each switch is a direct connection to the router, each AP has a direct connection to 1 switch.

Interesting behavior last night.
I was connected to switch 1 through AP 1, my wife was connected to switch 2 through AP 2. At some point my internet connection dropped off, eventually came back but was out for about 1-2 minutes that I noticed. During this time no impact to my wife’s connection.

Some additional notes:
I received an email alert noting the switch 1 and ap 1 were down “Alta devices have been detected offline:”.
The update of the switches and APs are in days, it didn’t go down.
I have persistent logging configured on the switch.
Checking my syslog server, can’t really see anything of substance.

Thoughts I what I can check next?

Thank you in advance

Hi,

I’ve found that my only S8 POE switch went down and wouldn’t come back up on its own without a manual power off. It’s only happened once to me so far since owning it so I haven’t really thought too much of it.

Something similar to this post: Alta Switch Stopped Working?

Would suggest taking a look at the way to configure SSH and the persistent logging.

Pulled some of the logs from the switch and looks like this switch wasn’t able to resolve to a particular host.
Will have to review if this is a local network resolution issue or something else.

Feb  9 23:39:22 Alta-Switch-1 daemon.notice rc: [2024/02/09 18:39:22:7198] N: JSON: {"reqStats":{"start":1707521901,"stop":1707521962,"period":"seconds","clientId":"removed"}}
Feb 10 00:06:34 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:06:34:0310] N: JSON: {"reqStats":{"start":1707523532,"stop":1707523593,"period":"seconds","clientId":"removed"}}
Feb 10 00:18:55 Alta-Switch-1 daemon.err rc: [2024/02/09 19:18:55:4612] E: ping timed out. reconnecting...
Feb 10 00:18:55 Alta-Switch-1 daemon.err rc: [2024/02/09 19:18:55:4618] E: Forcing disconnect!
Feb 10 00:18:55 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:18:55:4721] N: callback_unilever: closed
Feb 10 00:18:55 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:18:55:4743] N: __lws_lc_untag:  -- [wsicli|3|WS/h1/default/manage.alta.inc] (0) 10.808hr
Feb 10 00:19:27 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:19:27:9324] N: __lws_lc_tag:  ++ [wsicli|4|WS/h1/default/manage.alta.inc] (1)
Feb 10 00:19:32 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:19:32:9541] N: [wsicli|4|WS/h1/default/manage.alta.inc]: lws_client_connect_3_connect: dns lookup failed -3
Feb 10 00:19:39 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:19:39:7897] N: [wsicli|4|WS/h1/default/manage.alta.inc]: lws_client_connect_3_connect: dns lookup failed -3
Feb 10 00:19:42 Alta-Switch-1 daemon.err rc: [2024/02/09 19:19:42:9422] E: CLIENT_CONNECTION_ERROR: Closed before conn
Feb 10 00:19:42 Alta-Switch-1 daemon.err rc: [2024/02/09 19:19:42:9426] E: callback_unilever: connection attempts exhausted, waiting 500ms
Feb 10 00:19:42 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:19:42:9432] N: __lws_lc_untag:  -- [wsicli|4|WS/h1/default/manage.alta.inc] (0) 15.010s
Feb 10 00:19:43 Alta-Switch-1 daemon.alert rc: run "curl -s -f -6 -m 7 -X POST https://manage.alta.inc/api/device/boot -o /var/run/boot.json -H 'Content-Type: application/json' -d '{ "id": "removed", "model": "3", "version": "1.2m", "pubkey": " removed
Feb 10 00:19:48 Alta-Switch-1 daemon.alert rc: Warn: curl -s ... rc: 1536
Feb 10 00:19:48 Alta-Switch-1 daemon.warn rc: [2024/02/09 19:19:48:7324] W: reg6 failed
Feb 10 00:19:48 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:19:48:7331] N: __lws_lc_untag:  -- [wsi|0|pipe] (0) 2.649d
Feb 10 00:19:48 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:19:48:7338] N: __lws_lc_untag:  -- [vh|0|netlink] (1) 2.649d
Feb 10 00:19:48 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:19:48:7855] N: __lws_lc_untag:  -- [vh|1|default||-1] (0) 2.649d
Feb 10 00:19:48 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:19:48:7877] N:    /usr/lib/libwebsockets-evlib_uloop.so
Feb 10 00:19:48 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:19:48:7882] N: lws_create_context: LWS: 4.3.3-1.2m, NET CLI H1 H2 WS ConMon IPV6-off
Feb 10 00:19:48 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:19:48:7889] N: __lws_lc_tag:  ++ [wsi|0|pipe] (1)
Feb 10 00:19:48 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:19:48:7896] N: __lws_lc_tag:  ++ [vh|0|netlink] (1)
Feb 10 00:19:48 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:19:48:7906] N: __lws_lc_tag:  ++ [vh|1|default||-1] (2)
Feb 10 00:19:49 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:19:49:1638] N: __lws_lc_tag:  ++ [wsicli|0|WS/h1/default/manage.alta.inc] (1)
Feb 10 00:19:54 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:19:54:2210] N: [wsicli|0|WS/h1/default/manage.alta.inc]: lws_client_connect_3_connect: dns lookup failed -3
Feb 10 00:20:00 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:20:00:2292] N: [wsicli|0|WS/h1/default/manage.alta.inc]: lws_client_connect_3_connect: dns lookup failed -3
Feb 10 00:20:04 Alta-Switch-1 daemon.err rc: [2024/02/09 19:20:04:1820] E: CLIENT_CONNECTION_ERROR: Closed before conn
Feb 10 00:20:04 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:20:04:1826] N: __lws_lc_untag:  -- [wsicli|0|WS/h1/default/manage.alta.inc] (0) 15.018s
Feb 10 00:20:05 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:20:05:2288] N: __lws_lc_tag:  ++ [wsicli|1|WS/h1/default/manage.alta.inc] (1)
Feb 10 00:20:10 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:20:10:2453] N: [wsicli|1|WS/h1/default/manage.alta.inc]: lws_client_connect_3_connect: dns lookup failed -3
Feb 10 00:20:21 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:20:21:2731] N: [wsicli|1|WS/h1/default/manage.alta.inc]: lws_client_connect_3_connect: dns lookup failed -3
Feb 10 00:20:21 Alta-Switch-1 daemon.err rc: [2024/02/09 19:20:21:2736] E: CLIENT_CONNECTION_ERROR: Closed before conn
Feb 10 00:20:21 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:20:21:2764] N: __lws_lc_untag:  -- [wsicli|1|WS/h1/default/manage.alta.inc] (0) 16.047s
Feb 10 00:20:23 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:20:23:8001] N: __lws_lc_tag:  ++ [wsicli|2|WS/h1/default/manage.alta.inc] (1)
Feb 10 00:20:28 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:20:28:8052] N: [wsicli|2|WS/h1/default/manage.alta.inc]: lws_client_connect_3_connect: dns lookup failed -3
Feb 10 00:20:37 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:20:37:7208] N: callback_unilever: established
Feb 10 00:20:37 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:20:37:7311] N: writing connect
Feb 10 00:20:38 Alta-Switch-1 daemon.notice rc: [2024/02/09 19:20:38:1185] N: writing subscribe:

@donsandro @oakserver Thanks for reporting this! Can we get ask for full logs to dive into this further, please? First we are hearing of this and not something we can replicate in labs.

(touch /cfg/.persistent.log and reboot)

Also, @oakserver curious if you have another switch between your router and your S8-POE? If so, do you see anything in the logs of that switch?

@donsandro @oakserver Checking back in on this. Have you seen this behavior again since first reported?

No, as far as I recall it only happened to me once on the evening following installation of the POE only firmware update. I haven’t seen it occur since then.

1 Like

@Alta-Chase Thanks for following up, and happily additional events at this time.
Note the 3 events that have similarities, details/posts below.
Since moving the port per the suggestion in the thread I’ve had a whole network issues that looked to be ISP related and restarted the stack.

Will reply here should I see another event.

Thanks again

1 Like

@Alta-Chase unfortunately not an April fools.

This morning switch 1 and ap1 (connected through switch 1) lost connectivity. Other devices on switch 1, not wifi devices lost connectivity as well.

I exported logs and can sent to whomever when ready.

Thank you in advance.

@donsandro Thanks for the note! Sending you a DM now. We will investigate.

Morning @Alta-Chase,
Curious if there was anything in the logs?

Thanks,
Sandro

Morning @Alta-Chase wanted to follow up on this. I have not seen any additional issues since the last reported event a few months ago.
Thank you!

3 Likes

Thanks for the update @donsandro ! Great to hear!

1 Like