cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
88
Views
0
Helpful
1
Replies
Highlighted
Beginner

Changing native VLAN causes vms to no longer be able to talk

I have a Cisco 3850, and everything between my two vlans is just happy with ports being trunk and having a vlan of 30 with a native VLAN of 1. Inter VM communication stops working if I change the native VLAN to 30. I have the vswitch in esxi properly tagged as 30 as well.

But if I don't change the native VLAN, the Cisco that I'm trying to add to the network complains about a mismatched native VLAN on my original switch.

I'm newish to networking so I'm just kind of at a loss as to why this is being difficult

edit: Changed duplicate to mismatched.

1 REPLY 1
Enthusiast

Re: Changing native VLAN causes vms to no longer be able to talk

Hi

In cisco, native vlan means that the native vlan is untagged, and also by default this is vlan1, and this is per interface, so you can have different native vlans on different interfaces. If you change the native vlan from 1 to 30, means that on this interface vlan 30 is now untagged, and that will not match your VM.

For your new switch if you are doing a trunk port between them the native vlan should be the same, otherwise you got the mismatch.

If you are connecting two switches together with ports in access-mode, then you will get mismatch if the ports are on different vlans.

There may be situations where you are forced to have different native vlans, and in that case you can disable cdp on the interface, because it is the cdp protocol that warns about the native mismatch.

 

There are also a possibility to force the switch to tag the native vlan, but that is a global command, so it will take effect for all ports on the switch.

/Mikael

CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards