25 February 2010

OpsMgr SMS Notification with SysMan Integration - Part 5

In the final chapter of my 5-part series, I would like to share

what I would want to share is to trigger the notification channel on alert certain instances and target groups. You wouldn't want you Handphone to be bombarded with SMSes that is totally non-critical right.

In my example:
I will only trigger SMS alerts when certain the OpsMgr detected Health Service failures on business critical servers that is being monitored.

From the Operations console, navigate to Administration -> Notifications -> Subscription and select New -> Subscription

In the Notification Subscription Wizard, enter a name for the subscription and click Next

In the subscription criteria page, provide your filtering criteria and click Next to proceed

In the Subscriber page, add the subscriber that you have created earlier (please refer to Part 4 of this posting series if you missed out on the creating subscriber part). Click Next to proceed

In the notification channel page, add the notification channel that you have created earlier
(again... please refer to Part 4 of this posting series if you missed out on the creating subscriber part).

Finally, check the Enable this notification subscription checkbox and click Finish

OpsMgr SMS Notification with SysMan Integration - Part 4

A quick recap on what was covered so far, we have gone through:
  • Setting Up of Serial Over IP device that communicates with the GSM Modem device
  • Setting Up Port Mapping from OpsMgr server to the Serial Over IP device
  • Setting Up & Configure SysMan SMS Notification Server

In this chapter of my 5-part series, I will touch on the integration piece between OpsMgr & SysMan SMS Notification server.

From the operator console, navigate to the Administration space.

Go to Administration -> Notifications -> Channel

Right click on Channel and select New channel -> Command

In the Command Notification Channel Window, enter the name for the channel and click Next to proceed.

In the Settings page;

For the Full path of the command line field; enter the path where you SysManSMS_IClient.exe resides in.
(eg: %Program Files%\SysManSMS\Iclient\SysManSMS_IClient.exe)

In the command line parameters field, enter the .lst file to send the SMS to your intended audience and the contents of your SMS.
(eg: MyUserList.lst $Data/Context/DataItem/AlertName$)

In the StartUp folder for the commandline field, enter the folder which your SysManSMS_Iclient.exe resides in
%Program Files%\SysManSMS\Iclient\)

Once the configuration is completed, click Close.

Right click on Administration -> Notification -> Subscriber and select New Subscriber

In the Notification Subscriber Wizard, enter a user name and click Next

In the schedule page, select Always send notifications or you can configure the schedule for the notifications to be sent
(eg: you wouldn't want the SMS to come in the middle of your good sleep)

Click Next to proceed

In the Addresses page, click on the Add button to launch the Subscriber Address wizard

In the Subscriber Address wizard, enter a name for the Address.

In the channel page of the wizard, select Command as the Channel Type

For the Command Channel, select the notification channel that you have created earlier.

In the schedule Notifications, configure your preferred notification schedule and click Next

Back in the Subscriber Addresses page, click Finish

Click Close once the process is complete

The steps above literally means that we have configured OpsMgr to be able to send SMS notifications to intended recipients (that was defined in the .lst file) which is done through executing SysManSMS_Iclient.exe with the necessary parameters passed in.

01 February 2010

OpsMgr SMS Notification with SysMan Integration - Part 3

In this posting, I shall share on how to install & configure SysMan SMS Server to work with the Serial-Over-IP device that we have configured earlier.

A quick recap on what was being shared in my previous postings; our OpsMgr SMS notification system consists of 3 major components being:

  1. GSM Modem device - sends SMS notification to OpsMgr administrators
  2. Serial-Over-IP device - a bridge that connects to the GSM device via serial port and at the same time connected through COM Port mapping on the OpsMgr server
  3. OpsMgr server that triggers SMS notification commands the moment critical alerts are detected in the server.
Now we have successfully configured the Serial-Over-IP device as well as mapping it to a COM port in OpsMgr server; the next thing that we need to do is to configure SysMan SMS server to communicate with the GSM device via the Serial-Over-IP device.

Run the Installation Setup application from the SysMan installer CD. In the Setup.exe prompt; click Setup to kickstart installation & configuration of the application.

In the Installation Properties window, select the installation location and tick the Installation Type as Server - Require GSM hardware option.

Once you are ready; click on the Install button

In the SMS Server Properties window; enter your Company Name and the License Number.

You will also need to enter the Device Port to map the COM port number that you have assigned to your Serial-Over-IP device earlier.

Once you are done; click

Once you are done; start the SysMan Service by right clicking on the icon in the System Tray and select

Server Settings -> Start SysMan Service.

The next step that we will need to configure is to enter the necessary phone numbers which SysMan will send SMS notifications to.

Right click the SysMan systray icon and select Edit Number Files

In the window, click New and add the Contact Number information for your target numbers which SysMan will send notifications to. Once you are done; you can save the Number files into a location folder.

In my scenario here; I have saved it to a file call CPOC.lst file

Now that we had our core components readily installed & configured, the next posting will finally show how we can configure OpsMgr to send SMS notification to Administrators via SysMan SMS Gateway Server.