v1.2.3 and v1.2.4 FINAL bug reports and comments

[sirhc]

Just does not make any sense because these are all the changes from v1.2.2 to v1.2.4?

You are going to have to dig and figure out what is going on and let us know?

FIXES
- Fixed problem when disabling IP address on VLANs
- Fixed trunking VLAN ports with only the default VLAN configured

ENHANCEMENTS
- Changed default MTU 1528

KNOWN ISSUES
- Ubiquiti Discovery Protocol is still a little flaky

FIXES
- Fixed FALSE Loop Detection with Loop Protection across VLANs

KNOWN ISSUES
- Ubiquiti Discovery Protocol is still a little flaky

[anvilcom]

I agree it doesn't make sense, but that doesn't mean that it can't happen.

I was able to get 1.2.3 and 1.2.4 working by resetting to factory defaults and re-configuring from scratch. I then tried restoring my old config and I got the same problem.

Before I reset the WS-12-250-AC, I did a little more testing. My conclusion is that 1.2.3 and 1.2.4 caused the vlans to malfunction. Here's what I did.

After upgrading from 1.2.2 to 1.2.3 the switch passed absolutely no traffic. I configured my linux box with an alias IP to access the switch on the management VLAN. Ports 1-4 and 12 are on the managment VLAN. 1-4 are untagged and 12 is the trunk. Using the flat network alias ip on 1-4 I was able to access the switch. I was also able to access the switch on port 12, which I shouldn't have been able too without the management VLAN ID.

Reconfigured my linux box with a VLAN interface with the management vlan ID. Connected the cable to port 12 (trunk) and could not access the switch.

I had the same results with 1.2.4

Rolled back to 1.2.2 and tried the trunk port again with my linux box's vlan interface and it worked correctly.

Chris, if you like, I can PM you the config file. Maybe you can replicate?

[sirhc]

I agree it doesn't make sense, but that doesn't mean that it can't happen.

I was able to get 1.2.3 and 1.2.4 working by resetting to factory defaults and re-configuring from scratch. I then tried restoring my old config and I got the same problem.

Before I reset the WS-12-250-AC, I did a little more testing. My conclusion is that 1.2.3 and 1.2.4 caused the vlans to malfunction. Here's what I did.

After upgrading from 1.2.2 to 1.2.3 the switch passed absolutely no traffic. I configured my linux box with an alias IP to access the switch on the management VLAN. Ports 1-4 and 12 are on the managment VLAN. 1-4 are untagged and 12 is the trunk. Using the flat network alias ip on 1-4 I was able to access the switch. I was also able to access the switch on port 12, which I shouldn't have been able too without the management VLAN ID.

Reconfigured my linux box with a VLAN interface with the management vlan ID. Connected the cable to port 12 (trunk) and could not access the switch.

I had the same results with 1.2.4

Rolled back to 1.2.2 and tried the trunk port again with my linux box's vlan interface and it worked correctly.

Chris, if you like, I can PM you the config file. Maybe you can replicate?

You have to forgive me I am FRIED lately trying to do this MSRP price drop, get the DC switches ready to ship as I have to hand build all these first DC units myself.

If I understand you correctly when upgrading from v1.2.2 you hit this issue.
However if you factory default v1.2.3 or v1.2.4 an re-set it back up manually it works fine.
But if you try to import your config from v1.2.2 you have the issue.

So something in your v1.2.2 config does not like the upgrade to v1.2.3 or v1.2.4
But you are now working with v1.2.4 fine since you factory defaulted it - Correct?

If you are working fine then but just want to know what happened (as do I) can you hold on to that config file until end of next week and then email it to me and then call my cell. Late evenings work best for me after close of business day if possible.

[anvilcom]

Yes, you understand it correctly. I'll get back with you end of next week. Thanks.

[nickwhite]

Yes, you understand it correctly. I'll get back with you end of next week. Thanks.

I believe that I may be experiencing the same issue as you. My problem is I didn't have time to troubleshoot it further because the WS-12-250-AC that I put in place was sitting at a high traffic point in our network. I attempted to replace this with another WS-12-250-AC, and uploaded the backed up config from the first one and experienced the same thing. Some VLANs passed, but most did not. I suspect if I upgrade another one, default it, and configure it from scratch, that may fix my issue.

[andy]

well after upgrading to the latest firmware the switch is unusable. i cant even get in to it to down grade. there is a problem with 1.2.4

Andy

[Dave]

Andy

When you say unusable, what do you mean? You can't connect to it??

Dave

[sirhc]

well after upgrading to the latest firmware the switch is unusable. i can't even get in to it to down grade. there is a problem with 1.2.4

Andy

There have been a few reports that when upgrading they had to factory default the switch and then set it back up.

We are not sure what is causing this yet but it is a VERY RARE occurrence, this is the 3rd reported case.

I "think" it has something to do with certain VLAN configurations being mis handled in the upgrade process.

The solution is unfortunately to default the switch and reset back up. Importing the config will cause the same issue.

As soon as Eric has time I plan to work with him on this issue.

HERE IS A POST JUST A COUPLE POSTS UP

I agree it doesn't make sense, but that doesn't mean that it can't happen.

I was able to get 1.2.3 and 1.2.4 working by resetting to factory defaults and re-configuring from scratch. I then tried restoring my old config and I got the same problem.

Before I reset the WS-12-250-AC, I did a little more testing. My conclusion is that 1.2.3 and 1.2.4 caused the vlans to malfunction. Here's what I did.

After upgrading from 1.2.2 to 1.2.3 the switch passed absolutely no traffic. I configured my linux box with an alias IP to access the switch on the management VLAN. Ports 1-4 and 12 are on the managment VLAN. 1-4 are untagged and 12 is the trunk. Using the flat network alias ip on 1-4 I was able to access the switch. I was also able to access the switch on port 12, which I shouldn't have been able too without the management VLAN ID.

Reconfigured my linux box with a VLAN interface with the management vlan ID. Connected the cable to port 12 (trunk) and could not access the switch.

I had the same results with 1.2.4

Rolled back to 1.2.2 and tried the trunk port again with my linux box's vlan interface and it worked correctly.

Chris, if you like, I can PM you the config file. Maybe you can replicate?