Unable to ping my switch when i am on ipstatic.

[AGH]

Hello 

There's something I don't understand about the Meraki VLAN functionality.

I have a Cisco Catalyst 9200 switch that correctly appears in the Meraki dashboard when it's using DHCP in VLAN 1 because its uplink port is natively configured as VLAN 1 and tagged for all VLANs.

The uplink switch on the other side is untagged as VLAN 150, so the 9200 receives an IP address in VLAN 150.

However, when I want my switch to have a static IP address in management VLAN 150, I configure a static IP address in the correct range and set the VLAN to 150. The uplink switch on the other side is configured as natively configured as VLAN 1 and tagged as VLAN 150.n

My port on the 9200 is also natively configured as VLAN 1 and tagged for all VLANs.

As soon as I do that I lose ping to my 9200 switch, it stops responding on VLAN 150... I don't understand why.

I resume

Switch cisco 9200 / port uplink 2 / native vlan 1 / tagged all vlans.
Switch alcatel other side / port uplink 2 / Native vlan 1 / tagged all vlans.
Switch cisco 9200 / ip static vlan 150 + add vlan 150 on the configuration ip --> I loose the ping

Any idea ? Maybe there's something I'm doing wrong with Meraki

[alemabrahao]

I should need to change the native VLAN to 150.

https://community.cisco.com/t5/switching/purpose-of-the-native-vlan-in-modern-networks/td-p/5198400

[AGH]

Thanks but i am not sur that change native vlan is a good idea. You have to be on the same vlan both side. 

[alemabrahao]

Yes, but that's what I'm talking about, to define the native VLAN with the 150 on both switches.

[RWelch]

Under Dashboard > Switching > Configure > Switch settings you might check to see if you have the right VLAN (if you move away from VLAN 1).

 

Also, ensure that the native VLAN and allowed VLAN lists on both ends of trunks are identical. Mismatched native VLANs on either end can result in bridged traffic.

General MS Best Practices 

[AGH]

Thanks for your reply

I'm having trouble understanding the usefulness of this vlan management in Dashboard > Switching > Configure > Switch settings

if I have several switches in several buildings which simply do not have the same management vlan?

The document says "Assigning a static IP address and/or VLAN to a switch will override management VLAN settings configured on this page."

the documentation also states: If your network does not allow the native VLAN or any of the default VLANs to DHCP or connect to the internet, you will need to manually assign a management VLAN.
To do this, place the switch on a network running DHCP, then from dashboard navigate to Monitor >> Switches and select the target switch. From the details page, choose "Set IP Address" and save your changes.

ensure that the native VLAN and allowed VLAN lists on both ends of trunks are identical --> of course all vlan are identical both side

Thanks

[RWelch]

Perhaps a support case will help you better understand with a tech explaining, they can also see any mis-configurations that contribute to the issues you are experiencing.  Best of luck.

> if I have several switches in several buildings which simply do not have the same management vlan?
This could be problematic if you have many different management VLANs.  I would probably re-think this from a network wide scope.

[PhilipDAth]

Can you run DHCP on VLAN150 for a while?

I'd be tempted just to get it correctly using that VLAN via a tag first, since the current approach is not working, and then move it to a static IP.

[AGH]

I am receiving an IP address in my VLAN 150 because my switch on the other end is on access VLAN 150. But it's not a clean setup and it's not the architecture I want.

To be honest, I didn't expect it to be this difficult to configure a simple management VLAN.

[PhilipDAth]

It shouldn't be that difficult.  🙂

[PhilipDAth]

Can you get it to work using DHCP when using DHCP and VLAN trunking (and then go to the static IP address).

[AGH]

I will try tomorow, because now I'm remote and I've lost control of the switch.

What's strange is that this is normally how tagged and untagged VLANs work.

All my uplink ports across my entire network are configured the same way: native trunk VLAN 1, tagged VLAN 150.

On all switches (that aren't Meraki), I have a VLAN 150 interface configured with a static IP address, and everything works perfectly.

I only have this problem with my 9200 switch running Meraki.

As far as I'm concerned, I'm adding a switch to my network, so I shouldn't be touching the existing uplinks.

From what I understand, the VLAN management menu in the dashboard isn't relevant here because I'm using a static IP address.

There's definitely something I'm missing.

As soon as I assign it a static IP address with VLAN 150, I can no longer ping it. Even if I modify the uplink on other side in 1000 possible ways, it's not clear.

[RWelch]

One thing you also mentioned - worth looking into a bit more thorough is the following:

> Switch cisco 9200 / port uplink 2 / native vlan 1 / tagged all vlans.

The 9200 series supports a maximum of 512 VLANs per stand-alone switch or switch stack. By default, VLAN IDs 1-512 are configured, but you can modify the active VLANs via the local status page or dashboard.

If you attempt to allow more than 512 VLANs, the switch will not support it, and you may encounter configuration errors.

For management and other features, ensure that any VLANs used fall within the active VLAN range.

Catalyst 9200L-M Series Installation Guide (section: Assigning an IP Address).

[AGH]

I am aware of this limitation but I only have a few VLANs, not many.