Netonix Forums

Hi All

We have a few switches that have ports showing as disabled and will not change into an enabled state.
Tried disable/enable via Web and CLI.
Upgraded to latest FW and repeated the above.

Some ports have not had anything connected at any point in time and others have had non-PoE devices connected. Trend seems to be non-poe enabled ports though

Found the cause, no VLANs permitted on the port.

Seems odd to me to not bring up a L1 connection without having VLANs, but anyway.

I had the same situation in my firsts day with my netonix. I almost assumed the port was faulty until I tried setting a VLAN assignment to the port.

First switch I encounter that disables the port when not a VLAN member.

Maybe this need to be changed or at least informed in status page (disabled, not vlan member) or anything similar.

bayamon wrote:I had the same situation in my firsts day with my netonix. I almost assumed the port was faulty until I tried setting a VLAN assignment to the port.

First switch I encounter that disables the port when not a VLAN member.

Maybe this need to be changed or at least informed in status page (disabled, not vlan member) or anything similar.

If a port is not assigned to a VLAN then what should the switch do with the traffic?

We do put up a big "X" in the switch graphics (Christmas tree) which means disabled which should make you look as to why. I think the mouse over balloon tells you why but I could be wrong. I could see about having that added if it is not.

Some switches use a generic ingress filter on their switches so they appear to work even when set up wrong so people do not contact support.

Sort of like when you used to by a WRT-54G from Best Buy and people plugged it into their cable modem and it just worked because by default the security was disabled and it was set to channel 6 at full power.

We setup the VLAN ingress filters specifically as you specified so it you set it up wrong it does not work but when it is working you "know" the packets are going where they are told to go and nowhere else.

Our other option would be to set the ingress filters on all port to accept any packet Tagged or Untagged and fall back on the layer 2 switching fabric to decide where to send packets but does this not defeat the whole purpose of using VLANs so traffic only goes where it is specified to go? (segregated traffic)

Personally I would prefer the switch to only do what I tell it to do otherwise you may think you are segregating traffic and you really are NOT.

Now that I do know how netonix work I dont have a problem with it.

But I did have a problem with it in the beggining because is the only switch that I know that physically disables the port when not a VLAN member.

For me is not a problem anymore. Is more a suggestion to you because if you sell millions of your great switches and a small percentage of people have this confusion you will have a support nightmare.