Nodeum sends notifications when specific events occur.
The notifications services can be sent either via :
- SNMP Trap.
Both can be configured to send information and alerts to notify specific misusage or misconfiguration of the software.
1- Email Notifications
Send automatically an email alert to specify recipients when an event occurs.
Email notifications include specific information to describe the alert.
Once you have configured the notification services, Define for each users the the level of severity that will trigger the email notification. You have also the option to activate or deactivate the notification.
Go to the menu System / Notifications and then go to Email tab.
Two sections are available on this page, the first section (Email notifications) has to be filled in on time. The second one (Email recipients) is where the different recipient has to be configured.
Different configurations can be done. Either you have your own ISP SMTP Relay, either you can use a Microsoft Office 365 SMTP relay or Gmail SMTP relay depending of your email provider.
Configuration : ISP SMTP relay
|Hostname||smtp.smtprelay.com (which the SMTP relay server of the ISP provider)|
|From Email address||any type of email address|
|User Name||empty if your SMTP server doesn’t required any authentication|
|Password||empty if your SMTP server doesn’t required any authentication|
Configuration : Microsoft Office 365 SMTP relay
|From Email address||this has to be an email address which is recognized into your Office 365 account.|
|User Name||This has to be an authorized email address from your Office 365 organization.|
|Password||This is the password linked to the Username specified below.|
Configuration : Google Mail SMTP relay
Prerequisite: Request a Google App Passwords. This can be found in connecting to your Google account and access this url: https://myaccount.google.com/apppasswords. The App passwords you have generated will be used as password in the Nodeum SMTP relay configuration.
|From Email address||this has to be an email address which is recognized into your Google Mail account.|
|User Name||This has to be an authorized email address in your Google Mail organization.|
|Password||For passwords, it is required to create an App password in Google portal. This will allows to by pass the 2FA mechanism.|
For each user, activate if needed the email address and define the level of notification you will receive. See Point 3 for the level definition.
2- SNMP Notifications
Simple Network Management Protocol (SNMP) is a communication protocol that enables network administrators to manage network equipment, monitor and diagnose network and hardware problems remotely. Nodeum allows to send SNMP trap to SNMP collector(s).
You can set up an email notification in going to the menu System / Notifications and then go to SNMP tab.
Two sections are available in this page, the first section (SNMP server configuration) is the SNMP configuration of the server which hosts Nodeum. The second one (Trap Destination List) is the section where the Trap configuration is defined.
SNMP server configuration
The following parameters are required to define the host SNMP configuration:
|Version||This the SNMP version you want to configure.|
|Community||The community string you want to use; by default public should be used.|
|System Location||This is not mandatory but can be useful to define the solution location.|
|System Contact||This is not mandatory but can be useful to define the solution point of contact.|
Trap Destination List
This topic describes the steps to configure SNMP. You can add or remove an SNMP trap destination for SNMP traps and configure threshold and alarms for SNMP traps.
SNMP traps are typically sent to a Network Management System or to an Infrastructure Monitoring System.
To add a new Trap destination, you can add Trap recipients in this section in clicking on the '+' button:
Enter the following information
|Hostname or IP address of the server where the trap has to be sent.|
|The community string which is configured in your trap handler software.|
|SNMP version which is supported by your trap handler software.|
|Define the level of severity that will trigger the SNMP trap messages. (see point 3)|
3- Definitions of Level of Severity
This is a specific message which is triggered by the system to notify users about an action status.
NB: It is required to activate the level 0 to receive the notification when a task is finished.
A message of this severity is for information purposes only; no error was detected and no reply is needed. The message could indicate that a function is in progress or that it has reached a successful completion.
A message of this severity indicates a potential error condition. The software may have taken a default, such as supplying missing input. The results of the operation are assumed to be what was intended.
An error has been detected, but it is one for which automatic recovery procedures probably were applied, and processing has continued. A default may have been taken to replace input that was in error. The results of the operation may not be valid. The function may be only partially complete; for example, some items in a list may be processed correctly while others may fail.
The error detected is too severe for automatic recovery, and no defaults are possible. If the error was in source data, the entire input record was skipped. If the error occurred during program processing, it leads to an abnormal end of the program (severity 4). The results of the operation are not valid.
|5||Abnormal End of Program or Function||
The operation has ended, possibly because it was unable to handle invalid data, or possibly because the user ended it.
|6||Abnormal End of Task||The task was ended or was not started. A routing step may have ended abnormally or failed to start, a job-level function may not have been performed as required, or the job may have been ended.|
|7||System Status||A message of this severity is issued only to the system operator. It gives either the status of or a warning about a device, a subsystem, or the whole system.|
|8||Device Integrity||A message of this severity is issued only to the system operator. It indicates that a device is malfunctioning or in some way is no longer operational. You may be able to restore system operation, or the assistance of a service representative may be required.|
|9||System Alert||A message of this severity is issued only to the system operator. It warns of a condition that, although not severe enough to stop the system now, could become more severe unless preventive measures are taken.|
|10||System Integrity||A message of this severity is issued only to the system operator. It describes a condition that renders either a subsystem or the whole system inoperative.|
Let Us Know What You Thought about this Post.
Put your Comment Below.