Unsolved
This post is more than 5 years old
9 Posts
0
35971
OME doesn't detect my Hyper-V server as Microsoft Virtualization Servers
Hello,
I've a problem with OME who dosent detect my Hyper-V servers (OS WS2012) as Microsoft Virtualization Servers.
OME classified them on Servers group.
OMSA 8.1 is installed on my Hyper-V servers, and I use OME 2.1.
I really would like to classify my Hyper-V as Microsoft Virtualization Servers, to see guests of my Hyper-V servers.
When I use the troubleshooting tools on my Hyper-V, SNMP and WMI looks like to be good...
Did you have any idea of the problem ?
Thank's
Max_GUY
9 Posts
0
October 6th, 2015 01:00
Hi,
Thank's for the answer !
On all my Hyper-V server, I don't see "Hyper-V Information" on the device inventory page, but i see a table with the informations about the NIC of guest devices...
I join you the detail of the device inventory of one of my Hyper-V server, hope it can help you...
1 Attachment
h100-02.zip
DELL-Shivendra K
685 Posts
0
October 6th, 2015 01:00
Hi Max,
Thanks for the query.
Since you mentioned that troubleshooting SNMP and WMI protocols for the targets went well, please make sure that you see following tables on the device inventory page with proper details:
HyperV Information
Virtual Machine Guest Information
If possible, share the details of the device inventory page (you can export as HTML) for us to take a deeper look. Also, don't forget to mask any sensitive information it may have (like IP addresses, service tag, etc.).
Max_GUY
9 Posts
0
October 6th, 2015 02:00
Hi,
Thank's for the answer !
On all my Hyper-V server, I don't see "Hyper-V Information" on the device inventory page, but i see a table with the informations about the NIC of guest devices...
I join you the detail of the device inventory of one of my Hyper-V server, hope it can help you...
Max
1 Attachment
h100-02.zip
DELL-Shivendra K
685 Posts
0
October 6th, 2015 06:00
Thanks for the information, Max!
"HyperV Information" table needs to populated properly during discovery for OME to create necessary groups and associations (with virtual machines). As we can see that the data is missing, I would suggest you to try discovering using WMI protocol only (don't include SNMP) and post back with results.
If it still does not populate the necessary data, we may have to dig in deeper to reason out why OME is not able to collect this information from the target server.
Max_GUY
9 Posts
0
October 6th, 2015 06:00
I have tried to discover using WMI protocol only. The "HyperV Information" table doesn't appear anymore...
I have disabled firewall and anti virus to make my test. I join you the result of inventory on my HyperV server.
Thank's
1 Attachment
h100-02_wmi.zip
Dell-Ranveer
96 Posts
0
October 6th, 2015 23:00
Hi Max,
Thanks for the update!
By looking at the attachment it seems like Hyper-V role is not enabled on the target server. Can you please confirm? If not, then the recommendation is to enable Hyper-V role on the target server and then re-discover the server again in OME.
Because until Hyper-V role is not enabled, OME will not be able to fetch "Hyper-V Information" table and server will not get classified under "Microsoft Virtualization Server" group.
Hope this helps!
Regards
Ranveer
Max_GUY
9 Posts
0
October 7th, 2015 00:00
Hi,
Hyper-V is enabled on the server, I have 4 WM running on this one...
You can see it on the attachment.
I really don't know where is the problem (it's the same on my 12 Hyper-V server !)
Any idea ?
1 Attachment
Capture.JPG
DELL-Shivendra K
685 Posts
0
October 7th, 2015 04:00
Hi Max,
Is it possible for you to test if the "Msvm_ComputerSystem" WMI class returns valid instances once connected/queried from a remote system? You will have to run this test against the affected HyperV hosts. You can make use of "wbemtest" utility provided by Windows.
Please post back with results.
Max_GUY
9 Posts
0
October 7th, 2015 05:00
Hi,
Thank's for your answer.
Everything seems to be OK with the "Msvm_ComputerSystem" WMI class on my Hyper-V server.
The results are in the attachment.
Thank's
DELL-Shivendra K
685 Posts
0
October 7th, 2015 12:00
Many thanks for the details of the class, Max!
The class instance details are in French (also perceived from OME device details page). Which essentially means that the targets are French operating systems. Do you have any English operating system target, and, is it possible to validate OME behavior against them?
This seems more of an issue because of non-English data being received, which results in invalid / inaccurate information parsing.
DELL-Shivendra K
685 Posts
0
October 8th, 2015 01:00
Thanks for the information, Max!
English operating system output looks good for it to work seamlessly with OME. While it is not working as expected, I would ask you to analyse device details in OME if the required tables are getting populated with data. If the tables are missing for English operating system as well, try deleting the device from OME device tree and discover it again.
In addition to this, I would request you to open a support ticket on 800-945-3355. This will help us in taking a deeper look, and probably, finding a way for your French operating systems also to work.
Max_GUY
9 Posts
0
October 8th, 2015 01:00
Hi,
Yes, my OS are in french, because I am !
I have tried with an English OS, the result is the same... As you can see on the attachment !
My HyperV hosts are still classified as "Servers" and my VM as "Unknown".
Many thank's
1 Attachment
Msvm_ComputerSystem_en.xlsx
Max_GUY
9 Posts
0
October 8th, 2015 03:00
Hi,
I use this tips (http://en.community.dell.com/techcenter/systems-management/f/4494/t/19498307), and it seems to be good ! Now my server appears in both sections "Servers" and "Microsoft Virtualization Servers".
I will try to make some adjsutement to fix it !
DELL-Shivendra K
685 Posts
0
October 8th, 2015 04:00
Thanks for taking time and updating the thread.