Version numbering
Alarm template XML documents must contain a version number that must contain a fractional part represented as a whole number.
For example, 1.0, 2.0 and 3.0 are all valid version numbers whereas 1.1 is not.
This is to keep the versioning scheme in line with alarm definitions, which use the same version numbering system.
Usage
Usage for alarm_admin:
-h | -help | --help |
} | {
-load -t|-d <alarm_template_or_definition_xml_file> |
-load -t|-d -all <alarm_temp_def_files_directory> |
-drop -context <context> -name <name> -version <version> |
-unload -t|-d -context <context> -name <name> -version <version> -file <file> |
-unload -t|-d -all <alarm_temp_def_files_directory> |
-list |
-createcontext <document_context_path> |
-removecontext <document_context_path> [-r]
}
| Option | Description |
|---|---|
| -list | Shows a summary of all loaded alarm templates. |
| -load <alarm_template_xml_file> | Create or update a single template or definition from an XML file. |
|
Create or update all templates or definitions from a folder. |
| -drop -context <context> -name <name> -version <version> | Not currently supported. Requires the context, template name, and version. |
| -unload -t|-d -context <context> -name <name> -version <version> -file <file> | Unload a template or definition to a file. |
|
Unload all templates or definitions to a folder. |
| -createcontext <document_context_path> | Must be one or more path element names separated by "." For example, "IP Layer.IP Layer 1". |
| -removecontext <document_context_path> [-r] | Must be one or more path element names separated by ".". For example, "IP Layer.IP Layer 1". |