- Welcome page
- Solutions
- SMS from CRM
- SMS from Communication Softwares
- System Monitoring
- SCOM 2007/2012
- MOM 2005
- WhatsUp Gold
- IBM Tivoli
- Big Brother
- BMC
- CA Unicenter
- Nagios SMS
- Nagios XI
- Zenoss
- Zenoss 5
- Active Directory Integration
- Solarwinds Orion NPM
- Solarwinds Orion NPM 11.5.3
- E-mail-to-SMS gateway solution for GpsGate
- HP NNM
- SMS from CMS
- Helpdesk
- OTP
- SMS from Cloud
- Ozeki NG Interface
- SMS payment link
- Applications
- SMS Examples
- Products
- Contact
Ozeki brings you outstanding
SMS Gateway technology. Use our SMS Server products on Windows,Linux, or Android
C# SMS API
Developers can use our C# SMS API to send SMS from C#.Net. The C# SMS API comes with full source code
PHP SMS API
The ozeki PHP SMS gateway software can be used to send SMS from PHP and to receive SMS usig PHP on your website
SMPP SMS Gateway
SMS service providers use our SMPP gateway solution, that offers a high performance SMPP server and SMPP client gateway with amazing routing capabilities
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:
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. |
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. |
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. |
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. |
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. |
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: 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, |
$<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.
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: 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, 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
More information
- What is the best way to send SMS in SCOM 2007/2012
- Sending SMS alerts from MOM 2005
- 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 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