No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


New VMs cannot get IP

Publication Date:  2013-12-28 Views:  493 Downloads:  0

Issue Description

Customer has a DVS for the servers (Fusion Access) it are in the vlan 1, and it is working (there is a PortGroup). But for VM customer has to use vlan 16, 17 and 18, he created a new PortGroup for vlan 16, but the VM doesn´t get an IP.

Alarm Information


Handling Process

Change switch configuration to :


interface GigabitEthernet0/0/2

port hybrid tagged vlan 16 to 18



interface GigabitEthernet0/0/2

port link-type trunk

port trunk allow pass 16 to 18.

Root Cause

Checked the DHCP server, DHCP relay. They are all good. When checked the switch configuration, we found the switches ports configuration that connects each Host is like this


interface GigabitEthernet0/0/2

port hybrid untagged vlan 16 to 18

The switch port connects each host should be considered as the port connected to DVS link-up port. The ports between two switch should only allow tagged frame pass-by. So customer’s configuration is not correct.