Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > Error: No IP address is assigned

Error: No IP address is assigned

​Updated September 7, 2018

Overview

 

The LEM console in Hyper-V displays one of the following error messages:

  • Device "eth0" does not exist.
  • The virtual appliance is successfully installed but a networking problem was detected.
  • No IP address is assigned.

 

no_ip_detected.jpg

 

Causes


By default, Microsoft chose Hyper-V to have dynamic MAC addresses. If LEM (or any Linux-based host) received a MAC address, the linux networking ties the MAC to the IP address. Therefore this particular VM needs the same MAC address to function.

If the LEM was shutdown, and any other VM was created, that new VM could grab and keep the MAC address that belongs to LEM. When LEM boots up, it cannot tie it's configured IP address to the MAC address that is now owned by another VM.

 

Hyper-V can be set to allow the LEM to have a static MAC address, and no other VM can take the MAC address.
This is a configuration change under Hyper-V.

As compared to VMware:
This will not happen with VMware, as ESXi will reserve (make static) the MAC address assigned to LEM.
No other VM can take the MAC assigned to LEM.

 

Environment

  • All LEM versions
  • All Microsoft Hyper-V versions

Resolution

  1. On the LEM virtual console, select Advanced Configuration.
  2. At the cmc prompt, type appliance.
  3. Type shutdown, and then follow the prompts.
  4. In the Hyper-V Manager, select your LEM instance and go to the Settings.
  5. Highlight Network Adapter or Legacy Network Adapter and verify that LEM is using the proper virtual switch.
  6. Expand Network Adapter, and then select Advanced Features.
  7. On the right pane under MAC address, select Static.
  8. Click OK.
  9. no ip fixed.jpg
  10. Start your virtual machine.
  11. On the LEM virtual console, select Advanced Configuration.
  12. At the CMC Prompt, enter: appliance.
  13. Type resetsystemmac, and then press Enter.
  14. Enter yes, and then enter to reboot LEM.


On reboot, the LEM recognizes eth0 and applies the network settings to the interface. You should now see an assigned IP address or be able to configure one manually.

Cause

This issue is caused by Hyper-V using dynamic MAC addressing.

Last modified

Tags

Classifications

Public