WebLogic SNMP Management Guide
WebLogic Server can use Simple Network Management Protocol (SNMP) to communicate with enterprise-wide management systems. The WebLogic Server subsystem that gathers WebLogic management data, converts it to SNMP communication modules (trap notifications), and forwards the trap notifications to third-party SNMP management systems is called the WebLogic SNMP agent. The WebLogic SNMP agent supports the SNMPv1 and SNMPv2 protocols.
SNMP management is based on the agent/manager model described in the network management standards defined by the International Organization for Standardization (ISO). In this model, a network/systems manager exchanges monitoring and control information about system and network resources with distributed software processes called agents.
Any system or network resource that is manageable through the exchange of information is a managed resource. This could be a software resource, such as a Java Database Connectivity (JDBC) connection pool, or a hardware resource, such as a router.
Agents function as "collection devices" that gather and send data about the managed resource in response to a request from a manager. In addition, agents often have the ability to issue unsolicited reports to managers when they detect certain predefined thresholds or conditions on a managed resource. In SNMP terminology, these unsolicited event reports are called trap notifications.
A manager relies upon a database of definitions and information about the properties of managed resources and the services the agents support — this makes up the Management Information Base (MIB). When new agents are added to extend the management reach of a manager, the manager must be provided with a new MIB component that defines the manageable features of the resources managed through that agent. The manageable attributes of resources, as defined in an SNMP-compliant MIB, are called managed objects. Defining the heterogeneous components of an enterprise's distributed systems within a common MIB on the management station provides a unified perspective and single access point for managing system and network resources.
The WebLogic SNMP agent runs on a domain's Administration Server. (See Figure 1-1.)
A WebLogic Server administration domain is a logically related group of WebLogic Server resources. Domains include a special WebLogic Server instance called the Administration Server, which is the central point from which you configure and manage all resources in the domain. Typically, you configure a domain to include additional WebLogic Server instances called Managed Servers. You deploy applications, EJBs, and other resources on the Managed Servers and use the Administration Server for configuration and management purposes only.
Using multiple Managed Servers lets you balance loads and provide failover protection for critical applications, while using a single Administration Server simplifies the management of the Managed Server instances. For more information about domains, refer to "Overview of WebLogic Server Domains" in Configuring and Managing WebLogic Server.
For information on enabling and configuring the WebLogic SNMP agent, refer to "Enabling and Configuring the WebLogic SNMP Agent" in the Administration Console Online Help.
Resources on WebLogic Server instances use Java Management Extensions (JMX) Managed Beans (MBeans) to expose their management functions. An MBean is a concrete Java class that is developed in accordance with JMX specifications. It can provide getter and setter operations for each management attribute within a managed resource along with additional management operations that the resource makes available.
WebLogic Server MBeans that expose the configuration data of a managed resource are called Configuration MBeans while MBeans that provide performance metrics and other information about the runtime state of a managed resource are called Runtime MBeans. For example, a
ServerMBean Configuration MBean indicates the listen port for a server instance while the
ServerRuntimeMBean Runtime MBean indicates the current lifecycle state of a server instance.
While you can create MBeans (custom MBeans) to manage the applications or services that you deploy on WebLogic Server, the WebLogic SNMP agent does not recognize these custom MBeans as SNMP managed resources. You cannot configure the WebLogic SNMP agent to monitor or generate traps for custom MBeans.
The right pane displays the package summary. (See Figure 1-2.)
The right pane displays the package summary. (See Figure 1-3.)
The BEA WebLogic SNMP MIB conforms to a coding standard called Abstract Syntax Notation.1 (ASN.1). An ASN.1 file is a standard SNMP file that defines the objects that make up an SNMP-compliant MIB. Each object in the file is defined in compliance with the SNMP standard. The BEA WebLogic Server software includes the ASN.1 file BEA- WEBLOGIC-MIB.asn1 for defining the BEA WebLogic Server MIB for SNMP. The BEA WebLogic SNMP MIB is written in compliance with RFC 1212, as required by the SNMP standard.
The WebLogic Server MIB assigns a unique number called an object identifier (OID) to its MBean attributes. Each MBean attribute in the MIB is an SNMP managed object and is manageable by an SNMP management system.
The MIB creates a hierarchical relationship between managed objects and expresses the hierarchy in a tree structure, called the MIB tree or registration tree. Each OID in the MIB consists of a left-to-right sequence of integers. This sequence defines the location of the object in the MIB tree and specifies a unique path through the tree to the object. Each node in the path have both a number and a name associated with it. The path
.18.104.22.168.4.1 defines the
private.enterprises OID and each number beneath that node on the tree represents the branches in the tree reserved for a particular vendor.
All OIDs that represent WebLogic Server MBean attributes in the WebLogic Server MIB are identifiers for the MBean attribute type. For example,
.22.214.171.124.126.96.36.1995.360.1.60 is the OID for the
serverRuntimeState attribute type.
To identify a specific instance of an attribute type, the WebLogic SNMP agent generates and appends an additional set of numbers to the OID of an attribute type. For example, the OID that specifies the value of the
serverRuntimeState attribute for an active instance of the sample MedRecServer is
The WebLogic Server MIB Reference appends
(.*) to the OIDs that represent attribute types. This convention indicates that specific instances of the type are identified by additional numbers. For example, the WebLogic Server MIB Reference indicates that the OID for the
serverRuntimeState attribute type is
You can use the
snmpgetnext commands to see the object-instance OID for any WebLogic Server attribute. For more information, refer to "WebLogic SNMP Agent Command-Line Reference" in the WebLogic Server Command Reference.
To ensure that the entity requesting data from the WebLogic SNMP agent has permission to obtain the data, and to verify that the agent has permission to send trap notifications to a target manager, SNMP uses textual passwords called community names.
When you set up the SNMP agent capability of the Administration Server (described in "Enabling and Configuring the WebLogic SNMP Agent" in the Administration Console Online Help), one of the things you must specify is the community name that the agent expects from the SNMP manager. If the agent receives an SNMP request with an incorrect community name, it generates an
authenticationFailure trap and sends it to the source of the request.
You can use some SNMP managers to send requests to the WebLogic SNMP agent for the value of attributes. Because a WebLogic Server domain can have multiple server instances concurrently active, a request that specifies only an attribute name is potentially ambiguous. For example, the attribute
serverUptime exists for each WebLogic Server instance in a domain.
To request the value of an attribute on a specific Managed Server, when you send a request from an SNMP manager, append the name of the server instance to the SNMP password (community) that it sends with the request as follows:
community_prefix is the SNMP community name and
server_name is the name of the targeted Managed Server. The
community_prefix value sent by the manager must match the value that you set in the Community Prefix field when you configure the SNMP agent.