Cannot Send Monitoring Notifications From the Enterprise Service Manager

Document ID : KB000057586
Last Modified Date : 28/02/2018
Show Technical Document Details
  • In some circumstances, an email may not be received by the intended recipient and a notification will not appear to be transmitted from the Enterprise Service Manager ("ESM")¬†platform at all.
  • A packet capture will not show that an SMTP, SNMP, or HTTP notification leaves the ESM platform.
  • The intended recipient may not receive said email, trap, or HTTP request.
The ESM is capable of triggering alerts if certain monitoring conditions are met or exceeded. For example, the ESM can initiate signalling that indicates CPU utilization has been exceeded, the number of audit records is over a certain value, or if a node is online or offline. In order to facilitate centralized monitoring, the Enterprise Service Manager enables an administrator or operator to configure a Gateway to send notifications to an individual or group if certain conditions are met. The above behaviour is intended as the ESM platform is not responsible for actually sending the alerts. The ESM platform merely instructs the impacted node or cluster to send a request.
To enable a node or cluster to send SMTP, SNMP, or HTTP notifications, you must ensure that the required port is opened between the impacted node and the destination system. For example, port 25 would need to be opened between the Gateway and the mail transfer agent for unencrypted email. Alternatively, port 161 would need to be opened between the Gateway and the SNMP trap recipient for SNMP transactions. These port designations will vary based on implementation and an administrator or operator will need to consult with the system administrator for the desired application to determine the proper port.