Netonix Forums

PVST is propritary and seem not compatible with standard STP/RSTP, at less, not to use multple path. You should use MSTP instead that is standard and will be eventually support by netonix.

Is management vlan still on track for 1.2.0? For our deployments, it's pretty much the only feature we're missing on these switches.

mayheart wrote:Is management vlan still on track for 1.2.0? For our deployments, it's pretty much the only feature we're missing on these switches.

Not sure what your talking about, that is in v1.1.8, that has been in there for several versions?

The Default/Managment VLAN where the primary switch IP resides is always at the top but you can change the VLAN ID and Description.

We did not do it the same as UBNT where you check a box on which VLAN is management but you have the same abilities.

sirhc wrote:
Goals for v1.3.0
...
Change VLAN Trunk Port (allow all VLANs) to an allowed VLANs list
...
DHCP Server - MAYBE IF YOU WANT IT
IPERF

Seem like HP Procurve trunk where you set a a list of VLAN IDs in a trunk and assign the trunk to a port ? If so, multiple trunk like in procurve would be nice.

DHCP server, in my case, no need for it. If you ever made L3 swtich, that would be a other story
iperf, v2 or v3 ? The only device I know that use v3 are edgeos based device and I must install v2 manually on them to be able to do iperf test with other devices on my network. Both of them would be the best option but if the're not enough place on flash, I vote for v2.

hi all

any chance of getting the following features added ?

lldp
edp ( extreme discovery protocol )

regards

ellis

2nd the request for LLDP.

Would also like to have DHCP relay on the switch. We have a large quantity of Ruggedcom switches that have a simple setup for it - just provide the DHCP address and the port(s) that need to provide the relay function.

In our application we have client access points running in router mode that get their address and hostname from DHCP and hand out DHCP addresses to client devices when they connect. The switch just takes care of relaying the requests to the DHCP server.

What's next?

Feature requests;

The test function that is in some 'other' gear has, is a real nice feature as it sometimes prevents a long drive to remote locations to fix an 'operator error' issue. If that feature could be added it would be a nice one.


A feature where a device on a single port can be reset to factory defaults and then that ONE port could be put in a special NAT mode with the outside having a interface settings of 192.168.1.199/24 and the inside of the NAT be settable so we can use a subnet that does exist on that site. This would enable fewer site visits and if a AP or other type units needs to be defaulted, we have remote access to breath life back into it without a site visit. That mode would have to be added and removed as needed and could be used on only one port at a time, and if you wanted it could be a feature that could only be engaged for a max time of 300 to 600 seconds and then it would revert.

Maybe a power saving mode for the Solar sites. a option where the LEDs can be all off. Also maybe the fan could be put in a power save mode where it would not come on for a few (10 to 20C) more degrees.

Maybe a settable MIB where if the voltage drops below a per set level (about 45VDC) a trap would be sent.

Thanks for asking!

John

highlands wrote:The test function that is in some 'other' gear has, is a real nice feature as it sometimes prevents a long drive to remote locations to fix an 'operator error' issue. If that feature could be added it would be a nice one.

This is already in v1.3.8
If you apply a config to the switch it will revert back to the previous config if it loses contact with your UI. The time duration is configurable on the Device/Configuration Tab. The default timeout is 60 seconds.

highlands wrote:A feature where a device on a single port can be reset to factory defaults and then that ONE port could be put in a special NAT mode with the outside having a interface settings of 192.168.1.199/24 and the inside of the NAT be settable so we can use a subnet that does exist on that site. This would enable fewer site visits and if a AP or other type units needs to be defaulted, we have remote access to breath life back into it without a site visit. That mode would have to be added and removed as needed and could be used on only one port at a time, and if you wanted it could be a feature that could only be engaged for a max time of 300 to 600 seconds and then it would revert.

This is not just a software feature it requires hardware changes and would add to the cost of the unit and make it larger.

highlands wrote:Maybe a power saving mode for the Solar sites. a option where the LEDs can be all off. Also maybe the fan could be put in a power save mode where it would not come on for a few (10 to 20C) more degrees.

Maybe a settable MIB where if the voltage drops below a per set level (about 45VDC) a trap would be sent.

The LED's use so little power this would be of no real benefit.

The fans are already smart controlled fans that spin up and down based on need to keep the board at safe operating temperatures, we did not spin the fans to a specific RPM based on the tea leaf patterns at the bottom of a salad shooter but rather based them on component safe operating temperature required to maintain the MTBF of the component manufacturer's spec sheet. Decreasing the fan speed to conserve power would result in overheating of the switch and failures.

We also used low power NAME Brand fans "SUNON" which cost us more money but we felt quality fans were a must.

As ALWAYS you are 'Johnny on the spot' with your reply's. Also you made the WS completely TOP NOTCH and it is VERY much appreciated! I do not in ANY way want you to think I am bad mouthing it.

'safety' feature
As you may have guessed we did not upgrade to 1.3.7 due to the issues with it. As to the 1.3.8 we waited a few days to see if anything major surfaced and it did not, so I went in today at noon time upped them to 1.3.8 and needed to applied a change right after that and saw the 'safety' feature show up!! THANK YOU THANK YOU THANK YOU very much!!

defaulting feature
As to the defaulting feature, the additional $$ would not be too bad considering the saving on site trips and reducing possible outage times. As to the size I hope it would only make it deeper and not taller or wider. In fact it would be nice if two WS-12-250-DC or WS-12-DC were made so that 2 of them would go side to side and fit in 1U of space with rack ears.

LEDs and power
OK, I am not willing to do any damage to the switch so the fan is just fine, specially with good ones. I have seen too many fans fail, causing other issues with other manufacturers.


New product request.
We use lots of licensed microwave that is not compatible with the PoE switches. Maybe a 'box' that would connect to the WS-12-250-DC or the WS-12-DC and connect bus wise and provide 4 to 8 SPDT type connections with power monitoring. This could be some sort of add on or a complete new product. But I think if you have the WS-12-250-DC consume half the rack space and then create a accessory or option that can some how connect to the bus on the current product so that base product you presently have just 'extends' its self to an accessory or option box next to it, you could leverage your currently great product with new abilities. Lets be honest your current WISP Switch line up have processors, memory and code that is 'loafing it's meat' and is not be utilized even at 20%. To have it use MIBs to do monitoring and control would not add 10 to 20% more to them.

16 Digital out, 8 logic level outs and then 4 relays rated at 5 to 10amps and 4 rated at 10 to 20amp
16 Digital inputs (door open, generator issues, motion sensors, fault indicators, ETC.)
16 analog inputs (room temp, current level from a solar panel or wind generator, ETC)

This new option with the current basic switch would be one stop shopping to cover almost everyone's needs. Right now many of us use TP-DIN or raspberry pi, or Denkovi, to monitor our sites, with this type of option you would do it all except for the solar chargers and controllers. For those just provide 4 ports of RS-232 and RS-442 serial ports for communications to solar controllers and for serial access to Cisco or other manufactures routers and the data from those would flow through your device and back to the NOCC.

Then lastly add a USB port designed for remote access. Simply connect (and we pay for) a cellular modem for when all communications is lost to the site there is a built in back door to gain access to the site to get the switches, routers, microwave gear or whatever working again with out having to roll a truck! Now THERE is a complete product! Want a partner on this?

John