Management Vlan

[allantinker]

Im having an issue with the Management Vlan on the Netonix switches. Im trying to change the vlan ID of the management vlan, and its working, and my other vlan is passing traffic. I just loose access to the switch. Posting details below.

Equipment involved:
Cisco 7200 VXR Router
Cisco ME Switch
Netonix WS-24-400A with firmware 1.4.6

Right now I am untagging the vlan on the ME switch to the netonix, so it sees it as untagged traffic. Id like to tag it all the way to the netonix.

Set up of the Router involves 2 vlans for this setup. I have vlan 16 for traffic going to the switch, and Im trying to use vlan 280 for management.

I tried setting the "trunk" port on the management vlan to U and T. But neither of these configurations worked.

Before I hit save and apply, I set the IP address on the switch to an IP that falls into the interface tagged on 280 on the Router, and I switch the Access port on the ME switch to a trunk port, allowing both Vlans 16 and 280. When I do this, I only loose access to the Netonix switch, but everything on vlan 16 still works.

And If I click on the trunk port checkbox in the switch I loose everything. Ive got to be doing something wrong here...


Any ideas?

Thank You!

[Julian]

Can't see any of your images, so am having a devil of a time following what you're saying, here.

VLAN 280 is your management vlan, and up at the top of the vlan list on your vlan tab? the port you are looking for has a T in it?

VLAN 16 comes in on the same port, untagged?

Definitely need to see at least your vlan tab, prefer the device status tab as well. Take a capture in the working configuration, and annotate the modification that breaks it?

Thanks,

Julian

[allantinker]

Oh, those didnt upload very well did they... Whats the best way to upload images to the board (noob question I know)

Both vlans come in on the same port. Then Im basically un tagging every port on 16 except the trunk port.
Then changing the top vlan to 280.

[Julian]

below the 3 blue buttons that say save draft, preview, and submit, there's a grey bar that says options, with 'upload attachment' next to it, see picture

once you're done, you can scroll down and hit the 'place inline' button if you want the attachment displayed near a particular body of text.

[allantinker]

Im blind... Lol.

[Julian]

so which one of those works?

[allantinker]

Both setups work for the 16 vlan traffic. But I loose management access to the netonix..

Is the correct setup normally to T the trunk port on the MGNT Vlan? or to untag it?

[sirhc]

By the way you should be running v1.4.7rc14

We are not like other vendors and I am thinking of doing away with the RC designation all together.

If we release v1.4.7 FINAL today and tomorrow someone found a bug we would immediately release v1.4.8rc1

So if you are using v1.4.6 and not v1.4.7rc14 then all the bugs reported and fixed since then are still in the v1.4.6 you are running.

I think we will do away with RC designations in the future as people are so reluctant to use any RC versions and simply increment by a decimal value.

[sirhc]

So with this VLAN configuration one could ONLY talk to the switch through port 26 with Untagged packets.
Port 26 would only accept VLAN Tagged packets with an ID of 16 and Untagged Packets, all other packets would be refused or dropped.
Untagged packets coming in Port 26 would only go to the switch UI/CLI.
All Packets Tagged with VLAN ID 16 entering Port 26 would exit ports 1-25 as Untagged packets.

With this VLAN configuration one could ONLY talk to the switch through port 26 with Tagged packets with a VLAN ID of 280
Port 26 would only accept VLAN packets with IDs of 16 and 280, all other packets would be refused or dropped.
Ports 1-25 will only accept Untagged packets, all others would be refused or dropped.
Packet coming in port 26 and out Ports 1-25 would have the VLAN ID Tag 16 stripped off and exit as Untagged packets.
Untagged packets coming in Ports 1-25 and exiting Port 26 would be encapsulated with VLAN ID Tag 16.

[allantinker]

So the second configuration would be correct. I need to be able to access the switch through port 26, also the trunk port. I tried this setup but I failed to gain access to the switch..

But everything tagged on vlan 16 worked... Just no management access. There isnt like a native vlan setting somewhere Im missing is there?