| |
Home |
![[Table of Contents]](/dwicons/b_toc.gif)
|
SNMP SubAgent User's Guide (UNIX) |
![[-]](/dwicons/i_colpse.gif)
| Appendix C: Troubleshooting |
This appendix provides troubleshooting information for the master agent EMANATE and the Subagent. If the information in this appendix does not help you solve your problem, see "When to Contact Sybase Technical Support" before calling Sybase Technical Support.
Before you contact Sybase Technical support, you should try to resolve your issues with the information in this appendix. If you are encountering problems with master agent configuration files or network managers, see the following two sections for additional technical support requirements.
As part of the master agent installation, Sybase provides a default set of SNMP version 2 (V2) configuration files. If the default settings in these files are not acceptable, you can modify the existing V2 configuration files for your environment or create new configuration files. However, before you modify the default V2 configuration files, you should be completely familiar with RFCs 1441 through 1452.
If you encounter problems with the default V2 configuration files or if you need assistance producing V2 security files using snmpv2, you can contact Sybase Technical Support. However, if you modify the default parameters in the configuration files, Sybase Technical Support cannot help you debug your configuration.
To determine if you have the default configuration files, edit agt.pty in the $SR_AGT_CONF_DIR directory. In agt.pty, look for the entry that begins snmpUDPDomain. If the two lines following each snmpUDPDomain entry consist of a dash (-), you have the default configuration files. For example, the following is a default configuration file:
snmpUDPDomain 127.0.0.1 161 300 1458
1 nonVolatile true 0
-
-
However, if the second of the two lines following any of the snmpUDPDomain entries contain a set of hexadecimal numbers, you do not have the default configuration files. For example, the following is not a default configuration file:
snmpUDPDomain 127.0.0.1 161 300 1458
3 nonVolatile true 0
-
2a 47 66 37 5a 2f
Before you call Sybase Technical Support, you should reset your environment to the default configuration files using snmpdv2. See Appendix B, "SNMP Version 2 Configuration," for more information on creating a new set of default configuration files for your environment.
If you are developing a network manager and are having problems communicating with the master agent EMANATE, you should not contact Sybase Technical Support. Instead, you should contact SNMP Research, Inc. (support@snmp.com) or Sybase Professional Services. Both organizations have consultants that are willing to assist you.
The Subagent has two built-in diagnostic features: you can run the Subagent in diagnostic mode, or you can use the Subagent log file to capture messages. In addition, Sybase provides the getmany command that allows you to query the Subagent for current values. The following sections describe the Subagent's diagnostic capabilities and getmany.
You can start the subagent in two different modes: normal or diagnostic. When you start the Subagent in diagnostic mode, it:
Before you run the Subagent in diagnostic mode, make sure all of the SQL Servers and Open Servers that you listed in snmp.ini are running.
To run the Subagent in diagnostic mode, enter the command:
sybagt -D
After the Subagent connects to each server and updates snmp.ini, it shuts down. During the diagnostic process, the Subagent writes all status and error messages to sybagt.log in the /tmp directory. See Appendix A, "Messages," for details on messages and correcting problems.
Note: By default the -D flag directs the Subagent to send all messages to sybagt.log in the /tmp directory. However, you can send messages to a different file by using the -e flag. See "Starting the Subagent" for more information.
When you start the Subagent, you can direct it to send all informational, warning, and error messages to a log file. If you are encountering problems, the log file is a good tool to use for capturing information.
To direct the Subagent to use the log file, use the -e flag in the command line. For example, the command:
sybagt -e $SYBSNMP/subagent.log
directs the Subagent to send all log file messages to the file subagent.log in the $SYBSNMP directory. See "Starting the Subagent" for more information on the -e flag. See Appendix A, "Messages," for details about interpreting error messages and correcting problems.
Note: After you have diagnosed and resolved the problem, it is good practice to restart the Subagent without the -e flag.
As part of the Subagent distribution, Sybase provides getmany. getmany allows you to extract values from objects that the Subagent is maintaining. You typically use getmany to determine if the values the Subagent has are the same values that the network manager is displaying.
Before you use getmany, you must set the environment variable SR_MGR_CONF_DIR to the master agent utility directory. Typically, this directory is /etc/srconf/mgr, but it may be different for your environment. See "Setting Environment Variables" for more information.
getmany is in the $SYBSNMP/bin directory and its syntax is:
getmany host com_string object
where host is the name of the host on which the agents are running, com_string is a community string, and object is the MIB object whose value you want to check. For example, the command:
getmany squonk public sybase
contacts the master agent on "squonk" using the "public" community string for information on the "sybase" object. Using this command, getmany produces something similar to the following:
sybShortSleep.0 = 20
sybLongSleep.0 = 2
sybApplModIndex.1 = 1
sybApplIndex.1 = 0
sybApplModCMD.1 = addServer(1)
sybApplModNewPassword.1 = **********
sybApplModApplName.1 = Server Name
Note: If you use "system" to look at system variables, be aware that if there are any spaces after sysDescr, sysLocation, or sysContact, getmany displays numbers instead of the appropriate information. See "Modifying System Information" for more information.
The following sections describe possible situations you might encounter and the solutions to these problems.
When you monitor multiple servers, it is important to have an interval between ShortSleep and LongSleep intervals that allows the Subagent to adequately poll all the servers. If the network manager is getting no response or delayed response to queries for status updates, try increasing the ShortSleep and LongSleep polling intervals.
You can modify ShortSleep and LongSleep by editing snmp.ini or by setting new intervals from the network manager. See "Modifying snmp.ini" and "Modifying Object Values" for more information.
Note: If you are using the Subagent to monitor a server on a different host, response time is slower.
Sybase recommends that you have a Subagent on each host that has a server you want to monitor. However, the Subagent does not restrict you from monitoring servers on a different host. If you use the Subagent to monitor a server on a different host, be aware that values for applUptime will not always be correct.
If you have more than one Subagent sharing the same $SYBASE directory, the name of the snmp.ini file must be different for each Subagent to avoid duplicate monitoring. When you configure the snmpi.ini file during the installation process, rename the snmp.ini file and specify an alternate filename on the command line:
snmpconfig -c filename
When you start EMANATE, it reads its initialization file snmpd.cnf. This file is in the directory defined by the environment variable SR_AGT_CONF_DIR.
If you cannot start the master agent, make sure that the sysObjID entry in snmpd.cnf has no extra spaces at the end of the entry. If there are, the master agent cannot start. In addition, the master agent puts the following message in its log file:
ParseSubIdDecimal, bad digit:
at line num in file oid_lib.c
where num is the line number in snmpd.cnf.
|
|