Insight Remote Support Advanced for NonStop

• OSM generates an event 1146 with the trace message “Indication Subscription CREATING.”
The event detail contains the WEBES destination, that destination being a URL containing
7906, the CMS port used by WEBES to receive incident reports, in the format of WBEM
events, from OSM.
Trace Subject: "Indication Subscription CREATING (Primary)"
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
Periodic Incident Report Created
A Periodic Incident Report is created, either automatically or through the Test Incident Report
Delivery Paths action in the OSM Service Connection. When a Periodic IR is created, OSM creates
two events. The first is an OSM event 1101, “Periodic Incident Report has been created,” which
contains the unique ID# of the IR. The second is either event 1102 or 1103, depending on the
delivery outcome. The success or failure of the delivery and dial-out can be verified as follows:
• An OSM event 1102 indicates that the Periodic Incident Report was delivered successfully,
on at least one path, from the NonStop system to WEBES on the CMS and that an attempt
was made to send it to the HP Support Center. Example:
2011-03-08 22:13:31 \BLOSM3.$Z00S TANDEM.OSM.G06 001102
An Incident Report has been successfully sent from NonStop system to
the remote support console and has been attempted to be sent to the
Support Center for IR id#: 1340 OSM Process: \BLOSM3.$ZCMOM
The event detail lists and reports status for all configured delivery paths:
IR Delivery Path: Path Type Primary (1)
Connectivity Status Connected (1)
Delivery Status Dialout Completed (4)
Path Info None (1)
Destination "https://16.107.145.183:7906/Wbem/WbemIndication?MEId=90eb11"
"372e9932cd012e9933522c0004... "
" "
IR Delivery Path: Path Type Backup (2)
Connectivity Status Disconnected (2)
Delivery Status Unknown (0)
Path Info None (1)
Destination "https://16.107.145.137:7906/Wbem/WbemIndication?MEId=90eb11"
"352dc8bd7a012dc8c22c9f0005... "
" "
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 (see example below).
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.
2011-03-08 22:13:42 \BLOSM3.$Z00S TANDEM.OSM.G06 001144
An Alarm has been created.Resource Name: System \BLOSM3, Probable
Cause: Connection Establishment Error, Specific Problem: Incident
Report Delivery Failure, Perceived Severity: Major, Alarm Creation
Time: MAR 09, 2011 06:13:41 GMT, Problem IR Created: Yes, Process
Name: \BLOSM3.$ZCMOM
Periodic Incident Report Created 23