Insight Remote Support Advanced for NonStop

the first CMS on which Insight Remote Support Advanced was configured – before trying the
backup path.)
If the Problem Incident Report is successfully delivered to the HP Support Center, a case is
opened in Genesis for that problem.
If one delivery path fails, an “Incident Report Delivery Failure” alarm is created in the OSM
Service Connection. OSM generates an OSM event 1144 for this alarm. If this alarm is new
or has not resulted in a dial-out during the past 8 hours, OSM creates and sends a Problem
IR on to WEBES for dial-out.
NOTE: OSM automatically deletes failed delivery paths that have persisted for 10 days.
You can also delete them sooner, as described in “Remove Incident Report Delivery Paths for
Failed CMS or CMS to be Replaced” (page 20).
• An OSM event 1103 indicates that the IR failed to be delivered to HP SIM, for one of two
reasons:
— “Incident report delivery path not configured” means that the NonStop system has not
been properly configured to be monitored by Insight Remote Support Advanced, as
described in NonStop-Specific Tasks.
— “Problem detected in the delivery path(s)” means that delivery failed on all configured
paths. The event detail lists all of those paths on which delivery failed.
In this scenario, an “Incident Report Delivery Failure – None Functional” alarm is created
in the OSM Service Connection. OSM generates an OSM event 1144 for this alarm.
OSM does not create a Problem IR for this alarm because OSM has detected that there
is no delivery path working.
NOTE: OSM automatically deletes failed delivery paths that have persisted for 10 days.
You can also delete them sooner, as described in “Remove Incident Report Delivery Paths
for Failed CMS or CMS to be Replaced” (page 20).
Pending Incident Report Sent
A pending incident report is a Problem Incident Report that has not yet been delivered successfully.
If there are any pending incident reports when OSM completes a successful IR delivery, it will
attempt to send those Pending IRs again. When it does so, OSM generates an event 1146 with
the trace message “Sending Pending Incident Report” (see example below) for each Pending IR
sent. For each successful delivery, OSM generates an event 1102.
2011-03-08 22:13:31 \BLOSM3.$Z00S TANDEM.OSM.G06 001146
IR Alert Delivery --Send Pending Incident Report for IR id#: 1329
Failed IR Delivery Path Removed Through OSM Action
Failed incident report delivery paths can be as removed through the Test Incident Report Delivery
Paths action in the OSM Service Connection, as follows:
• When user responds Yes to the “Delete the failed path?” prompt, OSM creates a Periodic
Incident Report (which generates an 1101 event) and deletes the failed path(s) found during
the delivery of the IR.
• For each failed path, OSM generates two different 1146 events:
— Event 1146 with the trace message “Delete Indication Handler instance whose destination
is not reachable.”
— Event 1146 with the trace message “Indication Subscription DELETING.” The event detail
contains the WEBES destination, that destination being a URL containing 7906, the port
used by WEBES to receive incident reports, in the format of WBEM events, from OSM.
In the example below, both the primary and backup paths failed and were deleted, so there
are two of each of those 1146 events:
2011-03-11 16:22:51 \BLOSM3.$Z017 TANDEM.OSM.G06 001146
Delete Indication Handler instance whose destination is not reachable.
Pending Incident Report Sent 25