Skip to main content
  • EN

Hi All,

Occasionally there are a few Windows replica VMs that come up 169.x on NIC 0 during boot. They are VCD enabled replicas. We are using VLAN direct mapping without NSX in this case. Job network mappings are set and functional. 95% of them boot as they should. The few that come up with an APIPPA address will obtain the correct IP *if* I go to the NIC config in VCD for the VM and disable NIC 0, add NIC 1 and set to static pool along with the VLAN. (connected, primary). This has been tested as repeatable across reboots once it’s been changed in VCD. I took a look at the VMX and the Veeam statements look correct as far as I can tell. PCI ID also matches. This doesn’t seem to be limited to a single VCD Org. 

Troubleshooting I’ve tried so far, 

  1. Update VM tools to the latest. 
  2. Review device manager for ghosted adapters. 
  3. Add a second NIC (works)

I’m wondering if anyone else has bumped into this and what the findings were if so. TIA

Never seen this one before myself.  Maybe also do a check in the forums and/or open a support ticket with Veeam.

Forums - https://forums.veeam.com

 

When the VMs come up, are you using the same MAC address or is a new one being generated? 

When the VMs come up, are you using the same MAC address or is a new one being generated? 

It appears to be the original MAC when reviewing. I went on to generate a new MAC on NIC 0 with the same results. NIC 1 being functional after adding it in VCD throws me for a loop :)

Comment


Terms & Conditions