v1.3.3 FINAL bug reports and comments

[QuadeHale]

Factory defaults is not an option. This is a very busy switch with about 100mbps idle traffic and pushing 300 at peak hours, and the owner of the property it's stashed at is an asshole that doesn't like me coming around. It was pulling teeth just to replace the EdgeSwitch that was in there.

I'm using Firefox. I also tried Chromium, Chrome, Safari and (ewww) IE. None work, all report 'Invalid Fields'. I'm assuming it's because I changed something in the CLI that it didn't like and/or doesn't report, but I can't seem to figure out what since it's not telling me.

[QuadeHale]

I figured it out. Somehow there was an entry in 'accesscontrol' as '1' and nothing else. I turned it off after some (careful) screwing around, and now I can save. Lesson learned.

[Dave]

thanks a lot for posting the actual solution...information will help others.

[sirhc]

Anytime you get that error in the UI there must be an invalid entry somewhere as you found but you can always click the browser refresh button and it will reload the current running config from the switch.

[QuadeHale]

Any chance the 'Invalid Field' can write out which field - specifically - was invalid? Or pull it up underneath? It would save a lot of headache. The CLI doesn't reject invalid configurations the way the GUI does.

[sirhc]

Any chance the 'Invalid Field' can write out which field - specifically - was invalid? Or pull it up underneath? It would save a lot of headache. The CLI doesn't reject invalid configurations the way the GUI does.

A quick click through the Tabs should reveal the bad input field in red?

I will discuss your suggestion of a drop down or maybe it takes you to the bad input field with Eric.

[WisTech]

Disabling a port still kills voltage to that port. You have to re-enable and disable again to get voltage on the line again although the LED is lit on the port for POE.

[sirhc]

Disabling a port still kills voltage to that port. You have to re-enable and disable again to get voltage on the line again although the LED is lit on the port for POE.

I thought that was fixed in v1.3.3.....I "Know" this is fixed in v1.3.5 which is due out SOON, maybe tonight.

v1.3.5 has a lot of fixes and enhancements

[WisTech]

Great, thank you sir! Just loaded 1.3.3 on all of my switches here at the NOC and tested it on a DC switch I'm burning in and the problem persists. Looking forward to 1.3.5. Keep up the good work!

[sirhc]

Great, thank you sir! Just loaded 1.3.3 on all of my switches here at the NOC and tested it on a DC switch I'm burning in and the problem persists. Looking forward to 1.3.5. Keep up the good work!

Yea v1.3.5 has improved I2C error handling which is more for the DC switches.

It adds some glitter and flash to the UI.

Has the missing SNMP values for DC switches requested.