Technical data

Example: Disabling all Alarm Dial-outs Except a Specified Alarm
To enable the dial-out of a specified alarm (for example, Too Many Router Port Errors)
but disable the dial-outs of all other alarms, add the following lines to the OSMCONF file:
disableAllDialout = YES
enableDialout = Too Many Router Port Errors
Example: Disabling all Alarm Dial-outs Except an Alarm with a Specified Prefix
To enable the dial-out of an alarm (for example, Loss of ServerNet Fabric X for
Processor 3), with a specified prefix (for example, Loss of ServerNet Fabric) but disable
the dial-outs of all other alarms, add the following lines to the OSMCONF file:
disableAllDialout = YES
enableDialoutPrefix = Loss of ServerNet Fabric
You can re-enable remote notifications (dial-outs) by removing disableAllDialout = YES
from the OSMCONF file and then run Reload Configuration Settings or restart CIMOM. This will not,
however, cause alarms generated prior to this point to dial-out.
Suppressing Specific Alarms
With OSM version T0682 H02 ABV and later, you can specify that a specific alarm not be created
or dialed out for that system through use of the NoAlarm OSMCONF parameter, as follows:
NoAlarm = alarm_description
Where alarm_description is the exact description of the alarm as displayed in the alarm description
field.
For example, if you do not want the Loss of Running Processor alarm to be created or
dialed out, place the following setting in your OSMCONF:
NoAlarm = Loss of Running Processor
With OSM version T0682 H02 ABZ and later, the NoAlarm OSMCONF parameter is enhanced,
allowing you to suppress alarm creation and dial out for a specific resource. By adding a specific
resource name in parentheses following (separated by a space) the alarm description, you would
suppress the alarm only on that resource. In the example above, the Loss of Running
Processor alarm would be suppressed on all Logical Processors on the system. However, by
adding the name of a specific resource, as shown below, you suppress that alarm only on that
Logical Processor.
NoAlarm = Loss of Running Processor (Logical Processor 4)
You must specify the resource name as shown in the OSM Service Connection. In another example,
to suppress the Loss of ServerNet Fabric X alarm on Node (1.4), the OSMCONF setting
would be:
NoAlarm = Loss of ServerNet Fabric X (Node (1.4))
To make changes to your OSMCONF file take effect, see “Creating and Using an OSMCONF
File” (page 15). To remove this type of suppression, simply remove the specific NoAlarm parameter
from your OSMCONF file and repeat the process for making changes to your OSMCONF file
take effect.
Binding to an IP Address and Stack for OSM when Sending Indications
You can specify a source IP address and stack for OSM to use when sending indications to HP
SIM and Insight Remote Support Advanced/WEBES. This configuration flag does not affect the
OSM Service Connection client. The source stack name and IP address are required, while the
destination IP address and port parameters are optional and only needed if different destinations
require different source IP addresses.
Edit the OSMCONF file to specify the source stack name, IP address, destination IP and port:
IndicationSource=source stack name>,source IP[,destination IP[,destination port]]
Optional OSM Configuration 17