4.3.2 Format of the custom attribute mapping definition file

Specify a custom attribute mapping definition file in the following format:

Format

cia-map
name=NNMi-incident-name-1
cia_1=custom-attribute-name-1
cia_2=custom-attribute-name-2
 ...
cia-map-end

Information to be specified

cia-map

Indicates the beginning of the custom attribute mapping definition.

A custom attribute mapping definition continues to cia-map-end.

name

Defines the name of an NNMi incident. You must define an exact match character string that is case sensitive.

If two or more names are specified between cia-map and cia-map-end, the same mapping processing is executed at the time of the conversion of each NNMi incident name.

An error occurs if you specify the same name more than once in the entire custom attribute mapping definition file, not only between cia-map and cia-map-end but also in any other areas.

cia_$n

Defines a custom attribute name to be set at the index $n of a custom attribute.

You must define an exact match character string that is case sensitive. $n specifies the numbers 1 to 28 and there is no need to specify consecutive numbers.

You can also define this item in random order. (Example: The definition of only cia_15 is acceptable.)

If the same index $n is specified multiple times between cia-map and cia-map-end, search for a custom attribute name in the defined order and the matched attribute is mapped.

If you define this item as cia_3=.1.3.6.1.2.1.2.2.1.1.2, the name, type, and value of a custom attribute whose custom attribute name is .1.3.6.1.2.1.2.2.1.1.2 are set in NNMI_CIA_NAME_3, NNMI_CIA_TYPE_3, and NNMI_CIA_VALUE_3 respectively.

cia-map-end

Indicates the end of the custom attribute mapping definition.

A custom attribute mapping definition continues from cia-map to this item.

Example

 1:  cia-map
 2:  name=SNMPLinkUp
 3:  cia_1=.1.3.6.1.2.1.2.2.1.1.2
 4:  cia_2=cia.address
 5:  cia-map-end
 6:
 7:  cia-map
 8:  name=SNMPColdStart
 9:  name=SNMPWarmStart
10:  cia_5=cia.address
11:  cia-map-end

Definitions in line 1 to line 5

When NNMi incidents whose name is SNMPLinkUP are converted, the name, type, and value of a custom attribute whose custom attribute name is .1.3.6.1.2.1.2.2.1.1.2 are set in NNMI_CIA_NAME_1, NNMI_CIA_TYPE_1, and NNMI_CIA_VALUE_1 respectively.

In the same way, the name, type, and value of a custom attribute whose custom attribute name is cia.address are set in NNMI_CIA_NAME_2, NNMI_CIA_TYPE_2, and NNMI_CIA_VALUE_2 respectively.

Definitions in line 7 to line 11

When NNMi incidents whose name is SNMPColdStart or SNMPWarmStart are converted, the name, type, and value of a custom attribute whose custom attribute name is cia.address are set in NNMI_CIA_NAME_5, NNMI_CIA_TYPE_5, and NNMI_CIA_VALUE_5 respectively.

When the definitions are applied

When you start a service or execute the reload command (jegn_spmd_reload), the settings take effect.

If an error occurs during service startup, the service fails to start.

If an error occurs when the reload command is executed, the changes are not applied and the system operates according to the definitions before the execution of the command.

Note

A line beginning with a hash mark (#) is treated as a comment line.
The maximum size of the custom attribute mapping definition file is 10 MB.

To Page Top