Technical data

To unsuppress a problem attribute, select the attribute, right-click, and select Unsuppress. You
cannot suppress a Service State or Subcomponent State attribute. A Service State attribute of
something other than OK is caused by one or more alarms on the resource. You must suppress the
alarm to acknowledge (or clear) the Service State. To acknowledge a problem reported by the
Subcomponent State attribute, you must find the root of the problem by expanding the object in
the tree pane to find the one or more subcomponents causing problems to be propagated, then
suppress those attributes or alarms.
Suppressing Alarms
To suppress an alarm, select the alarm (in either the Alarms tab or the Alarms dialog box), right-click,
and select Suppress, the either Temporary or Permanent. If you select Temporary suppression and
the same alarm is generated again on this object at a later time, state propagation will occur. If
you select Permanent suppression and the same alarm is generated again on this object at a later
time, state propagation will not occur. Even if the alarm is generated again in the future, state
propagation does not occur until you unsuppress the alarm. OSM Rediscover actions have no
effect on suppressed alarms.
With OSM version T0682 H02 ABX and later, suppression of alarms is persistent by default. That
means alarms suppressed in the OSM Service Connection remain suppressed even after the OSM
server has been stopped and restarted, unless the conditions for ending Temporary suppression
have been met. To disable suppression persistence with OSM T0682 H02 ABX and later, see
“Disabling Alarm and Attribute Suppression Persistence” (page 21) for the necessary OSMCONF
parameter.
Persistence is not available in OSM versions prior to T0682 H02 ABX, meaning that all suppressed
values revert to unsuppressed when the current OSM server session is ended.
To unsuppress an alarm, select the alarm, right-click, and select Unsuppress.
Suppressing BladeCluster Alarms
Available on OSM version T0682 H02 ABZ or later, the "Place Local Node in Service" action on
the BladeCluster object allows you to prevent all other directly-connected nodes from remotely
notifying (dialing out) an alarm as soon as SNETMON is stopped on the local node, or that node
is halted. This alarm suppression only works on remote nodes that are running T0682 H02 ABZ
or later as well. For more information, see the OSM Service Connection online help or the NonStop
BladeCluster Solution Manual.
Suppressing Problem Incident Report Creation
A system-level action allows you to suppress the creation of Problem Incident Reports (IRs) and
remote notifications (dial-outs) for a specified period of time.. This is often used by guided procedures
or called for by service procedures to prevent remote notifications caused by activities related to
the procedure. The default suppression time of 40 minutes can be changed in the OSMCONF file
or extended for an action currently in progress by using the Extend Problem Incident Report
Suppression Time action. Suppression can also be canceled at any time through the Unsuppress
Problem Incident Report Creation action, also found under the System object.
With OSM T0682 AAY and later, you can also prevent ServerNet Problem IRs on one node from
being propagated to other nodes on the same ServerNet Cluster (see “Suppressing Redundant IRs
from ServerNet Cluster Nodes” (page 22)).
Rediscover Actions
Rediscover is supported as an action on all system and some cluster objects. For most objects,
Rediscover is available only in the shortcut menu.
Rediscover causes OSM to refresh and reanalyze the object and all subcomponents. You can
update all system resources by performing the Rediscover action under the System object, or save
52 Getting Started With OSM Applications