HPE GreenLake Administration
Server Management - Systems Insight Manager
1833514
Members
3016
Online
110061
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
Forums
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
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
10-21-2008 12:48 AM
10-21-2008 12:48 AM
PMP
Oct 16, 2008 14:54:40 GMT
--------------------------------------------------------------------------------
I have just installed HP SIM 5.2 and PMP 4.7. when i try and run the PMP it is saying that the servers are ready for licensing. i have run the license manager and assign the licenses but it is saying non used. Anyone any ideas. The servers are a DL385g2 and a DL320 g5 running windows server 2003 am i doing something stupid
they also come up with unsupported config but as far as i can see they are on the ok list
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2008 07:26 AM
10-30-2008 07:26 AM
Re: PMP
I have the similar issue with BL 30p.
I have found in intranet (not remember where) next hints:
For licensing & monitoring, PMP is sensitive to server details, such as
OS name, OS version, Management Agent version & so on, so you might want
to verify these values against the PMP support matrix. Some of the
probable causes of getting "unsupported ..." are:
- For a given server, discovery using WBEM might give version no.
as 5.2.*, whereas the same field is populated as just "5.2", when
discovered using SNMP. In that case, you can edit this field to make it
"5.2", as required by PMP.
- Similarly WBEM discovery populated OS name with extra (R), which
is not required by PMP. So, after referring support matrix, you may want
to edit that field as per the supported OS name.
You can edit these fields & same will be reflected in SIM database, but
PMP database may store the older values, so you can either restart PMP
service (HP Perfromance Management Pack) to refresh its database OR use
a 'Update Server List' button, available on 'Monitoring Administration'
page.
The easy way to do this exercise, is to disable WBEM during initial
discovery of all monitored servers, license them in PMP & set them for
monitoring AND if required, enable WBEM & do the rediscovery.
Good luck
I have found in intranet (not remember where) next hints:
For licensing & monitoring, PMP is sensitive to server details, such as
OS name, OS version, Management Agent version & so on, so you might want
to verify these values against the PMP support matrix. Some of the
probable causes of getting "unsupported ..." are:
- For a given server, discovery using WBEM might give version no.
as 5.2.*, whereas the same field is populated as just "5.2", when
discovered using SNMP. In that case, you can edit this field to make it
"5.2", as required by PMP.
- Similarly WBEM discovery populated OS name with extra (R), which
is not required by PMP. So, after referring support matrix, you may want
to edit that field as per the supported OS name.
You can edit these fields & same will be reflected in SIM database, but
PMP database may store the older values, so you can either restart PMP
service (HP Perfromance Management Pack) to refresh its database OR use
a 'Update Server List' button, available on 'Monitoring Administration'
page.
The easy way to do this exercise, is to disable WBEM during initial
discovery of all monitored servers, license them in PMP & set them for
monitoring AND if required, enable WBEM & do the rediscovery.
Good luck
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP