Quantcast
Channel: All Server Management - Systems Insight Manager posts
Viewing all 4342 articles
Browse latest View live

Discover windows 2008 R2 server

$
0
0

Installed HP SIM 7.5 and setup to discover windos 2008 r2 server.

Here is the discovery results 

********* Significant issues and overall target discovery/identification
status:
Major: The system cannot be identified properly for HP SIM to manage;
unable to get one or more of the following: model, serial number or
unique identifier (UUID). For management processors, verify the
system is running the latest firmware. For Linux based operating
systems, you must have dmidecode installed, enable the
PermitRootLogin and PasswordAuthentication in sshd, and use root
sign-in credential. For HP-UX, verify the sign-in credential. For
Windows, check if WMIMapper is configured correctly on the CMS and
verify the sign-in credential.
Normal: Identification status is only available for servers, workstations,
or desktops, where monitoring is enabled.

********* 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.
* 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...
Normal: IPMI protocol not detected so skipping IPMI Identification.
* Running SSH Protocol identification...
Minor: The system(s) do not have Secure Shell (SSH) installed or it is not
running on the managed system(s).
* Running SSH Identification...
Normal: SSH Protocol is not enabled so skipping SSH Identification.
* 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 Virtual Center Identifier.
* Running Virtual Machine Management (VMM) Plug-in Identification...
* Building system relationships...
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.

Do I need to enable on HPSIM and target windows server.


Re: HP SIM 7.5 on SQL 2008 R2 SP3

$
0
0

Can you simply move the DB from an SQL 2008 R2 DB to a SQL 2014 Server and then point the odbc connection there and upgrade then to 7.5 or so you need to export the DB first with the HP Insight manager tools? 

Re: HP SIM 7.5 on SQL 2008 R2 SP3

$
0
0
You could try to move the database and edit the config files in the config die in SIM. Do you know wich files to edit?

I'm not a SQL expert so i'm not sure, when changing the servername don't forget the portnumber for the new SQL.

Re: Discover windows 2008 R2 server

$
0
0
What type of hardware is the server, what version on Windows 2008 is the server and sis you install any agent on the 2008 server ?

Did you imclude any Admin account when discovering the server. Without any info expert a log this is only guessing but by looking at the log you might not have an agent installed and did mot use an Admin account to discover the server.

Re: Discover windows 2008 R2 server

$
0
0

Hi

Thanks for reply.

Yes I did added account (which is used for discovery) in the admin group on the target server.

OS installed is Windows 2008 R2 with SNMP and WMI enabled ( added the account in security group of wmi configuration)  but still seeing this error

Minor: Identification cannot get computer system hardware data from the
WBEM / WMI providers.
Minor:    The system did not respond to WS-Management (WS-Man) request.
Is any configuration require for WBEM/WMI and WS-MAN to work ??

Also I have not installed agent on the target server. 

Thanks

 

Help with email alerts standalone server

$
0
0

ML350 G6 standalone.

Here is what is installed

HP Insight Management WBEM Providers
          Test WBEM Events
HP Management Agents
          Event Notifier Config
          Event Notifier Help
          HP System Management Homepage
Hp System Tools
   HP Proliant Integrated Management Log Viewer
   HP Arrary Confiruation Utility
   HP Array Confiruation Utility CLI
   HP Array Diagnostics and SmartSSD Wear Gauge Utility
   HP Insight Diagnostics Online Edition for Windows
   HP Lights-Out Online Configuration Utility

I need this server to send RAID array email alerts. Email must be able to authenticate w/ username and password, over port 465 with SSL.

Is this possible?

Vmware vsphere ssh and sim 7.5

$
0
0

Discovery end with with statu complete (sucess with wbem) but why ssh not working ?

Can someone check if this normal ?

Minor:    The system cannot be logged in using SSH protocol; check
          credentials or check the settings in the SSH configuration file

 

 

Re: Vmware vsphere ssh and sim 7.5


Re: Help with email alerts standalone server

Not receiving System Unreachable eMail Alert

$
0
0

Guys,  we are us.ing SIM 7.4.0...

We have an alert set up to advise when a VM goes off-line.. and comes back on-line.

We get the on-line alert.. but not the alert when the system goes off-line.

Any ideas waht this might be ??

Feel free to ask more info ...

 

 

Problem discovering server running WBEM agents on HP SIM 7.5.1

$
0
0

I've upgraded WBEM agents to version 10.40.0.0 and system management homepage to version 7.5.4.3 on a server and i can see on the system management homepage it shows WBEM is working etc, but when i do discovery of the server in HP SIM 7.5.1 I get teh following error.

I've logged in using the account details i've set and it loads HP SMH  up fine, that administrator account also allows me to login to the server.

I can telnet the server from HP SIM server on port 5989 and 5988 which is what i believe it uses for WBEM

So any ideas?

Anyone testing these new version of WBEM And SMH with HP SIM 7.5.1 as these agents only came out 1APR2016.

 

********* Significant issues and overall target discovery/identification
status:
Major: The system cannot be identified properly for HP SIM to manage;
unable to get one or more of the following: model, serial number or
unique identifier (UUID). For management processors, verify the
system is running the latest firmware. For Linux based operating
systems, you must have dmidecode installed, enable the
PermitRootLogin and PasswordAuthentication in sshd, and use root
sign-in credential. For HP-UX, verify the sign-in credential. For
Windows, check if WMIMapper is configured correctly on the CMS and
verify the sign-in credential.
Normal: Identification status is only available for servers, workstations,
or desktops, where monitoring is enabled.

********* 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...
Normal: IPMI protocol not detected so skipping IPMI Identification.
* Running SSH Protocol identification...
Minor: The system(s) do not have Secure Shell (SSH) installed or it is not
running on the managed system(s).
* Running SSH Identification...
Normal: SSH Protocol is not enabled so skipping SSH Identification.
* 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 Virtual Center Identifier.
* Running Virtual Machine Management (VMM) Plug-in Identification...
* Building system relationships...
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.

 

 

Re: Not receiving System Unreachable eMail Alert

$
0
0

this is the setting i use in automatic event handling to send us emails for any minor, majot and critical event.

Server being unreachable will generate an critical alert so will send out email with these details

screenshot attached

Re: Vmware vsphere ssh and sim 7.5

$
0
0

Can also check if password got @ then wbem is not working ?

Adding ESXi 6.0 Hosts to HP SIM

$
0
0

Guys,  previously when adding out ESXi hosts to HP SIM we simply added their root account / password to the Global Settings.  Everything worked great ...

Recently we had to update each of our ESXi Hosts to have a unique root password.

Since updating our ESXi Hosts to 6.0 the new root password lockout feature has been enabled on the host.

The fucntion can be disabled on the ESXi 6.0 Host...

Can I ask if anyone else has the same issue with an ESXi 6.0 Host, unique root passwords and HP SIM.

Do you add your hosts to HP SIM using root?

Is there another way to add the host to HP SIM without using root?

Any advice would be greatly apprecaited ...

 

 

Re: Vmware vsphere ssh and sim 7.5


Discovering Virtual Machines in HP SIM

$
0
0

Guys,  when I add an ESXi Host to HP SIM... should it auto disocver the VM (guests) ... ?

Re: Not receiving System Unreachable eMail Alert

$
0
0

Thanks... this works all good!

Do you also alert when the device comes back on-line?

Re: Not receiving System Unreachable eMail Alert

$
0
0

No I don't. Only sees it go missing,  when it comes back I get no email 

Re: Discovering Virtual Machines in HP SIM

$
0
0

Make sure that in your discover general settings that this setting is checked:

*Automatically discover VM guest(s) when the host is identified.

Also make sure you have hp wbem providers installed for the esxi host.

HP SIM Agent not sending email alert before disk space is run out.

$
0
0

Hi All,

Can anyone here please let me know how to configure the HP SMH or HP SIM agent so that it send out email alert to me when the disk space threshold is 90% full ?

In my case below it is already 0 bytes free but no email alert is sent out.

DiskSpace.JPG

Thanks in advance

Viewing all 4342 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>