Alert not generating on HPE SIM

[Rajshree1]

Hello Team,

Recently I have configured HPE SIM server.

On which only System failure alerts are generating.

I obeserver on some servers there is hardware failure like disk or physical memory degrated but no alerts generated in HPE SIM.

Also, can you help me to understand how can I configure SNMP Trap settings on HPE SIM server?

Need your urgent help!!

Thanks in advance.

[Suman_1978]

Hi,

Kindly mention the SIM version you have depolyed or using.

Here are some user manuals which may help.

Thank You!
I work with HPE but opinions expressed here are mine.
Recent Support Video Releases

[Rajshree1]

Hello,

HPE SIM version is 7.6

Could also tell me how can I check if there is any issue with certificate.

Only recieving system failure alerts on HPE SIM.

[Bunsol]

You can use below steps to configure SNMP on HPSIM:-

ConfiguringSNMPto sendtrapsto the CMS
•On the managed system,add the full host name or IP address of the CMS as a trapdest in the following file:
/etc/SnmpAgent.d/snmpd.conf
trap-dest:hostname_or_ip_address
•Stop the SNMP Masteragent and all subagents with the command:
/sbin/init.d/SnmpMasterstop
•Restartthe SNMPM asteragent and all subagents with the command:
/usr/sbin/snmpd

Below is the user guide which shares this information:-
https://support.hpe.com/hpesc/public/docDisplay?docId=c05330372

[Rajshree1]

Forgot to mention that my HPSIM server is windows 2016 Datacenter.

Please suggest solution for this as I'm not able to track the hardware failures via HPSIM.

only hearbeat failure incidents are generating.

Thanks in advance!

[Vinky_99]

@Rajshree1 

There could be a few reasons why hardware failure alerts are not being generated. Go through some troubleshooting steps to help you resolve the issue:

* Ensure that the SNMP (Simple Network Management Protocol) settings are correctly configured on the monitored servers. SNMP is used by HPE SIM to receive hardware status information. Check that SNMP traps are enabled and the correct community string is set on each server.

* Verify that the HPE SIM server can successfully communicate with the monitored servers via SNMP. Ensure that there are no network connectivity issues or firewall restrictions that might be blocking SNMP traffic between the servers.

* Make sure that the SNMP Management Information Bases (MIBs) are up to date on your HPE SIM server. The MIBs contain the definitions and descriptions of SNMP variables and are required for interpreting SNMP traps received from the monitored servers.

* Check the event thresholds and settings on the monitored servers. Some hardware failures might not trigger an alert if the threshold for generating an event is not reached. Adjust the thresholds if necessary to ensure that alerts are triggered appropriately.

* Review the event handling settings in HPE SIM. Ensure that the appropriate event filters and notification rules are configured to generate alerts for hardware failures. Double-check that the events related to disk and physical memory degradation are included in the event filters.

[Vinky_99]

Regarding configuring SNMP Trap settings on your HPE SIM server running Windows Server 2016 Datacenter, you can follow these steps:

>> Launch the HPE SIM console on the server.
>> Go to "Options" in the top menu and select "Events and Thresholds Settings."
>> In the left pane, click on "SNMP Trap Settings."
>> Click on the "Add" button to define a new SNMP trap destination.
>> Enter the IP address or hostname of the device that will receive the SNMP traps.
>> Set the SNMP community string and port number as required.
>> Save the settings.
>> Make sure to configure SNMP Trap settings for each server from which you want to receive traps.

After implementing these steps, monitor the HPE SIM console and check if the hardware failure alerts are now being generated properly. If the issue persists, it may be helpful to review the HPE SIM documentation(You can find it in: https://support.hpe.com/) or contact HPE support for further assistance.

[Rajshree1]

Hello,

Thanks for your suggestion.

SNMP Management Information Bases (MIBs) are up to date on your HPE SIM server - How can I check that ... do I need install MIBs on SIM server ?

Also please suggest how to set disk threshold.

SNMP trap setting is correctly configured.

[Rajshree1]

If server firmware version is below 2.0, will it be monitored by HP SIM 7.6v ?

I have updated MIBs on my HPPsim server and then restarted it.

Now when I'm discovering a new server it is giving me below error ::

Major: The system cannot be identified properly for HPE 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.

********* 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 responded to an SNMP request; it supports SNMP Protocol
and has a valid read community string.
* 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 HPE ProLiant management agent identification...
Normal: The ProLiant SNMP Foundation agents for servers are not installed
or are not configured.
* Running SNMP base cluster identification using common cluster
MIB...
Normal: This system does not have the common cluster MIBs support.
* 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 HPE 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 HPE Integrity VM Host)
Identification...
Normal: The system is not a VM Host (non HPE 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 HPE NetServer identification...
Normal: System supports the NetServer SNMP agent, adding system type.
* Running HP-UX SNMP identification...
Normal: System does not have the HP-UX SNMP agents installed.
* 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...
Major: Using SSH Protocol in discovery is disabled on the Central
Management Server (CMS).
* Running SSH Identification...
Major: Using SSH Protocol in discovery is disabled on the Central
Management Server (CMS).
* 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 HPE 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: No matching SNMP System Type Manager rule for sysObjID was found.
* Running SNMP subtypes identification...
* No additional subtype(s) found from SNMP.
* Resolving DNS names...
* Checking if the Node is a Virtual Center...
Normal: Skipping Virtual Center Identifier.
* Running HPE Synergy identification...
* Running Virtual Machine Management (VMM) Plug-in Identification...
* System passed the discovery filter and will be added.
* 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.

what should I do here.

Thanks in advance!

[Vinky_99]

---

@Rajshree1 wrote:

Hello,

Thanks for your suggestion.

SNMP Management Information Bases (MIBs) are up to date on your HPE SIM server - How can I check that ... do I need install MIBs on SIM server ?

Also please suggest how to set disk threshold.

SNMP trap setting is correctly configured.

---

To check if the SNMP Management Information Bases (MIBs) are up to date on your HPE SIM server, you can follow these steps:

- Open the HPE SIM console on the server.
- Go to "Options" in the top menu and select "Events and Thresholds Settings."
- In the left pane, click on "SNMP MIB Kit" or "SNMP MIB Browser."

* If you have the SNMP MIB Kit installed:

- Click on the "Launch MIB Browser" button. This will open the MIB Browser tool.
- In the MIB Browser, you can browse and search for specific MIB objects related to the hardware devices you want to monitor. This confirms that the MIBs are installed and accessible on your HPE SIM server.

* If you don't have the SNMP MIB Kit installed:

- Click on the "Download MIB Kit" button. This will redirect you to the HPE website.
- Download the latest version of the HPE SNMP MIB Kit for your specific hardware devices.
- Install the downloaded MIB Kit on your HPE SIM server by following the provided instructions.
- After the installation, you can launch the MIB Browser and verify that the MIB objects you need are available.

* Regarding setting disk thresholds in HPE SIM, you can adjust the threshold settings using the following steps:

- Open the HPE SIM console on the server.
- Go to "Options" in the top menu and select "Events and Thresholds Settings."
- In the left pane, click on "Events."
- Select the "Thresholds" tab.
- Scroll through the list of event thresholds and locate the disk-related thresholds.
- Adjust the thresholds for the specific events related to disk degradation or failure. This may include events such as "Drive Fault," "Drive Predictive Failure," or similar disk-related events.
- Set the desired severity level and actions for each threshold. This determines how HPE SIM will respond when the specified threshold is met or exceeded.
- Save the threshold settings, and HPE SIM will now monitor the disk status according to the configured thresholds, generating alerts when the specified thresholds are reached.

Remember to regularly review and update the threshold settings based on your requirements and the specific hardware devices being monitored.