cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
831
Views
5
Helpful
2
Replies

Nexus1000v Virtual machine guest tagging (VGT)

davidcheung
Level 1
Level 1

Hi all,

I am going to build a virtual F5 LB which will run on nexus1000v. So i have to use the vthernet trunk interface to support multiple vlans.

"In the nexus1000v configuration guide, i see the following:

The virtual machine interfaces can be either access ports or trunk ports. If a VEthernet interface is set as a trunk port, the VLAN is 4095."

Could you please provide the configuration example for my reference? Do i need to create vlan 4095 before i create the vethernet trunk interface port profile?

BTW, as F5 and Nexus1000v won't do any STP. do i need to configure the vether interface as below on Nexus1000v?

spanning-tree port type edge trunk

switchport mode trunk

Your help is highly appreciated.

1 Accepted Solution

Accepted Solutions

lwatta
Cisco Employee
Cisco Employee

I've never done it but that vlan 4095 bit seems odd. I would think you simply create a veth port-profile with switchport mode trunk and then put the vlans you want on the port with switchport trunk allowed vlan x,x,x,x or all.

The vlan 4095 bit is true for vSwitches but I don't think it has any bearing on N1KV.

I'm thinking you simply do this

n1kv-5-beta(config)# port-profile type veth vm-trunk
n1kv-5-beta(config-port-prof)# switchport mode trunk
n1kv-5-beta(config-port-prof)# switchport trunk allowed vlan all
n1kv-5-beta(config-port-prof)# vmware port-group
n1kv-5-beta(config-port-prof)# no shut
n1kv-5-beta(config-port-prof)# state enabled
n1kv-5-beta(config-port-prof)#

Then assign VM to the port-profile. I'll test it out this morning and let you know if it works.

louis

View solution in original post

2 Replies 2

lwatta
Cisco Employee
Cisco Employee

I've never done it but that vlan 4095 bit seems odd. I would think you simply create a veth port-profile with switchport mode trunk and then put the vlans you want on the port with switchport trunk allowed vlan x,x,x,x or all.

The vlan 4095 bit is true for vSwitches but I don't think it has any bearing on N1KV.

I'm thinking you simply do this

n1kv-5-beta(config)# port-profile type veth vm-trunk
n1kv-5-beta(config-port-prof)# switchport mode trunk
n1kv-5-beta(config-port-prof)# switchport trunk allowed vlan all
n1kv-5-beta(config-port-prof)# vmware port-group
n1kv-5-beta(config-port-prof)# no shut
n1kv-5-beta(config-port-prof)# state enabled
n1kv-5-beta(config-port-prof)#

Then assign VM to the port-profile. I'll test it out this morning and let you know if it works.

louis

Hi Iwatta,

Thank you very much for your reply

As my said:

In the Cisco nexus1000v configuration guide, i see the following:

"The virtual machine interfaces can be either access ports or trunk ports. If a VEthernet interface is set as a trunk port, the VLAN is 4095."

vlan 4095 is reserved vlan.

It is the reason why i ask if the vlan need to be created or not before creating the port profile.

Issue fixed.!!!

Review Cisco Networking for a $25 gift card