273 lines
14 KiB
XML
273 lines
14 KiB
XML
<?xml version="1.0"?>
|
|
<!--
|
|
Alarm configuration
|
|
Root: CODAC_AlarmHandler
|
|
CODAC-VERSION: 6.3.2
|
|
WARNING: This is an automatically generated file. PLEASE DO NOT MODIFY.
|
|
-->
|
|
<config name="CODAC_AlarmHandler">
|
|
<component name="EC">
|
|
<component name="EC-GN">
|
|
<component name="EC-GN-SYSM">
|
|
<pv name="EC-GN-SYSM-52RF-01:PLC4110-PLCHLTS">
|
|
<description>Connection or frame of the communication for 4110 configuration and state is invalid</description>
|
|
<latching>true</latching>
|
|
<delay>0</delay>
|
|
<guidance>
|
|
<title>4110 communication failed</title>
|
|
<details>The connection for configuration and state to 4110 was broken or the frame is not correct</details>
|
|
</guidance>
|
|
<guidance>
|
|
<title>Causes related to the alarm</title>
|
|
<details>Timestamp update error (TIME)
|
|
Data block header, footer or length mismatch (FERROR)
|
|
Data block version mismatch (FVERS)
|
|
Data block alive counter update error (ALIVEC)
|
|
Frame lost due (FLOST)
|
|
PLC communication broken (CFGSTAT)
|
|
Lost a redundant CPU (CPU0-ALIVE, CPU1-ALIVE)</details>
|
|
</guidance>
|
|
<guidance>
|
|
<title>Corrective action</title>
|
|
<details>Check whether the PLC is running\n Check whether network is ok\n Contact maintenance service (if needed)</details>
|
|
</guidance>
|
|
<display>
|
|
<title>4110 State Comm. Alarm OPI</title>
|
|
<details>/opt/codac/opi/boy/resources/alarmpages/healthMonitoring/ITER-SYSM-PLCHLTS_Alarm.opi "CBS1=EC, CBS2=GN, PP=01, NNNN=4110, TTT=PLC, PPPP=52RF, ALARM_PV=EC-GN-SYSM-52RF-01:PLC4110-PLCHLTS, ALARM_PATH=/CODAC_AlarmHandler/EC/EC-GN/EC-GN-SYSM, LEVEL=ITER-EC-GN-SYSM, ALARM_GUIDANCE1_TITLE=PLC communication failed, ALARM_GUIDANCE1_DETAILS=The connection for configuration and state to PLC is broken or the frame is not correct."</details>
|
|
</display>
|
|
</pv>
|
|
<pv name="EC-GN-SYSM-52RF-01:PLC4110-EVTHLTS" >
|
|
<description>Connection or frame of the communication for PLC Event is invalid</description>
|
|
<latching>true</latching>
|
|
<delay>0</delay>
|
|
<guidance>
|
|
<title>PLC Event communication failed</title>
|
|
<details>The connection for event to PLC was broken or the frame is not correct</details>
|
|
</guidance>
|
|
<guidance>
|
|
<title>Causes related to the alarm</title>
|
|
<details>Event Frame count update error (FRAMEC)
|
|
PLC Event communication broken (EVTSTAT)</details>
|
|
</guidance>
|
|
<guidance>
|
|
<title>Corrective action</title>
|
|
<details>Check whether the PLC is running\n Check whether network is ok\n Contact maintenance service (if needed)</details>
|
|
</guidance>
|
|
<display >
|
|
<title>PLC Event Comm. Alarm OPI</title>
|
|
<details>/opt/codac/opi/boy/resources/alarmpages/healthMonitoring/ITER-SYSM-EVTHLTS_Alarm.opi "CBS1=EC, CBS2=GN, CBS3=SYSM, PP=01, NNNN=4110, TTT=PLC, PPPP=52RF, ALARM_PV=EC-GN-SYSM-52RF-01:PLC4110-EVTHLTS, ALARM_PATH=/CODAC_AlarmHandler/EC/EC-GN/EC-GN-SYSM, LEVEL=ITER-EC-GN-SYSM, ALARM_GUIDANCE1_TITLE=PLC Event communication failed, ALARM_GUIDANCE1_DETAILS=The connection for event to PLC was broken or the frame is not correct."</details>
|
|
</display>
|
|
</pv>
|
|
<pv name="EC-GN-SYSM-52RF-01:PCF4210-SHLT">
|
|
<description>Any one of CPU, MEM, Disk, FD, Process of the host is in alarm state</description>
|
|
<latching>true</latching>
|
|
<delay>0</delay>
|
|
<guidance>
|
|
<title>System is an abnormal state</title>
|
|
<details>Check the mentioned alarm load and identify the cause</details>
|
|
</guidance>
|
|
<guidance>
|
|
<title>System resources related to the alarm</title>
|
|
<details>1 - one of CPU, Disk, Memory, FD load is high or necessary process has been stopped
|
|
2 - two of CPU, Disk, Memory, FD load are high and/or necessary process has been stopped
|
|
3 - three of CPU, Disk, Memory, FD load are high and/or necessary process has been stopped</details>
|
|
</guidance>
|
|
<guidance>
|
|
<title>Corrective action</title>
|
|
<details>If any load remains high continuously, contact maintenance service.
|
|
In addition, check if the necessary processes are running</details>
|
|
</guidance>
|
|
<guidance>
|
|
<title>Temporary actions to suppress</title>
|
|
<details>Change the alarm limits or severity for each load in alarm state.
|
|
|
|
Ex1) alarm limits
|
|
% caput EC-GN-SYSM-52RF-01:PCF4210-CPUUTL.HIGH 90
|
|
% caput EC-GN-SYSM-52RF-01:PCF4210-CPUUTL.HIHI 100
|
|
|
|
Ex2) alarm severity
|
|
% caput EC-GN-SYSM-52RF-01:PCF4210-MEMUTL.HSV NO_ALARM
|
|
% caput EC-GN-SYSM-52RF-01:PCF4210-MEMUTL.HHSV NO_ALARM</details>
|
|
</guidance>
|
|
<display>
|
|
<title>System Health Alarm OPI</title>
|
|
|
|
<details>/opt/codac/opi/boy/resources/alarmpages/healthMonitoring/ITER-SYSM-SHLT_Alarm.opi "CBS=EC-GN-SYSM, PPPP=52RF, PP=01, TTT=PCF, NNNN=4210, ALARM_PV=EC-GN-SYSM-52RF-01:PCF4210-SHLT, ALARM_PATH=/CODAC_AlarmHandler/EC/EC-GN/EC-GN-SYSM, LEVEL=ITER-EC-GN-SYSM, ALARM_GUIDANCE1_TITLE=System resource utilization is high, ALARM_GUIDANCE1_DETAILS=Any one of CPU / MEM / Disk / FD / Process of the host is in alarm state. Check the mentioned alarm load and identify the cause. If any load remains high continuously contact maintenance service."</details>
|
|
</display>
|
|
</pv>
|
|
<pv name="EC-GN-SYSM-52RF-01:PCF4210-SYSHLTS">
|
|
<description>Any one of CPU, MEM, Disk or FD of the host is in alarm state</description>
|
|
<latching>true</latching>
|
|
<delay>0</delay>
|
|
<guidance>
|
|
<title>System resource utilization is high</title>
|
|
<details>Check the mentioned alarm load and identify the cause</details>
|
|
</guidance>
|
|
<guidance>
|
|
<title>System resources related to the alarm</title>
|
|
<details>1 - CPU utilization high (CPUUTL) : CPU utilization is high
|
|
2 - Memory utilization high (MEMUTL) : Memory utilization is high
|
|
3 - CPU, Mem util high (CPUUTL, MEMUTL) : CPU and Memory utilizations are high
|
|
4 - Disk utilization high (DISKUTL) : Disk utilizations are high
|
|
5 - CPU, Disk util high (CPUUTL,DISKUTL) : CPU and Disk utilizations are high
|
|
6 - Mem, Disk util high (MEMUTL,DISKUTL) : Memory and Disk utilizations are high
|
|
7 - CPU, Mem, Disk util high (CPUUTL,MEMUTL,DISKUTL) : CPU/Memory/Disk utilizations are high
|
|
8 - FD utilization high (FDUTL) : FD utilization is high
|
|
9 - CPU, FD util high (CPUUTL,FDUTL) : CPU and FD are in alarm state
|
|
10 - Mem, FD util high (MEMUTL,FDUTL) : Memory and FD are in alarm state
|
|
11 - CPU, Mem, FD alarm (CPUUTL,MEMUTL,FDUTL) : CPU/Memory/FD are in alarm state
|
|
12 - Disk, FD util high (DISKUTL,FDUTL) : Disk and FD are in alarm state
|
|
13 - CPU, Disk, FD alarm (CPUUTL,DISKUTL,FDUTL) : CPU/Disk/FD are in alarm state
|
|
14 - Mem, Disk, FD alarm (MEMUTL,DISKUTL,FDUTL) : Memory/Disk/FD are in alarm state
|
|
15 - CPU,Mem,Disk,FD alarm (CPUUTL,MEMUTL,DISKUTL,FDUTL) : CPU/Memory/Disk/FD alarm</details>
|
|
</guidance>
|
|
<guidance>
|
|
<title>Corrective action</title>
|
|
<details>If any load remains high continuously, contact maintenance service</details>
|
|
</guidance>
|
|
<guidance>
|
|
<title>Temporary actions to suppress</title>
|
|
<details>Change the alarm limits or severity for each load in alarm state.
|
|
|
|
Ex1) alarm limits
|
|
% caput EC-GN-SYSM-52RF-01:PCF4210-CPUUTL.HIGH 90
|
|
% caput EC-GN-SYSM-52RF-01:PCF4210-CPUUTL.HIHI 100
|
|
|
|
Ex2) alarm severity
|
|
% caput EC-GN-SYSM-52RF-01:PCF4210-MEMUTL.HSV NO_ALARM
|
|
% caput EC-GN-SYSM-52RF-01:PCF4210-MEMUTL.HHSV NO_ALARM</details>
|
|
</guidance>
|
|
<display>
|
|
<title>System Health Alarm OPI</title>
|
|
<details>/opt/codac/opi/boy/resources/alarmpages/healthMonitoring/ITER-SYSM-SYSHLTS_Alarm.opi "CBS=EC-GN-SYSM, PPPP=52RF, PP=01, TTT=PCF, NNNN=4210, ALARM_PV=EC-GN-SYSM-52RF-01:PCF4210-SYSHLTS, ALARM_PATH=/CODAC_AlarmHandler/EC/EC-GN/EC-GN-SYSM, LEVEL=ITER-EC-GN-SYSM, ALARM_GUIDANCE1_TITLE=System resource utilization is high, ALARM_GUIDANCE1_DETAILS=Any one of CPU / MEM / Disk / FD of the host is in alarm state. Check the mentioned alarm load and identify the cause. If any load remains high continuously contact maintenance service."</details>
|
|
</display>
|
|
</pv>
|
|
<pv name="EC-GN-SYSM-52RF-01:PCF4210-TSTATUS">
|
|
<description>Current state of TCNd and the synchronization state of the device</description>
|
|
<latching>true</latching>
|
|
<delay>0</delay>
|
|
<guidance>
|
|
<title>System time synchronization is not fully operational</title>
|
|
<details>If status is N/A, then check that tcnd is running.
|
|
If status is not operational for some time, please contact maintenance service.</details>
|
|
</guidance>
|
|
<display>
|
|
<title>Documentation TCNd</title>
|
|
<details>firefox file:///opt/codac/doc/pdf/TCNd_User_Manual.pdf</details>
|
|
</display>
|
|
<display>
|
|
<title>TCNd Sync. Alarm OPI</title>
|
|
<details>/opt/codac/opi/boy/resources/alarmpages/healthMonitoring/ITER-SYSM-TSTATUS_Alarm.opi "CBS=EC-GN-SYSM, PPPP=52RF, PP=01, TTT=PCF, NNNN=4210, ALARM_PV=EC-GN-SYSM-52RF-01:PCF4210-TSTATUS, ALARM_PATH=/CODAC_AlarmHandler/EC/EC-GN/EC-GN-SYSM, LEVEL=ITER-EC-GN-SYSM, ALARM_GUIDANCE1_TITLE=System clock synchronization with respect to ITER time, ALARM_GUIDANCE1_DETAILS=The computer system clock is synchronized to ITER time using the TCN daemon (TCNd) component of CODAC Core SYstem. Please see TCNd User Manual (ITER_D_MUYNT6 - /opt/codac/doc/pdf/TCNd_User_Manual.pdf).
|
|
The clock synchronization has been detected to have been in an abnormal state. i.e. STATUS different from 'Operational' after two minutes of uptime."</details>
|
|
</display>
|
|
</pv>
|
|
<pv name="EC-GN-SYSM-52RF-01:PSH4410-SHLT">
|
|
<description>Any one of CPU, MEM, Disk, FD, Process of the host is in alarm state</description>
|
|
<latching>true</latching>
|
|
<delay>0</delay>
|
|
<guidance>
|
|
<title>System is an abnormal state</title>
|
|
<details>Check the mentioned alarm load and identify the cause</details>
|
|
</guidance>
|
|
<guidance>
|
|
<title>System resources related to the alarm</title>
|
|
<details>1 - one of CPU, Disk, Memory, FD load is high or necessary process has been stopped
|
|
2 - two of CPU, Disk, Memory, FD load are high and/or necessary process has been stopped
|
|
3 - three of CPU, Disk, Memory, FD load are high and/or necessary process has been stopped</details>
|
|
</guidance>
|
|
<guidance>
|
|
<title>Corrective action</title>
|
|
<details>If any load remains high continuously, contact maintenance service.
|
|
In addition, check if the necessary processes are running</details>
|
|
</guidance>
|
|
<guidance>
|
|
<title>Temporary actions to suppress</title>
|
|
<details>Change the alarm limits or severity for each load in alarm state.
|
|
|
|
Ex1) alarm limits
|
|
% caput EC-GN-SYSM-52RF-01:PSH4410-CPUUTL.HIGH 90
|
|
% caput EC-GN-SYSM-52RF-01:PSH4410-CPUUTL.HIHI 100
|
|
Ex2) alarm severity
|
|
% caput EC-GN-SYSM-52RF-01:PSH4410-MEMUTL.HSV NO_ALARM
|
|
% caput EC-GN-SYSM-52RF-01:PSH4410-MEMUTL.HHSV NO_ALARM</details>
|
|
</guidance>
|
|
<display>
|
|
<title>System Health Alarm OPI</title>
|
|
<details>/opt/codac/opi/boy/resources/alarmpages/healthMonitoring/ITER-SYSM-SHLT_Alarm.opi "CBS=EC-GN-SYSM, PPPP=52RF, PP=01, TTT=PSH, NNNN=4410, ALARM_PV=EC-GN-SYSM-52RF-01:PSH4410-SHLT, ALARM_PATH=/CODAC_AlarmHandler/EC/EC-GN/EC-GN-SYSM, LEVEL=ITER-EC-GN-SYSM, ALARM_GUIDANCE1_TITLE=System resource utilization is high, ALARM_GUIDANCE1_DETAILS=Any one of CPU / MEM / Disk / FD / Process of the host is in alarm state. Check the mentioned alarm load and identify the cause. If any load remains high continuously contact maintenance service."</details>
|
|
</display>
|
|
</pv>
|
|
<pv name="EC-GN-SYSM-52RF-01:PSH4410-SYSHLTS">
|
|
<description>Any one of CPU, MEM, Disk or FD of the host is in alarm state</description>
|
|
<latching>true</latching>
|
|
<delay>0</delay>
|
|
<guidance>
|
|
<title>System resource utilization is high</title>
|
|
<details>Check the mentioned alarm load and identify the cause</details>
|
|
</guidance>
|
|
<guidance>
|
|
<title>System resources related to the alarm</title>
|
|
<details>1 - CPU utilization high (CPUUTL) : CPU utilization is high
|
|
2 - Memory utilization high (MEMUTL) : Memory utilization is high
|
|
3 - CPU, Mem util high (CPUUTL, MEMUTL) : CPU and Memory utilizations are high
|
|
4 - Disk utilization high (DISKUTL) : Disk utilizations are high
|
|
5 - CPU, Disk util high (CPUUTL,DISKUTL) : CPU and Disk utilizations are high
|
|
6 - Mem, Disk util high (MEMUTL,DISKUTL) : Memory and Disk utilizations are high
|
|
7 - CPU, Mem, Disk util high (CPUUTL,MEMUTL,DISKUTL) : CPU/Memory/Disk utilizations are high
|
|
8 - FD utilization high (FDUTL) : FD utilization is high
|
|
9 - CPU, FD util high (CPUUTL,FDUTL) : CPU and FD are in alarm state
|
|
10 - Mem, FD util high (MEMUTL,FDUTL) : Memory and FD are in alarm state
|
|
11 - CPU, Mem, FD alarm (CPUUTL,MEMUTL,FDUTL) : CPU/Memory/FD are in alarm state
|
|
12 - Disk, FD util high (DISKUTL,FDUTL) : Disk and FD are in alarm state
|
|
13 - CPU, Disk, FD alarm (CPUUTL,DISKUTL,FDUTL) : CPU/Disk/FD are in alarm state
|
|
14 - Mem, Disk, FD alarm (MEMUTL,DISKUTL,FDUTL) : Memory/Disk/FD are in alarm state
|
|
15 - CPU,Mem,Disk,FD alarm (CPUUTL,MEMUTL,DISKUTL,FDUTL) : CPU/Memory/Disk/FD alarm</details>
|
|
</guidance>
|
|
<guidance>
|
|
<title>Corrective action</title>
|
|
<details>If any load remains high continuously, contact maintenance service</details>
|
|
</guidance>
|
|
<guidance>
|
|
<title>Temporary actions to suppress</title>
|
|
<details>Change the alarm limits or severity for each load in alarm state.
|
|
|
|
Ex1) alarm limits
|
|
% caput EC-GN-SYSM-52RF-01:PSH4410-CPUUTL.HIGH 90
|
|
% caput EC-GN-SYSM-52RF-01:PSH4410-CPUUTL.HIHI 100
|
|
|
|
Ex2) alarm severity
|
|
% caput EC-GN-SYSM-52RF-01:PSH4410-MEMUTL.HSV NO_ALARM
|
|
% caput EC-GN-SYSM-52RF-01:PSH4410-MEMUTL.HHSV NO_ALARM</details>
|
|
</guidance>
|
|
<display>
|
|
<title>System Health Alarm OPI</title>
|
|
<details>/opt/codac/opi/boy/resources/alarmpages/healthMonitoring/ITER-SYSM-SYSHLTS_Alarm.opi "CBS=EC-GN-SYSM, PPPP=52RF, PP=01, TTT=PSH, NNNN=4410, ALARM_PV=EC-GN-SYSM-52RF-01:PSH4410-SYSHLTS, ALARM_PATH=/CODAC_AlarmHandler/EC/EC-GN/EC-GN-SYSM, LEVEL=ITER-EC-GN-SYSM, ALARM_GUIDANCE1_TITLE=System resource utilization is high, ALARM_GUIDANCE1_DETAILS=Any one of CPU / MEM / Disk / FD of the host is in alarm state. Check the mentioned alarm load and identify the cause. If any load remains high continuously contact maintenance service."</details>
|
|
</display>
|
|
</pv>
|
|
</component>
|
|
|
|
<component name="EC-GN-P01">
|
|
<component name="EC-GN-P01-GAF">
|
|
|
|
|
|
|
|
|
|
</component>
|
|
|
|
<component name="EC-GN-P01-GBF">
|
|
|
|
|
|
|
|
|
|
</component>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</component>
|
|
</component>
|
|
</component>
|
|
</config> |