v1.3.3 FINAL bug reports and comments

[QuadeHale]

I had the same problem (the DHCP transition). I just got a whack of WS-6-MINIs in, flashed them all to 1.3.3, and realized they don't play nice on the DHCP transition. It's like they only think to communicate with the DHCP server on a cold boot - unplugging/replugging cables doesn't cut it, and I couldn't make anything 'work' via console, but toggling power made them come back up and snag an IP. As well, just FYI, they don't do a DHCP 'release' either when you go back to static.

I'm having a problem with the UI - it's blank, and I can't do anything about it really. Here's what it looks like:
I had just upgraded to 1.3.3 a couple hours prior. It came back up okay, but in the last three hours (wherein the switch now has every port full) this is all I've got. I can SSH in to it, rebooting it doesn't help (cold or otherwise), I can ping it, but the UI is just straight up gone.

Any hints?

[sirhc]

I had the same problem (the DHCP transition). I just got a whack of WS-6-MINIs in, flashed them all to 1.3.3, and realized they don't play nice on the DHCP transition. It's like they only think to communicate with the DHCP server on a cold boot - unplugging/replugging cables doesn't cut it, and I couldn't make anything 'work' via console, but toggling power made them come back up and snag an IP. As well, just FYI, they don't do a DHCP 'release' either when you go back to static.

I'm having a problem with the UI - it's blank, and I can't do anything about it really. Here's what it looks like:
I had just upgraded to 1.3.3 a couple hours prior. It came back up okay, but in the last three hours (wherein the switch now has every port full) this is all I've got. I can SSH in to it, rebooting it doesn't help (cold or otherwise), I can ping it, but the UI is just straight up gone.

Any hints?

Try:
1) Hit refresh on browser
2) Try different browser
3) Factory default it - viewtopic.php?f=17&t=409

[lligetfa]

[ctrl]-[F5] or better still, clear the browser cache.

[QuadeHale]

Well that was annoying and weird. I tried private mode (which usually fixes firefox issues like this) and it didn't work, and Chrome, last night - all with the same issue. This afternoon I wake up and it's just 'working' in Firefox mode without needing a CTRL-F5... I'll remember it for the future though. Thanks.

[ralliart12]

So I'm on v1.3.3 as well & I noticed something that doesn't make sense to me (it may be because I'm a newbie to networking & PoE but...):

All ports had PoE-Smart enabled.
I accidentally activated PoE on Port 9 when there's nothing connected to Port 9 of the switch, i.e. there's not even a LAN cable physically inserted into Port 9. However, as you can see, apparently the PoE-Smart test was passed on Port 9 (& PoE was activated)? What gives?

[sirhc]

So I'm on v1.3.3 as well & I noticed something that doesn't make sense to me (it may be because I'm a newbie to networking & PoE but...):

All ports had PoE-Smart enabled.
I accidentally activated PoE on Port 9 when there's nothing connected to Port 9 of the switch, i.e. there's not even a LAN cable physically inserted into Port 9. However, as you can see, apparently the PoE-Smart test was passed on Port 9 (& PoE was activated)? What gives?

All POE Smart does is check for cross shorts, it will turn POE so long as it does not detect cross shorts and having no cable in the port will show all OPENs so POE Smart will turn POE on.

It will also try to determine if you are turning on 24VH to a port that it "thinks" might be a standard 24V device and refuse to turn POE on for that port.

EXAMPLE - Legacy airMAX 10/100 devices will be seen by the switch as:
Pair 1: OK/OPEN/ABNORMAL TERMINATION
Pair 2: OK/OPEN/ABNORMAL TERMINATION
Pair 3: SHORT
Pair 4: SHORT

24VH will fry the Legacy 10/100 device and fry the switch port.

People complained that we were too restrictive with POE Smart and were just turning it OFF so we decided it would be best to only check for things we" KNOW" 100% are wrong and act on those limited issues.

Search for POE Smart on the forums and read the conversations regarding this issue.

[QuadeHale]

Just as a heads up, my switches are having continuous DHCP failures. It's not getting or holding an address. I thought it was just a one-time thing, but it seems like it's not renewing after the lease is up.

[lligetfa]

Just as a heads up, my switches are having continuous DHCP failures...

Have you seen the posts where DS (DHCP Snooping) is causing issues?

[QuadeHale]

No I haven't, links? For the record, I don't have snooping on.
As well, I'm having a super annoying bug, could have been prior to this firmware, but no matter what changes I make, when I go to "Save/Apply" them, there's a window that pops up from the UI saying "Invalid Field". I can't seem to find where I went wrong.
Further, when I went in to the console to try and make changes to SNMP, the snmp-server command demands a port number for community/location/contact, and won't take a string input.
In addition, while in console configuration, accesscontrol asks for what seems like a VLAN number. When I input the proper one, it seems to 'hang' - but really, I can just type in new commands - the <hostname>(config)# just disappears. Not until I type 'exit' does it come back.

[lligetfa]

If you don't have DS selected then providing links is moot.

Sounds like a few gremlins in the config. What browser are you using? I realize that when using the console that browser version should not matter unless the browser previously wrote bad bits into the config.

Would factory defaulting and setting it up again be an option? Maybe sending Eric your config might show up something?