Hitachi

JP1 Version 12 JP1/Extensible SNMP Agent Description, Operator's Guide and Reference


7.6.1 MIB values cannot be acquired

If SNMP Agent cannot acquire MIB values from the manager product even though it is running, check the following:

  1. Check whether the community name of SNMP Agent is the same as that of the manager product.

    If you change the community name of SNMP Agent, make sure that you restart SNMP Agent or the OS.

  2. Check whether a firewall exists between the manager product and SNMP Agent, and, if so, check whether SNMP communications are permitted.

    If necessary, reconfigure the firewall settings.

    You can also use the OS-provided packet trace command to acquire a packet trace to check whether SNMP requests are reaching the OS.

    For details about how to use the OS-provided packet trace command, see the man pages for the relevant command.

    HP-UX(IPF): nettl command

    Solaris: snoop command

    AIX: iptrace command

    Linux: tcpdump command

    • If a MIB value cannot be acquired at times due to a timeout or a noSuchName error

      This type of event occurs if the timeout period for SNMP requests from the manager product is too short.

      Refer to 3.7 Notes about operations to determine an appropriate timeout period.

    • If a MIB value cannot be acquired due to some other cause

      A command that SNMP Agent uses to acquire MIB values is not installed on Solaris, AIX, or Linux.

      Execute the /opt/CM2/ESA/bin/snmpcmdchk command to check whether all required commands are installed. For details, see 2.2.2 Installing the commands used to acquire MIB values (for an OS other than HP-UX (IPF)).