The nimalarm command provides a method of publishing alarms onto the UIM message bus.
It can be used to forward events from HPOMU/OpenView to UIM.
• In HPOV, select Options-> Event Configuration -> snmpTraps ->SNMP_Link_Down (Double-click)
Command for Automatic Action:
nimalarm -s "1.1.3" -S $A -l 5 "Interface Down ($1)"
Note that you MUST install a UIM Robot (agent) to be able to access and use the nimalarm function from the Management server node. nimalarm is located in the installation directory ->bin AND you must setup an Automatic Action for each alarm you want to send to UIM. For example:
C:\Program Files (x86)\Nimsoft\bin\nimalarm <arguments>
...\Program Files\Nimsoft\bin>nimalarm.exe -?
usage: nimalarm [options] message-string
You can see the effects of the different options by setting them and looking at the alarm with the DrNimbus tool on the primary hub. nimalarm can be executed from the command line for testing as well to make sure its working from that node.
C:\Program Files (x86)\Nimsoft\bin>nimalarm -l 5 -c test-0512-01 -S server1 -i "This is a TEST alarm"
nimalarm is similar to HP's opcmsg commands in some ways.
Simplest usage is:
ALL options are optional. More detailed explanations below:
Sets the alarm severity.
Sets the subsystem ID.
Sets the suppression key.
Sets the internal debug level (ie. loglevel) of the utility.
Sets the source/hostname alarm fields.
Makes the utility print the nimid of the generated alarm.
Sets the custom fields 1 through 5.
Needs to be set together, decides the CI device ID.
The CI metric ID.
The alarm token, fills the udata->token field in the alarm PDS. Used for e.g. UMP for fetching internationalized alarm messages.
Sets values to be used in above mentioned internationalized alarm messages. See the properties files in the wasp/i18n directory for examples on how these are used.
In HPOV, select Options-> Event Configuration -> snmpTraps ->SNMP_Link_Down (Double-click) Command for Automatic Action: nimalarm -s "1.1.3" -S $A -l 5 "Interface Down ($1)"