SNMPv1 and SNMPv2

Use this task if you selected v1v2 for the snmp-agent-mode parameter in the system-config element to configure SNMPv1 and SNMPv2, which includes the configuration of the SNMP community and the trap receiver.

SNMPv1v2 Community Configuration

SNMPv1v2 community configuration consists of setting a community name, an access mode and IP addresses of the servers. Configurations accept multiple addresses. You can provide both READ and WRITE mode to a single manager by creating two objects with different names and access modes, but the same IP address.

Determine your planned name, address type (IPv4 vs IPv6) and modes before starting.

Configure the SNMP Community

1. Access the snmp-community configuration element.

   ORACLE# configure terminal
   ORACLE(configure)# system
   ORACLE(system)# snmp-community
   ORACLE(snmp-community)# 

2. Type community-name to specify the SNMP community name of an active community where this Oracle Communications Session Border Controller can send or receive SNMP information.
3. access-mode—Set the access level for all network management servers (NMSs) defined within this SNMP community. The access level determines the permissions that other NMS hosts can wield over this Oracle Communications Session Border Controller. The default is read-only. The valid values are:

   • read-only—allows GET requests.

   • read-write—unsupported.

4. ip-addresses—Specify a valid IPv4 or IPv6 address within this SNMP community that corresponds to one or more NMS that monitors or configures this SBC. If you are specifying more than one IP address, separate each IP address with a space and enclose with parenthesis.

   ORACLE#(snmp-community)ip-addresses (10.1.1.1 10.2.2.2)

5. Type done to save your configuration.

SNMPv1v2 Trap Receiver Configuration

Determine the community, addressing (IPv4 or IPv6) and filter level for each trap receiver before configuration.

Note:

Configure each Oracle Communications Session Delivery Manager that manages an SBC as trap receivers on the SBC.

Configure Trap Receivers

1. Access the trap-receiver configuration element.

   ORACLE# configure terminal
   ORACLE(configure)# system
   ORACLE(system)# trap-receiver
   ORACLE(trap-receiver)# 

2. Select the trap-receiver object to specify a trap receiver.

   ORACLE(trap-receiver)# select
   <ip-address>:
   
   ORACLE(trap-receiver)#

3. ip-address — Set the IPv4 or IPv6 address of an authorized network management system (NMS) where traps are sent. If you do not specify a port number, the default SNMP trap port of 162 is be used.
4. filter-level — Set the filter level threshold that indicates the severity level at which a trap is to be sent to this particular trap receiver. The default for this parameter is critical.

   Example: When a trap with a severity level of critical is generated, the SNMP agent sends this trap only to NMSs that are configured in a trap-receiver element and have a filter-level value of critical.

   The following table maps Syslog and SNMP alarms to trap receiver filter levels.

   Filter Level	Syslog Severity Level	(SNMP) Alarm Severity Level
   Critical	Emergency (1) Critical (2)	Emergency Critical
   Major	Emergency (1) Critical (2) Major (3)	Emergency Critical Major
   Minor	Emergency (1) Critical (2) Major (3) Minor (4)	Emergency Critical Major Minor
   All	Emergency (1) Critical (2) Major (3) Minor (4) Warning (5) Notice (6) Info (7) Trace (8) Debug (9)	Emergency Critical Major Minor Warning

   When configuring the trap-receiver element for use with Oracle Communications Session Element Manager systems, Oracle recommends that the value of filter-level be set to All for that configuration element that includes those servers.

5. community-name — Set the community name to which this trap receiver belongs. This community must be defined in the SNMP community element.
6. Type done to save your configuration.