Solaris WBEM Services Administration Guide

Syntax of the Contents of a Mapping File

The following table describes the elements and the syntax of the contents of a mapping file.

Table 3–1 Contents of a Mapping File

Element 

Description 

Required? 

# 

A comment, which is always ignored. 

No 

Version 1.0

The version of the mapping file. The text string that specifies the version must be the first uncommented line. If you do not specify a version as shown, the mapping file is ignored.  

Yes 

1.3.6.1.2.1.1.1.0

The SNMP Object Identifier, or OID, which is the key you want to extract from the SNMP request. The SNMP OID describes an SNMP variable. Because the Adapter currently supports scalars only, the OID must end with the text string .0.

Yes 

Solaris_ComputerSystem

The CIM class name that is associated with the variable. 

Yes 

Description

The CIM property name that defines a characteristic of the specified class and that maps to the SNMP OID variable. 

Yes 

SnmpString

The ASN.1 data type. Values that you can specify, including how they are mapped, are:

  • SnmpString – Move string, number, or CIM LocalDateTime into SnmpString.

  • SnmpInt – Move CIM number data types (including a string in number format) into SnmpInt (signed, 32-bit integer).

  • SnmpCounter – Move CIM number data types (including string in number format) into SnmpCounter (unsigned, 32-bit integer).

  • SnmpGauge – Move CIM number data types (including string in number format) into SnmpGauge (unsigned, 32-bit integer).

  • SnmpTimeticks – Move the time difference, represented in hundredths of a second, into SnmpTimeticks. This value is calculated by subtracting the CIM value from the current time. For example, sysUpTime is calculated by subtracting bootTime from currentTime.

  • SnmpIpAddress – Move string into SnmpIpAddress. You must specify the string in IP address format.

  • SnmpOid – Move string into SnmpOid. You must specify the string in OID format.

  • SnmpOpaque – Move vector of bytes into SnmpOpaque.

Yes