Downloads
0.4KB
Description
Download
When monitoring remote systems with Hardware Sentry KM for PATROL, the mc_host and mc_host_address slots of Sentry events (of class 41) in BEM and BPPM do not contain the actual hostname/IP address of those systems but the PATROL Agent's ones.
This article describes how to configure and retrieve those values.
Prerequisites
First, carefully follow the instructions described in this KB article to properly set the hostname and IP address when configuring the remote monitoring.
Solution
The BEM rule will use those values so make sure you see them as shown in the event description above.
On the BEM test sever:
Download refine.mrl.zip, unzip and copy refine.mrl into the MCELL_HOME\etc\<cellname>\kb\rules directory and edit the MCELL_HOME\etc\<cellname>\kb\rules\.load file to add it there.
Eg:
# File name: .load
# Version: 7.4.00
# Copyright 1998-2010 BMC Software, Inc. All Rights Reserved
#
kbversem
kbverssim
mc_startup
im_internal
mc_intevt
impact_admin_server
ips
mc_sm_start
mc_sm_associate
mc_ci_policies
mc_sm_maintenance
mc_sm_elect
mc_sm_attach
mc_sm_shadow
mc_sm_slm
bii4p
refine
sentry
admin_propagate
patrol_portal
ibrsd_event_association
ibrsd_event_incident_info
ibrsd_error_event_association
ibrsd_bem_categorization
ibrsd_sim_remote_action
ibrsd_orphaned_root_cause
ibrsd_root_cause
ibrsd_causal_priority
ibrsd_propagate_causal_events
propagate_bppm
Save the .load file.
Run:
Mcontrol -n <cellname> reload kb
Generate a new event of class 41 and check out the result in the Impact Explorer/BPPM Ops console.
Example
Here is the original event:
PATROL_EV;
mc_client_address='192.168.7.42';
adapter_host='sam.internal.sentrysoftware.net';
mc_location='internal.sentrysoftware.net';
mc_service='';
mc_host_class='NT 6.1 Windows 7 Ultimate Professional (Service Pack 1) AMD64';
mc_host='sam.internal.sentrysoftware.net'; =>Patrol Agent's hostname
mc_host_address='192.168.7.42'; =>Patrol Agent's IP address.
mc_host_id=0;
mc_account='';
mc_object_class='MS_HW_TEMPERATURE';
mc_object='MS_HW_CpMgServNThdffermat-cmdb_01'; =>Actual hostname of the monitored system
mc_object_uri='';
mc_object_owner='';
mc_tool_class='BII4PATROL 7.3.60';
mc_tool='sam.internal.sentrysoftware.net:3181';
mc_tool_id='';
mc_tool_rule='';
mc_tool_key='258812';
mc_tool_sev='3';
mc_tool_address='';
mc_tool_uri='';
mc_tool_time=0;
mc_tool_suggestion='';
mc_origin_class='V4.1';
mc_origin='sam.internal.sentrysoftware.net:3181';
mc_origin_key='258812';
mc_origin_sev='3';
mc_parameter='Temperature';
mc_parameter_value='';
mc_parameter_unit='';
mc_parameter_threshold='';
mc_event_category=;
mc_event_subcategory=OTHER;
mc_event_model_version='1.1.00';
status=OPEN;
severity=CRITICAL;
mc_original_severity=CRITICAL;
mc_priority=PRIORITY_5;
mc_original_priority=PRIORITY_5;
mc_owner='';
mc_long_msg='';
msg='Hardware problem on fermat-cmdb (10.0.10.169) with 0.1 (CPU). Although not yet critical, the temperature is abnormally high (30.0 degrees C) =>this value will be extracted and used by the cell rule.
Hardware health report (Tue Apr 23 13:19:17 2013)
======================
Monitored object : 0.1 (CPU)
Type : Temperature
On host : fermat-cmdb
PATROL object ID : /MS_HW_TEMPERATURE/MS_HW_CpMgServNThdffermat-cmdb_01
Internal device ID : 0.1
Connector used : MS_HW_CpMgServNT.hdf
This object is attached to:
Computer: HP ProLiant BL260c G5
============================================================
Parameter: Temperature (Currently in ALARM state)
------------------------------------------------------------
Current value: 30.0 degrees C
Unit : Celsius Degrees (C?)
Current state: ALARM
Thresholds (manually set):
- If Temperature is in the [25.0 degrees C ; 35.0 degrees C] range: Trigger an ALARM
- If Temperature is in the [35.0 degrees C ; 50.0 degrees C] range: Trigger an ALARM
Problem: Although not yet critical, the temperature is abnormally high (30.0
degrees C)
Consequence: An out-of-range temperature may lead to a system crash or even
damaged hardware.
Recommended action: Check why the temperature is out of the normal range (it may
be due to a fan failure, or a severe system overload).
.';
duration=0;
mc_timeout=0;
repeat_count=0;
mc_action_count=0;
administrator='';
mc_acl=[];
mc_notes=[];
mc_operations=[];
mc_notification_history=[];
mc_bad_slot_names=[];
mc_bad_slot_values=[];
mc_history=[];
mc_modhist=[];
mc_abstraction=[];
mc_abstracted=[];
mc_associations=[];
mc_cause=0;
mc_effects=[];
mc_event_relations=[];
mc_relation_source='';
mc_smc_id='';
mc_smc_alias='';
mc_smc_impact=NOT_ELECTED;
mc_smc_type='';
mc_smc_priority=0.000000e+000;
mc_smc_causes=[];
mc_smc_effects=[];
itsm_category='';
itsm_type='';
itsm_item='';
itsm_product_name='';
itsm_model_version='';
itsm_manufacturer='';
itsm_operational_category1='';
itsm_operational_category2='';
itsm_operational_category3='';
itsm_company='';
itsm_location='';
pn_detail_diag=0;
pn_detail_diag_count=0;
pn_device_name='';
p_agent='sam.internal.sentrysoftware.net';
p_agent_address='192.168.7.42';
p_agent_port=3181;
p_agent_version='V4.1';
p_application='MS_HW_TEMPERATURE';
p_catalog='STD';
p_class='41';
p_diary='';
p_expectancy='';
p_handler='Patrol';
p_instance='MS_HW_CpMgServNThdffermat-cmdb_01';
p_node='fermat-cmdb.internal.sentrysoftware.net';
p_origin='MS_HW_TEMPERATURE.MS_HW_CpMgServNThdffermat-cmdb_01.Temperature';
p_owner='';
p_source_id='890';
p_status='0';
p_type='5';
p_args=['Hardware problem on fermat-cmdb (10.0.10.169) with 0.1 (CPU). Although not yet critical, the temperature is abnormally high (30.0 degrees C)
Hardware health report (Tue Apr 23 13:19:17 2013)
======================
Monitored object : 0.1 (CPU)
Type : Temperature
On host : fermat-cmdb
PATROL object ID : /MS_HW_TEMPERATURE/MS_HW_CpMgServNThdffermat-cmdb_01
Internal device ID : 0.1
Connector used : MS_HW_CpMgServNT.hdf
This object is attached to:
Computer: HP ProLiant BL260c G5
============================================================
Parameter: Temperature (Currently in ALARM state)
------------------------------------------------------------
Current value: 30.0 degrees C
Unit : Celsius Degrees (C?)
Current state: ALARM
Thresholds (manually set):
- If Temperature is in the [25.0 degrees C ; 35.0 degrees C] range: Trigger an ALARM
- If Temperature is in the [35.0 degrees C ; 50.0 degrees C] range: Trigger an ALARM
Problem: Although not yet critical, the temperature is abnormally high (30.0
degrees C)
Consequence: An out-of-range temperature may lead to a system crash or even
damaged hardware.
Recommended action: Check why the temperature is out of the normal range (it may
be due to a fan failure, or a severe system overload).
'];
p_diary_text=[];
p_diary_time=[];
p_diary_operator=[];
p_class_group='normal_group';
pes=0;
pes_tcp_port=0;
pes_udp_port=0;
pes_icon_name='';
pes_parent_instance='';
pes_param_status='';
pes_alert_date='';
pes_alert_time='';
pes_tz='';
pes_last10='';
pes_ave10='';
pes_last10_ts='';
pes_last10_tp=0.000000e+000;
pes_user_defined='';
pes_alarm_min='';
pes_alarm_max='';
pes_patrol_home='';
pes_custom_id1='';
pes_custom_id2='';
mc_parameter2=0.000000e+000;
mc_parameter_value2=0.000000e+000;
END
Related Topics
- Class-41 Events not Sent to Cell After Upgrading PATROL Agent to v9.5
- Empty Values for mc_object_class, mc_object and mc_parameter Slots in the Sentry KMs ' Events
- Closing Sentry Class-41 Events in BEM/BPPM when Class-9 Events are Generated
- Generating Test Events with Hardware Sentry KM for PATROL
- Problem: Missing Sentry Software's KMs in BPPM CMA Monitoring Repository