05-07-2013 10:58 AM - edited 03-01-2019 11:01 AM
I've been looking all over net for help on this one but I can't seem to find anything. We just recently upgraded our UCS Chassis, FI's and Blades from 2.0(1q) to 2.1(1e) and we're receiving an error message on all our provisioned VLAN's. The VLAN's are functioning and passing traffic, but I'd like to try clearing the 900+ warnings. Here's the details of the error:
<faultInst
ack="no"
cause="referenced-vlan-unresolvable"
code="F0933"
created="2013-05-06T18:05:12"
descr="The named vlan QA-VLAN_406 for vNIC VM1 cannot be resolved"
dn="org-root/ls-QA_ESXi-1/ether-VM1/if-QA-VLAN_406/fault-F0933"
<snip>
rule="vnic-ether-if-vlan-unresolvable"
severity="warning"
status="created"
tags=""
type="configuration">
</faultInst>
Any help is greatly appreciated and I thank you in advance.
Solved! Go to Solution.
05-07-2013 11:33 AM
You've removed a VLAN from the system under the "LAN" tab, but there's a vNIC template or service profile template referencing it. We've only just now in 2.1 added a "check" to ensure any VLANs referenced in a vNIC template resolve to an active VLAN.
Find and remove it from the template/policy and it will go away.
Regards,
Robert
05-07-2013 11:33 AM
You've removed a VLAN from the system under the "LAN" tab, but there's a vNIC template or service profile template referencing it. We've only just now in 2.1 added a "check" to ensure any VLANs referenced in a vNIC template resolve to an active VLAN.
Find and remove it from the template/policy and it will go away.
Regards,
Robert
05-07-2013 11:47 AM
Ah ha! I found them. Someone had removed the VLAN's from the Fabric Interconnects but not from the Service Profiles / Templates.
Thank you very much!
05-07-2013 11:49 AM
Anytime Richard. Let us know if you have any other questions!
Cheers,
Robert
06-20-2013 05:00 PM
Hi Robert,
I've done exactly what you suggested and after unbinding the vnic to the template and deleting the VLANs, I will bind the vnic back to the template, but the error comes back. Any ideas or thoughts with this?
Thank you!
Richard C.
06-20-2013 08:58 PM
Nevermind, I found the stale VLANs in the vnic templates, vNIC Interfaces tab. Thanks anyway.
Richard C.
11-14-2013 09:32 AM
Did not want to start another thread, but I will if I need to. I am also experiencing this error:
Error F0933: The named VLAN for vNIC cannot be resolved
However, I have removed the VLAN from the Global VLAN area. I have removed the VLANs from each of the vNIC Templates (A side and B side), but I am using a LAN Connectivity Policy and that policy still sees the deleted VLANs and therefore my ESX servers do as well.
How can I remove these deleted VLANs from the LAN Connectivity Policy?
11-14-2013 10:03 AM
And nvm...i figured it out. It was another bug in the interface it seems. If I went to VNIC Templates and selected the template in question and clicked modify VLANs the VLANS I had deleted were not showing up. However, if you went to vNIC Templates and stayed clicked at the top level then went and looked at the templates in the window to the right.. they still showed up. I deleted them there and voila...gone.
03-20-2017 10:13 PM
Hi,
Does this require a reboot of the server or ay be the complete POD/FI. ?
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