| |
Home |
![[Table of Contents]](/dwicons/b_toc.gif)
|
SNMP SubAgent User's Guide (UNIX) |
![[-]](/dwicons/i_colpse.gif)
| Glossary |
A special type of security trap. When EMANATE receives a PDU, it verifies that the community string has privileges to set or get object information. If the community string is invalid, EMANATE sends a trap to each of the hosts defined in the trap definition section of snmpd.cnf.
An SNMP password that allows a network manager to access a Subagent. The community string is part of the PDU the network manager sends. See PDU.
The context specifies the MIB view or proxy relationship of an agent. You specify the context in the configuration file, context.pty.
A time interval the Subagent waits between polling the server to update data. LongSleep specifies the number of times the Subagent cycles through its ShortSleep polls. The default value is 4 ShortSleep cycles. The range is from 1 to 20 ShortSleep cycles.
A request broker that listens to port 161 and routes the requests to the appropriate subagent. The master agent returns responses from subagents to the network manager using port 162. As part of the Subagent distribution, Sybase provides the master agent EMANATE. See Chapter 2, "Using EMANATE" for more information on EMANATE.
A Management Information Base describes common metrics of relational database systems. The MIB describes the data elements that are supported by a Subagent. The MIB states the maximum accessibility (such as Read-Only, Read-Write, or Not accessible), data type (such as Integer or DisplayString), description, and unique object identifier for each data element. There are three MIBs included with SQL Server SNMP Subagent: RDBMS, Network Services, and Sybase Common. Nearly all the data in the MIB is in table format. See also Network Services MIB, Relational Database Management System MIB, SYBASE MIB.
The portion of a MIB that is accessible to an agent. You define the view in the snmpV2 security configuration file, view.pty.
Requests information from objects in the network. Network managers can also modify the values of some objects. The network manager sends requests to User Datagram Protocol (UDP) port 161 and listens to UDP port 162 for responses to requests and for event traps generated by the Subagent. To request information and to modify values, network managers use protocol data units (PDU).
An Internet standard for supplying information on network service applications. The Subagent supports the application table (applTable) of this MIB. The application table contains an entry for each SQL Server or Open Server that the Subagent is monitoring. A network manager reads a compiled version of the Network Services MIB so that it knows which servers are available. See Chapter 4, "Objects in the Network Services MIB and RDBMS MIB" for more information on the Network Services MIB.
An entity described in a MIB that a network manager can use.
See OID.
The unique object identifier (OID) for each data object supported by SQL Server SNMP Subagent. Data objects are described in the MIBs.
A protocol data unit enables a network manager to get a value from a managed object, set or modify a value, and be alerted through a trap. Version 1 of SNMP supports five PDUs: get-request, get-next-request, set-request, get-response, and trap. Version 2 of SNMP supports an additional two PDUs: get-bulk-request and get-bulk-response. With the exception of traps, all messages originate with the network manager. The Subagent generates traps.
The industry standard ports for sending and receiving PDUs and traps. The network manager sends PDUs requesting information to port 161 and receives responses and traps from port 162.
See PDU.
An Internet standard for supplying information about installed servers, databases, and the relation of servers and databases. A network manager reads a compiled version of the RDMBS MIB so that it knows what types of information it can access about a server or database. See Chapter 4, "Objects in the Network Services MIB and RDBMS MIB" for more information on the RDBMS MIB.
A time interval (measured in seconds) that SQL Server SNMP Subagent waits between polling the server to update data. These polls are called frequent polls. The range is from 10 to 1800 seconds.
The Subagent initialization file created during installation when you enter password and polling interval information in response to prompts. The file contains an entry for each server to be monitored and information SQL Server SNMP Subagent must retain while it is down. The information includes the ShortSleep and LongSleep polling intervals and the scrambled passwords the Subagent must use to log into monitored servers. You can edit the file to change passwords and polling intervals.
The master agent configuration file created by the installation process. The file contains entries that define the host on which the master agent is running, hosts on which you can do set operations, hosts to which you send traps, and so on. You also disable or enable authentication-failure traps in this file. You can edit the file.
Monitors characteristics of the SQL Servers and Open Servers and stores this information in an internal cache. When the Subagent receives a request from a master agent, it accesses the internal cache and returns the requested information to the master agent. In addition, the Subagent also detects events and reports these events as SNMP traps on port 162.
An intermediate process between a network manager and a monitored object. Subagents obtain data from the monitored objects and presents the information to the network manager using the SNMP protocol. See also master agent, SQL Server SNMP Subagent.
The lowest level of information in a MIB that is accessible to an agent. You define the subtree view in the snmpV2 security configuration file, view.pty.
A Sybase-specific MIB that identifies polling intervals and login information used by the Subagent to monitor servers. A network manager reads a compiled version of this MIB so that it can read and modify polling intervals and login information. See Chapter 5, "Objects in the SYBASE MIB" for more information on the SYBASE MIB.
A notification that a specific event has occurred. See also Authentication trap.
|
|