Hey Guys,
My Manager (V1.0.17) is acting a little weird after reloading onto WIN 10 Pc.
The Devices LED's on the left side show red the periodically change to green.
Not sure whats up with this.
One of the Switches I'm connecting to is a WS-8-150AC with FW 1.5.0.
Haven't performed a firmware update yet to maybe see if this is whats up.
I have disabled my server pc firewall temporarily to see if that may be the cause but no joy there.
Any thoughts would be appreciated.
Here is the error in question:
Device 'Studio Site Netonix' (10.1.11.5) changed state to Offline: Error: write EPROTO 1988:error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol:c:\ws\deps\openssl\openssl\ssl\statem\statem_lib.c:1929:
Manager quirks
- sambo521
- Member
- Posts: 11
- Joined: Wed Jul 27, 2016 3:24 pm
- Has thanked: 0 time
- Been thanked: 0 time
-
Stephen - Employee
- Posts: 1033
- Joined: Sun Dec 24, 2017 8:56 pm
- Has thanked: 85 times
- Been thanked: 181 times
Re: Manager quirks
Please upgrade your switch to the latest code 1.5.5
There was a bug awhile back in the switch firmware that could cause issue's like this with the manager.
There was a bug awhile back in the switch firmware that could cause issue's like this with the manager.
- sambo521
- Member
- Posts: 11
- Joined: Wed Jul 27, 2016 3:24 pm
- Has thanked: 0 time
- Been thanked: 0 time
Re: Manager quirks
My test subject is running the latest FW version 1.5.5.
What I'm seeing on wireshark is that they quit communicating and when it does I get the RED dot.
Its very sporadic.
I have disabled my Firewall to see if that helps but no cigar.
It would help if I knew more about how manager actually works along with its relationship with Jnode.
here are the logs for the failure event:
2/14/2020 9:29:00 AM Device 'Netonix Switch 3' (192.168.10.252) changed state to Offline: Error: write EPROTO 4668:error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol:c:\ws\deps\openssl\openssl\ssl\statem\statem_lib.c:1929:
2/14/2020 9:29:23 AM Device 'Netonix Switch 3' (192.168.10.252) changed state to Online
2/14/2020 9:30:53 AM Device 'Netonix Switch 3' (192.168.10.252) changed state to Offline: Error: write EPROTO 4668:error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol:c:\ws\deps\openssl\openssl\ssl\statem\statem_lib.c:1929:
I have uninstalled everything to do with Manager and reinstalled a couple of times now. However I apparently missed something because it still remebers my settings.
Anyway this is very annoying.
There are no clear instructions as to installing JNODE, do you just install the basic LTS program or do you also click on any extra check boxes?
Maybe I'm overthinking this whole thing.
What I'm seeing on wireshark is that they quit communicating and when it does I get the RED dot.
Its very sporadic.
I have disabled my Firewall to see if that helps but no cigar.
It would help if I knew more about how manager actually works along with its relationship with Jnode.
here are the logs for the failure event:
2/14/2020 9:29:00 AM Device 'Netonix Switch 3' (192.168.10.252) changed state to Offline: Error: write EPROTO 4668:error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol:c:\ws\deps\openssl\openssl\ssl\statem\statem_lib.c:1929:
2/14/2020 9:29:23 AM Device 'Netonix Switch 3' (192.168.10.252) changed state to Online
2/14/2020 9:30:53 AM Device 'Netonix Switch 3' (192.168.10.252) changed state to Offline: Error: write EPROTO 4668:error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol:c:\ws\deps\openssl\openssl\ssl\statem\statem_lib.c:1929:
I have uninstalled everything to do with Manager and reinstalled a couple of times now. However I apparently missed something because it still remebers my settings.
Anyway this is very annoying.
There are no clear instructions as to installing JNODE, do you just install the basic LTS program or do you also click on any extra check boxes?
Maybe I'm overthinking this whole thing.
- sambo521
- Member
- Posts: 11
- Joined: Wed Jul 27, 2016 3:24 pm
- Has thanked: 0 time
- Been thanked: 0 time
Re: Manager quirks
I think I found the issue:
It appears to be with TLS.
I uninstalled JSNODE V14 and installed V4 and now it works properly. Apparently it had to do with not seeing TLS 1 from what I understand. There is a switch to allow JSnode to accept TLS 1 but thats too much for me so I went with the earlier version and it seems stable.
Hope this helps.
It appears to be with TLS.
I uninstalled JSNODE V14 and installed V4 and now it works properly. Apparently it had to do with not seeing TLS 1 from what I understand. There is a switch to allow JSnode to accept TLS 1 but thats too much for me so I went with the earlier version and it seems stable.
Hope this helps.
-
Stephen - Employee
- Posts: 1033
- Joined: Sun Dec 24, 2017 8:56 pm
- Has thanked: 85 times
- Been thanked: 181 times
Re: Manager quirks
Thank you for your input. I think you've shown that the manager has some deprecated code in it. Which version of nodejs did you go back too that is stable for you?
- sambo521
- Member
- Posts: 11
- Joined: Wed Jul 27, 2016 3:24 pm
- Has thanked: 0 time
- Been thanked: 0 time
-
Stephen - Employee
- Posts: 1033
- Joined: Sun Dec 24, 2017 8:56 pm
- Has thanked: 85 times
- Been thanked: 181 times
Re: Manager quirks
It should also work with 8.9.0 If you run into issue's with the version you have. You might want to try 8.9 next.
8 posts
Page 1 of 1
Who is online
Users browsing this forum: No registered users and 26 guests