- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: HP SIM VMM cannot correctly identify ESX Linux...
Server Management - Systems Insight Manager
1753274
Members
4785
Online
108792
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2008 07:56 AM
09-23-2008 07:56 AM
Re: HP SIM VMM cannot correctly identify ESX Linux guests
You should not have to edit the machine properties at all. SIM should be able to pickup all the info it needs from the Host via WBEM.
1.Delete the VM from the SIM db (If you are using VSE and it returns and error saying that it is a container object, delete the logical server first from VSE).
2. You must have WBEM credentials properly setup in Global Protocol settings of SIM for the ESX server.
3. Make sure you are on SIM 5.2 SP1 or later.
4. Vmware tools MUST be installed on Linux in the VM.
5. Installing the vmware tools is also not enough. You have to run vmware-config-tools.pl and answer any prompts. On the first run, it will ask about X display resolution. After that, it just asks if you want to change it (yes/no). This is ABSOLUTELY critical in discovering the Linux VMs (Windows too) correctly.
You can check to see if the tools are running properly a few different ways:
1. Service vmware-tools restart
If they restart just one service and return an error, you didn't config them yet
If they restart about 10 services, then you are OK
If they say they aren't started, you need to config the tools
or
2. Chkconfig --list | grep vmware
It should show vmware-tools set to start at level 3 (and probably 5)
If it lists nothing, you need to config the tools as described above.
Hope this is helpful to you
1.Delete the VM from the SIM db (If you are using VSE and it returns and error saying that it is a container object, delete the logical server first from VSE).
2. You must have WBEM credentials properly setup in Global Protocol settings of SIM for the ESX server.
3. Make sure you are on SIM 5.2 SP1 or later.
4. Vmware tools MUST be installed on Linux in the VM.
5. Installing the vmware tools is also not enough. You have to run vmware-config-tools.pl and answer any prompts. On the first run, it will ask about X display resolution. After that, it just asks if you want to change it (yes/no). This is ABSOLUTELY critical in discovering the Linux VMs (Windows too) correctly.
You can check to see if the tools are running properly a few different ways:
1. Service vmware-tools restart
If they restart just one service and return an error, you didn't config them yet
If they restart about 10 services, then you are OK
If they say they aren't started, you need to config the tools
or
2. Chkconfig --list | grep vmware
It should show vmware-tools set to start at level 3 (and probably 5)
If it lists nothing, you need to config the tools as described above.
Hope this is helpful to you
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP