Well first try telling the Manager NOT to monitor it and see what happens. If there is a BAD connection/path from the Manager to the switch "maybe"????
Next I would try factory default and set back up.
v1.5.1rcX Bug Reports and Comments
-
sirhc - Employee
- Posts: 7416
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1608 times
- Been thanked: 1325 times
Re: v1.5.1rcX Bug Reports and Comments
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
- wirelessblue
- Member
- Posts: 34
- Joined: Wed Apr 22, 2015 5:50 pm
- Has thanked: 9 times
- Been thanked: 1 time
Re: v1.5.1rcX Bug Reports and Comments
In looking at top output in the console, I see seven "switch" processes and one "dropbear" that are all basically taking 10% CPU. Is that what should normally be happening?
- wirelessblue
- Member
- Posts: 34
- Joined: Wed Apr 22, 2015 5:50 pm
- Has thanked: 9 times
- Been thanked: 1 time
Re: v1.5.1rcX Bug Reports and Comments
sirhc wrote:Well first try telling the Manager NOT to monitor it and see what happens. If there is a BAD connection/path from the Manager to the switch "maybe"????
Next I would try factory default and set back up.
I removed it from Manager. No change on the switch itself. I also shutdown Manager completely and that made no difference.
-
sirhc - Employee
- Posts: 7416
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1608 times
- Been thanked: 1325 times
Re: v1.5.1rcX Bug Reports and Comments
Well your down to trying a factory default and manually set back up I guess?
If that does not fix it then it has to be something with your network as I am not seeing this on any of my WISP deployed switches and I even just played with one here?
I know this is ok little help but I can not create this or see this?
If that does not fix it then it has to be something with your network as I am not seeing this on any of my WISP deployed switches and I even just played with one here?
I know this is ok little help but I can not create this or see this?
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
- wirelessblue
- Member
- Posts: 34
- Joined: Wed Apr 22, 2015 5:50 pm
- Has thanked: 9 times
- Been thanked: 1 time
Re: v1.5.1rcX Bug Reports and Comments
sirhc wrote:Well your down to trying a factory default and manually set back up I guess?
If that does not fix it then it has to be something with your network as I am not seeing this on any of my WISP deployed switches and I even just played with one here?
I know this is ok little help but I can not create this or see this?
Understood. Thank you. I'll see what I can figure out.
- wirelessblue
- Member
- Posts: 34
- Joined: Wed Apr 22, 2015 5:50 pm
- Has thanked: 9 times
- Been thanked: 1 time
Re: v1.5.1rcX Bug Reports and Comments
It turns out I was still on 1.5.0 where I thought I had already upgraded that switch. I upgraded it to 1.5.1rc1 at 2:30am and am monitoring now. So far so good. I am also monitoring with Manager again with no issues so far. Thanks for your help.
-
sirhc - Employee
- Posts: 7416
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1608 times
- Been thanked: 1325 times
v1.5.1rc2 Released
v1.5.1rcX wrote:FIXED/CHANGED
- Fixed voltage input calibration for the WS-8-150-DC - RC1
- Fixed services running on IPv6 - RC2
- Fixed being able to bypass console login by hitting CTRL-C - RC2
- Fixed MSTP setting instance forwarding state - RC2
ENHANCEMENTS
KNOWN ISSUES
- WEB UI issues when not at 100% Zoom on browser especially on VLAN TAB
- Some language templates need help - please private message Eric Stern to help
- IGMP snooping over VLANS, MSTP, and ERPS are still being developed
RC1 Released 6/20/2018
RC2 Released 7/10/2018
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
-
sakita - Experienced Member
- Posts: 206
- Joined: Mon Aug 17, 2015 2:44 pm
- Location: Arizona, USA
- Has thanked: 93 times
- Been thanked: 80 times
Re: v1.5.1rcX Bug Reports and Comments
v1.5.1rc1 - Tested hibernation with the WS-8-250-DC ... goes in and out of hibernation correctly and as expected... except that upon resume from hibernation the board temperature reading is always unknown so the fan spins up to maximum speed and stays there. A warm restart (reboot from the UI) will bring back the board temperature and the fan will resume normal operation. Have tested this multiple times. Also noted power supply firmware is version 70.
Also tested the WS-12-250-DC the same way. On this model the board temperature reading is working after resuming from hibernation so no problem.
...and then v1.5.1rc2 is released
Also tested the WS-12-250-DC the same way. On this model the board temperature reading is working after resuming from hibernation so no problem.
...and then v1.5.1rc2 is released
Today is an average day: Worse than yesterday, but better than tomorrow.
Re: v1.5.1rcX Bug Reports and Comments
On the VLAN tab if the 'Trunk Port' has a vlan listed that is also below in the table, that vlan can't be excluded by setting the 'E'. We use to be able to, is that expected or a bug?
-
mike99 - Associate
- Posts: 837
- Joined: Tue Nov 25, 2014 10:53 am
- Location: Quebec, Canada
- Has thanked: 95 times
- Been thanked: 245 times
Re: v1.5.1rcX Bug Reports and Comments
Don't know if that expected but trunk should be configure as an allow list like and not via the "U, T, Q, D" Tab. When you check the "trunk" option, you can change the default list
0-4095
for something like this
0-15,18-22,39-4095
None include VID number will be exclude juste like with the E option.
0-4095
for something like this
0-15,18-22,39-4095
None include VID number will be exclude juste like with the E option.
Who is online
Users browsing this forum: No registered users and 60 guests