Configuring Agent Alerts – Hitachi Tuning Manager (Linux)

—Linux based configuration—

  • Default path locations:
    Tuning Manager Commands : /opt/HiCommand/TuningManager/PerformanceReporter/Tools/
    RAID Agent Commands : /opt/jp1pc/tools/
  • Procedure to configure alerts:
    1. Configuring Trap Generator service properties to send SNMP traps.
    2. Configure Action Handler service properties to send e-mail alerts.
    3. Creating an alarm definition file.
    4. Verifying alarm definition file.
    5. Bind Alarm table to an agent.
  1. Login to Management server as root on which HTnM server installed.
  1. Navigate to RAID Agents Commands path.

Configuring Trap Generator service properties to send SNMP Traps:

  1. HTnM server assigns a Service ID for each Service running.

Issue Command ./jpcctrl list “*” host=”*” – To Display all the services running.

img1

Note the Service ID of “Action Handler” & “Trap Generator” Services.

  1. Trap Generator Service Properties need to be configured in order to generate SNMP traps. Navigate to Tuning Manager Commands Path.

     Issue command ./jpctgprp output –o TrapGenerator.xml PC4sanman2 – To generate default XML file.  Where PC4sanman2 is the Service ID of Trap Generator service.img2

img3

  1. Edit the file and change the Service ID In this case : Service id = “PC4sanman2”

img4

6. Issue the command ./jpctgprp create TrapGenerator.xml – To activate the modified service properties of Trap Generator.

img5

Configuring Action Handler service properties to send e-mail alerts:

  1. Issue the command ./jpcahprp output –o ActionHandler.xml PH1sanman2 – To get the current Action Handler XML file. Where PH1sanman2 is the Service ID of Action Handler.          

img6

Edit the file and change the “Service id=PH1sanman2” & sender email and subject.

img7

  1. Issue command ./jpcahprp update ActionHandler.xml – To activate the modified service properties of Action Handler XML.

img8

 Creating the Alarm definition file:

Alarm definition file is a standard format file. All the parameters which needs to be monitored should be added to alarm definition file.
To get the current active Alarm definition file:
Issue command “./jpcalarm export –f /tmp/tmpfile –key agtd”

Standard Format of Definition file:

Alarm Definition File Version=0001           # 0001 for HTnM version 5.0 or later ; 0002 for Version 8 or later
Alarm Definition File Code=C
###############################################################
[Alarm Data]
[[General]]
Product=D7.2
Alarm Table Name="RAID Alarms"
Alarm Name="Pool Usage"
Message Text="Pool usage % is %CVS %"
Check Value Exist=N

[[Advanced Setting]]
Active Alarm=Y
Regular Alarm=N
Evaluate All Data=N
Monitoring Regularly=Y
Damping=Y
Damping Count=1/1

[[Alarm Condition Expressions]]
Condition=PD_PLC_USAGE_RATE>=80.000000,70.000000

[[Actions]]
Report="Reports/RAID/Monthly Trend/Pool Usage Trend(7.1)"
SNMP=Abnormal,Warning,Normal
JP1 Event=N

[[Action Definition E-mail]]
E-mail Address=storageadmin@xxx.com
Action Handler=PH1sanman2

[[[Message Text]]]
Date: %SCT
Host: %HNS
######################################################################

For each additional parameter another set of above context needs to be repeated in the same definition file.
For more details on Alarm definition file, Please refer document ‘Hitachi Tuning Manager Agent Administration Guide’

  1. Create the Alarm Definition file with required parameters to be monitored.  In this case Alarm table “RAID Alarms” and the following Alarms has been created

Alarm Table Name: RAID Alarms
Alarm Name:
LDEV Response Time
LDEV1 Response Time
LDEV2 Response Time
LDEV3 Response Time
Pool Usage
Processor Busy Rate
Raid Group
Read Cache Hit Rate
Write Cache Hit Rate
Write Cache Pending

  1. Pre-check the Alarm definition file for any syntax or invalid error. Issue command ./jpcalarm check –f alarms

img9

Check for any errors and rectify them.

img10

  1. Activate the updated alarms definition file.

Issue command “./jpcalarm import –f alarms”

img11

Binding alarm table to an agent:

  1. Bind the Alarm table with an Storage Arrays which needs to be monitored.

Issue command ./jpcinslist agtd – to list the configured storage arrays in Tuning Manager

Issue command ./jpcctrl list “*” host=”*” – To list all the running services of Tuning Manager.

Note the Service IDs of Storage Arrays which needs to bind with an agent.

In this case configure storage arrays are

HUS3
HUS4
VSP1
USPv1

And the service IDs of Arrays are

DA1HUS3[sanman2]
DA1HUS4[sanman2]
DA1VSP1[sanaman2]
DA1USPv1[sanman2]

img12

  1. Bind the Alarm table to Storage Array based on their respective Service IDs

Issue Commands ./jpcalarm bind –key agtd –table “RAID Alarms” –id “DA1HUS3[sanman2]”
                            ./jpcalarm bind –key agtd –table “RAID Alarms” –id “DA1HUS4[sanman2]”
                            ./jpcalarm bind –key agtd –table “RAID Alarms” –id “DA1VSP1[sanman2]”

img13

  1. Verify the activity. Issue the Command ./jpcalarm list –key agtd –table “RAID Alarms”

img14

 

One Reply to “Configuring Agent Alerts – Hitachi Tuning Manager (Linux)”

  1. Excellent.

Leave a Reply