This screen catalogs the actions configured for the Post-Processing (Automation) rule you have configured in previous screens.

Click Add Action to create a new action in the editor. The Actions column lets you revise (Edit this entry) or Delete entries in this table. Click Save to preserve the action(s) configured here, or Cancel to abandon any edits.

Clicking Add Action lets you select from the following:


Forward Northbound


Click Apply to accept configured actions, or Cancel to abandon their editor and return to this screen.

Actions available here are like those for Discovery Profiles. You can also use actions to Execute Proscan. See Change Management / ProScan.


This screen lets you configure Action based on Adaptive CLI actions available in the system. Notice that you can select by most common or by keyword search, depending on which of the links in the upper right corner of the screen you select.

The most common actions include those you have used most recently. To search for actions, either enter a keyword, or click the search icon (the magnifying glass) to produce a pick list below the Action field. Select an action by clicking on its appearance in that list.

Select the device target of the custom action by selecting from the Target pick list. If you do not specify an explicit target, Open Manage Network Manager uses the default entity for the event as the target.

If you want to select an action with additional parameters, those parameters appear in the screen below the Target field. To see definitions for such parameters, hover the cursor over the field and a tooltip describing the field appears.

You can specify parameter variables, dependent on the specifics of the event, rule, and selected targets. Do this with either NOTIFICATION or VARBIND.

The following are valid attributes to use in a phrase like [[NOTIFICATION: <attr name>]]:

• TypeOID

• AlarmOID

• EntityOID

• EquipMgrOID

• DeviceIP

• SourceIP

Consult the relevant portlet to find and verify an OID. For example, Event Definitions portlet has an OID column, and the varbind OIDs appear in the Message Template screen of the event editor.

Correct spelling is mandatory, and these are case sensitive. NOTIFICATION and VARBIND must be all caps, and within double brackets. The colon and space after the key word are also required.

Open Manage Network Manager converts anything that conforms to these rules and then passes the converted information into the action before execution. Anything outside the double square brackets passes verbatim.

For example, the string:

This is the alarm OID [[NOTIFICATION: AlarmOID]] of notification type [[NOTIFICATION: TypeOID]] having variable binding [[VARBIND:]]

becomes something like...

This is the alarm OID 1OiE92tUjll3G03 of notification type having variable binding 151.

Click Apply to accept your edits, or Cancel to abandon them.


Email actions configure destinations and messages for e-mail and SMS recipients. You can include fields that are part of the event by using the variables described in Email Action Variables.

Notice that below the Description of the e-mail action, you can check to send this mail (and/or SMS) to associated Contacts, if any are available, even if you specify no mail address destination. The SMS tab is similar to the e-mail tab, but limits the number of characters you can enter with a field at its bottom. You must send SMS to the destination phone carrier’s e-mail-to-SMS address. For example sending text to 916-555-1212 when Verizon is the carrier means the destination address is

When enabled, notification emails go to the Contact associated with the Managed Equipment for the notification event. For the contact's email address, mail goes to the first specified address from either the Work Email, Home Email or Other Email fields in the Contact editor. SMS messages go to the Pager Email field for the contact. If a Contact was not found or the required addresses are not specified for the Contact, then Open Manage Network Manager uses the Recipient addresses configured in the Email Action.

Programs other than Open Manage Network Manager let you manipulate mail outside the scope of Open Manage Network Manager. For example IFTTT (If This Then That) lets you send SMS in countries whose providers do not provide e-mail equivalents to SMS addressing. You can also use such applications to save mail attachments like reports to Dropbox accounts.

This screen has the following fields:

Recipient Addresses -- Enter an e-mail address in the field below this label, then click the plus (+) sign to add it to the list of recipients. The minus (-) removes selected recipients.

Subject -- The e-mail subject.

Email Header / Footer -- The e-mail’s heading and footing.

SMS Body -- The e-mail contents to be sent as text.

SMS Max Length -- The maximum number of characters to send in the SMS. Typically this is 140, but the default is 0, so be sure to set to your carrier’s maximum before saving.

Here is what Email looks like when it arrives:

Sent: Wednesday, March 02, 2011 2:37 PM


Subject: Web Test

Notification: redcellInventoryAttribChangeNotification

Notification Attributes:


sysUpTime.0 = 5 hours, 16 mins, 43 secs

snmpTrapOID.0 =

redcellInventoryAttrName.0 = RedCell.Config.EquipmentManager_Notes

redcellInventoryAttrChangedBy.0 = admin

redcellInventoryAttrNewValue.0 = hello




redcellInventoryAttrOldValue.0 = hello



Forward Northbound

When you want to forward an SNMP v2 event (trap) to another host, then configure automation in this screen to do that.

Enter the following fields:

Destination Address -- The IP address of the northbound destination.

Destination Port -- The port on the northbound destination.

Community String -- The SNMP community string for the northbound destination.

Send as Proxy -- When checked, this sends the IP address of the application server as the source of the event. Unchecked, it sends the IP address of the source device. (See Send as Proxy for more.)

For details of trap forwarding, see the Trap Forwarding Process.