Page 1 of 3
v1.4.1 Bug Reports and Comments
Posted: Sun May 29, 2016 11:18 am
by sirhc
Please post comments and report bugs with v1.4.1 in this thread
This version fixed 2 CRITICAL BUGS in v1.4.0
There may still be some issues to be worked out but we NEEDED v1.4.X to start shipping out the new WS-8-150-AC and WS-8-150-DC.
v1.4.1 wrote:FIXED
- Fixed the ability to DISABLE Loop Protection
- Fixed Discovery interfering with STP & LACP
- Fixed some UI bugs
ENHANCEMENTS
- Added some help mouse over balloons
- Added some help text to upgrade menu
KNOWN ISSUES
- Some language templates need help
- IGMP Snooping does not work for everyone - investigating
- SFP Stats for WS-10-250-AC broken - will be fixed in v1.4.2rcX
- Disabling the Discovery Tab requires a reboot to really disable the service.
- Enabling the Discovery Tab has caused some people to experience high CPU usage.
- I suggest using v1.4.2rc6 or later
Released 5/29/2016
SFP port counters
Posted: Mon May 30, 2016 1:20 pm
by 6gnet
Am I missing something or is there an issue on the latest 1.4.1rc2 with counters on SFP ports:
- Screenshot 2016-05-30 19.17.36.png (11.18 KiB) Viewed 9273 times
-G
Re: SFP port counters
Posted: Mon May 30, 2016 1:33 pm
by sirhc
I will have to go load up WS-10-250-AC later as I do not have one in service but you should always upgrade to the latest version and see if the problem is still there.
Current version is v1.4.1 FINAL
We are addressing some other issues people have found so there will be a v1.4.2rcX this week and if this is a bug we will get it put in the v1.4.2rcX but for now please verify the problem is there with v1.4.1.
I also pinged Eric on this.
Re: SFP port counters
Posted: Mon May 30, 2016 3:23 pm
by 6gnet
I'll load 1.4.1 tonight and will let you know.
-G
Re: SFP port counters
Posted: Mon May 30, 2016 4:47 pm
by sirhc
Apparently Eric says SFP stats on the WS-10-250-AC are broken even in v1.4.1
I will be putting up a v1.4.2rcX tonight or tomorrow sometime and it will be fixed. - SORRY!!!
Re: v1.4.1 Bug Reports and Comments
Posted: Mon May 30, 2016 7:50 pm
by 6gnet
Just tried upgrading to 1.4.1 and some errors popped up, I hope it comes up when it reboots....
Do not turn off power while upgrade is in progress!
Uploading firmware file ...
Unpacking firmware ...
sh: missing ]
/usr/bin/firmware_upgrade: line 150: WS-10-250-AC: not found
Running preflash script ...
Unlocking /dev/mtd8 ...
Writing from redboot_recovery_config to /dev/mtd8 ...
Unlocking linux ...
Writing from kernel.img to linux ...
Updating FIS entry linux
Unlocking FIS directory ...
Writing from fisdir to FIS directory ...
Unlocking Redundant FIS ...
Writing from redundant_fisdir to Redundant FIS ...
Unlocking rootfs ...
Writing from rootfs.img to rootfs ...
-G
Re: v1.4.1 Bug Reports and Comments
Posted: Mon May 30, 2016 8:12 pm
by 6gnet
It came up......
Now regarding discovery on WS-10-250-AC: I enabled Discover Tab, LLDP and Ubiquity:
Port 1 -> Airfiber 5x -> Airfiber 5x -> Netonix mini -> Other Ubiquity deviecs...
I see only Netonix mini on port 1
Port 3 -> Rocket 5AC PTMP
I don't see any devices in discovery tab on that port
Port 10 -> Juniper SRX with LLDP enabled on the port
No devices seen either...
Soft version 1.4.1
-G
Re: v1.4.1 Bug Reports and Comments
Posted: Tue May 31, 2016 2:03 am
by jg0007
Problem After updating the WS-12-250-AC unit to firmware v1.4.1 - FINAL the unit will not start correctly
Just sent this message
The interface will reload when complete restart
help
Re: v1.4.1 Bug Reports and Comments
Posted: Tue May 31, 2016 7:37 am
by jg0007
It could only be solved completely disconnected all power to the unit
The problem was I had to wait seven hours to be able to do all that while the network segment was no communication
That mistake is very bad for taking it into account to correct it
Re: v1.4.1 Bug Reports and Comments
Posted: Tue May 31, 2016 7:45 am
by sirhc
jg0007 wrote:It could only be solved completely disconnected all power to the unit
The problem was I had to wait seven hours to be able to do all that while the network segment was no communication
That mistake is very bad for taking it into account to correct it
Have no idea what caused this, obviously this is not something anyone else has experienced?
I do not even begin to know what it is?
I would pull that unit from service and do a hard default where you hold the default button in for 20 seconds when applying power.
Then I would perform the upgrade again then test it out completely on a bench before putting it back in service.