This section explains how to configure Simple Network Management Protocol (SNMP) communities and trap receivers. These features are not essential for baseline Oracle Enterprise Communications Broker service, but they are necessary to use an element management system to manage Oracle Enterprise Communications Brokers. They provide important monitoring and system health information that contribute to a robust deployment of the Oracle Enterprise Communications Broker.


SNMP is used to support monitoring of network-attached devices for conditions that warrant administrative attention. SNMP is comprised of three groups of settings on a Oracle Enterprise Communications Broker. These settings are system-wide configurations including MIB contact information, SNMP community settings, and trap receivers.

Basic SNMP Parameters

The Oracle Enterprise Communications Broker includes several parameters that control basic SNMP functionality. The MIB-related elements are for informational purposes, and are helpful if set. The remainder of the parameters determines if certain Oracle Enterprise Communications Broker events are reported to the SNMP system.

SNMP Community

An SNMP community is a grouping of network devices and management stations used to define where information is sent and accepted. An SNMP device or agent might belong to more than one SNMP community. SNMP communities provide a type of password protection for viewing and setting management information within a community. You can define multiple SNMP communities on a Oracle Enterprise Communications Broker to segregate access modes per community and NMS host.

Trap Receivers

A trap receiver is an application used to receive, log, and view SNMP traps for monitoring the Oracle Enterprise Communications Broker. An SNMP trap is the notification sent from a network device, the Oracle Enterprise Communications Broker in this case, that declares a change in service. Multiple trap receivers can be defined on a Oracle Enterprise Communications Broker either for redundancy or to segregate alarms with different severity levels to individual trap receivers.

Each server that an element management system is installed on should be configured as a trap receiver on all Oracle Enterprise Communications Broker’s managed by that element management system.

SNMP Community Settings

Follow the steps below to configure an SNMP community on your device.

  1. Community name—Enter an SNMP community name of an active community where this Oracle Enterprise Communications Broker can send or receive SNMP information. A community name value can also be used as a password to provide authentication, thereby limiting the NMSs that have access to this Oracle Enterprise Communications Broker. With this field, the SNMP agent provides trivial authentication based on the community name that is exchanged in plain text SNMP messages. For example, public. Valid values are alpha-numeric characters. Default is blank.
  2. From the SNMP community list, click the Add link. The system displays the Add dialog.
  3. IP addresses—Enter an IPv4 address that is valid within this SNMP community. This IPv4 address corresponds with the IPv4 address of the NMS application that monitors or configures this Oracle Enterprise Communications Broker. You can enter multiple addresses, if desired.
  4. Click OK to close the Add dialog.

Set Trap Receiver Settings

Follow the steps below to configure trap receivers on your device.

  1. From the Trap receiver list, click Add.
    The system displays the Add SNMP Trap Settings dialog.
  2. Community name—Enter the SNMP community name to which this trap receiver belongs. For example, Public. Valid values: Alpha-numeric characters. Default: Blank.
  3. IP address—Enter the IPv4 address of an authorized NMS. This value is the IPv4 address of an NMS where traps are sent. Enter the IP address in dotted decimal format.
  4. IP Port—Enter the port number of an authorized NMS. If you do not specify a port number, the default SNMP trap port of 162 is used.