Problem with tagged management after 1.2.0 to 1.3.2 upgrade

[mayheart]

I'm having problems with tagged management with upgrading from 1.2.3 to 1.3.2.

After the switch reboots, I can no longer access the devices without having native vlan enabled on the switch facing it.

I can provide access if needed.

[sirhc]

Can you post up your VLAN Tab first.

Also if there is a VLAN access list assigned to any ports (Port Trunking) or a secondary IP assigned to any VLANs.

[mayheart]

I EDITED YOUR POST TO INCLUDE THE IMAGE. YOU CAN UPLOAD JPG GRAPHICS WITH THE LINK BELOW THE SUBMIT BUTTON

Untitled.jpg (22.67 KiB) Viewed 4136 times

I have no secondary IPs enabled.

After the switch reboots, I can no longer access the devices without having native vlan enabled on the switch facing it.

[sirhc]

After the switch reboots, I can no longer access the devices without having native vlan enabled on the switch facing it.

What is the switch facing it?

Does port 8 goto a router or another switch across a wireless bridge, and if a wireless bridge what kind?
I know this would be a pain but I vaguely remember someone else talking about this issue and they said they factory defaulted the switch then manually set it back up and it worked.
I know it would be a pain but would you be willing to go out during off peak times and default this and manually set it back up? If that fixed it that would tell us something.

[sirhc]

Actually I just talked to Eric.

This is a bug and is Fixed in v1.3.3rc5 which I will be posting shortly after I install it on a few of my switches as a sanity check.

(1) RF Armor warehouse switch
(3) Switches at my WISP NOC
(2) Live Towers

[mayheart]

Actually I just talked to Eric.

This is a bug and is Fixed in v1.3.3rc5 which I will be posting shortly after I install it on a few of my switches as a sanity check.

(1) RF Armor warehouse switch
(3) Switches at my WISP NOC
(2) Live Towers

Thanks for the update. I will test it on rc5 when it's released.

I have another 1.2.3 switch to upgrade so I'll wait on that and report back as well.

What is the switch facing it?

Does port 8 goto a router or another switch across a wireless bridge, and if a wireless bridge what kind?
I know this would be a pain but I vaguely remember someone else talking about this issue and they said they factory defaulted the switch then manually set it back up and it worked.
I know it would be a pain but would you be willing to go out during off peak times and default this and manually set it back up? If that fixed it that would tell us something.

It's plugged into a Cisco 3750G switch just for your data.

[cbl]

I saw this as well going to 1.3.2 on a couple of switches. The problem is that the management traffic coming into the Cisco was "UNTAGGED" after upgrade even though on the Netonix it's marked as TAGGED on a trunk port . It came through tagged correctly prior to the upgrade. My quick fix is to set the native vlan on the cisco to the mgmt vlan ID, or downgrade.

[mayheart]

Thanks sirhc for the fast firmware turnaround.

I upgraded that 1.3.2 switch to 1.3.3rc5, tagged management is working again.

1.2.3 to 1.3.3rc5 was also successful without any problems.