Setting Management Vlan?

[iggy05]

Thanks for adding this. I just got it setup by renaming it on my 24 port I just bought and so far it seems to work. Going to see if I can get this out next week on the network and check to see if I can get to it from the office. Now I can move on to complaining that there is no QnQ yet.

Like what you guys are doing and keep up the good work!

[sirhc]

Thanks! Glad you did not install v1.1.0rc12 - BIG MESS UP

But you should install v1.1.0rc13 which I did test to work fine, but there still maybe a bug in the NTP service which I asked Eric to look into. Some of my switches get the correct time from our NTP server but sometimes a couple fail to acquire the correct time. The bad thing is if the switch fails to get the correct time it will not allow scheduled port bounces to occur, and log entries are not very useful when you do not know the exact time events occurred.

Yes I hear you on QnQ - here are some enhancements we are considering and or working on:
- QnQ
- MSTP
- Granular Flow Control options
Configure Obey and or Generate pause frames per port
Possibly able to configure pause frame duration from the standard 50 micro seconds

However these features will take a back seat to the firmware development needed for the DC switches coming out in about a month.

Also we need to put more development time into the CAP to finish it and get it on the market.

[adairw]

[quote="sirhc"]We are soon releasing a version that allows the following VLAN options

Also
Port isolation ----- <------!!!!!!!! THIS ******

[adairw]

Slightly unrelated - but can you also "auto-enable" the VLAN when you make it?
I've already a dozen times made a new vlan, did all the appropriate tagging/untagging/excluding and forgot to click the "enable" box :(

I agree, I think it should be enabled by default after adding.

[iggy05]

No worries man. Actually the pm you sent on the messup reminded me to check back with you to see where you were at on this so it was a positive for me! I am not totally banging for qnq as of right now. It would just be nice for for one of our customers private connections using airfiber. Currently our core switch is taking care of it but would be nice to move it onto this eventually.

[jready]

What ever happened to Trunking. I had just purchased 8 of the ws-2 250-dc & ws-12-250-dc and low & behold vlan trunking does not work. I can't really use until trunking is working for my backhauls. Also when I change the Management Vlan to 10 I cannot log back in the switch via vlan 10. running 1.3.3

[sirhc]

What ever happened to Trunking. I had just purchased 8 of the ws-2 250-dc & ws-12-250-dc and low & behold vlan trunking does not work. I can't really use until trunking is working for my backhauls. Also when I change the Management Vlan to 10 I cannot log back in the switch via vlan 10. running 1.3.3

Changing the management VLAN to 10 does work, how are you trying to do this?

The management VLAN is the first VLAN in the list (always at the top of the list).
By default the Management VLAN has an ID of 1 with a U on all ports and is expecting Untagged packets but you can change it to VLAN ID 10 if you like.
If you are passing the switch Tagged packets destined to the switch UI/CLI on a port there needs to be a T on that port of the default/management VLAN.

Trunking does work, there is just a bug that can affect you under some circumstances in relationship to the VLAN Matrix.
The bug was reported here: viewtopic.php?f=14&t=1142&p=8508#p8501
Eric addressed that it will be fixed in v1.3.5 here: viewtopic.php?f=14&t=1142&p=8508#p8508

But other than that Trunking does function.

[jready]

I got the Management Vlan working fine. Also loaded 1.3.6. When I use the Trunk Box & list all the Vlans I am still not able to pass these without having to list them in the Matrix also. This is Ok for some locations but for others when there are a lot of Vlans that need to pass through it's kinda impractical to have to list them all in the Maxtrix.

[sirhc]

I got the Management Vlan working fine. Also loaded 1.3.6. When I use the Trunk Box & list all the Vlans I am still not able to pass these without having to list them in the Matrix also. This is Ok for some locations but for others when there are a lot of Vlans that need to pass through it's kinda impractical to have to list them all in the Maxtrix.

We tested the Access List to work?

Oh well give me a couple days and I will test again. Right now were are working on v1.3.7 to better deal with switches that are possibly damaged from surges. Since the new v1.3.5 firmware makes people aware of out of range volts boards that have damaged current sensors can cause false voltage readings so we are adapting the code to better deal with these errors so for the next couple days we will be tied up.

So ping me back late next week if I do not get back to you on this issue to remind me to look at it again.

[jready]

Just check back to see if we are going to have true Vlan trunking without having to list all the Vlans in the Matrix.