Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Nexus 1000v trunk native vlan

Hello,

could you help me with a problem -

I have N1K, mgmt 10.40.1.221 - vlan 1, cntrol/packet int - vlan 3, L2 mode

I configured port-profile for uplink trunk and port-profile for vlan1.

But VM connected via vlan 1 is unaccessible if trunk native vlan is vlan 1.

When I change native vlan then my VM is acceesible.

port-profile system_uplink

type: Ethernet

description:

status: enabled

max-ports: 32

min-ports: 1

inherit:

config attributes:

  switchport mode trunk

  switchport trunk allowed vlan 1-3967,4048-4093

  no shutdown

evaluated config attributes:

  switchport mode trunk

  switchport trunk allowed vlan 1-3967,4048-4093

  no shutdown

assigned interfaces:

  Ethernet3/1

port-group: system_uplink

system vlans: 1,3

capability l3control: no

capability iscsi-multipath: no

capability vxlan: no

capability l3-vservice: no

port-profile role: none

port-binding: static

-------------------------------------------

port-profile vlan1

type: Vethernet

description:

status: enabled

max-ports: 32

min-ports: 32

inherit:

config attributes:

  switchport mode access

  switchport access vlan 1

  no shutdown

evaluated config attributes:

  switchport mode access

  switchport access vlan 1

  no shutdown

assigned interfaces:

  Vethernet2

port-group: vlan1

system vlans: none

capability l3control: no

capability iscsi-multipath: no

capability vxlan: no

capability l3-vservice: no

port-profile role: none

port-binding: static

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Nexus 1000v trunk native vlan

So is the Virtual connect like a passthrough or does it have any configuration?

If it is passthrough, what is the configuration on the Cisco switchport that is connected to it?

Either way, it looks to be a native VLAN mismatch issue. The vSwitch does not do the native VLAN concept. So it is going to forward your VLAN 1 as tagged (and this works). Similarly, when you define any other VLAN as native VLAN on the N1k, VLAN 1 is tagged (and this works).

Thanks,

Shankar

4 REPLIES
Cisco Employee

Nexus 1000v trunk native vlan

Hi Semyon,

What is connected to the ESX host (switch etc)?

What is the configuration on the corresponding switchport?

Only possible reason, that I could think of, for your problem is a native VLAN mismatch. Please make sure that the native VLAN is 1 on the other side also.

Thanks,

Shankar

New Member

Nexus 1000v trunk native vlan

Hi Sprasath,

ESX host is connected to HP Virtual Connector and then to a cisco switch.

When I use VMware vSwitch I don't have problems with vlan 1.

Now my mgmt int of N1K on the VM network of vSwitch works well.

Cisco Employee

Nexus 1000v trunk native vlan

So is the Virtual connect like a passthrough or does it have any configuration?

If it is passthrough, what is the configuration on the Cisco switchport that is connected to it?

Either way, it looks to be a native VLAN mismatch issue. The vSwitch does not do the native VLAN concept. So it is going to forward your VLAN 1 as tagged (and this works). Similarly, when you define any other VLAN as native VLAN on the N1k, VLAN 1 is tagged (and this works).

Thanks,

Shankar

New Member

Nexus 1000v trunk native vlan

You are right.

HP Virtual Connector has profiles for uplink and for servers. And the server profile didn't have vlan 1 as untagged.

Also the information about tagging by vSwitch was unknown for me.

Now it works.

Thanks a lot!

540
Views
0
Helpful
4
Replies
CreatePlease to create content