Problema force 300-25

Temos um par de force 300-25!

Enlace de 10km! Aleatoriamente todo o trafego lan para!

Ao reiniciar o equipamento, o trafego volta ao normal!

Alguma ideia do que pode ser?

1 Like

a mi me pasa lo mismo y eso que actualize a la version 4.5.6 donde se solucionan esos problemas pero siguen y eso me sale en el log

Nov 24 22:12:29 F300-25_2827f0 admin[192.168.0.100] web_interface: User: 'admin' role: 'admin' is logged inā€¦
Nov 24 22:11:54 F300-25_2827f0 DEVICE-AGENT[4238]: platform_set_cns_connection_state: New CNS_STATE cns_serv_stat Connecting(4)
Nov 24 22:11:37 F300-25_2827f0 netifd: Network device 'eth0' link is up
Nov 24 22:11:36 F300-25_2827f0 netifd: Network device 'eth0' link is down
Nov 24 22:10:52 F300-25_2827f0 DEVICE-AGENT[4238]: platform_set_cns_connection_state: New CNS_STATE cns_serv_stat Connecting(4)
Nov 24 22:09:51 F300-25_2827f0 DEVICE-AGENT[4238]: platform_set_cns_connection_state: New CNS_STATE cns_serv_stat Connecting(4)
Nov 24 22:09:12 F300-25_2827f0 DEVICE-AGENT[4238]: Trap data received: name STA_REG timestamp 1606273752 mac 00:04:56:28:56:49 status 0 msg []
Nov 24 22:09:12 F300-25_2827f0 kernel: [ 5037.527482] SM[00:04:56:28:56:49] aid=1 associated with AP
Nov 24 22:09:12 F300-25_2827f0 hostapd: ath0: STA 00:04:56:28:56:49 WPA: pairwise key handshake completed (RSN)
Nov 24 22:09:12 F300-25_2827f0 hostapd: ath0: STA 00:04:56:28:56:49 RADIUS: starting accounting session 1A40093FD4580F1E
Nov 24 22:09:12 F300-25_2827f0 hostapd: ath0: STA 00:04:56:28:56:49 IEEE 802.11: associated
Nov 24 22:08:49 F300-25_2827f0 DEVICE-AGENT[4238]: Trap data received: name STA_DROP timestamp 1606273687 mac 00:04:56:28:56:49 status 48 msg [COMMUNICATION LOST]
Nov 24 22:08:49 F300-25_2827f0 DEVICE-AGENT[4238]: Trap data received: name STA_REJECT timestamp 1606273687 mac 00:04:56:28:56:49 status 48 msg [COMMUNICATION LOST]
Nov 24 22:08:49 F300-25_2827f0 DEVICE-AGENT[4238]: platform_set_cns_connection_state: New CNS_STATE cns_serv_stat Connecting(4)
Nov 24 22:08:49 F300-25_2827f0 DEVICE-AGENT[4238]: Attempting (re)connection in 5 minutes
Nov 24 22:08:49 F300-25_2827f0 DEVICE-AGENT[4238]: Unable to discover cnMaestro URL (re-discover in 335 seconds)
Nov 24 22:08:49 F300-25_2827f0 DEVICE-AGENT[4238]: OpenConnection: getaddrinfo -2:(Name or service not known)
Nov 24 22:08:49 F300-25_2827f0 DEVICE-AGENT[4238]: OpenConnection to cloud.cambiumnetworks.com:443 failed
Nov 24 22:08:07 F300-25_2827f0 hostapd: ath0: STA 00:04:56:28:56:49 IEEE 802.11: disassociated
Nov 24 22:08:07 F300-25_2827f0 kernel: [ 4972.517235] SM[00:04:56:28:56:49] aid=1 disassociated. Reason: 48 (COMMUNICATION LOST)
Nov 24 22:07:49 F300-25_2827f0 DEVICE-AGENT[4238]: OpenConnection: hostname [cloud.cambiumnetworks.com] port [443/443]
Nov 24 22:07:49 F300-25_2827f0 DEVICE-AGENT[4238]: platform_set_cns_connection_state: New CNS_STATE cns_serv_stat Connecting(4)
Nov 24 22:07:49 F300-25_2827f0 DEVICE-AGENT[4238]: build_http_get_request: No cambium_id available
Nov 24 22:07:49 F300-25_2827f0 DEVICE-AGENT[4238]: build_http_get_request: Data serialNo: &serialNo=E6UA014GD500
Nov 24 22:07:43 F300-25_2827f0 DEVICE-AGENT[4238]: platform_set_cns_connection_state: New CNS_STATE cns_serv_stat Connecting(4)
Nov 24 22:07:43 F300-25_2827f0 DEVICE-AGENT[4238]: Attempting (re)connection in 5 seconds
Nov 24 22:07:43 F300-25_2827f0 DEVICE-AGENT[4238]: platform_set_cns_connection_state: New CNS_STATE cns_serv_stat Not Connected(0)
Nov 24 22:07:43 F300-25_2827f0 DEVICE-AGENT[4238]: callback_websocket: LWS_CALLBACK_CLOSED
Nov 24 22:07:43 F300-25_2827f0 DEVICE-AGENT[4238]: Websocket not closed destroying
Nov 24 22:07:12 F300-25_2827f0 DEVICE-AGENT[4238]: Saving reason string [1606273632:DEV_PING_TIMEOUT]
Nov 24 22:07:12 F300-25_2827f0 DEVICE-AGENT[4238]: send_close_frame_to_cnmaestro: da.state=3, writing close reason [DEV_PING_TIMEOUT]
Nov 24 22:07:12 F300-25_2827f0 DEVICE-AGENT[4238]: send_close_frame_to_cnmaestro: Sent CLOSE frame
Nov 24 22:07:12 F300-25_2827f0 DEVICE-AGENT[4238]: Missed 5 consecutive PONGS, disconnecting with server
Nov 24 22:07:12 F300-25_2827f0 DEVICE-AGENT[4238]: Not received PONG for the last ping (5)
Nov 24 22:06:47 F300-25_2827f0 DEVICE-AGENT[4238]: Not received PONG for the last ping (4)
Nov 24 22:06:28 F300-25_2827f0 DEVICE-AGENT[4238]: Not received PONG for the last ping (3)
Nov 24 22:05:59 F300-25_2827f0 DEVICE-AGENT[4238]: Not received PONG for the last ping (2)
Nov 24 22:05:32 F300-25_2827f0 DEVICE-AGENT[4238]: Not received PONG for the last ping (1)
Nov 24 21:57:50 F300-25_2827f0 admin[190.42.216.130] web_interface: User: 'admin' role: 'admin' is logged inā€¦
Nov 24 20:47:29 F300-25_2827f0 DEVICE-AGENT[4238]: Trap data received: name SYS_UP timestamp 1606268849 mac (null) status 1 msg [The Initialization State]
Nov 24 20:46:54 F300-25_2827f0 kernel: [ 98.912515] SM[00:04:56:28:56:49] aid=1 associated with AP
Nov 24 20:46:54 F300-25_2827f0 DEVICE-AGENT[4238]: Trap data received: name STA_REG timestamp 1606268814 mac 00:04:56:28:56:49 status 0 msg []
Nov 24 20:46:54 F300-25_2827f0 hostapd: ath0: STA 00:04:56:28:56:49 WPA: pairwise key handshake completed (RSN)
Nov 24 20:46:54 F300-25_2827f0 hostapd: ath0: STA 00:04:56:28:56:49 RADIUS: starting accounting session 85F4365163CF2EF5
Nov 24 20:46:54 F300-25_2827f0 hostapd: ath0: STA 00:04:56:28:56:49 IEEE 802.11: associated
Nov 24 20:46:24 F300-25_2827f0 DEVICE-AGENT[4238]: platform_set_cns_connection_state: New CNS_STATE cns_serv_stat Connected(6)
Nov 24 20:46:19 F300-25_2827f0 )
Nov 24 20:46:19 F300-25_2827f0 DEVICE-AGENT[4238]: handle_cns_msg: MSG_REGISTER_SUCCESS received
Nov 24 20:46:19 F300-25_2827f0 DEVICE-AGENT[4238]: platform_set_cns_connection_state: New CNS_STATE cns_serv_stat Device Approval Pending(5)
Nov 24 20:46:19 F300-25_2827f0 DEVICE-AGENT[4238]: Primary NTP server [193.5.216.14]
Nov 24 20:46:19 F300-25_2827f0 DEVICE-AGENT[4238]: SessionID unavailable, regenerating
Nov 24 20:46:19 F300-25_2827f0 DEVICE-AGENT[4238]: Connected to cnMaestro (0)
Nov 24 20:46:18 F300-25_2827f0 /OU=Domain Control Validated/OU=Issued through Cambium Networks Ltd E-PKI Manager/OU=COMODO SSL Wildcard/CN=.cloud.cambiumnetworks.com
Nov 24 20:46:18 F300-25_2827f0 DEVICE-AGENT[4238]: Server cert validation is enabled
Nov 24 20:46:18 F300-25_2827f0 DEVICE-AGENT[4238]: da_lws_client_connect: Trying connection with ip [3.232.226.205], ai_next 0x349b90
Nov 24 20:46:18 F300-25_2827f0 DEVICE-AGENT[4238]: Device-Agent Waiting for connectā€¦ to cnMaestro:[us-e1-s15-ojfthf7zs0.cloud.cambiumnetworks.com] ctimer=(nil)
Nov 24 20:46:18 F300-25_2827f0 DEVICE-AGENT[4238]: SSL_connect successful
Nov 24 20:46:18 F300-25_2827f0 DEVICE-AGENT[4238]: SSL_ERROR_WANT_READ try again
Nov 24 20:46:17 F300-25_2827f0 /OU=Domain Control Validated/OU=Issued through Cambium Networks Ltd E-PKI Manager/OU=COMODO SSL Wildcard/CN=
.cloud.cambiumnetworks.com
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: Server cert validation is enabled
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: SSL_ERROR_WANT_READ try again
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: Openssl connection to cloud.cambiumnetworks.com : 443
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: OpenConnection: Trying connection with ip [2600:1f18:1bb:f401:fdb2:574a:d8bf:3a3e], ai_next 0x349208
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: OpenConnection: Trying connection with ip [52.206.40.231], ai_next 0x349250
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: connect() Network is unreachable
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: Resolved cloud.cambiumnetworks.com to IPv4 address
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: connect() Network is unreachable
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: Resolved cloud.cambiumnetworks.com to IPv6 address
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: OpenConnection: Trying connection with ip [2600:1f18:1bb:f401:3629:79fb:b358:1c9], ai_next 0x3491a0
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: Resolved cloud.cambiumnetworks.com to IPv6 address
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: connect() Network is unreachable
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: OpenConnection: Trying connection with ip [2600:1f18:1bb:f400:fc5f:1e1d:87e9:9da3], ai_next 0x349138
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: Resolved cloud.cambiumnetworks.com to IPv6 address
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: connect() Network is unreachable
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: OpenConnection: Trying connection with ip [2600:1f18:1bb:f400:8be0:3a3f:51de:6b5c], ai_next 0x3490d0
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: Resolved cloud.cambiumnetworks.com to IPv6 address
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: Resolving URL cloud.cambiumnetworks.com
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: OpenConnection: hostname [cloud.cambiumnetworks.com] port [443/443]
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: platform_set_cns_connection_state: New CNS_STATE cns_serv_stat Connecting(4)
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: build_http_get_request: No cambium_id available
Nov 24 20:46:17 F300-25_2827f0 DEVICE-AGENT[4238]: build_http_get_request: Data serialNo: &serialNo=E6UA014GD500
Nov 23 05:24:44 F300-25_2827f0 firewall: Reloading firewall due to ifup of wan6 (ath0)
Nov 23 05:24:44 F300-25_2827f0 procd: - init complete -
Nov 23 05:24:42 F300-25_2827f0 mactelnetd[4408]: Bound to 0.0.0.0:20561
Nov 23 05:24:42 F300-25_2827f0 DEVICE-AGENT[4238]: platform_set_cns_connection_state: New CNS_STATE cns_serv_stat Connecting(4)
Nov 23 05:24:42 F300-25_2827f0 DEVICE-AGENT[4238]: Attempting (re)connection in 5 seconds
Nov 23 05:24:42 F300-25_2827f0 DEVICE-AGENT[4238]: platform_set_cns_connection_state: New CNS_STATE cns_serv_stat Not Connected(0)
Nov 23 05:24:36 F300-25_2827f0 firewall: Reloading firewall due to ifup of wan (ath0)
Nov 23 05:24:29 F300-25_2827f0 snmpd[3346]: DFS status: N/A
Nov 23 05:24:27 F300-25_2827f0 netifd: Network device 'ath1' link is up
Nov 23 05:24:27 F300-25_2827f0 dropbear[3322]: Not backgrounding
Nov 23 05:24:26 F300-25_2827f0 kernel: [ 38.698118] All STAs disassociated. IEEE80211_REASON_TDD_STOP (20)
Nov 23 05:24:26 F300-25_2827f0 kernel: [ 38.368073] All STAs disassociated. IEEE80211_REASON_TDD_STOP (20)
Nov 23 05:24:26 F300-25_2827f0 kernel: [ 38.048204] All STAs disassociated. IEEE80211_REASON_TDD_STOP (20)

Me pasa lo mismo, deja de pasar trĆ”fico,pero el link inalĆ”mbrico sigue up. Alguna SoluciĆ³n?

We have a F300 backhaul which has this symptom. The wireless link remains, but there is no traffic. We use the ā€œping watchdogā€ to reset the interfaces, and thatā€™s reasonable quick, until we can replace it.

Itā€™s worth mentioning - the ping watchdog options and interface is horribleā€¦ not at all flexible enough, and not at all worthy of some of the most expensive gear in itā€™s class. BUT, itā€™s a functional - and can work in an emergency.

1 Like

Everyone has these symptoms, you didnā€™t ā€œwelcome to the beakā€ yourself, disassemble the f300, step on it, donā€™t sell it on ebay because you will make someone angry. Put the f200 back in place and enjoy. If you donā€™t have f200 anything else but donā€™t f300.
Cambium got lost on AC, everything on AC has a problem.

Same as you pal.

I found the following - This is an ePMP Force 300-25 link, both sides, 3km distance on 40Mhz channel width and ePMP mode: one side (AP) always on, not a single problem. SM side, always loosing Ethernet LAN side conection on a regular basis.
Found that, anytime the Ethernet link SM side was down, the AP side kinda flaps on Wireless side. Not even making the link down, but displaying that quick disconnection in the log.

Turn Spectrum Analyzer on and found some fuzzy noise and overlapping with other fellowā€™s RF in the link (something that Cambium never used to be aware of, butā€¦)

Move the link 5Mhz to the lower part of the spectrum and the problem seemed to decrease, but not dissappear.

Then i thought that if it was related to the wireless side, and the link frequency was quite clean now, as we know ePMP mode is good at low latency but not the best at stability, i setted the link power from 22dbm both sides, to 25dbm both sides.

72 hours from that, problem seem to dissapper. :crossed_fingers:

For what itā€™s worth, on anything running 4.7.1-RC18 we havenā€™t had this issue at all. Of course RC18 is only about 2 weeks old, so that might just be ā€˜one of those thingsā€™ where the problem doesnā€™t show up for 2 weeks. But for us 4.7.1-RC18 has solved everything that Iā€™m aware of as a bug.