Configure SMS alerts for HP Network Node Manager

This guide explains in details how you can setup Ozeki NG SMS Gateway with HP Network Node Manager to send SMS alerts effectively. Follow the configuration guide to start to setup your system right now.

HP Network Node Manager can be configured to send notifications in cases when there are any changes in the IT network. Now this useful application can be further improved by adding SMS technology to it.

When you introduce Ozeki NG SMS Gateway, you will be able to configure your system to send SMS alerts if there is any change in the network.

Configuration steps for HP NNMI SMS solution

In HP NNMI you can create an action for cases when there is a problem with the network, for example, if the server is not available for some reason. For these cases you can also specify some conditions. If these conditions are fulfilled, then the action will be triggered.

When the created action occur, SendSMS.exe will be executed in your system and Ozeki NG SMS Gateway will also send an SMS alert to the predefined phone number (Figure 1).

Figure 1 - SMS is sent from HP NNMI via Ozeki NG

Got to the web interface of HP NNMI (it is available via port 8004). Click on Launch NNMI Console (Figure 2).

Figure 2 - Launch NNMI Console

Log into HP NNMI as system (Figure 3).

Figure 3 - Login

After login click on Configuration menu item (Figure 4).

Figure 4 - Click Configuration

In Configuration menu expand Incidents menu item and click on Management Event Configurations (Figure 5).

Figure 5 - Management Event Configurations

In Management Event Configurations window you can create a new one by click on the Star icon in the toolbar (Figure 6).

Figure 6 - New Management Event Configurations

In the appeared window you can specify the Name, the Category, Family and Severity of the incident (Figure 7).

Figure 7 - Specify details for the created incident

In the right section of the same window click on Actions tab. Check Enable checkbox and click on the Star icon to create a new action (Figure 8).

Figure 8 - Create new action

In the appeared window you can specify the follows:
LifeCycle State: set this option as your system requires.

Command Type: ScriptOrExecutable

Command: SendSMS.exe -h 127.0.0.1:9500 -u admin -p abc123 -r "+36201234567" -m "Hello world"

Parameters:

-h Hostname and port of Ozeki NG SMS Gateway (Mandatory)
-u Username
-p Password
-r Recipient address
-m Message text

Finally click on Save and Close (Figure 9).

Figure 9 - Specify parameters

You can us the following variables in your command:

Valid Parameters Visible From an Incident's Form

Parameter Value	Description
$category, $cat	Value of the Category attribute in the Incident form.
$count, $cnt	Value representing the number of Custom Incident Attributes that appear in the Incident form.
$family, $fam	Value from the Family attribute in the Incident form.
$firstOccurrenceTime, $fot	Value from the First Occurrence Time attribute in the incident form.
$lastOccurrenceTime, $lot	Value from the Last Occurrence Time attribute in the incident form.
$lifecycleState, $lcs	Value from the Lifecycle State attribute in the Incident form.
$name	Value of the Name attribute from the incident configuration.
$nature, $nat	Value from the Nature attribute in the Incident form.
$origin, $ori	Value from the Origin attribute in the Incident form.
$originOccurrenceTime, $oot	Value from the Origin Occurrence Time attribute in the incident form.
$priority, $pri	Value from the Priority attribute in the Incident form.
$severity, $sev	Value of the Severity attribute of the Incident form.

The function described in the following table replaces the specified numeric value with the associated text value stored in the CIA.

Note: The associated MIB must have been loaded using the nnmloadmib.ovpl command.

Under LifeCicle Transition Actions you can see the created action in Management Event Configurations. Click Save and Close again (Figure 10).

Figure 10 - Save settings