Hello,
Did you install the agents here ?
This is just the Insight Manager Agents, you would also need the System Management page.
Hello,
Did you install the agents here ?
This is just the Insight Manager Agents, you would also need the System Management page.
Hello What is the type model of hardware you use ? This way i can search the website.
We run HPSUM on the local servers one at a time with Altiris or HP RDP for that matter.
I don't work at HP but there is a new version, i don't use it yet because as you said it'still needs work. So no argument there.
You don't need to have the VCRM for seeing the installed software. The datacollection collects/does that for you and you can report from the report fuction in SIM.
Here are the H/W models
server rx4640
server rx2600
Could some one share the HP SMH software download link for Windows server 2003 R2 32 bit?
Hello, I have a very similar issue to this post:
In the last post, the user stated he solved the problem. However, I have no idea what he is talking about or what the fix actually is.
I run `/opt/mx/bin/mxinitconfig -a` , but it failes on configuring database. It says it cannot start the hpsmdb service. When I run `/etc/rc.d/init.d/hpsmdb status` I get active (exited).
Please help! If you want to see a log file, please let me know the location! I looked for log files to help, but found none that would help.
/var/opt/mx/logs/PgSQL_Config.log
Starting postgresql (hpsmdb)
Waiting for hpsmdb to start ...
Waiting for hpsmdb to start ...
Waiting for hpsmdb to start ...
I am pretty sure I have all dependencies, and running CIM binary has no failures. I have not run any commands on hpsmdb (to initialize, or run any commands). I ran the SIM binary, then immediately ran mxinitconfig -a (per the manual).
Do I need to do anything with this:
Success. You can now start the database server using: /opt/hpsmdb/bin/postgres -D /var/opt/hpsmdb/data or /opt/hpsmdb/bin/pg_ctl -D /var/opt/hpsmdb/data -l logfile start
Nevermind, just went to CentOS 6.7, and it installed without a single issue
Hello,
Successfully installed SIM 7.5 for linux.
Website works just fine. I have no idea what to log in as! Is there a default username / password?
I tried using root / password (what I use to login to linux), didn't work. Is there a way to manually add a user?
I tried creating a new user and adding the user to wheel (admin) agroup. Could not log in.
The machine is not part of a domain. Do iI still have to specify a domain? I tried localdomain\root , but it still did not work...
Should be an easy one, but I can't find the answer!
Thanks!
Hello,
You should use the user that you used to install the software of the local afdministrator account on the server.
Hello again,
The link below is for this kind of hardware :
http://h20565.www2.hpe.com/hpsc/swd/public/readIndex?sp4ts.oid=346360&swLangOid=8&swEnvOid=1060
Expand Software System Management to find your software.
Hello,
Could anyone of you please help me resolve this issue. I am new to the HPSIM and have setup new HPSIM7.4 and doing testing.
Trying to discover ESXi server but go. Here is the discovery report that shows WBEM credentials is not correct but I am 100% sure the credentials is ok.
Please check the logs and suggest correct steps that can solve me problem.
Regards,
Satish
********* Significant issues and overall target discovery/identification
status:
Major: There is no working sign-in credential for this system. Go to
Options -> Security -> Credentials -> System Credentials and either
enter the credentials there or be sure that the checkbox enabling
HP SIM to try other credentials is checked.
Minor: The discovered blade is not in an enclosure. For c-Class
enclosures, verify that the supported OA firmware version is
installed and verify that the OA has been discovered in HP SIM. For
p-Class enclosures, verify that the iLO firmware and the HP Insight
Management Agents on the server are installed and verify that the
iLO has been discovered in HP SIM.
Normal: The system has valid hardware data (model, serial number, and
unique identifier) and has been identified properly for SIM to
manage.
Critical: There are no valid WBEM / WMI credentials for the system(s).
********* Additional results (listed for information only):
* Starting identification process...
* Checking for known running web servers...
* Checking for SNMP protocol support on system...
Normal: The system did not respond to SNMP. Verify security settings and
community strings in Options->Security->Credentials->System
Credentials
* Checking for SNMPv3 protocol support on system...
Normal: The system did not respond to SNMPv3. Verify security settings and
v3 credentials in Options->Security->Credentials->System
Credentials
* Running HP ProLiant management agent identification...
Normal: The system does not support SNMP.
* Running SNMP base cluster identification using common cluster
MIB...
Normal: SNMP is not supported or globally disabled, skipping SNMP cluster
identification.
* Checking for WBEM protocol support on system...
Minor: This system does not have any SMI-S CIMOMs installed. No storage
systems will be found on this system.
Minor: The Central Management System (CMS) cannot communicate with the
CIMOM locally installed on the managed system using the WBEM
protocol, Identification will try to identify Windows systems using
the WMI Mapper as proxy; for Linux and HP-UX systems, check
credentials by going to Options->Security->Credentials->System
Credentials. For Linux systems also check if the HP WBEM provider
is installed.
Critical: There are no valid WBEM / WMI credentials for the system(s).
* Running WBEM rules based identification...
Minor: Identification cannot get computer system hardware data from the
WBEM / WMI providers.
* Running Virtual Machine (VM) Host (non HP Integrity VM Host)
Identification...
Normal: The system is not a VM Host (non HP Integrity VM Host), or WBEM
credentials may not be specified so skipping VM Identification.
* Running Storage identification...
* Did not detect the WBEM protocol support on this system. SMI
storage identification will be skipped.
* Storage identification completed.
* Running HP NetServer identification...
Normal: The system does not support SNMP.
* Running HP-UX SNMP identification...
Normal: The system does not support SNMP.
* Running OA Identifier which will discover systems in an enclosure
if the automatic enclosure discovery option for OA is enabled...
Normal: The system is not an Onboard Administrator, skipping automatic
discovery of systems in the enclosure.
* Running XMLReply Identifier which will discover systems in a
rack/enclosure if the automatic discovery option for the container
node is enabled...
* Running iLO Identifier which will discover the server if the
automatic server discovery option for iLO is enabled...
Minor: The system responds to the HTTP request but cannot get the XML
output. It is normal for servers not to get the XML data.
Minor: If the http communication from CMS to target is working, but if it
is found to be slow then try increasing the Default connection
timeout parameter for http in global protocol settings.
* Running p-Class Identifier...
Normal: The system is not a p-Class so skipping p-Class identification.
* Running IPMI protocol identification...
Minor: Running an ipmiutil command failed and the IPMI protocol is not
supported.
* Running SSH Protocol identification...
Normal: This system has SSH protocol support.
* Running SSH Identification...
Minor: The system cannot be logged in using SSH protocol; check
credentials or check the settings in the SSH configuration file
* Running WS-Man identification...
Minor: The system did not respond to WS-Management (WS-Man) request.
* Running Monarch OA Identification...
Normal: The system is not a monarch OA so skipping monarch OA
identification.
* Checking for System Management Homepage and other HP web agents...
Normal: The system is not a server, storage or desktop. Skipping the check
for System Management Homepage.
* Running HP Serviceguard Identification...
* Running SNMP System Type manager ...
Normal: The system does not support SNMP.
* Running SNMP subtypes identification...
* Resolving DNS names...
Normal: The fully qualified domain name was successfully resolved for the
system.
* Checking if the Node is a Virtual Center...
Normal: Skipping MxVirtualCenter Identifier.
* Running Virtual Machine Management (VMM) Plug-in Identification...
* Building system relationships...
Minor: The Secure Shell key-based access authentication is not configured
on the system(s).
Minor: System Management Homepage (SMH) is not installed or is not
responding on the system(s).
* Running system Manage Communication diagnosis...
* System identification finished on system.
Hello there,
What is the hardware type ? Gen8 or lower ?
The credentials on a Gen7 or lower need to be the root user or an other user with root like rights. This is a system user not an ESX user. Is the server is a Gen8 or higher you need to discover the ILO and use Agentless Management Service software.
Hello Again,
can you please tell me how i can monitor ESXi 5 servers and virtual machines hosted on them? i see those discovered with thier Serial number but not the host name.
Cheers
Hello again,
Did you install the offline bundle from HP that contains agents and drivers? This package is needed for monitoring your HP hardware servers. The software csn be found here http://h20565.www2.hpe.com/hpsc/swd/public/detail?sp4ts.oid=3884100&swItemId=MTX_ba94e3edea26495d8540bc88de&swEnvOid=4166
The needed credentials are root or yet better a new account with root rights.