<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic NIC not reading correct status in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/NIC-not-reading-correct-status/m-p/2993041#M290843</link>
    <description>&lt;P&gt;I am trying to figure out why the ESXI is not getting the correct status of the NIC uptime state. We had issues with MAC Address flapping and it seemed to be pointing towards our esxi server with the NIC Teaming. I had to rip out the other nic uplinks from the vSwitch so the flapping would stop and the traffic would flow normally.&lt;/P&gt;&lt;P&gt;Anyhow I went to disable the nic uplink and when i went to check the physical nic status it still showing as a up status in esxi but when i check the vbdo logs it does show the link status is off&lt;/P&gt;&lt;P&gt;2023-10-27T10:07:04.294Z: [netCorrelator] 91045838868663us: [vob.net.vmnic.linkstate.up] vmnic vmnic6 linkstate up&lt;BR /&gt;2023-10-27T10:07:04.395Z: [netCorrelator] 91045838968767us: [vob.net.pg.uplink.transition.up] Uplink:vmnic6 is up. Affected portgroup: UC&amp;nbsp; Port Group. 2 uplinks up&lt;BR /&gt;2023-10-27T10:07:06.002Z: [netCorrelator] 91045840566797us: [esx.clear.net.redundancy.restored] Uplink redundancy restored on virtual switch "UC-Switch", portgroups: "UC&amp;nbsp; Port Group". Physical NIC vmnic6 is up&lt;BR /&gt;2023-10-27T10:07:15.174Z: [netCorrelator] 91045849748598us: [vob.net.vmnic.linkstate.down] vmnic vmnic4 linkstate down&lt;BR /&gt;2023-10-27T10:07:15.776Z: [netCorrelator] 91045850350523us: [vob.net.pg.uplink.transition.down] Uplink: vmnic6 is down. Affected portgroup: UC&amp;nbsp; Port Group. 1 uplinks up. Failed criteria: 128&lt;BR /&gt;2023-10-27T10:07:15.776Z: [netCorrelator] 91045850350786us: [vob.net.vmnic.linkstate.down] vmnic vmnic6 linkstate down&lt;BR /&gt;2023-10-27T10:07:16.002Z: [netCorrelator] 91045850566733us: [esx.problem.net.vmnic.linkstate.down] Physical NIC vmnic4 linkstate is down&lt;BR /&gt;2023-10-27T10:07:17.002Z: [netCorrelator] 91045851566815us: [esx.problem.net.redundancy.lost] Lost uplink redundancy on virtual switch "UC-Switch". Physical NIC vmnic6 is down. Affected port groups: "UC Port Group"&lt;BR /&gt;2023-10-27T10:07:17.647Z: [netCorrelator] 91045852221708us: [vob.net.vmnic.linkstate.up] vmnic vmnic4 linkstate up&lt;BR /&gt;2023-10-27T10:07:18.000Z: [netCorrelator] 91045852564927us: [esx.clear.net.vmnic.linkstate.up] Physical NIC vmnic4 linkstate is up&lt;BR /&gt;2023-10-27T10:07:18.247Z: [netCorrelator] 91045852821908us: [vob.net.vmnic.linkstate.up] vmnic vmnic6 linkstate up&lt;BR /&gt;2023-10-27T10:07:18.350Z: [netCorrelator] 91045852923905us: [vob.net.pg.uplink.transition.up] Uplink:vmnic6 is up. Affected portgroup: UC Port Group. 2 uplinks up&lt;BR /&gt;2023-10-27T10:07:20.002Z: [netCorrelator] 91045854566872us: [esx.clear.net.redundancy.restored] Uplink redundancy restored on virtual switch "UC-Switch", portgroups: "UC Port Group". Physical NIC vmnic6 is up&lt;BR /&gt;2023-10-27T10:15:44.291Z: [netCorrelator] 91046358865634us: [vob.net.pg.uplink.transition.down] Uplink: vmnic6 is down. Affected portgroup: UC Port Group. 1 uplinks up. Failed criteria: 128&lt;BR /&gt;2023-10-27T10:15:44.292Z: [netCorrelator] 91046358866706us: [vob.net.pg.uplink.transition.up] Uplink:vmnic8 is up. Affected portgroup: UC&amp;nbsp; Port Group. 1 uplinks up&lt;BR /&gt;2023-10-27T10:15:44.315Z: [netCorrelator] 91046358889140us: [vob.net.pg.uplink.transition.up] Uplink:vmnic8 is up. Affected portgroup: UC Port Group. 1 uplinks up&lt;BR /&gt;2023-10-27T10:15:46.002Z: [netCorrelator] 91046360566875us: [esx.problem.net.redundancy.lost] Lost uplink redundancy on virtual switch "UC-Switch". Physical NIC vmnic6 is down. Affected port groups: "UC Port Group"&lt;BR /&gt;2023-10-27T10:15:46.002Z: [netCorrelator] 91046360567141us: [esx.clear.net.connectivity.restored] Network connectivity restored on virtual switch "UC-Switch", portgroups: "UC&amp;nbsp; Port Group", "UC Port Group". Physical NIC&lt;BR /&gt;2023-10-27T11:49:48.523Z: [netCorrelator] 91052003097282us: [vob.net.vmnic.linkstate.down] vmnic vmnic6 linkstate down&lt;BR /&gt;2023-10-27T11:49:49.002Z: [netCorrelator] 91052003566762us: [esx.problem.net.vmnic.linkstate.down] Physical NIC vmnic6 linkstate is down&lt;BR /&gt;2023-10-27T11:49:51.015Z: [netCorrelator] 91052005589152us: [vob.net.vmnic.linkstate.up] vmnic vmnic6 linkstate up&lt;BR /&gt;2023-10-27T11:49:52.002Z: [netCorrelator] 91052006566713us: [esx.clear.net.vmnic.linkstate.up] Physical NIC vmnic6 linkstate is up&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I noticed that even when turning off the nic it ended with linkstate up. Even though that is not true at all. I am hopping someone can point me in the right direction so I can renable failover on the vSwitch&lt;/P&gt;</description>
    <pubDate>Fri, 27 Oct 2023 13:36:13 GMT</pubDate>
    <dc:creator>rtarson98</dc:creator>
    <dc:date>2023-10-27T13:36:13Z</dc:date>
    <item>
      <title>NIC not reading correct status</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/NIC-not-reading-correct-status/m-p/2993041#M290843</link>
      <description>&lt;P&gt;I am trying to figure out why the ESXI is not getting the correct status of the NIC uptime state. We had issues with MAC Address flapping and it seemed to be pointing towards our esxi server with the NIC Teaming. I had to rip out the other nic uplinks from the vSwitch so the flapping would stop and the traffic would flow normally.&lt;/P&gt;&lt;P&gt;Anyhow I went to disable the nic uplink and when i went to check the physical nic status it still showing as a up status in esxi but when i check the vbdo logs it does show the link status is off&lt;/P&gt;&lt;P&gt;2023-10-27T10:07:04.294Z: [netCorrelator] 91045838868663us: [vob.net.vmnic.linkstate.up] vmnic vmnic6 linkstate up&lt;BR /&gt;2023-10-27T10:07:04.395Z: [netCorrelator] 91045838968767us: [vob.net.pg.uplink.transition.up] Uplink:vmnic6 is up. Affected portgroup: UC&amp;nbsp; Port Group. 2 uplinks up&lt;BR /&gt;2023-10-27T10:07:06.002Z: [netCorrelator] 91045840566797us: [esx.clear.net.redundancy.restored] Uplink redundancy restored on virtual switch "UC-Switch", portgroups: "UC&amp;nbsp; Port Group". Physical NIC vmnic6 is up&lt;BR /&gt;2023-10-27T10:07:15.174Z: [netCorrelator] 91045849748598us: [vob.net.vmnic.linkstate.down] vmnic vmnic4 linkstate down&lt;BR /&gt;2023-10-27T10:07:15.776Z: [netCorrelator] 91045850350523us: [vob.net.pg.uplink.transition.down] Uplink: vmnic6 is down. Affected portgroup: UC&amp;nbsp; Port Group. 1 uplinks up. Failed criteria: 128&lt;BR /&gt;2023-10-27T10:07:15.776Z: [netCorrelator] 91045850350786us: [vob.net.vmnic.linkstate.down] vmnic vmnic6 linkstate down&lt;BR /&gt;2023-10-27T10:07:16.002Z: [netCorrelator] 91045850566733us: [esx.problem.net.vmnic.linkstate.down] Physical NIC vmnic4 linkstate is down&lt;BR /&gt;2023-10-27T10:07:17.002Z: [netCorrelator] 91045851566815us: [esx.problem.net.redundancy.lost] Lost uplink redundancy on virtual switch "UC-Switch". Physical NIC vmnic6 is down. Affected port groups: "UC Port Group"&lt;BR /&gt;2023-10-27T10:07:17.647Z: [netCorrelator] 91045852221708us: [vob.net.vmnic.linkstate.up] vmnic vmnic4 linkstate up&lt;BR /&gt;2023-10-27T10:07:18.000Z: [netCorrelator] 91045852564927us: [esx.clear.net.vmnic.linkstate.up] Physical NIC vmnic4 linkstate is up&lt;BR /&gt;2023-10-27T10:07:18.247Z: [netCorrelator] 91045852821908us: [vob.net.vmnic.linkstate.up] vmnic vmnic6 linkstate up&lt;BR /&gt;2023-10-27T10:07:18.350Z: [netCorrelator] 91045852923905us: [vob.net.pg.uplink.transition.up] Uplink:vmnic6 is up. Affected portgroup: UC Port Group. 2 uplinks up&lt;BR /&gt;2023-10-27T10:07:20.002Z: [netCorrelator] 91045854566872us: [esx.clear.net.redundancy.restored] Uplink redundancy restored on virtual switch "UC-Switch", portgroups: "UC Port Group". Physical NIC vmnic6 is up&lt;BR /&gt;2023-10-27T10:15:44.291Z: [netCorrelator] 91046358865634us: [vob.net.pg.uplink.transition.down] Uplink: vmnic6 is down. Affected portgroup: UC Port Group. 1 uplinks up. Failed criteria: 128&lt;BR /&gt;2023-10-27T10:15:44.292Z: [netCorrelator] 91046358866706us: [vob.net.pg.uplink.transition.up] Uplink:vmnic8 is up. Affected portgroup: UC&amp;nbsp; Port Group. 1 uplinks up&lt;BR /&gt;2023-10-27T10:15:44.315Z: [netCorrelator] 91046358889140us: [vob.net.pg.uplink.transition.up] Uplink:vmnic8 is up. Affected portgroup: UC Port Group. 1 uplinks up&lt;BR /&gt;2023-10-27T10:15:46.002Z: [netCorrelator] 91046360566875us: [esx.problem.net.redundancy.lost] Lost uplink redundancy on virtual switch "UC-Switch". Physical NIC vmnic6 is down. Affected port groups: "UC Port Group"&lt;BR /&gt;2023-10-27T10:15:46.002Z: [netCorrelator] 91046360567141us: [esx.clear.net.connectivity.restored] Network connectivity restored on virtual switch "UC-Switch", portgroups: "UC&amp;nbsp; Port Group", "UC Port Group". Physical NIC&lt;BR /&gt;2023-10-27T11:49:48.523Z: [netCorrelator] 91052003097282us: [vob.net.vmnic.linkstate.down] vmnic vmnic6 linkstate down&lt;BR /&gt;2023-10-27T11:49:49.002Z: [netCorrelator] 91052003566762us: [esx.problem.net.vmnic.linkstate.down] Physical NIC vmnic6 linkstate is down&lt;BR /&gt;2023-10-27T11:49:51.015Z: [netCorrelator] 91052005589152us: [vob.net.vmnic.linkstate.up] vmnic vmnic6 linkstate up&lt;BR /&gt;2023-10-27T11:49:52.002Z: [netCorrelator] 91052006566713us: [esx.clear.net.vmnic.linkstate.up] Physical NIC vmnic6 linkstate is up&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I noticed that even when turning off the nic it ended with linkstate up. Even though that is not true at all. I am hopping someone can point me in the right direction so I can renable failover on the vSwitch&lt;/P&gt;</description>
      <pubDate>Fri, 27 Oct 2023 13:36:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/NIC-not-reading-correct-status/m-p/2993041#M290843</guid>
      <dc:creator>rtarson98</dc:creator>
      <dc:date>2023-10-27T13:36:13Z</dc:date>
    </item>
  </channel>
</rss>

