- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: I cannot apply the Insight Dynamics License to...
Server Management - Systems Insight Manager
1753474
Members
4781
Online
108794
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
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО12-10-2009 08:02 AM
тАО12-10-2009 08:02 AM
I'd like to integrate my ESX Server (BL460) into VSE. Do do so I tried to apply the Insight Dynamics License to that blade. But this can not be acconplished because of the error:
==============================================
This tool cannot run on tstesx1 as it does not pass the conditions required for running it.
Device Type must equal Server and Device Sub-type must contain ProLiant
The properties that tstesx1 has for the failing conditions :
Device Sub-type: [Blade, c-Class, VMHost, VMWARE_ESX_VMHost]
Device Type: Server.
=============================================
What i'm doing wrong??
==============================================
This tool cannot run on tstesx1 as it does not pass the conditions required for running it.
Device Type must equal Server and Device Sub-type must contain ProLiant
The properties that tstesx1 has for the failing conditions :
Device Sub-type: [Blade, c-Class, VMHost, VMWARE_ESX_VMHost]
Device Type: Server.
=============================================
What i'm doing wrong??
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2009 08:48 AM
тАО12-10-2009 08:48 AM
Solution
Hi
Surely nothing ;-) it must be the computer !
One can reasonnably think about an identification issue here since properties are not correct.
The two most important protocols responsible for bad identifications are SNMP and WBEM.
SNMP: check the snmpd.conf on the esx server located in /etc/snmp/ be sure that trap destinations are correct, snmp community strings should be checked as well.
WBEM:
be sure that a user had been set up in the system protocol settings for the machine.
be sure that the pegasus service (wbem layer)is runnning properly on the esx server (retsarting it sometimes fixes identification issues : service pegasus restart followed by a hp sim identification)
be sure that the vmm agent service is runniong on the esx : restart using service hpvmmsvccnt restart or use the hp sim web ui to restqrt the vmm agent
You can also use the CRA configure and repair agents to fix these communications issues.
Try these different options, I would start with the wbem part personnally ;-)
Once the server is properly identified , the licensing will go fine.
hope it helps
fred
Surely nothing ;-) it must be the computer !
One can reasonnably think about an identification issue here since properties are not correct.
The two most important protocols responsible for bad identifications are SNMP and WBEM.
SNMP: check the snmpd.conf on the esx server located in /etc/snmp/ be sure that trap destinations are correct, snmp community strings should be checked as well.
WBEM:
be sure that a user had been set up in the system protocol settings for the machine.
be sure that the pegasus service (wbem layer)is runnning properly on the esx server (retsarting it sometimes fixes identification issues : service pegasus restart followed by a hp sim identification)
be sure that the vmm agent service is runniong on the esx : restart using service hpvmmsvccnt restart or use the hp sim web ui to restqrt the vmm agent
You can also use the CRA configure and repair agents to fix these communications issues.
Try these different options, I would start with the wbem part personnally ;-)
Once the server is properly identified , the licensing will go fine.
hope it helps
fred
тАЬLife is pleasant. Death is peaceful. It's the transition that's troublesome.тАЭ Isaac Asimov
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-15-2009 11:32 PM
тАО12-15-2009 11:32 PM
Re: I cannot apply the Insight Dynamics License to a ESX Server 3.5
That was the right rirection. I had to remove all hpagent rpms on the ESX server with
# rpm -e package
And reinstall it over Configure or Repaire Agent.
Case Closed.
# rpm -e package
And reinstall it over Configure or Repaire Agent.
Case Closed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-15-2009 11:33 PM
тАО12-15-2009 11:33 PM
Re: I cannot apply the Insight Dynamics License to a ESX Server 3.5
Done.
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