Mapping host to guest relationships correctly in the virtual environment

Portal User asked a question.

August 9, 2018 at 7:00 AM

Hello everyone,

Currently the host to guest relationship in our VMM environment is wrong. The relationships are not mapped correctly from Host to Guest.

Currently, one agent is installed on each VM and each server. If we now activate the VMM connector we have the virtual machines twice in the SLM (once from the agent and once from the conector).

Unfortunately, the conector does not take a complete inventory like the agent.

Is there a defined process or configuration for this case?

I'm very grateful for your help.

SamuelBaughan
8 years ago
Hi Julian, What you describe should not happen, there must be a misconfiguration somewhere. What have you done to troubleshoot so far? When you take 2 duplicate computers (from VMM connector and form Snow agent) do you see differences between the 2? Remember that Snow will consider that 2 computers are different if they present more than a given number of differences (apparently out of a set of 5 criteria). There is interesting input on an issue similar to yours in this thread . Please tel us know if that proves to be helpful. Regards
Expand Post
- Portal User
  8 years ago
  Hi Samuel, i configured the hostname only mode and removed the connector. Unfortunately , i donot get the information of the Hostcomputer by only using the agent. The dupplicate have the ConfigurationName of the connector, i thought if we activate the hostname only mode the information will be consolidated. So if we configure the same ConfigurationName , the devices should not be shown twice or is there a better way?
  Expand Post
  - Community Manager (Flexera Software)
    8 years ago
    Hi Julian, thanks for calling me. As discussed, it is not necessary to install the Snow Inventory Agent on virtualization hosts. The inventory of these hosts will be covered solely by the Snow Integration Manager. After setting everything up correctly and after doing a little cleanup, everything should work as expected. We will cover this through our consultancy. Please reach out to our Professional Services Coordinator to arrange an appointment. /marcel
    Expand Post
    SamuelBaughan
    8 years ago
    Hi ‌, In our environment, we have the agent on all servers, including the physical hosts. So far, we have seen no real conflict (apart from a few random duplicate computers, less than 0.5% of the server estate) Should we still actively remove the Snow agent from those hosts? Is there a risk in not removing the agent? Thank you for your advice.
    Expand Post
    Community Manager (Flexera Software)
    8 years ago
    Hi Samuel, I can only speak for VMware, where it is strongly NOT recommended to install any foreign software on physical hosts. This has stability reasons. When it comes to Hyper-V, I don't have that much experience. I didn't see any clear advice to equip hosts with an agent yet. But no clear warning not to do so either. In your case: Did you do this on your own or in cooperation with any consultancy? /marcel
    Expand Post
    Community Manager (Flexera Software)
    8 years ago
    Hi Samuel, I can only speak for VMware, where it is strongly NOT recommended to install any foreign software on physical hosts. This has stability reasons. When it comes to Hyper-V, I don't have that much experience. I didn't see any clear advice to equip hosts with an agent yet. But no clear warning not to do so either. In your case: Did you do this on your own or in cooperation with any consultancy? /marcel
    Expand Post
    SamuelBaughan
    8 years ago
    I just inherited a fresh running system from a predecessor, so I'm not sure but the initial setup was made by Snow so I guess the technical advice was available and has been followed. But I can confirm we have nothing on VMWare hosts ... I thought there was actually no Snow agent for VMWare. Thanks for your input.
    Expand Post
  - SamuelBaughan
    8 years ago
    Hi Julian, We too configured the HostName only mode and it has significantly reduced the number of duplicates we get. We still have a few, probably due to some setting that needs fixing, and the situation is currently under investigation with Snow Support. I would assume that if the duplicate computers existed before you implemented the HostName only mode, they would not be consolidated during the DUJ. Rather, I would expect only new computers to be merged with an existing twin-computer. I can't be dogmatic on that point of view though, but ‌ will probably be able to shed some light. If the above is correct, your duplicate computers could either be deleted manually (beware of license assignment and attached documents loss ...) or they would eventually be cleaned thanks to the auto-quarantine management. Regards
    Expand Post
Community Manager (Flexera Software)
8 years ago
Hi Julian, you should set up this scenario like follows: Use the Snow Integration Connector to connect your virtualization center. This will give you information about the hosts and about host-guest-relations. Regarding guests, you will get a pretty low information depth, which is normal, because you are viewing from the datacenter perspective. Use the Snow Inventory Agent to inventory the guest machines. This will give you full visibility inside the machine. By setting it up like this, you should get a correct view of your datacenter. Please let me know, if you need further information. /marcel
Expand Post

Related Product Forums

→ Flexera One

→ Snow Atlas

→ FlexNet Manager

→ Snow License Manager

→ App Broker

Need help finding an answer?

Ask a Question →