v1.3.8 FINAL bug reports and comments

[bradsdb]

I guess what I am seeing might be a bug that crashes the switch if the ntp server is un-reachable. I setup the switch on the bench, and it is not able to reach the ntp server "yet".

This should not crash the switch and make it un-responsive and stop passing arp/traffic. I have ordered a second switch and once it arrives, I will try to copy the config from this switch to the new one.

If your switch crashes due to an un-reachable ntp server this is not a good feature.

I will do more testing and see if I can isolate what is going on.

[bradsdb]

I will try the 1.3.9, thanks for the amazing switch. It is exactly what I have been looking for.

[TheHox]

I fail to see the value in the "Test" Button over the way we do it? Please explain the benefit?

You can set the Revert timer to whatever period of time in seconds within reason you want or "0" for Disable.

When you hit Save/Apply if the UI/CLI loses communications with the switch and does not regain it within the defined period of time it reverts to the previous config, if it connects back to the switch in the allotted time it assumes all is good.

The test button is literally right there to push it. It gives us full instant control. If I know what I am doing and want to apply, I hit apply and expect it to apply changes no matter what.
If I decided I want to test, I hit test.

With your method, I would always have to go and change the time from 60 or to 0 depending on what I wanted to do. Not to mention when applying those changes I have to worry about getting back to the switch just applying the change of the time to reset changes,

If nobody else has a problem with it, thats fine I don't expect just a few people to make a change. I'll deal with it, I still love the switches.

[adairw]

I'm with TheHox.

To me, it makes more sense to give someone the ability to control the revert changes on a case by case bases.
For instance, the other day, I had a crappy connection to a switch for some reason, I.E. the red bar at the top showed up from time to time telling me I had lost connection. But it wasn't so often that I was worried. Until I applied some vlan changes and just after that lost connection with the switch for a bit. Something happened with the browser and I didn't get back to the switch in time before it reverted... so I got to make all the changes all over again... I knew the changes wouldn't lock me out so I wasn't worried, but I'll be damn the switch was.
I just find it annoying that I have to go adjust or turn off the time on every switch every time I install one or have to think about those settings before I make changes. Like with the UBNT stuff, I get a big fat button the top that lets me chose (think about) what I changed before I click it.
Even the way mikrotik does it is pretty nice. If I think I'm getting in to sketchy water making changes that might lock me out of the router, I kick on test mode in winbox. otherwise it's off and I do my thing.

I can deal with it either way I guess, I just want to make sure it's the most functional.

[bradsdb]

What is the best way to report possible bugs? I can send an email.


I just noticed if you type "exit" on the console you no longer can log back in over serial unless you reboot the switch.


Not sure if that is a bug

[sirhc]

What is the best way to report possible bugs? I can send an email.


I just noticed if you type "exit" on the console you no longer can log back in over serial unless you reboot the switch.


Not sure if that is a bug

NEVER report bugs or ask for help in email. I am but one person and if I take the time to debug someones problem I hope that there is record here so someone with the same problem does not need be to resolve the same issue.

I am not sure I can reproduce what your saying, do you have it set that console requires you to login under the Device/Configuration Tab?

Please provide step by step to reproduce

[Buganah]

hi
1.3.8 installed on 7 Switches with no issue except one switch which is showing incorrect power readings
the pic included shows the issue

[sirhc]

Is it possible that the current sensors were off before the upgrade and you just did not notice them?

v1.3.8 sorta puts a spot light on them.

I would try a power cycle to see if they clear but if they do not this is indication of the current sensors being damaged.

If a reboot does not correct it I would collect that unit and bench test it as outlined in post #2 of this post
viewtopic.php?f=6&t=1259

Then if need be follow instructions on post #1 of that same thread above for RMA instructions.

If your current sensors are blown these are 2 good threads to read
viewtopic.php?f=30&t=188
viewtopic.php?f=30&t=1429

[Buganah]

hi ,, thnx for the quick reply
how the current sensors would be off ?
i have rebooted the switch with the same condition , also noted that port 7 give normal readings than the others.
just as a note to you i have upgraded from 1.3.3 directly to 1.3.8 - but this also apply to all the other switches - and i have tried downgrading it back to 1.3.3 with no change
i will check the posts you referred and i will let you know how it goes

[joshaven]

I've been really enjoying your hardware, thanks! 1.3.8 has been running well for me. We replaced a mess including an old gigabit Netgear, various poe injectors and a web power switch from digilogger for a client and now things are not only cleaner looking but we are seeing a side effect of things running much better too.