3.2.6 SCPAuditErrorResponse

Table 3-10 SCPAuditErrorResponse

Field	Description
Severity	Info
Conditions	ocscp_audit_error_response > 0
OID used for SNMP Traps	1.3.6.1.4.1.323.5.3.35.1.2.4001
Description	Alert is raised when Audit module receives a 3xx, 4xx, or 5xx error from NRF. This alert is labeled with specific nftype, nrfRegionOrSetId, and auditmethod. Note: Alert is cleared on the next audit cycle.
Recommended Actions	Cause: When the configured NRF sends error responses, down, or not reachable. Diagnostic Information: Check if NRF is up and reachable. To check the NRF status, see Oracle Communications Cloud Native Core, Network Repository Function User Guide. Check if the NF is reachable or not using one of the following steps: Run the ping command from primary/secondary nodes using IP of NRF. Example of a ping command: ping <IpAddress>. Run the ping command from inside the pod if FQDN of NRF is used. Instead of using ping, you can collect tcpdump for ensuring connectivity. Example of a tcpdump: tcpdump -w capture.pcap -i <pod interface>. Monitor audit and worker service logs: kubectl logs <pod name> -n <namespace> Check jaeger traces for scp-worker. Recovery: The alert is cleared automatically during the next audit cycle and when no more errors are received. Collect audit and worker service logs and contact My Oracle Support for any assistance.