Configuring Alert Manager for SNMP Notifier

7.2.1 Configuring Alert Manager for SNMP Notifier

This section describes the procedure to configure SNMP Notifier.

Configure the IP and port of the SNMP trap receiver in the SNMP Notifier using the following procedure:

Run the following command to edit the deployment:
```
kubectl edit deploy <snmp_notifier_deployment_name> -n <namespace>
```
Example:
```
kubectl edit deploy occne-snmp-notifier -n occne-infra
```
SNMP deployment yaml file is displayed.
Edit the SNMP destination in the deployment yaml file as follows:
```
--snmp.destination=<destination_ip>:<destination_port>
```
Example:
```
--snmp.destination=10.75.203.94:162
```
Save the file.

Checking SNMP Traps

Following is an example on how to capture the logs of the trap receiver server to view the generated SNMP traps:

docker logs <trapd_container_id>

Sample output:

NET-SNMP version 5.8 2024-04-19 08:32:01 <UNKNOWN> [UDP: [10.121.27.121]:29375->[192.168.200.191]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (483032200) 55 days, 21:45:22.00 SNMPv2-MIB::snmpTrapOID.0 = OID: ORACLENEF-MIB::OcnefQOSServiceDown ORACLENEF-MIB::OcnefQOSServiceDown.1 = STRING: "1.3.6.1.4.1.323.5.3.39.1.2.7021[job=occne-infra/occne-nf-cnc-podmonitor]" ORACLENEF-MIB::OcnefQOSServiceDown.2 = STRING: "critical" ORACLENEF-MIB::OcnefQOSServiceDown.3 = STRING: "Status: critical - Alert: OcnefQOSServiceDown   Summary: namespace: sanity, podname: , timestamp: 2024-04-19 08:32:01.354 +0000 UTC : QOS service down   Description: OCNEF QOS service qualityofservice is down" 2024-04-19 08:37:01 <UNKNOWN> [UDP: [10.121.27.121]:6699->[192.168.200.191]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (483062200) 55 days, 21:50:22.00 SNMPv2-MIB::snmpTrapOID.0 = OID: ORACLENEF-MIB::OcnefQOSServiceDown ORACLENEF-MIB::OcnefQOSServiceDown.1 = STRING: "1.3.6.1.4.1.323.5.3.39.1.2.7021[job=occne-infra/occne-nf-cnc-podmonitor]" ORACLENEF-MIB::OcnefQOSServiceDown.2 = STRING: "clear" ORACLENEF-MIB::OcnefQOSServiceDown.3 = STRING: "Status: OK"

MIB Files for NEF

There are two MIB files which are used to generate the traps. The user need to update these files along with the Alert file in order to fetch the traps in their environment.

ocnef_mib_tc_24.2.0.mib: This is considered as NEF and CAPIF top level mib file, where the Objects and their data types are defined.
ocnef_mib_24.2.0.mib: This file fetches the Objects from the top level mib file and based on the Alert notification for NEF, these objects can be selected for display.
ocnef_capif_mib.mib: This file fetches the Objects from the top level mib file and based on the Alert notification for CAPIF, these objects can be selected for display.

Note:

MIB files are packaged with Custom_Templates.zip. You can download the file from My Oracle Support as described in Oracle Communications Cloud Native Core, Network Exposure Function Installation, Upgrade, and Fault Recovery Guide.