Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Create SNMP agents

SNMP agents gather management data from WebLogic Server MBeans and custom MBeans and make the data available to SNMP managers.

A WebLogic Server SNMP agent can always communicate with managers using the SNMPv3 protocol. You can configure whether the agent also supports the SNMPv1 and v2 protocols. While you cannot prevent an agent from receiving SNMPv3 requests, an agent processes only requests from known users that you configure through the WebLogic Server security realm.

To create SNMP agents:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the Administration Console, under Domain Structure, expand Diagnostics and select SNMP.
  3. On the Summary of SNMP Agents page, in the Server SNMP Agents table, click the New button.

    Note: The SNMP page also displays a Domain SNMP Agent table, which provides access to the domain-scoped SNMP agent. This agent is provided to support domains that were created with WebLogic Server release 9.2 and earlier. Oracle recommends that you do not use this agent for new domains. For more information, see Use SNMP to monitor WebLogic Server.

  4. On the Create a New Server SNMP Agent page, enter a name for the SNMP agent and click the Finish button.

    Once you create an SNMP agent, you cannot change its name. Instead, you must delete it and create a new one.

  5. On the Summary of SNMP Agents page, in the Server SNMP Agents table, click the name of the new SNMP agent.
  6. On the SNMP Agent: Configuration: General page, make the following minimal changes to the default values:
    1. Check the Enabled box.
    2. In the SNMP UDP Port field, enter the port number on which you want the SNMP agent to listen for UDP requests from SNMP managers.

      An SNMP agent communicates through a port that accepts UDP traffic and another port that accepts TCP traffic. By default, all TCP traffic uses the host server's listen port. For example, if you target this agent to a server named ManagedServer1 and ManagedServer1 listens for requests on port 7001, then the SNMP agent listens for TCP requests on port 7001. When communicating through a TCP port, WebLogic Server protects SNMP communication from denial of service (DOS) attacks.

      If you want to separate SNMP TCP traffic from business traffic, you can create a custom network channel. See Create an SNMP network channel.

    3. If you want this agent to generate notifications, in the Trap Version field, specify whether you want the agent to generate SNMPv1, v2, or v3 notifications. Choose a protocol that matches the capabilities of your SNMP managers.
  7. Secure SNMPv3 communication.
  8. To enable the agent to communicate with managers using the SNMPv1 or v2 protocols:
    1. Check the Community Based Access Enabled box.
    2. In the Community Prefix field, enter the SNMP community (password) that SNMP managers must specify when sending requests to the WebLogic SNMP agent. Oracle recommends that you enter something other than the default value of public.
  9. Modify default values for the other attributes by clicking More Info next to the attribute or by referring to Configuration Options.
  10. Click Save.
  11. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).

After you finish

Do the following:

  1. Target SNMP agents.
  2. (Optional) Create trap destinations.

Back to Top