3.7 Notes about operations

This section provides notes about SNMP Agent operations common to all OSs. For OS-specific notes, see the relevant subsections.

• Notes about a file whose size continually increases with no capacity limits

  The following table shows a log file whose size continually increases after operations start.

  Table 3‒4: Notes about a file whose size continually increases with no capacity limits

  Path	Process that outputs logs	Note
  /tmp/esa.log	Shell during installation and uninstallation	You can delete this file, except when this product is being installed or uninstalled.

  There are no capacity limits for this file.

• Notes about log files

  The following table provides notes about the log files that are output after operations start.

  Table 3‒5: Notes about the log files that are output after operations start

  Path#1	Process that outputs logs	Note
  /var/adm/snmpd.logn	snmpdm	By default, 10 log files (n: 1 to 10) with a file size of 10 megabytes each are acquired in wraparound mode. If this default value introduces an operating problem, change the log file size, number of log files, and output destination path.#2

  #1: For AIX, the files are located under /usr/adm.

  #2: For details about changing the log file size, number of files, and output destination path, see 7.3 Collecting logs.

• Notes about the files used by SNMP Agent

  SNMP Agent uses the files in and under the /tmp/.AgentSockets directory. Do not delete any of these files while SNMP Agent is running.

  You can delete these files while SNMP Agent is stopped. SNMP Agent creates this directory when it starts.

• Notes about changing the IP address of the node

  If you have changed the IP address of the node while SNMP Agent is running, restart SNMP Agent.

• Notes about backing up the environment variable definition files

  • When you back up an environment variable definition file, make sure that the name of the backup file does not begin with Snmp. The following shows an example of a name for a backup file:

    Example: Backup file of /opt/CM2/ESA/opt/SnmpMaster

    /opt/CM2/ESA/opt/Bak.SnmpMaster

  • If your OS is Solaris, do not create backup environment variable definition files under /etc/rc.config.d.

• Notes about the native agent adapter function

  In Solaris, AIX and Linux systems, use the same community name for SNMP Agent's native agent adapter and the OS-provided native agent.

• Notes about SNMP Agent execution permissions

  Only a user with root permissions can access SNMP Agent files. Do not change the file access permissions.

• Language environment for SNMP Agent

  SNMP Agent outputs only English messages regardless of the language environment used to run SNMP Agent. You can also change the system's language environment after you have installed SNMP Agent without any problem.

• Notes about using JP1/SSO to collect resources

  • Specify a timeout value and retry count for each platform.

    The table below lists the timeout values recommended for each OS. The timeout value depends on the system load and the network environment. Specify a timeout value appropriate to your environment.

    Table 3‒6: Recommended timeout value

    OS	Recommended timeout value
    Solaris	6.0 seconds or more
    AIX	3.0 seconds or more
    Linux	3.0 seconds or more
    HP-UX (IPF)	0.8 seconds or more

    The SNMP requests use UDP, but you must specify a retry count because UDP does not have a retry function.

  • If you use NNM to acquire enterprise-specific MIBs, refer to the notes about MIBs. For details, see the notes about groups in 4.2.2 Description of Hewlett-Packard enterprise-specific MIB objects and 4.3.2 Description of Hitachi enterprise-specific MIB objects.

• Notes about changing the system time

  To advance the system time, no special procedure is needed.

  To set back the system time, follow the procedure below:

  1. Use the snmpstop command to terminate SNMP Agent.

     If the OS being used is Solaris or AIX, and you do not want to shut down the native agent, execute the snmpstop command with the -n option.

  2. Change the system time.

  3. Use the snmpstart command to restart SNMP Agent.

     If the OS being used is Solaris or AIX, and you do not want to start up the native agent, execute the snmpstart command with the -n option.

• Notes about sending coldStart traps when the OS starts up

  By default, the snmpdm process of the master agent sends a coldStart trap 15 seconds after it starts up.

  No response is sent to the manager's request during this time because the process sends a coldStart trap without checking whether startup processing is completed for other subagents. Normally 15 seconds are sufficient for subagents to complete their startup processing; however, some subagents might require more time depending on the environment. If this is the case, adjust the timing of coldStart transmission by specifying the appropriate time (in seconds) before the coldStart trap can be sent in the SNMP_HTC_INIT_WAIT_TIME environment variable in the SnmpMaster file.

  The following shows a specification example for the SNMP_HTC_INIT_WAIT_TIME environment variable.

  Example:

  SNMP_HTC_INIT_WAIT_TIME=15

  export SNMP_HTC_INIT_WAIT_TIME

• Notes about reloading the configuration file (/etc/SnmpAgent.d/snmpd.conf) during SIGNUP reception

  While SNMP Agent is running, the configuration file (/etc/SnmpAgent.d/snmpd.conf) is not re-loaded during SIGNUP reception.

Organization of this section

• 3.7.1 Notes about operations (for Solaris)

• 3.7.2 Notes about operations (for AIX)

• 3.7.3 Notes about operations (for Linux)

• 3.7.4 Notes about renaming a host

To Page Top