FusionCompute all version
The phenomenon of [question]
New distributed virtual machine can be normal dynamic access to the IP, but after the lease expired, not normal, IP displayed as 0.0.0.0, disabled, enabled adapter or restart the virtual machine are unable to get the IP,
[problem analysis]
(1) to check the card Internet protocol attribute, confirm the IP is dynamic access,
(2) the virtual machine is disabled, enable the network card in the process, in the virtual machine where the CNA nodes using the tcpdump tool to grab bag of back-end network card, not be found on the back-end network card caught the DHCP Request message, the Request message is not issued to the back-end network card, hence the problem inside the virtual machine,
(3) the virtual machine configuration, click "start - & gt; Run, "input" services. MSC ", open the "service" window, find the DHCP Client service did not start, open service after restart card, virtual machine can be normal access to the IP,
(4) the place from the customer to understand in order to facilitate management, game point all virtual machines are using static IP, customers in the domain controller set strategy, when the virtual machine to join domain control will disable the DHCP Client service, therefore, has just issued by the virtual machine to dynamically access to the IP, but prior to the expiry of the lease, as domain control strategy into effect, lead to the DHCP Client service closed, so I can't, the lease expires IP into 0.0.0.0,
[the solution]
Use DHCP for virtual machine access to IP, need to open the DHCP Client service,
[summary & amp; recommendation]
(1) advice in a virtual machine dynamic IP access failure, the virtual machine configuration, first check the service and drive running situation,
(2) under the normal operation of the virtual machine configuration, in the virtual machine, virtual machine back-end network adapter and CNA caught on the physical network card, analysis the DHCP Request message is normally distributed,
Failed to get the IP (3), can also check the Windows logs, determine whether there is an error or warning,
CodePudding user response:
