jpctool alarm import
- Organization of this page
Format
jpctool alarm import -f alarm-definition-file-name [-y|-n] [-wait number-of-seconds]
Function
The jpctool alarm import command imports alarm definitions from the specified file, and defines and updates an alarm table and alarms.
Definition information is imported in units of alarms. If the alarm definition file contains definitions of multiple alarms and importation of one alarm's definition terminates abnormally, import processing continues for the next alarm definition. If multiple errors occur while the command is importing multiple alarm definitions, the return code set by the command is for the last error that occurred.
Before importing definition information, this command checks the syntax of the alarm definition file and the validity of the definition information. If there is an error in the syntax of the alarm definition file or the validity of the definition information, the command displays an error message containing the row number in the file and the nature of the error only for the first error that occurred.
The following table lists and describes the cause and nature of the errors that can be displayed in the error message:
Cause of error |
Nature of error |
---|---|
The specified entry is invalid |
A specified label name or section name is invalid. |
The specified value is invalid |
A specified value is invalid. |
The syntax is invalid |
There is a syntax error in the alarm definition file. |
The entry (label-name-or-section-name) is not specified |
The indicated required label or section is missing. |
The specified product is invalid |
A specified product ID or data model version is invalid. |
The specified field is not defined |
A specified record name or field name is not supported by the PFM - Agent or PFM - RM with the specified product ID. |
The specified report is not defined |
A specified report is not defined in the PFM - Agent or PFM - RM with the specified product ID. |
The specified Action Handler is not defined |
The specified action handler is missing. |
The specified Action Handler does not have capability |
The specified action handler has not been set to execute the specified action. |
A Character-code is invalid |
The specified character encoding is invalid. |
The specified definition is too many |
The number of alarm definitions exceeds the permitted maximum. |
Total length of Abnormal condition definition is too long |
The length of an abnormal condition statement in the alarm definition exceeds the permitted maximum length. |
Total length of Warning condition definition is too long |
The length of a warning condition statement in the alarm definition exceeds the permitted maximum length. |
Hosts that can execute the command
PFM - Manager
Execution permission
- In Windows:
-
User with Administrators permissions
- In UNIX:
-
User with root user permissions
Installation directory
- In Windows:
installation-folder\tools\
- In UNIX:
/opt/jp1pc/tools/
Arguments
-f alarm-definition-file-name
Specifies the name of the alarm definition file that is to be imported. The file name can be expressed as a relative path or an absolute path.
The string you specify can have double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:
% - ( ) _ . @ [ ]
If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.
-y|-n
Specifies whether or not the existing definition information is to be updated forcibly if an alarm definition to be imported already exists.
When -y is specified, the command forcibly updates the existing alarm definition.
When -n is specified, the command skips update processing.
When this option is omitted, the command displays a confirmation message asking whether or not an existing alarm definition is to be overwritten.
-wait number-of-seconds
Specifies the maximum wait period (in seconds) applied when a command that cannot be executed with this command is running. When the setting to suspend execution of wait alarm commands (Alarm Command Wait Mode) is enabled in the startup information file (jpccomm.ini), if you want to specify a wait period (in seconds) separately from the wait period specified in the jpccomm.ini file, specify a value in the range from 1 to 3,600 for this option.
If you omit the option, this command runs with the wait period (in seconds) specified in the jpccomm.ini file.
For details on the commands that cannot be executed with this command, see Commands that cannot be executed with alarm commands. For details on the jpccomm.ini file and Alarm Command Wait Mode, see F. Startup Information File (jpccomm.ini).
Alarm definition file format
List of settings values
-
Alarm Definition File Version label
Specifies the version of the alarm definition file syntax. The specified location is at the beginning of the file.
Type |
Description |
---|---|
Description |
Indicates the version of the alarm definition file syntax. |
Specifiable value |
0001 or 0002 can be specified.
|
Omissible |
No |
-
Alarm Definition File Code label
The encoding for the alarm definition file is specified immediately after the Alarm Definition File Version label.
Type |
Description |
---|---|
Description |
Indicates the encoding for the alarm definition file. |
Specifiable value |
|
Omissible |
No |
-
Alarm Data section
Specifies the definition for a single alarm. When multiple alarms are defined, an Alarm Data section is created for each alarm definition. The Alarm Data section cannot be omitted.
The subsections that can be specified within the Alarm Data section are as follows.
Subsection name |
Description |
Optional |
---|---|---|
General |
Sets basic information such as alarm name. |
No |
Advanced Setting |
Sets the alarm type and options. |
Yes |
Check Value Exist |
Sets the monitored values for alarms that monitor the existence of a value. |
Yes (depending on the alarm definition) |
Alarm Condition Expressions |
Sets an alarm conditional expression for alarms other than those that monitor the existence of a value. |
Yes (depending on the alarm definition) |
Actions |
Sets the executed action and displayed report for an alarm. |
Yes |
Action Definition E-mail |
Specifies the settings for when an email is executed by an alarm. |
Yes (depending on the alarm definition) |
Action Definition Command |
Specifies the settings for when a command is executed by an alarm. |
Yes (depending on the alarm definition) |
Action Definition JP1 Event |
Specifies the settings for when a JP1 event is executed by an alarm. |
Yes (depending on the alarm definition) |
- Legend:
-
Yes: Can be omitted.
No: Cannot be omitted.
-
General subsection
Specifies basic alarm information (such as the alarm name and message text). This subsection cannot be omitted.
The labels that can be specified for this subsection are as follows.
Type |
Description |
---|---|
Description |
Indicates the product and data model version for the alarm. |
Specifiable value |
<product-ID><data-model-version>
|
Omissible |
No |
Type |
Description |
---|---|
Description |
Indicates the alarm table name. |
Specifiable value |
A string that is 1 to 64 bytes long and consists of double-byte and/or single-byte characters. Any spaces after equals signs (=) and before line returns are ignored. Names starting with PFM (case-insensitive) cannot be specified. |
Omissible |
No |
Type |
Description |
---|---|
Description |
Indicates the alarm name. |
Specifiable value |
A string that is 1 to 20 bytes long and consists of double-byte and/or single-byte characters. Any spaces after equals signs (=) and before line returns are ignored. |
Omissible |
No |
Type |
Description |
---|---|
Description |
Indicates the message text output when the alarm event occurs. |
Specifiable value |
A string that is 0 to 255 bytes long and consists of double-byte and/or single-byte characters. Any spaces after equals signs (=) and before line returns are ignored. If the equals sign is only followed by spaces, these spaces are treated as not being specified. |
Omissible |
Yes |
Type |
Description |
---|---|
Description |
Indicates whether the alarm monitors the existence of a value. |
Specifiable value |
Y or N can be specified.
|
Omissible |
Yes |
-
Advanced Setting subsection
Specifies extended alarm information (such as the alarm type and monitoring time). This subsection can be omitted.
The labels that can be specified for this subsection are as follows.
Note that you can specify the Notify State label only when the value of the Alarm Definition File Version label is 0002.
Type |
Description |
---|---|
Description |
Indicates the alarm status. |
Specifiable value |
Y or N can be specified.
|
Omissible |
Yes |
Type |
Description |
---|---|
Description |
Indicates whether the alarm setting Always notify is enabled. |
Specifiable value |
Y or N can be specified.
|
Omissible |
Yes |
Type |
Description |
---|---|
Description |
Indicates whether the alarm setting Evaluate all data is enabled. |
Specifiable value |
Y or N can be specified.
|
Omissible |
Yes |
Type |
Description |
---|---|
Description |
Indicates whether to enable the notification of a change of status. |
Specification format |
Notify State=Alarm|Instance |
Specifiable value |
Alarm or Instance can be specified.
|
Omissible |
Yes (When omitted, specification of Alarm is assumed.) |
Remarks |
When Instance is specified, a syntax error occurs if the value of the Regular Alarm label and Evaluate All Data label is Y. |
Type |
Description |
---|---|
Description |
Indicates whether the Always monitor alarm setting is enabled. |
Specifiable value |
Y or N can be specified.
|
Omissible |
Yes |
Type |
Description |
---|---|
Description |
Indicates the monitoring time when the Always monitor alarm setting is disabled. |
Specifiable value |
start-time-end-time This specifies the local time in HH:MM format. start-time and end-time are joined with a hyphen (-).
|
Omissible |
Yes (but not when the value of the Monitoring Regularly label is N) |
Type |
Description |
---|---|
Description |
Indicates whether the Report alarm when the following damping condition is reached alarm setting is enabled. |
Specifiable value |
Y or N can be specified.
|
Omissible |
Yes |
Type |
Description |
---|---|
Description |
Indicates the number of times the threshold was exceeded and the measurement interval, when the Report alarm when the following damping condition is reached alarm setting is enabled. |
Specifiable value |
number-of-times-threshold-exceeded/interval-value Integers from 1 to 32767 can be specified for number-of-times-threshold-exceeded and interval-value, joined with a slash (/). If interval-value is less than number-of-times-threshold-exceeded, interval-value is treated for processing as having the same value as number-of-times-threshold-exceeded. This cannot be omitted when the value of the Damping label is Y. If the value of the Damping label is N, or the label is omitted, this specification is ignored. |
Omissible |
Yes (but not when the value of the Damping label is Y) |
-
Check Value Exist subsection
If the Monitor whether the value exists alarm setting is enabled, this subsection specifies the record and values to be monitored. This subsection can be omitted, except when the Check Value Exist label is set to Y in the General subsection.
The labels that can be specified for this subsection are as follows.
Type |
Description |
---|---|
Description |
If the Monitor whether the value exists alarm setting is enabled, this shows the records for the target to be monitored. |
Specifiable value |
This specifies the record ID of the records to monitor, in 1 to 7 single-byte characters. You can specify only the record ID of a multi-instance record. For details about record IDs, see the chapter in the PFM - Agent or PFM - RM manuals that describes records. |
Omissible |
No |
Type |
Description |
---|---|
Description |
If the Monitor whether the value exists alarm setting is enabled, this shows the record fields for the target to be monitored. |
Specifiable value |
This specifies the PFM - Manager name for the fields to be monitored, in 1 to 50 single-byte characters. |
Omissible |
No |
Type |
Description |
---|---|
Description |
If the Monitor whether the value exists alarm setting is enabled, this shows the value to monitor for existence. |
Specifiable value |
The value that can be specified differs depending on the field value. You can specify an integer, a fractional value, or a string that is 1 to 127 bytes long and consists of double-byte and/or single-byte characters. Control characters and (, ), [, ], <, >, =, or " cannot be specified. To specify these characters, use the wildcard character to specify the values. To use the hash mark (#) in the value to monitor for existence, specify \#. To use the backslash (\) in the value to monitor for existence immediately before a specified wildcard character, use \\. |
Omissible |
No |
-
Alarm Condition Expressions subsection
This subsection specifies records and values to be monitored by alarms. This subsection can be omitted, except when the Check Value Exist label does not exist in the General subsection, or is set to N.
The labels that can be specified for this subsection are as follows.
Type |
Description |
---|---|
Description |
Indicates the conditional expressions for monitoring by using an alarm. |
Specifiable value |
Conditional expressions for monitoring by using an alarm are specified in the following format: <monitored-field><condition><abnormal-value>,<warning-value>
To set multiple conditions, join each condition with AND. As many as five conditional expressions can be specified together. If multiple conditional expressions are specified, they are evaluated in the order specified (starting with the expression that begins from the left). Note that if measurement values are displayed by using %CVS variables, field locations are determined in the order specified (starting with the expression that begins from the left). If an alarm definition that contains three or more conditional expressions is displayed in PFM - Web Console, these conditional expressions are listed within parentheses (()) in the priority order (the expression with the lowest priority comes first).
When an alarm for which the conditions for the abnormal value and warning value are different (such as abnormal value < 50 and warning value <= 60) is exported, the warning value is given priority for export (or the abnormal value if the warning value does not exist). When an alarm with no abnormal value or warning value is exported, <abnormal-value> or <warning-value> are left blank. When registered to PFM - Manager, conditional expressions are divided into abnormal conditions and warning conditions. An
error will occur and registration will fail when the length of any conditional expression exceeds 749 bytes. The length of
conditional expressions that can be registered with PFM - Manager can be calculated by the following formula, where n (1 Length of conditional expression for abnormal values = Length of conditional expression for warning values = ai: The length of the ith <monitored-field>, in bytes bi: The length of the ith <condition>, in bytes ci: The length of the ith <abnormal-value>, in bytes. When a string is specified, the length does not include quotation marks. di: The length of the ith <warning-value>, in bytes. When a string is specified, the length does not include quotation marks. |
Omissible |
No |
-
Actions subsection
This subsection specifies the actions executed and reports displayed when an alarm event occurs. This subsection can be omitted.
The labels that can be specified for this subsection are as follows.
Type |
Description |
---|---|
Description |
Indicates the name of the displayed report when the alarm event occurs. |
Specifiable value |
An absolute path of the folder tree (from the Reports/ folder) that is 0 to 1,024 bytes long and consists of double-byte and/or single-byte characters. If the name contains \ or / (except for the folder separator character), each should be entered as \\ and \/. If the label value or label itself is omitted, this specification is treated as unspecified. |
Omissible |
Yes |
Type |
Description |
---|---|
Description |
Indicates the alarm event for the e-mail execution target of the action executed by the alarm. |
Specifiable value |
The following values can be specified.
To perform execution on multiple alarm events, specify a string indicating the statuses, with each status separated by a comma (,). The statuses are in random order, but an error will occur if the same status is specified more than once. Warning cannot be specified when the Check Value Exist label is set to Y in the General subsection. Normal cannot be specified when the Regular Alarm label is set to Y in the Advanced Setting subsection. |
Omissible |
Yes |
Type |
Description |
---|---|
Description |
Indicates the alarm event used as the command execution target for the action executed by alarm. |
Specifiable value |
The following values can be specified.
To perform execution on multiple alarm events, specify a string indicating the statuses, with each status separated by a comma (,). The statuses are in random order, but an error will occur if the same status is specified more than once. Warning cannot be specified when the Check Value Exist label is set to Y in the General subsection. Normal cannot be specified when the Regular Alarm label is set to Y in the Advanced Setting subsection. |
Omissible |
Yes |
Type |
Description |
---|---|
Description |
Indicates the kind of statuses for which an alarm performs SNMP trap notification. |
Specifiable value |
The following values can be specified.
To perform execution on multiple alarm events, specify a string indicating the statuses, with each status separated by a comma (,). The statuses are in random order, but an error will occur if the same status is specified more than once. Warning cannot be specified when the Check Value Exist label is set to Y in the General subsection. Normal cannot be specified when the Regular Alarm label is set to Y in the Advanced Setting subsection. |
Omissible |
Yes |
Type |
Description |
---|---|
Description |
Indicates whether JP1 event execution is set for action execution. |
Specifiable value |
Y or N can be specified.
If no value is specified for the Command label, this specification is ignored. |
Omissible |
Yes |
-
Action Definition E-mail subsection
This subsection specifies the settings for executed actions (e-mail) when an alarm event occurs. This subsection can be omitted, except when e-mail execution is specified in the Actions subsection.
The labels and sub-subsections that can be specified for this subsection are as follows.
Type |
Description |
---|---|
Description |
Indicates the e-mail recipient. |
Specifiable value |
The value can be specified in 1 to 127 single-byte characters. Multiple recipients can be specified by separating each with a comma (,). In this case, the total length must be within 127 bytes. |
Omissible |
No |
Type |
Description |
---|---|
Description |
Indicates the service ID of the action handler for which e-mail is sent. |
Specifiable value |
The value can be specified in 1 to 258 single-byte characters. Even when the product name display functionality is enabled, the product name cannot be specified. To specify a local action, specify LOCAL. |
Omissible |
No |
Type |
Description |
---|---|
Description |
Indicates the message contents sent by e-mail. |
Specifiable value |
A string that is 0 to 1,000 bytes long and consists of double-byte and/or single-byte characters. In this sub-subsection, contents until the first line of the next section or subsection, or end of the file (EOF), can be set as the defined value. Note that any comments in the sub-subsection are excluded. Also, valid line return characters in the final line of the sub-subsection are excluded. |
Omissible |
Yes |
-
Action Definition Command subsection
This subsection specifies settings for executed actions (command) when alarm events occur. This subsection can be omitted, except when command execution is specified in the Actions subsection, and the value of the JP1 Event label is set to N (this is ignored when the JP1 Event label is set to Y).
The labels and sub-subsections that can be specified for this subsection are as follows.
Type |
Description |
---|---|
Description |
Indicates the name of the command (script) executed for the action. |
Specifiable value |
The value can be specified in 1 to 511 single-byte characters. When specifying this label, specify an absolute path or relative path from the current service directory when using a command (script) other than those in the following directories:
|
Omissible |
No |
Type |
Description |
---|---|
Description |
Indicates the service ID of the action handler for which the command is executed. |
Specifiable value |
The value can be specified in 1 to 258 single-byte characters. Even when the product name display functionality is enabled, the product name cannot be specified. To specify a local action, specify LOCAL. |
Omissible |
No |
- Note
-
Depending on the alarm action setting specified in the PFM - Web Console, the load might concentrate on the PFM - Manager host. To prevent this, open the New Alarm > Action Definitions page or the Edit > Action Definitions page, and then, in the Command field, select LOCAL for the command execution action handler. If you want actions to be triggered by alarms in a large-scale system, make sure that you select LOCAL to prevent the PFM - Manager host from being heavily loaded.
Type |
Description |
---|---|
Description |
Indicates parameters to pass to executed commands. |
Specifiable value |
A string that is 0 to 2,047 bytes long and consists of double-byte and/or single-byte characters. In this sub-subsection, contents until the first line of the next section or subsection, or end of the file (EOF), can be set as the defined value. Note that any comments in the sub-subsection are excluded. Also, valid line return characters in the final line of the sub-subsection are excluded. |
Omissible |
Yes |
-
Action Definition JP1 subsection
This subsection specifies settings for actions (JP1 events) executed when an alarm event occurs. This subsection can be omitted, except when command execution is specified in the Actions subsection, and the JP1 Event label is set to Y.
The labels that can be specified for this subsection are as follows.
Type |
Description |
---|---|
Description |
Indicates the event ID sent to the JP1 event. |
Specifiable value |
The event ID is specified as a hexadecimal number. Values from 0 to 1fff and 7fff8000 to 7fffffff can be specified. |
Omissible |
No |
Type |
Description |
---|---|
Description |
Indicates the action handler to be executed for the JP1 event. |
Specifiable value |
The value can be specified in 1 to 258 single-byte characters. Even when the product name display functionality is enabled, the product name cannot be specified. To specify a local action, specify LOCAL. |
Omissible |
No |
Type |
Description |
---|---|
Description |
Indicates the message sent to the JP1 event. |
Specifiable value |
A string that is 0 to 1,023 bytes long and consists of double-byte and/or single-byte characters. To issue JP1 events with the Action Handler service in version 09-00 or earlier, specify a string that is 0 to 128 bytes long and consists of double-byte and/or single-byte characters. |
Omissible |
Yes |
Type |
Description |
---|---|
Description |
Indicates whether the alarm level is converted to a JP1 event priority. |
Specifiable value |
Y or N can be specified.
|
Omissible |
Yes |
Type |
Description |
---|---|
Description |
Indicates the name of the event server registered for the JP1 event. Specified when the event server is operating on a logical host. |
Specifiable value |
The value can be specified in 0 to 255 single-byte characters. If no value is specified, this is treated as being omitted. |
Omissible |
Yes |
The following shows an example of an alarm definition file.
Example of an alarm definition file
Alarm Definition File Version=0002 Alarm Definition File Code=US_ASCII [Alarm Data] [[General]] Product=T3.0 Alarm Table Name=Example Alarm Name="CPU Usage" Message Text="CPU is at %CVS% utilization" Check Value Exist=N [[Advanced Setting]] Active Alarm=Y Regular Alarm=N Evaluate All Data=N Notify State=Alarm Monitoring Regularly=Y #Monitoring Time= Damping=Y Damping Count=2/3 #[[Check Value Exist]] #Record= #Field= #Value= [[Alarm Condition Expressions]] Condition=PI_PCT_TOTAL_PROCESSOR_TIME>90.000000,80.000000 [[Actions]] Report="Reports/Windows/Operating System/Troubleshooting/Real-Time/CPU Usage - Top 10 Processes" E-mail=Abnormal,Warning Command=Abnormal SNMP=Abnormal,Warning,Normal JP1 Event=N [[Action Definition E-mail]] E-mail Address=administrator@example.com Action Handler=PH1host01 [[[Message Text]]] Date: %SCT Host: %HNS Product: %PTS Agent: %ANS Alarm: %AIS (%ATS) State: %SCS Message: %MTS [[Action Definition Command]] Command Name=userprogram.exe Action Handler=LOCAL [[[Message Text]]] %CVS #[[Action Definition JP1 Event]] #Event ID= #Action Handler= #Message=%MTS #Switch Alarm Level=Y #Exec Logical Host=
Notes
-
This command cannot be executed concurrently.
-
This command cannot be executed if any of the Name Server, Master Manager, and View Server services is stopped.
-
You can define a maximum of 250 alarms in an alarm definition file.
-
You can define a maximum of 250 alarms in an alarm table, including alarms that have already been defined. Even if the number of alarms in an imported alarm definition file does not exceed 250, an error results if the total count including the imported alarms will exceed 250.
-
If the alarm definition file contains a read-only alarm table (whose name begins with PFM), an error results; the command does not overwrite such alarm definitions even if the -y option is specified.
-
If the alarm definitions you import include double-byte characters, the LANG environment variable for the shell that is used to execute the command must be set to Japanese (Shift JIS, EUC, or UTF-8) or Simplified Chinese (GB18030 or UTF-8). In addition, the value of that LANG environment variable must be the same as the value of the LANG environment variable that is loaded when PFM - Manager starts. Before you execute this command, make sure that the LANG environment variable settings of the shell and PFM - Manager match.
-
If the file name you specify includes double-byte characters, the LANG environment variable for the shell that is used to execute the command must be set to Japanese (Shift JIS, EUC, or UTF-8) or Simplified Chinese (GB18030 or UTF-8). Before you execute this command, check the setting of the LANG environment variable for the shell.
-
If PFM - Manager is installed on a logical host, execute the command on the executing node.
-
You can define a maximum of 250 alarms at once by using the jpctool alarm import command.
This command is useful when you define alarms on multiple servers in a large-scale system.
Note that the number of alarms that you can define at once cannot exceed 250 even if the import file contains multiple alarm tables.
An import using the following file succeeds:
Import file 1:
100 alarms are defined in alarm table A.
150 alarms are defined in alarm table B.
An import using the following file fails:
Import file 2:
200 alarms are defined in alarm table A.
150 alarms are defined in alarm table B.
-
When performing multiple monitoring, you cannot execute this command from the secondary PFM - Manager host.
-
If you specify an alarm table bound to an agent that does not support the notification of state changes for each instance, a KAVE05970-E message will be output each time an alarm defined to report state changes for each instance occurs.
-
In the alarm definition file to be imported, 0001 or 0002 must be specified for the Alarm Definition File Version label. If another version of alarm definition file is specified, an error message will be output.
-
If an alarm to report state changes for each instance is defined in the alarm definition file to be imported, 0002 must be specified for the Alarm Definition File Version label in the alarm definition file.
-
To import an alarm definition file exported from PFM - Manager 10-10 or later to PFM - Manager 10-00 or earlier, the alarm definition file must be modified. The following table describes the required modifications of the alarm definition file:
Label to be modified
Setting before modification
Modification
Alarm Definition File Version
0002
Change the setting to 0001.
Notify State
Alarm|Instance
Delete the setting because PFM - Manager 10-00 or earlier does not support the definition of the notification of state changes for each instance.
-
For notes on successive stopping of the monitoring using alarms and the monitoring target system, see Notes on execution of jpctool alarm commands.
Return values
0 |
The command terminated normally. |
1 |
An argument specification is invalid. |
2 |
The user does not have execution permission for the command. |
3 |
At least one of the Name Server, Master Manager, and View Server services is not running. |
4 |
The startup stop command or another setup command was executed on the same machine. |
5 |
The command was executed on a host that is not the PFM - Manager host. Or else, an attempt was made to execute the command from the secondary PFM - Manager host when multiple monitoring is performed. |
6 |
There is an error in the contents of the alarm definition file. |
11 |
The user canceled the processing. |
13 |
The notification of state changes for each instance cannot be specified because the alarm table is bound to an agent that does not support the notification of state changes for each instance. |
100 |
The Performance Management environment is invalid. |
200 |
A memory shortage occurred. |
210 |
A disk space shortage occurred. |
211 |
Alarm definition file cannot be accessed, or alarm definition or updating failed because the alarm was being updated. |
222 |
A communication error occurred. |
223 |
Communication processing resulted in a timeout. |
255 |
An unexpected error occurred. |
Usage example
This example imports the alarmtest1.cfg alarm definition file stored in the /tmp directory:
jpctool alarm import -f /tmp/alarmtest1.cfg