Netonix Forums

Info to report with your issue wrote:When making a post about an issue please include the following information:
Screen grabs of any Tabs with config changes if a software issue.
Always include screen grabs of main Status Tab and Device Status Tab
Always describe the tower and box situation including what you have for grounding.

EXAMPLE DESCRIPTION OF GROUNDING: Tower has (3) 8' ground rods about 10' apart connected to main ground bus at base of tower with #2 TIN. Electric service has (2) 8' ground rods separated by 10'. The service ground is bonded with the the tower ground rods with #2 Tin. We have a #2 Green running up the tower to a ground bus near the antennas and #6 green with ground lug to each antenna.

EXAMPLE DESCRIPTION OF POWER: We get power from an another building 100' away. Since we did not want to run a bonding ground wire of at least #2 preferably #1 we only use the Hot and Neutral from the source and use the tower Earth Ground to the receptacle in the box. This way the equipment in the box and on the tower share the same common Earth Ground to prevent ground potential differnce.

v1.4.2 wrote:FIXED
- Fixed SFP Stats for WS-10-250-AC
- Fixed Disabling Discovery Tab in the UI so it actually disables the service
- Fixed HIGH CPU utilization wen Discovery Tab was enabled
- Fixed port watt usage on the WS-8-150-DC
- Fix null switch name in emails
- Fix problem with ubnt discovery interfering with STP (we think this is fixed waiting on feed back)
- Fix for IGMP Snooping with VLANs (we think this is fixed waiting on feed back)

ENHANCEMENTS
- Added option to disable IGMP querier per VLAN if IGMP snooping is enabled
- Increased the acceptable voltage ranges to prevent false alerts
- Tweaked Pause Frame Storm Protection

KNOWN ISSUES
- Some language templates need help - please contact us to help
- Clearing Stats on SFP ports singly is broken on some models - Known broken on WS-10-250-AC and WS-12-250-XX
- If you add a port bounce via the CLI it will corrupt your config file - URGENT
- If you have SMTP alerts enabled and the switch can not reach the SMTP server or the SMTP server is slow for what ever reason it messes up
- Bug with shell exit
- Missing field on scheduled port bounces created in CLI will cause a config file to become corrupt
- Occasional invalid statistics reported to the UI
- Clearing of stats on SFP ports broken
- SNMP ifName/ifDescr/ifAlias incorrect
- Bug with console login when using passwords with special characters
- Power budget on WS-8-150-DC incorrect
- CDP and LLDP on SFP ports on 12 port models broken
- SMTP can caused UI to become unresponsive if there was an issue with server
- Reboot command does not do warm boot properly
- IGMP snooping with vlans broken
- Incorrect port number on LACP notification
- Colour of 100M links on SFP ports incorrect
- Bug that can cause duplicate switch processes to start whenever an email alert is sent and eat up CPU time.

Released 6/15/2016

canpandave wrote:So far, no drama, 1-WS-8-250DC and 1-WS-12-DC

Errors during upgrade:
/usr/bin/firmware_upgrade:line 150: WS-8-250-DC: not found

and

/usr/bin/firmware_upgrade:line 150: WS-12-250-DC: not found

No apparent impact, upgrade went OK, switches are back and working

NB: Just upgraded WS-12-250-AC and the error does not appear

/d

bonac wrote:Hello,

on both this new FW and previous stock FW,
on both WS-12-250-DC and WS-10-250-DC,

we cannot enter an email address with only one char before the @domain, though this is perfectly legible, see RFC2822 ( https://tools.ietf.org/html/rfc2822 ).
More readable: https://www.cs.tut.fi/~jkorpela/rfc/822addr.html At least, any of the following chars:

!"#$%&'*+-/0123456789=?@ABCDEFGHIJKLMNOPQRSTUVWXYZ^_`abcdefghijklmnopqrstuvwxyz{|}~

can be used in the "local-part" of the email address, including only one char.

And we do have such emails ...

Rgds.

Hightech wrote:Just got a new WS-10-250-AC firmware 1.4.2 final don't pass management vlan on tagget trunk ports on the switch if the port is untagget on management vlan it pass the trafic.

We have had this error before on some very old firmware versions.

We use STP on this ports that don't pass management vlan.

firmware 1.4.2rc6 work just fine, so you have changed some thing on the final version!

We have 1.4.2 final running on a WS-12-250A with same configuration working just fine, so it is me by related to the ws-10-250-AC switch

Br.
Carsten