System Status Monitor (Events)

Event 100001

• Severity: Major Warning
• Event Summary:Cannot resolve the IP address for system systemname.
• Event Class: System
• Problem Description:
  The monitor failed to resolve the IP address for the target system systemname. Without the IP address, the system cannot be monitored.
• Probable Cause / Recommended Action:
  The services to resolve the the target systemname to IP address may be unavailable. Please make sure that the command nslookup systemname' can be executed successfully.
  
  Alternatively, /etc/host file may be absent or corrupted.
  
  Alternatively, the systemname in the configuration file (/var/stm/config/tools/monitor/sysstat_em.cfg) could be wrong.
  
  Alternatively, there may be network problems.
  
  
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence
• Fault Notifier Event Generation Threshold: 1 occurrence

Event Details:
None.

Event 100002

• Severity: Information
• Event Summary:The system systemname is now responding to the monitor's query.
• Event Class: System
• Problem Description:
  This system will now be monitored.
• Probable Cause / Recommended Action:
  Previously this system was not responding to the monitor's query because of one of the following reasons :
  
  * system's name could not be resolved to IP address
  * the network was down or the network response was poor
  * the Online Diagnostic software was not present or was not running on it
  
  
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence
• Fault Notifier Event Generation Threshold: 1 occurrence

Event Details: None.

Event 100005

• Severity: Major Warning
• Event Summary: Failed to initialize STM UI on the current system.
• Event Class: System
• Problem Description:
  The monitor was not able to perform the initialization of the STM UI on the current system, in preparation for sending a message to the pre-determined port of diagmond on the systems to be monitored. No systems are being monitored.
• Probable Cause / Recommended Action:
  There were insufficient system resources on the STM User Interface (UI) system to complete the initialization. This may be an internal application error. Please refer to the STM System Activity Log for more detail.
  
  Also, make sure that /usr/sbin/stm can be run and the "system->sel system to test->connect to system.." command from the pull-down menu can be run successfully using the target host id.
  
  
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence
• Fault Notifier Event Generation Threshold: 1 occurrence

Event Details:
None.

Event 100006

• Severity: Major Warning
• Event Summary: Failed to initialize STM UI on the current system.
• Event Class: System
• Problem Description:
  The monitor was not able to perform the initialization of the STM UI on the current system, in preparation for sending a message to the pre-determined port of diagmond on the systems to be monitored. No systems are being monitored.
• Probable Cause / Recommended Action:
  The host_id parameter does not contain a valid information about the system on which the STM User Interface (UI) needs to be initialized. This is most likely due to an internal application error.
  
  Also, make sure that /usr/sbin/stm can be run and the "system->sel system to test->connect to system.." command from the pull-down menu can be run successfully using the target host id.
  
  
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence
• Fault Notifier Event Generation Threshold: 1 occurrence

Event Details: None.

Event 100007

• Severity: Major Warning
• Event Summary: Failed to initialize STM UI on the current system.
• Event Class: System
• Problem Description:
  The monitor was not able to perform the initialization of the STM UI on the current system, in preparation for sending a message to the pre-determined port of diagmond on the systems to be monitored. No systems are being monitored.
• Probable Cause / Recommended Action:
  The network connection between the STM User Interface (UI) system and the system to be monitored is down. When attempting to build a local IPC port, to communicate to the target system, an error was returned indicating that the network is down and the IPC facility is unusable as a result. Please contact your network system administrator.
  
  Also, make sure that /usr/sbin/stm can be run and the "system->sel system to test->connect to system.." command from the pull-down menu can be run successfully using the target host id.
  
  
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence
• Fault Notifier Event Generation Threshold: 1 occurrence

Event Details: None.

Event 100008

• Severity: Critical
• Event Summary: Failed to initialize STM UI on the current system.
• Event Class: System
• Problem Description:
  The monitor was not able to perform the initialization of the STM UI on the current system, in preparation for sending a message to the pre-determined port of diagmond on the systems to be monitored. No systems are being monitored.
• Probable Cause / Recommended Action:
  Initialization of the STM User Interface (UI) environment was not successful due to unexpected errors. This was needed to establish communication with the system to be monitored. This is most likely due to an internal application error.
  
  Alternatively, ensure that '/usr/sbin/stm' command can be successfully executed.
  
  
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence
• Fault Notifier Event Generation Threshold: 1 occurrence

Event Details: None.

Event 100009

• Severity: Critical
• Event Summary: Online Diagnostic software on the system at IP address <ip_address> is not responding to the monitor's query.
• Event Class: System
• Problem Description:
  The Online Diagnostic software (diagmond) is not responding on the system to be monitored. Without the help of the diagnostic software, the system cannot be monitored.
• Probable Cause / Recommended Action:
  The network connection between the host and the target system to be monitored is down. While attempting to send an IPC request the target system to get the information about OnLine Diagnostic software running on it, an error was returned, indicating the problem. Additional test using /etc/ping command indicated that the network may be experiencing problems or may be down.
  
  Alternatively, the system might have crashed or may be hung. Please investigate.
  
  Alternatively, the system might be down or temporarily shutdown. In that case, boot the target system.
  
  Alternatively, there may be some sort of problem on the path to the target system. In this case also, please contact your network administrator.
  
  Alternatively, the system may be in process of booting. If this is the case, these errors will stop being generated when the system is up.
  
  
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence
• Fault Notifier Event Generation Threshold: 1 occurrence

Event Details: None.

Event 100010

• Severity: Serious
• Event Summary: Online Diagnostic software on the system at IP address <ip_address> is not responding to the monitor's query.
• Event Class: System
• Problem Description:
  The Online Diagnostic software (diagmond) is not responding on the system to be monitored. Without the help of the diagnostic software, the system cannot be monitored.
• Probable Cause / Recommended Action:
  The network connection between the host and the target system to be monitored is down. While attempting to send an IPC request the target system to get the information about OnLine Diagnostic software running on it, an error was returned, indicating the problem. Additional test using /etc/ping command indicated that the network may be experiencing problems or there is heavy network traffic. In this case, please contact your network administrator.
  
  
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence
• Fault Notifier Event Generation Threshold: 1 occurrence

Event Details: None.

Event 100011

• Severity: Critical
• Event Summary: Online Diagnostic software on the system at IP address <ip_address> is not responding to the monitor's query.
• Event Class: System
• Problem Description:
  The Online Diagnostic software (diagmond) is not responding on the system to be monitored. Without the help of the diagnostic software, the system cannot be monitored.
• Probable Cause / Recommended Action:
  There were insufficient system resources on the target system to get the information about the OnLine Diagnostic software on it. This may be an internal application error. Please refer to STM system logs on the target system.
  
  
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence
• Fault Notifier Event Generation Threshold: 1 occurrence

Event Details: None.

Event 100012

• Severity: Major Warning
• Event Summary: Online Diagnostic software on the system at IP address <ip_address> is not responding to the monitor's query.
• Event Class: System
• Problem Description:
  The Online Diagnostic software (diagmond) is not responding on the system to be monitored. Without the help of the diagnostic software, the system cannot be monitored.
• Probable Cause / Recommended Action:
  In process of getting information about OnLine Diagnostic software on the target system, the monitor was informed that Diagmond on the local machine is going down. It must be restarted in order to successfully gather the information from the target system. Restart it by running STM
  
  
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence
• Fault Notifier Event Generation Threshold: 1 occurrence

Event Details: None.

Event 100013

• Severity: Major Warning
• Event Summary: Online Diagnostic software on the system at IP address <ip_address> is not responding to the monitor's query.
• Event Class: System
• Problem Description:
  The Online Diagnostic software (diagmond) is not responding on the system to be monitored. Without the help of the diagnostic software, the system cannot be monitored.
• Probable Cause / Recommended Action:
  In process of getting information about OnLine Diagnostic software on the target system, the monitor was unsuccessful due to unexpected errors.
  
  Alternatively, diagmond may not be running on the system. The system may be running in a single-user mode. In that case, transition the system into multi-user mode by using command '/etc/init 2'.
  
  Alternatively, the system may be in process of booting. If this is the case, these errors will stop being generated when the system is up.
  
  Alternatively, diagmond is hung on the system. Log on to the target system and ensure that /usr/sbin/stm can successfully be executed.
  
  Alternatively, the software may not be installed on the system. Use '/usr/sbin/swlist @ systemname or ip_address' command to find out if Online Diagnostic software is installed on the system. Without the help of the diagnostic software, the system cannot be monitored.
  
  Alternatively, the software may be improperly installed, in which case, re-install it.
  
  
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence
• Fault Notifier Event Generation Threshold: 1 occurrence

Event Details: None.