Configuration file (naa.cnf)
- Organization of this page
Format
read object-ID write object-ID readcomm community-name writecomm community-name
Overview
This file defines the following settings:
-
MIB objects to be acquired from or set to the native agent
-
Adding read-only MIB objects (read)
-
Adding read-write MIB objects (write)
-
-
Community name of the SNMP request to be sent by the native agent adapter to the native agent
-
Specifying the community name used in GET requests (readcomm)
-
Specifying the community name used in SET requests (writecomm)
-
naa.cnf is loaded when the native agent adapter starts. MIB groups to be acquired from the native agent are determined by naa.cnf. SNMP requests regarding the MIB objects defined in naa.cnf are issued from NNM or NNMi.
Location
Solaris, AIX, and Linux: /etc/srconf/agt/naa.cnf
Detailed description
- read object-ID
-
Adds read-only MIB objects when MIB objects are registered on the native agent.
To define MIB subtrees or individual MIB objects as read-only, add read tag lines.
This object-ID is the object identifier of a MIB subtree or an individual MIB object. It must be specified in a numeric format. You cannot use object names here. It is not necessary to specify a suffix to the object ID; however, doing so will not result in an error. The object ID must not begin with a dot (.).
-
object-ID: The table below shows the default object IDs of MIB objects defined in naa.cnf.
-
- write object-ID
-
Adds read-write MIB objects when MIB objects are registered on the native agent.
To specify individual MIB objects as read-write objects, add write tag lines.
This object-ID is the object identifier of an individual MIB object. It must be specified in a numeric format. You cannot use object names here. It is not necessary to specify a suffix to the object ID; however, doing so will not result in an error. The object ID must not begin with a dot (.).
Although it is possible to register MIB subtrees as read-write, this is not recommended.
-
object-ID: The following table shows the default object IDs of MIB objects defined in naa.cnf.
Table 6‒2: Default object IDs of MIB objects defined in the naa.cnf definition file MIB object ID
read/write
Applicable OS
Solaris
AIX
Linux
.1.3.6.1.2.1.2
read
Y
Y
Y
.1.3.6.1.2.1.3
read
Y
Y
Y
.1.3.6.1.2.1.4
read
Y
Y
Y
.1.3.6.1.2.1.5
read
Y
Y
Y
.1.3.6.1.2.1.6
read
Y
Y
Y
.1.3.6.1.2.1.7
read
Y
Y
Y
.1.3.6.1.2.1.10
read
N
Y
N
.1.3.6.1.2.1.12
read
N
Y
N
.1.3.6.1.2.1.25
read
N#
Y
Y
.1.3.6.1.2.1.31
read
N
N
Y
.1.3.6.1.2.1.55
read
N
N
Y
.1.3.6.1.4.1.2
read
N
Y
N
.1.3.6.1.4.1.4
read
N
Y
N
.1.3.6.1.4.1.42
read
Y
N
N
.1.3.6.1.4.1.2021
read
N#
N
Y
- Legend:
-
Y: Defined.
N: Not defined.
- #
-
If you need to acquire the MIB group .1.3.6.1.2.1.25 or .1.3.6.1.4.1.2021 from the native agent, add it to the default MIB objects defined in the naa.cnf configuration file.
-
- readcomm community-name
-
This option specifies the community name used in a GET request sent to the native agent.
To specify a community name (default is public) used in a GET request that is sent from the native agent adapter to the native agent, add a line with the readcomm tag.
Match this community name to the GET community name of the native agent.
The following are notes about specifying community names used in GET requests:
-
Place one space between the readcomm tag and the community name.
-
The maximum length of a community name is 60 characters.
-
In the naa.cnf definition file, specify only one readcomm tag.
-
If you use the readcomm tag, do not specify the -readcomm option in the naaagt process.
-
- writecomm community-name
-
This option specifies the community name used in a SET request sent to the native agent.
To specify a community name (default is public) in a SET request that is sent from the native agent adapter to the native agent, add a line with the writecomm tag.
Match this community name to the SET community name of the native agent.
The following are notes about specifying community names used in SET requests:
-
Place one space between the writecomm tag and the community name.
-
The maximum length of a community name is 60 characters.
-
In the naa.cnf definition file, specify only one writecomm tag.
-
If you use the writecomm tag, do not specify the -writecomm option in the naaagt process.
-
Notes
-
Notes about deleting the naa.cnf definition file
Do not start the native agent adapter after deleting the naa.cnf definition file.
If you start the native agent adapter after deleting the naa.cnf definition file, only MIB-II information is acquired from the native agent. Therefore, specify the MIB objects to be acquired in the naa.cnf definition file.
-
Notes about naa.cnf definition file specifications (in Solaris)
The path names and definition specifications are different for two different naa.cnf configuration files: the one referenced by the naaagt process of the Solaris edition of SNMP Agent, and the one referenced by the naaagt process provided by NNM. The naa.cnf configuration file provided by NNM cannot be used as is by SNMP Agent.
Definition examples
-
This example specifies .1.3.6.1.2.1.2 to define MIB subtrees or individual MIB objects as read-only:
read 1.3.6.1.2.1.2
-
If the naa.cnf configuration file contains the following definitions, the native agent adapter will attempt to retrieve MIB-II interfaces, at, ip, icmp, tcp, udp and host groups from the native agent:
read 1.3.6.1.2.1.2 read 1.3.6.1.2.1.3 read 1.3.6.1.2.1.4 read 1.3.6.1.2.1.5 read 1.3.6.1.2.1.6 read 1.3.6.1.2.1.7 read 1.3.6.1.2.1.25
-
This example specifies .1.3.6.1.4.1.116 to define individual MIB objects as read-only:
write 1.3.6.1.4.1.116
-
This example specifies snmpread as the community name in a GET request:
readcomm snmpread
-
This example specifies snmpwrite as the community name in a SET request:
writecomm snmpwrite