Insight Remote Support Advanced for NonStop
2011-03-11 16:22:51 \BLOSM3.$Z017 TANDEM.OSM.G06 001146
Delete Indication Handler instance whose destination is not reachable.
2011-03-11 16:22:52 \BLOSM3.$ZCMOM TANDEM.OSM.G06 001146
Indication Subscription DELETING (Primary)
2011-03-11 16:22:52 \BLOSM3.$ZCMOM TANDEM.OSM.G06 001146
Indication Subscription DELETING (Backup)
• OSM generates an event 1102 or 1103, depending on whether both or just one path fails.
The event detail indicates “Path is removed as action result” for each failed path deleted by
OSM. In the example below, both the primary and backup paths failed, so they were both
reported as being removed in the event detail of an 1103 event:
Incident Report ID:* 1361
OSM Process Name: "\BLOSM3.$ZCMOM"
Dialout Reason: "Problem detected in the delivery path(s)."
Perceived Severity: Unknown (12599)
Event Tag: 0
Incident Type: Periodic Incident (2)
IR Delivery Path Count: 2
IR Delivery Path: Path Type Primary (1)
Connectivity Status Disconnected (2)
Delivery Status Unknown (0)
Path Info Path is removed as action result (2)
Destination "https://16.107.145.241:7906/Wbem/WbemIndication?MEId=90eb11"
"7126b52f8b0126b52fa7c90007... "
" "
IR Delivery Path:- Path Type Backup (2)
Connectivity Status Disconnected (2)
Delivery Status Unknown (0)
Path Info Path is removed as action result (2)
Destination "https://zullu2.fc.hp.com:7906/Wbem/WbemIndication?MEId=8f86"
"a10226238a420126238b4a2e0024... "
" "
Failed IR Delivery Path Removed Automatically by OSM After Ten Days
OSM knows when an incident report delivery path has failed for more than ten consecutive days.
When OSM sends an IR after this threshold has been reached, OSM generates the following events
for each failed path:
• OSM event 1146 with the trace message “Delete Indication Handler instance whose destination
is not reachable.”
2011-03-11 16:22:51 \BLOSM3.$Z017 TANDEM.OSM.G06 001146
Delete Indication Handler instance whose destination is not reachable.
• OSM 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.
2011-03-11 16:22:52 \BLOSM3.$ZCMOM TANDEM.OSM.G06 001146
Indication Subscription DELETING (Backup)
In the example above, the trace subject line informs that the deleted path was the one to the
“Backup” CMS. The event detail (see example below) shows the IP address of that CMS, in
the URL containing port 7906:
Trace Subject: "Indication Subscription DELETING (Backup)"
Trace Message:- "Subscription: CIM_IndicationSubscription.Filter=R"CIM_IndicationFilter.CreationClassName=\""
"CIM_IndicationFilter\",Name=\"HPWEBES_16.107.145.183_2_Filter_HP_AlertIndication\",SystemCr"
"eationClassName=\"CIM_ComputerSystem\",SystemName=\"System \BLOSM3 [Logical]\"",Handler=R"C"
"IM_IndicationHandlerCIMXML.CreationClassName=\"CIM_IndicationHandlerCIMXML\",Name=\"HPWEBES"
"_16.107.145.183_2_Handler_HP_AlertIndication\",SystemCreationClassName=\"CIM_ComputerSystem"
"\",SystemName=\"System \BLOSM3 [Logical]\""Filter: CIM_IndicationFilter.CreationClassName=""
"CIM_IndicationFilter",Name="HPWEBES_16.107.145.183_2_Filter_HP_AlertIndication",SystemCreat"
"ionClassName="CIM_ComputerSystem",SystemName="System \BLOSM3 [Logical]",Query="select * fro"
"m HP_AlertIndication",QueryLanguage="WQL"" ?10 "Handler: CIM_IndicationHandlerCIMXML.Creati"
"onClassName="CIM_IndicationHandlerCIMXML",Name="HPWEBES_16.107.145.183_2_Handler_HP_AlertIn"
"dication",SystemCreationClassName="CIM_ComputerSystem",SystemName="System \BLOSM3 [Logical]"
"",FaultTolerantState=Primary,Destination="https://16.107.145.183:7906/Wbem/WbemIndication?M"
"EId=90eb11372e176e3f012e177048de0004&MEName=blosm3.caclab.cac.cpqcorp.net&ruleSet=NonStop%3"
"AWBEM_NonStop%3BNonstop_IncidentReportRule%3ANS_IR-9-29-09%3BUX_WIN_WBEM%3AUX_V2_7-24-09""
?10
OSM also generates an event 1102 or 1103, depending on whether one or all path fails. However,
unlike when you delete a failed path by performing the Test Incident Report Delivery Paths action
manually, the 1102/1103 event detail in this case does not specifically state that a failed path
26 Description of OSM Event and Data Flow