07-29-2015 03:43 AM
Hi all,
we have configured Nexus1000V with layer3 capability.
I have created a port-profile as follows:
port-profile type vethernet Vlan135
switchport mode access
switchport access vlan 135
no shutdown
capability l3control
system vlan 135
state enabled
vmware port-group
vlan 135 is also configured as a system vlan, on my uplink port-profile and the svs-domain is configured as:
svs-domain
domain id 6
control vlan 1
packet vlan 1
svs mode L3 interface mgmt0
switch-guid 6601da9c-6a20-43cd-91b6-8e0b16fc0d9d
no enable l3sec
Every time there is a VSM switchover, I get the following message:
VEM_MGR-SLOT4-1-VEM_SYSLOG_ALERT: sfswitchdata : L3 Control and System VLAN configurations not applied
on vethernet port. VMware Port[50331760] DVPortGroup[dvportgroup-90]. L3 Control can be applied only on VMKernel port.
What could be the problem?
Thanks in advance,
Katerina
Solved! Go to Solution.
07-29-2015 12:50 PM
Is likely that you are using the port-profile "Vlan135" on a VM... the "capability l3control" is for the VMKernel on the host, only...hence the error.
-Kenny
07-29-2015 12:50 PM
Is likely that you are using the port-profile "Vlan135" on a VM... the "capability l3control" is for the VMKernel on the host, only...hence the error.
-Kenny
07-29-2015 11:46 PM
Hi Keny,
I created another port-profile for vlan135, without layer3 control capability. I then assigned all vms which should belong to vlan135, to the new port-profile and that resolved the issue.
Found these links really helpful:
https://communities.cisco.com/docs/DOC-28631
https://supportforums.cisco.com/document/12167596/nexus-1000v-vem-ports-blocking-state-after-reboot-esx-host
Thanks!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide