Skip navigation.

Administration Console Online Help

PreviousNextvertical dots separating previous/next from contents/index/pdfContents

SNMP Trap Destinations

Column Display     Related Tasks     Related Topics

Trap destinations specify the SNMP management station and the community name used by the SNMP agent to send traps.

This page summarizes each trap destination that has been configured in the current WebLogic Server domain.

Column Display

You can show fewer or additional data points on this page by expanding Customize this table and modifying the Column Display list. Each data point displays in its own table column.

The following table lists all of the data points that you can display in columns on this page.

Name Description
Name

The name that you specified when you created the trap destination.

Community

The password (community name) that WebLogic Server sends to the SNMP manager.

Note that there are two community names that are needed when WebLogic Server interacts with an SNMP manager:

  • The community name that the SNMP manager defines. The community name that you enter in this trap destination must match the name that the SNMP manager defines. The WebLogic SNMP agent sends this name when connecting to the manager.

  • The name that you specify in the WebLogic SNMP agent's Community Prefix. All SNMP managers must send this name when connecting to the WebLogic SNMP agent.

MBean Attribute:
SNMPTrapDestinationMBean.Community

Changes take effect after you redeploy the module or restart the server.

Host

The DNS name or IP address of the computer on which the SNMP manager is running.

The WebLogic SNMP agent sends trap notifications to the host and port that you specify on this tab.

MBean Attribute:
SNMPTrapDestinationMBean.Host

Secure value: 127.0.0.1

Changes take effect after you redeploy the module or restart the server.

Port

The port on which the SNMP manager is listening.

MBean Attribute:
SNMPTrapDestinationMBean.Port

Minimum value: 1

Maximum value: 65535

Changes take effect after you redeploy the module or restart the server.

Related Tasks

Related Topics

 

Skip navigation bar   Back to Top