---

Send SMS from HP Openview using a command line exe

Video:		Send SMS from HP Openview (part 1/3, configure your modem)
Video:		Send SMS from HP Openview (part 2/3, configure HP Openview)
Video:		Send SMS from HP Openview (part 3/3, configure Ozeki NG SMS Gateway)

With the aid of HP Openview one can efficiently monitor the network applications and workstations. It provides an overall and detailed picture from the eventlog to the temperature of the processor. In addition to that it can supervise the availability of the computer. Rules can be configured fully and elaborate criteria can be added to them.

An exterior program can be conditioned to run when a rule completes, thus SMS sending can be integrated to HP Openview with the help of Ozeki NG SMS Gateway system. In practice it means that SMS notifications will be sent on various events occurred in your system. This solution also ensures receiving replies in a form of delivery messages. Please follow the installation guide's steps to ensure the proper functioning of this solution and know the services provided by it.

System requirements

In order to setup this solution you need to find a way to connect your system to the mobile network. You can do this by using an Internet connection or you can setup a wireless connection by attaching a GSM phone/GSM modem to your computer. To help you make a decision, we have prepared a webpage for you: Internet based SMS connections vs. GSM modem based (wireless) SMS connections. Depending on what you select, you need the following prerequisites.

Prerequisites for Internet based connection to the Mobile network

If you wish to connect your system to an SMS service provider over the Internet you need the following components:

Figure 1/a - Prerequisites for Ozeki NG SMS Gateway IP SMS connection

In this case you need to find an SMS service provider who can reach the mobile phones in your area. This SMS service provider should be able to provide SMS service through the Internet. To find such a provider, you can check our website where we list some of them: SMPP SMS Service providers. Once you have found such a provider, you need to sign up for their service to get the connection parameters. You can use these parameters to configure your Ozeki NG SMS Gateway software.

Prerequisites for wireless (GSM modem) connection to the Mobile network

If you wish to connect your system to the mobile network wirelessly, you need a GSM modem or GSM phone, that you can attach to your computer with a data cable. In this case your Ozeki NG SMS Gateway software will operate this phone and will send and receive SMS messages wirelessly. To setup this connection method, you need the following components:

Figure 1/b - Prerequisites for Ozeki NG SMS Gateway GSM modem connection

Your checklist (for GSM modem connection):

	SIM Card - You can get this from your local mobile network operator.*
	Modem - Use a Wavecom, Siemens or Multitech modem.
	Data cable - Comes with the modem
	Computer - Recommended: Intel P4 3Ghz Dual Core, 2 GB RAM, 500 Mb HDD
	Ozeki NG SMS Gateway - Download it from http://www.sms-integration.com
	HP Openview

*The SIM card will come with a plan, that will determine how much money you will spend on each SMS.

How SMS alerting works in HP Openview

When in the supervised IT infrastructure an alert occurs HP Openview creates a rule. This rule runs the "SendSMS.exe" program which forwards this report through the command line client to Ozeki NG SMS Gateway software. The gateway program then connects to the GSM modem or to an IP SMS connection and forwards the message to the SMSC (SMS center) of the service provider. Finally the mobile user receives the report generated by HP Openview to his or her cellphone (Figure 2).

Figure 2 - SMS alerts from HP Openview using Ozeki NG SMS Gateway

Installation guide for HP Openview SMS solution

Step 1 - Configuring HP Openview

First, you need to run HP Operations Manager Console and extend "Policy Management" view and then "Policy Groups" view, as well. After this, right click on "Policy Groups" submenu and select "New" menu and here click on "Policy Group" (Figure 3).

Figure 3 - Create new Policy Group

The newly created policy group appears in the "Policy Groups" list. Now you need to provide a name for it (e.g. Notification) (Figure 4).

Figure 4 - Policy Group name

Then right click on the created policy group and select "Windows Event Log" within "New" menu. In this way rules will be applied to this EventLog (Figure 5).

Figure 5 - New EventLog policy

In the pop-up window, specify the EventLog to be monitored (in this example: Application) then click on "Rules" tab (Figure 6).

Figure 6 - The monitored EventLog

On "Rules" tab click on the "New..." button (Figure 7).

Figure 7 - Add new rule

In the appeared window provide the criteria (in the example):

Rule Description: SMS Notification
Source: EventCreate
Type: Error.

When it is done click on "Actions" tab (Figure 8).

Figure 8 - Criteria for the rule

In the next window choose the "Active Msg. Browser and" menu item then click on "Automatic Command" tab (Figure 9).

Figure 9 - Automatic command

Type the following in the "Command" field:

"C:\Program Files\Ozeki\OzekiNG - SMS Gateway\SendSMS.exe" -h 127.0.0.1:9500 -u admin -p abc123 -r '+36301111111' -m Alert!_An_error_occurred_on_ <$MSG_NODE_NAME>._Log_source:<$LOGFILE>.

After "-h": provide the IP address of the computer on which Ozeki NG SMS Gateway has been installed.
After "-u": provide your username you use to log into Ozeki NG SMS Gateway. The default username in the program is "admin".
After "-p": enter your password used in Ozeki NG SMS Gateway.
"+36301111111" is the recipient phone,
<$MSG_NODE_NAME> will stand for the monitored computer and <$LOGFILE> is the log file's description.
The <$MSG_NODE_NAME> and the <$LOGFILE> are replaceable for any variables provided in the following table:

<$FULLNAME>	Returns the name of the policy and the source (concatenated with -). As defined for templates, this would return the same as <$NAME> This variable, along with <$NAME> and <$FULLNAME>, can be used in the field Program Name as follows so that when you are renaming a policy, you would not need to modify the Program name field. mymonitorscript.bat <$NAME>-<SRCNAME> mymonitorscript.bat <$FULLNAME>
<$MSG_APPL>	Returns the name of the application associated with the event that caused the message. Only events from the Open Message Interface (parameter: application) or the Windows Event Log (parameter: source) will set this variable. Sample output: /usr/bin/su(1) Switch User
<$MSG_GRP>	Returns the default message group of the message. Only events from the Open Message Interface (parameter: message_group) will set this variable. Sample output: Security
<$MSG_ID>	Returns the unique identity number of the message, as generated by the message agent. Note that identity numbers are not generated for suppressed messages. Sample output: 6e998f80-a06b-71d0-012e-0f887a7c0000
<$MSG_NODE>	Returns the IP address of the managed node on which the message originates. Sample output: 14.136.122.123
<$MSG_NODE_ID>	Returns the GUID that the management server assigned to the node on which the message originates. Because this value is only known by the management server, this variable cannot be resolved on the managed node. This variable is valid for the service_id message attribute and in the Command box for an automatic or operator-initiated command. Sample output: {6e998f80-a06b-71d0-012e-0f887a7c0000}
<$MSG_NODE_NAME>	Returns the name of the managed node on which the message originates. This variable is not fixed, however, and can be changed by a policy on a per-message basis. For example, if the policy is intercepting SNMP traps that originate from other devices, you might want to set this variable to the name of the device where the trap originated. If the policy is monitoring a logfile on a network share where applications on several nodes write messages, you could extract the name of the node from the error message, save it in a user-defined variable, and assign it to MSG_NODE_NAME.
<$MGMTSV_KNOWN_MSG_NODE_NAME>	Returns the name of the managed node on which the message originates. The management server resolves this variable to the node's hostname. This variable may be different to <$MSG_NODE_NAME>, which is the hostname that the agent resolves. You can use <$MGMTSV_KNOWN_MSG_NODE_NAME> in the following message attributes: Service ID Message Key Message Type Message Group Application Object Message Text CMA Name CMA Value Automatic Command Automatic Command Node Operator-initiated Command Operator-initiated Command Node This variable is useful in environments where management servers and agents resolve different hostnames for the same the node (for example, NAT environments).
<$MSG_OBJECT>	Delivers the name of the object associated with the event. Only events from the Open Message Interface (parameter: msg_object) and Windows Event Log (parameter: category) will set this variable.
<$MSG_SEV >	Returns the default value for the severity of the event. Only events from the Open Message Interface (default is "Normal') and the Windows Event Log (parameter: converted) will set this variable. Note that the following severity conversions are performed when this variable is set by the Windows Event Log: information=Normal, warning=Warning, error=critical, success audit=Normal, failure audit=Critical, default=unknown). Sample output: Normal
<$MSG_TEXT>	Returns the full text of the message. For the Open Message Interface, this value is the msg_text parameter. For the Windows Event Log this value is the event ID and description. In general, there are default texts for all editors derived from incoming event properties (this is shown in the message text field of outgoing message properties). Sample output: SU 03/19 16:13 + ttyp7 bill-root
<$MSG_TYPE>	Delivers the name set for Message Type.
<$NAME>	Returns the name of the measurement threshold policy or the scheduled task policy that sent the message. Sample output: cpu_util This variable, along with <$FULLNAME> and <$SRCNAME>, can be used in the field Program Name as follows so that when you are renaming a policy, you would not need to modify the Program name field. mymonitorscript.bat <$NAME>-<SRCNAME> mymonitorscript.bat <$FULLNAME>
<$OPC_GUI_CLIENT>	Returns the hostname of the client where the HP Operations GUI is currently running. This variable is valid in the Node box for an operator-initiated command and for message attributes.
<$OPC_GUI_CLIENT_WEB>	Returns the hostname and default web browser of the client where the HP Operations GUI is currently running. This can be used with an operator-initiated command to load a web page in the default browser on the HP Operations GUI client. This variable is valid in the node field for an operator-initiated command and for message attributes.
<$OPC_MGMTSV>	Returns the name of the current HP Operations management server. This variable is valid in the Command text box and in the Node text box for an automatic or operator-initiated command. This variable is only resolved on the management server. Sample output: zucchini.veg.com
<$OPTION(N)>	Returns the value of an optional variable that is set by opcmsg or opcmon (for example, $OPTION(A) $OPTION(B), and so on.).
<$SRCNAME>	Returns the name of the source for a policy. For a template, this would return an empty string. This variable, along with <$NAME> and <$FULLNAME>, can be used in the field Program Name as follows so that when you are renaming a policy, you would not need to modify the Program name field. mymonitorscript.bat <$NAME>-<SRCNAME> mymonitorscript.bat <$FULLNAME>
<$MSG_NODE_NAME>	Returns the name of the managed node on which the message originates. This variable is not fixed, however, and can be changed by a policy on a per-message basis. For example, if the policy is intercepting SNMP traps that originate from other devices, you might want to set this variable to the name of the device where the trap originated. If the policy is monitoring a logfile on a network share where applications on several nodes write messages, you could extract the name of the node from the error message, save it in a user-defined variable, and assign it to MSG_NODE_NAME.

Find further variables and additional information in Policy variables file.

In "Node" field you need to provide the application on which the command will run. By default it is the monitored computer (Figure 10).

Figure 10 - Automatic Command

Download SendSMS.exe

If you click on "OK" the created automatic command will appear in a window. In this window, click on "OK", as well (Figure 11).

Figure 11 - Created automatic command

At the bottom of the window you can see the entire text of the rule. Here click on "Save and Close" button (Figure 12).

Figure 12 - Created rule properties

You need to provide a name for the rule and this created rule will be seen in the rule list (Figure 13).

Figure 13 - Created rule

In order to come into operation, the rule needs to be installed on the monitored computer. To do so, right click on the created rule's name and click on "Deploy on" submenu in "All tasks" menu (Figure 14).

Figure 14 - Deploy rule

In the appeared window select the name of the monitored computer, then click on "OK" (Figure 15).

Figure 15 - Deploy policy on the managed computer

This step concludes the configuration of HP Openview. The next phase is to test the system.

Step 2 - Test the System of HP Openview SMS alert solution

For testing the system I will generate an Error in the "ApplicationLog", which will conform to the requirements of the rule created in the HP Operations Console.
To generate an Error the following command needs to be typed in the Windows command line:

eventcreate /T ERROR /ID 1000 /L APPLICATION /D "Test Alert"

(Figure 16).

Figure 16 - Eventcreate command

In the "Operation Console" expand "Node" view. Right click on the name of the computer, then choose "Active Messages" submenu in "View" menu (Figure 17).

Figure 17 - View active messages

The generated error can be seen with the name of "Critical" (Figure 18).

Figure 18 - Generated Error

Double clicking on the "Critical" log at the commands tab will show that the command has been successfully executed (Figure 19).

Figure 19 - Command properties

The message will be in the sent library of "admin" in Ozeki NG SMS Gateway (Figure 20).

Figure 20 - Sent message

In order to implement this solution, please go to the download page to download Ozeki NG SMS Gateway >>>

More information

• Send SMS in HP Openview with text file

---