Knowledge Search


×
 

[Junos Space] How to configure e-mail notifications for events in the Network Monitoring Workspace

  [KB27090] Show Article Properties


Summary:

This article describes the issue of being unable to configure e-mail notifications for events in the Network Monitoring Workspace.

Symptoms:

The Network Application platform has integrated the OpenNMS third-party tool for monitoring purposes. It is a module that provides solutions for enterprises and carriers.

OpenNMS is installed as part of Platform, which exposes some of OpenNMS functionality via the Network Monitoring workspace. The default performance management configuration of OpenNMS for Space supports generic counters, CPU, memory, temperature, and mobility counters.

Currently, configuring e-mail notifications for various events being received by the Network Monitoring workspace is not straight forward.

Cause:

A few probable causes for this issue are as follows:

  • Issues with SMTP configuration

  • Issues with selecting the right UEI, when configuring event notifications

  • Issues with the Destination Path configuration

Solution:

First, the SMTP server should be configured and validated before configuring e-mail notifications in the Network Monitoring workspace.

Perform the following procedure:

  1. Log in to the Junos Space WebUI via the VIP.
  2. Go to Platform > Administration > SMTP Servers.

  3. Configure the SMTP Server Name, Host Address, Port Number, and From Email Address. Also, configure SMTP Authentication with the required credentials:

  1. When the details are configured, click the Test Connection button to verify that the connection is working. If the settings are correct, you should receive an e-mail, which confirms that the SMTP Server is working.

The next step is to configure a destination path with details of e-mail addresses and the format in which you want to be notified when Network Monitoring receives an event.

  1. Go to Platform > Network Monitoring > Admin > Configure Notification > Configure Destination Paths.
  2. Configure a new path by clicking the New Path button on the right window panel and providing the name, initial delay, and initial targets. Escalation is an optional configuration that must be configured only if you would want the notification to be escalated after a certain period of time.

  3. Click Finish.

The next step is to identify the event for which you want to be notified via e-mail. For better understanding, the example of a nodeDown event is being used here.

  1. Go to Platform > Network Monitoring > Admin > Configure Notification > Configure Event Notifications.
  2. Click the Add New Event Notification button on the right window panel.

  3. Select the nodeDown event (UEI) for which you want the notification to be enabled (in this example), and click Next:

  1. The settings on the next screen are optional. They are used to build a rule that determines if a notification is sent for this event based on the interface and service information that is contained in the event. This can be skipped by clicking the Skip results validation link, which is located at the bottom of the screen.

  2. The next screen is where the destination path is selected. The name of the destination path should be selected from the Choose a Path drop-down menu.

  3. Other customization can be done, such as changing the subject, contents of the e-mail, and so on. When complete, click Finish, which is located at the bottom of the screen:

  1. As the final step, the event notification switch should be On. Turn it On, if it is not:

  1. Another switch should be turned on in the main screen as well, as shown in the following screenshot. To do so, go to Platform - Network Monitoring - Admin. Click Update after turning on the switch:

By performing the above procedure, you should be able to get an e-mail notification in the address that is configured in the Destination Path whenever OpenNMS notes a nodeDown event for any of the devices that are being managed.

Modification History:

2019-09-04 Updated the KB with latest screenshots and added partner and customer to available groups since it was already Public

Related Links: