12-17-2009 06:50 PM - edited 03-06-2019 08:59 AM
I have an ESXi vmhost setup to trunk vlans 2, 100 and 101 to a 6509; vlan 2 is working, but neither 100 nor 101 come up. I can't see any reason for one to work and the others not --- the only difference is the vlan id. Native is the default vlan 1 and is not being used.
IOS (tm) c6sup2_rp Software (c6sup2_rp-JK2O3SV-M), Version 12.1(27b)E4, RELEASE SOFTWARE (fc3)
cisco WS-C6509 (R7000) processor (revision 3.0) with 227328K/34816K bytes of memory.
Processor board ID SAL0827BAAS
R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 1024KB L3 Cache
# sho run
...
interface GigabitEthernet5/1
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 2,100-102
switchport mode trunk
...
interface GigabitEthernet5/6
switchport
switchport access vlan 101
switchport mode access
...
#sho int gi5/1 trunk
Port Mode Encapsulation Status Native vlan
Gi5/1 on 802.1q trunking 1
Port Vlans allowed on trunk
Gi5/1 2,100-102
Port Vlans allowed and active in management domain
Gi5/1 2
Port Vlans in spanning tree forwarding state and not pruned
Gi5/1 2
#sho int gi5/1
GigabitEthernet5/1 is up, line protocol is up (connected)
#sho int gi5/6
GigabitEthernet5/6 is up, line protocol is up (connected)
#show int vlan 2
Vlan2 is up, line protocol is up
#show int vlan 101
Vlan101 is up, line protocol is down
Solved! Go to Solution.
12-17-2009 08:45 PM
Do show vlan to double check and if it doesn't exist, do the following
config t
vlan xxx
exit
and confirm it with show vlan
Regards,
jerry
12-17-2009 07:17 PM
Hi Alan,
Usually this happens when you do not have spanning tree instance for that VLAN.
Can you do a:
sh spanning-tree vlan 100 or 102?
HTH
Reza
12-17-2009 08:42 PM
It's true, there's not, but that sounds like a chicken-egg problem. Though, actually, ESXi specifically doesn't do spanning tree because their virtual switches don't talk to each other, preventing loops (according to their docs). Also, vlan2 is working, and I would expect it to have the same problem as the other vlans.
I did try adding:
switchport nonegotiate
spanning-tree portfast trunk
12-17-2009 08:45 PM
Do show vlan to double check and if it doesn't exist, do the following
config t
vlan xxx
exit
and confirm it with show vlan
Regards,
jerry
12-17-2009 09:15 PM
Progress! I had defined the interface to get an ip address for testing, but not the vlan itself:
#sho int gi5/1 trunk
Port Mode Encapsulation Status Native vlan
Gi5/1 on 802.1q trunking 1
Port Vlans allowed on trunk
Gi5/1 2,100-102
Port Vlans allowed and active in management domain
Gi5/1 2,101
Port Vlans in spanning tree forwarding state and not pruned
Gi5/1 2,101
#sho vlan name VLAN0101
VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
101 VLAN0101 active Gi3/7, Gi5/1, Gi5/6
VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
101 enet 100101 1500 - - - - - 0 0
Remote SPAN VLAN
----------------
Disabled
Primary Secondary Type Ports
------- --------- ----------------- ------------------------------------------
# sho run
...
interface Vlan101
description ServerNet NG
ip address 172.20.19.253 255.255.252.0
no ip redirects
hold-queue 2048 in
hold-queue 2048 out
12-18-2009 06:33 AM
Check your native VLAN under ESXi, i think vmware is using something like VLAN0 as native, don't remember that 100%.
Regards,
jerry
12-18-2009 10:05 AM
I don't why the native vlan would matter (assuming it doesn't conflict with a tagged vlan), as I have all the virtual nics in tagged port groups (save for a management lan on a different physical interface).
12-18-2009 11:13 AM
I think VMware uses VLAN 0 for all untagged frames (native vlan) and I believe you have to configure service console port group with VLAN id 0.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: