Netonix Forums

I've got a WS250-B that's unreachable over layer 3, and I think I know why.
I've set the IP and subnet on the VLAN I want as management, and it's reachable over layer 2 (any device can reach it on that same VLAN).
But I can't reach it via Layer 3, through my routers. I think it's because there's no gateway address for the IPs/subnets we put in to the VLAN.

There's no spot for it in the config - can we 'simplify' this and just punch a Management VLAN in to the config? The DNS settings are different on the management VLAN vs my untagged as well, so it's kind of screwing me up.

I don't see an option in the command line to change any of this newer stuff, either. The pile of JSON it spits out with "show config" is a touch difficult to navigate without dropping it in to a "prettifier".

This is not a router it is a Layer 2 switch, the VLAN IP is NOT route-able and must be reached from within the same sub-net within the same layer 2 network.

If you want to access a secondary VLAN IP via a routed network why not just just use the MAIN IP address which is route-able??????

And if you do a "show run" on a cisco you get the same type of output as our "show config".

The whole reason for an IP on the VLANs is so the switch can ping the radio directly that is connected to it without having to go through the router for ping watch dog. Or you can access the UI if you are within the same sub-net and Layer 2 segment.

Why on Earth would you ever want or need multiple route-able IPs, makes no sense to have more then 1 IP address that is route-able to access the UI or CLI.?????

I have a management VLAN. It's 3020.
The IP of the device is 10.39.2.223 - or that's what I would like it to be.
I can't reach it from 10.36.1.100 (my office computer) because I can't put a gateway on that VLAN in the switch.
All other devices have management addresses on 3020, with a gateway of 10.39.2.1 - my router.
I have no way of setting the gateway for the WispSwitch to 10.39.2.1 on VLAN 3020, so far as I can tell.

My untagged traffic is entirely Internet traffic to my clients, and I want to keep it that way.
I am fully against running multiple subnets on the same layer 2 network.

I answered this previously?

sirhc - Sun Feb 15, 2015 5:26 pm
wrote:This is not a router it is a Layer 2 switch, the VLAN IP is NOT route-able and must be reached from within the same sub-net within the same layer 2 network.

sirhc - Sun Feb 15, 2015 5:38 pm
wrote:The whole reason for an IP on the VLANs is so the switch can ping the radio directly that is connected to it without having to go through the router for ping watch dog. Or you can access the UI if you are within the same sub-net and Layer 2 segment.

Those secondary IP's were not meant to be routed, if we had multiple gateways then this would become a router and you would have to create routing tables.

I am not familiar with any Layer 2 Switch that allows multiple IP addresses with multiple default gateways just for accessing the management interface?

As I said the only reason we allowed the secondary IP's inside each VLAN was because people requested the ability for the switch to be able to ping the device (radio) plugged into the port without having to reply on the router to get there so it would not be power cycling radios just because the router is down.

I'm not asking for a gateway, so much as to pick a management VLAN on the device config. the ToughSwitch did it (a radio button beside the VLAN) that let you pick which VLAN the management sat on. That's what I'm after. I don't need multiple default gateways, I need the management of the switch to be on a VLAN other than 1/UT.

QuadeHale wrote:I'm not asking for a gateway, so much as to pick a management VLAN on the device config. the ToughSwitch did it (a radio button beside the VLAN) that let you pick which VLAN the management sat on. That's what I'm after. I don't need multiple default gateways, I need the management of the switch to be on a VLAN other than 1/UT.

And you can with our switch as well?

The "Management or Default" VLAN which by default has an ID of "1" can be changed to whatever VLAN ID value you want between 1 and 4096.

You can also rename it as well from "Management or Default" to whatever you desire?

The Switch' s MAIN IP address resides on the "Default or Management" VLAN, if you renumber this VLAN ID the MAIN IP goes with it which is why the little gear to the right of the description on this VLAN is greyed out and you can NOT disable it.

CLICK ON IMAGE BELOW TO SEE FULL SIZE

When did that become available? When I last checked I couldn't change that VLAN.

sirhc wrote:

QuadeHale wrote:I'm not asking for a gateway, so much as to pick a management VLAN on the device config. the ToughSwitch did it (a radio button beside the VLAN) that let you pick which VLAN the management sat on. That's what I'm after. I don't need multiple default gateways, I need the management of the switch to be on a VLAN other than 1/UT.

And you can with our switch as well?

The "Management or Default" VLAN which by default has an ID of "1" can be changed to whatever VLAN ID value you want between 1 and 4096.

You can also rename it as well from "Management or Default" to whatever you desire?

The Switch' s MAIN IP address resides on the "Default or Management" VLAN, if you renumber this VLAN ID the MAIN IP goes with it which is why the little gear to the right of the description on this VLAN is greyed out and you can NOT disable it.

CLICK ON IMAGE BELOW TO SEE FULL SIZE

default vlan.png

Sorry to resurrect an ancient post, but my issue is somewhat similar.

I have ~15 Wisp-6 switches at remote site(s), we'd like to have a flat management network, and use the switches to take untagged (customer) traffic and bundle it into clusters of VLAN's which will be directed at various gateways.

I'd like to change the management interface from VLAN1 to VLAN64.
I'd need to change the management address to one that our management gateway can route to.

I can't make simultaneous changes to the VLAN tab and the Device>Configuration tab, is there a way to change the VLAN settings and Management address simultaneously? (I've been too scared to touch the CLI).

Any help appreciated,

Cheers,
Liam.

That a reason why I left management untag, so change can be done on management VID. You will probably have to do it locally.