v1.2.2 FINAL bug reports and comments

[sirhc]

I guess what he was referring to was the remote syslog.

Ah, good point!

I will discuss it with the programmer (Eric)

Thanks for passing it along!

[nickwhite]

I think I found a bug with the alias IP addresses on VLANs.

I have a WS-12-250-AC that is not removing the IP address when I remove it from a VLAN and Save/Apply. If I login via SSH I am still seeing the subinterfaces under "ifconfig." Additionally, if I change something else in the GUI and hit Save/Apply, the VLAN IP addresses come back even though they are not enabled in the GUI.

[nickwhite]

I think I found a bug with the alias IP addresses on VLANs.

I have a WS-12-250-AC that is not removing the IP address when I remove it from a VLAN and Save/Apply. If I login via SSH I am still seeing the subinterfaces under "ifconfig." Additionally, if I change something else in the GUI and hit Save/Apply, the VLAN IP addresses come back even though they are not enabled in the GUI.

\

I'm still troubleshooting, but I may simply have a bad switch... I tried adding a new VLAN IP and lost access to the switch... can still ping on the management IP, but can't get to HTTPS or SSH. It was also not passing some VLANs through it, until I added a VLAN IP and then removed... Finally had to pull a throw a TS back in.

FYI, this was happening on 1.3.0rc9 as well.

Going to test this out on a different switch now...

[sirhc]

This is not a type of problem that would be hardware related but rather firmware.
So if you think you have found a bug you need to provide a config and a do this and this and this happens so we can recreate what you see.

IMPORTANT - We have also been discussing that if you are doing anything with VLANs you NEED to have the MTU set to at least 1522

We are changing the default MTU in the next firmware to 1522 instead of 1518 which is NOT large enough if you are passing VLAN Tags out any ports.

We know we have these issues discussed in other threads:
Trunking does not work properly unless a second VLAN is defined.
Work around is to just create a second VLAN even if it does nothing

Loop Protection can provide false positives under some configuration.
Work around is to just disable it under Device Config

These issues will be addressed in a firmware release soon.

[nickwhite]

Thanks Chris.

Where do you want me to send the configs?

I just tested the VLAN IP issue on a different switch, VLAN 115 in this case, running 1.3.0rc9, and disabling a VLAN IP didn't actually remove it/shutdown the subinterface on that one either. I set the Address field to "Address" and Netmask field to "Netmask", fields turned red obviously, I hit OK, then Saved and it appears that worked... very odd. The red box warning around those fields is visual only, it doesn't appear to actually prevent you from putting bad data in a field. So I then erased the Address and Netmask fields, left Enabled unchecked, and Saved - this would appear to be the workaround for now (not that we'll be adding and removing a ton of IPs from VLANs...). But this still doesn't remove the eth0.115 subinterface - it's still there and up, it just doesn't have an IP address on it any longer.

The web and SSH access issue I'm stumped on, but as soon as my techs get the switch back to the shop I can troubleshoot further.

I'm wondering if the issue we saw with VLANs not passing (unless I added an IP to the VLAN) was somehow related to Loop Protection... Hmm.

I had about 20 VLANs loaded on the switch that we pulled, so I don't think this is the Trunking bug you referred. We run these at 1600, so MTU wouldn't appear to be an issue either.

[sirhc]

As far as your explanation of the trouble you had when you remove an IP addresses from the VLAN, that is pretty easy for Eric to fix.

I think you are also saying that if you have an IP address on a VLAN then disable or delete the VLAN that the secondary IP and the sub interface remains?

Yes I have pleaded and pleaded to make input fields more intelligent to limit users to only valid inputs but.....

Josh Reynolds has also said he has issues with VLANs no passing traffic until he adds an IP to it but I am not sure where Eric is with him on this as Eric asked him if he could
work with him maybe TeamViewer into his computer with him and have Josh demonstrate this but Josh has not responded to my knowledge.

Basically describe the VLAN issue and config here on the forums or pm them to Eric.

You did not answer me if your MTU was set to 1522 or higher.

[Eric Stern]

But this still doesn't remove the eth0.115 subinterface - it's still there and up, it just doesn't have an IP address on it any longer.

This is normal. That interface will disappear after the next reboot, in the meantime it has no address and therefore has no effect on the operation of the switch.

[nickwhite]

As far as your explanation of the trouble you had when you remove an IP addresses from the VLAN, that is pretty easy for Eric to fix.

I think you are also saying that if you have an IP address on a VLAN then disable or delete the VLAN that the secondary IP and the sub interface remains?

Correct.

Yes I have pleaded and pleaded to make input fields more intelligent to limit users to only valid inputs but.....

Josh Reynolds has also said he has issues with VLANs no passing traffic until he adds an IP to it but I am not sure where Eric is with him on this as Eric asked him if he could
work with him maybe TeamViewer into his computer with him and have Josh demonstrate this but Josh has not responded to my knowledge.

Basically describe the VLAN issue and config here on the forums or pm them to Eric.

Ok, thanks. I'll be curious to see if what Josh is experiencing is the same as us. It sounds similar. The odd thing is we have dozens of these in the field, and this is the first one I've experienced this issue on. I'll do a more detailed write up and take some screenshots.

You did not answer me if your MTU was set to 1522 or higher.

Yes, we run MTU at 1600.

[nickwhite]

But this still doesn't remove the eth0.115 subinterface - it's still there and up, it just doesn't have an IP address on it any longer.

This is normal. That interface will disappear after the next reboot, in the meantime it has no address and therefore has no effect on the operation of the switch.

Except when you just disable the VLAN IP address... the interface and IP stays.