---

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.

 

Valid Parameters Visible from a Node Form

Parameter Value	Description
$managementAddress, $mga	Value from the Management Address attribute of the incident's source Node's form or SNMP Agent form.
$otherSideOfConnectionManagementAddress, $oma	If the incident's Source Node is part of a Layer 2 connection, this attribute is the value of the Management Address of a node on the other side of the Layer 2 connection.
$sourceNodeLongName, $sln	The fully-qualified DNS name as displayed in the Hostname attribute of the incident's source Node's form.
$sourceNodeName, $snn	Value from the Name attribute of the incident's source Node's form.
$sysContact, $sct	Value from the System Contact attribute of the incident's source Node form: General tab.
$sysLocation, $slc	Value from the System Location attribute of the incident's source Node form: General tab.

 

Valid Parameters Visible from an Interface Form

Parameter Value	Description
$ifAlias, $ifa	Value from the IfAlias attribute for the interface that is the incident's source object.
$ifConfigDupSetting, $icd	Configured Duplex Setting on the port associated with the interface that is the incident's source object.
$ifDesc, $idc	Value from the ifDesc attribute for the interface that is the incident's source object.
$ifIndex, $idx	Value from the ifIndex attribute for the interface that is the incident's source object.
$ifIpAddr, $iia	IP Address values associated with the interface that is the incident's source object. If multiple IPaddresses are associated with the interface, this parameter returns a comma-separated list.
$ifName, $ifn	Value from the ifName attribute for the interface that is the incident's source object.
$ifPhysAddr, $ipa	Value from the Physical Address attribute for the interface that is the incident's source object.
$ifSpeed, $isp	Value from the ifSpeed attribute for the interface that is the incident's souce object.
$ifType, $itp	Value from the ifType attribute for the interface that is the incident's souce object.

 

Valid Parameters Visible from a Layer 2 Connection Form

Parameter Value	Description
$otherSideOfConnectionConfigDupSetting, $ocd	If the incident's source Node is part of a Layer 2 connection, this parameter contains the Configured Duplex Setting on the port associated with the interface on the other side of the connection.
$otherSideOfConnectionIfAlias, $oia	If the incident's Source Node is part of a Layer 2 connection, this parameter is the value of the ifAlias of one of the interfaces on the other side of the Layer 2 connection.
$otherSideOfConnectionIfDesc, $odc	If the incident's Source Node is part of a Layer 2 connection, this parameter contains the ifDescr attribute value for the interface on the other side of the Layer 2 connection.
$otherSideOfConnectionIfIndex, $odx	If the incident's Source Node is part of a Layer 2 connection, this parameter contains the ifIndex attribute value for the interface on the other side of the connection.
$otherSideOfConnectionIfName, $ofn	If the incident's Source Node is part of a Layer 2 connection, this parameter contains the ifName attribute value for the interface on the other side of the connection.

 

Valid Parameters Visible from a VLAN Form

Parameter Value	Description
$impVlanIds, $ivi	Value from the VLAN Id attribute associated with the interface that is the incident's source object. To access this information from an interface form, navigate to the VLAN Port tab and open the form for the VLAN of interest. If the interface is part of more than one VLAN, this parameter returns a comma-separated list.
$impVlanNames, $ivn	Value from the VLAN Name attribute associated with the interface that is the incident's source object. To access this information from an interface form, navigate to the VLAN Ports tab of the Interface form. If the interface is part of more than one VLAN, this parameter returns a comma-separated list.

 

Valid Parameters Not Visible From a Form

Parameter Value	Description
$id	Unique Object Identifier attribute value for the incident (unique across the entire NNMi Database).
$firstOccurrenceTimeMS, $fms	Value from the First Occurrence Time attribute in the incident form, converted to millseconds (measured since January 1, 1970, 00:00:00 GMT - Greenwich Mean Time).
$lastOccurrenceTimeMS, $lms	Value from the Last Occurrence Time attribute in the incident form, converted to millseconds (measured since January 1, 1970, 00:00:00 GMT - Greenwich Mean Time).
$messageFormat, $msg	Valid for Incident actions only. Message text displayed for an incident when this parameter is included as an argument to an incident action.
$oid	Value of the unique object identifier (oid) for the incident configuration that originated from either an SNMP trap, Management Event, or Remote NNM 6.x or 7.x event.
$otherSideOfConnection, $osc	If the incident's Source Node is part of a Layer 2 connection, this attribute is the following combination of values for the node and one of its interfaces on the other side of the Layer 2 connection: The fully-qualified DNS name of the node appended with the interface Name in the following format: <fully-qualified DNS name>[interface_name]
$originOccurrenceTimeMS, $oms	Value from the Origin Occurrence Time attribute in the incident form, converted to millseconds (measured since January 1, 1970, 00:00:00 GMT - Greenwich Mean Time).
$sourceNodeUuid, $snu	Universally Unique Object Identifier attribute value of the source node object for the incident (unique across all databases). This identifier distinguishes the source node object instance from all other node objects.
$sourceObjectClass, $soc	Value of the object class for the object you want to include. Use this parameter when you need to request more details of a class of objects through a web service. Examples of object classes include: com.hp.ov.nms.model.core.Interface and com.hp.ov.nms.model.snmp.SnmpAgent.
$sourceObjectName, $son	Value from the Name attribute of the source object. For example, an interface object is named according to the MIB ifName. Each ifName varies according to the vendor's conventions. Using the name 4/1 as an example, 4 represents the board number and 1 represents the port number.
$sourceObjectUuid, $sou	Universally Unique Object Identifier attribute value of the source object for the incident (unique across all databases). This identifier distinguishes the source object instance from all other similar object instances..
$uuid	Universally Unique Object Identifier attribute value of the incident (unique across all databases). This identifier distinguishes the incident object instance from all other incident objects.

 

Valid Parameters Established in Custom Incident Attributes

Parameter Value	Description
$<position_number>	Value of the custom incident attribute (CIA) position number for any CIA that originated from a varbind or was added by NNMi. For example, to indicate you want to use the varbind in position 1, enter: $1 NNMi stores varbind values as Custom Incident Attributes. If you know the varbind position number, use this parameter.
$<CIA_name>	Value of the name that is used for the custom incident attribute. For example, $mycompany.mycia. NNMi provides CIA values for configuring Management Events. See Custom Incident Attributes Provided by NNMi for more information about custom incident attributes.
$<CIA_oid>	Value of the object identifier for any custom incident attribute that originated as a varbind. For example, $.1.3.6.1.6.3.1.1.5.1. Use this parameter when you are not certain of a custom incident attribute (varbind) position number.
$*	Used to indicate you want all of the custom incident attribute values originating as varbinds, to be passed to the action configuration. Each varbind is returned in the following format: $<CIA_name>:<CIA_value> in which the custom incident attribute name appears followed by the custom incident attribute value.

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.

 

Functions to Generate Values Within Incident Messages

Function	Description
$text($<position_number>)	The <position_number> argument specifies the numeric value of the custom incident attribute (CIA) position number for any CIA that originated from a varbind or was added by NNMi. For example, to indicate you want to use the varbind in position 1, enter: $1. After the function runs, NNMi replaces the numeric value with the text value stored in the CIA. Note: If a text value is not available, NNMi returns the numeric value.
$text($<CIA_oid>)	The <CIA_oid> argument specifies the object identifier for any custom incident attribute that originated as a varbind. For example, $.1.3.6.1.6.3.1.1.5.1. Use this argument to the $text function when you are not certain of a custom incident attribute (varbind) position number. After the function runs, NNMi replaces the numeric value with the text value stored in the CIA. Note: If a text value is not available, NNMi returns the numeric value.

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

For more information or assistance please contact us at info@ozekisms.com!

More information

• What is the best way to send SMS in SCOM 2007/2012
• Sending SMS alerts from MOM 2005
• How to send SMS from HP Openview
• How implement SMS in WhatsUP Gold
• How to connect to IBM Tivoli to SMS Service
• How to update SMS connection in Big Brother
• Workaround for SMS sending in BMC Performance Manager
• How to implement SMS solutions into CA Unicenter NSM
• How to send SMS from HP Systems Insight Manager
• How to send alert SMS from Nagios
• Nagios XI
• Alert SMS messaging with Zenoss
• Alert SMS messaging with Zenoss 5
• How to send SMS text messages to Active Directory users
• Implement SMS alerts into Solarwinds Orion Network Performance Monitor
• Solarwinds Orion NPM 11.5.3
• E-mail-to-SMS gateway solution for GpsGate

---