The cnBNG CP supports the following alarm categories.

• CP-UP Connectivity—Alarms are generated if Control Plane (CP) - User Plane (UP) association fails, active, or inactive. Expressions can be formulated on CP defined UPF and Packet Forwarding Control Protocol (PFCP) metrics.

• cnBNG Session—Alarms can be generated if session bring-up or bring-down success rate is less than the specificied threshold, drop rate, and if subscriber limit is crossed. Expressions can be formulated on Session Manager (SM) and First Sign of Life (FSOL) metrics.

• Accounting—Alarms can be generated if accounting start, interim, and stop success rate is less than the specified certain threshold and so on. Expressions can be formulated on accounting metrics.

• Radius —Alarms can be generated for RADIUS server for the following events:

  • Active or Inactive server state

  • Statistics success, failure, or reject rates for Authorization and Accounting based on threshold

  • Change of Authorization (CoA) success or failure rates.

  Expressions can be formulated on RADIUS metrics.

• IP Pool —Alarms can be generated if IP pool allocation reaches the specified threshold. Expressions can be formulated on IPAM metrics.

Based on alarm categories, the following alert configurations are recommended.

Note	The Threshold field is configurable as per requirement. The interval-seconds and duration can vary based on requirements.

The CNEE SNMP Trapper supports alert or alarm routing. Login to the CNEE Ops center to enable the SNMP Trapper because it is disabled by default. To enable SNMP traps, see Configuring SNMP Traps.

The SNMP agent uses the Management Information Base (MIB) to handle SNMP trap notifications in the CISCO-CNEE-MIB.my. The CNEE generates two types of notifications with the following trap object identifiers (OID):

• cneeFaultClearNotif—The CNEE generates this notification when fault or alert gets cleared.

• cneeFaultActiveNotif—The CNEE generates this notification when fault or alert gets triggered.

For more details, see the "SMI MIB Reference" chapter in the Ultra Cloud Core Subscriber Microservices Infrastructure Operations Guide.

The Alert Logger allows to view active and silenced alerts or history of alerts triggered from CNEE Ops Center using show commands. Alert routing is enabled by default.

For more details, see the "Viewing Alert Logger" section in the "Common Execution Environment" chapter of the Ultra Cloud Core Common Execution Environment Configuration and Administration Guide.

The alert or alarm severity levels are as follows:

• Critical

• Major

• Minor

• Warning

All severity level alerts are routed to the SNMP Trapper. The CNEE does not have a mechanism to route only critical or major alerts or alarms to the SNMP Trapper while configuring alerts rules. To address this requirement, configure the following CLI command to avoid routing minor or warning alerts or alarms to the SNMP Trapper.

cee# alerts silence add matchers { name severity isRegex true value 
\"warning\|minor\" } 

Use the following command to view silenced alerts or alarms.

show alerts silenced { summary | detail } 

Use the following commands to configure alert rules:

config 
   alerts rules group alert_group_name 
   interval-seconds seconds 
   rule rule_name 
      expression promql_expression 
      duration duration 
      severity severity_level 
      type alert-type 
      annotation annotation_name 
      value annotation_value 
      exit 
   exit 

NOTES:

• alerts rules : Specifies the Prometheus alerting rules.

• group alert_group_name : Specifies the Prometheus alerting rule group. One alert group can have multiple lists of rules. alert-group-name is the name of the alert group. The alert-group-name must be a string in the range of 0 to 64 characters.

• interval-seconds seconds : Specifies the evaluation interval of the rule group in seconds.

• rule rule_name : Specifies the alerting rule definition. rule_name is the name of the rule.

• expression promql_expression : Specifies the PromQL alerting rule expression. promql_expression is the alert rule query expressed in PromQL syntax.

• duration duration : Specifies the duration of a true condition before it is considered true. duration is the time interval before the alert is triggered.

• severity severity_level : Specifies the severity of the alert. severity-level is the severity level of the alert. The severity levels are critical, major, minor, and warning.

• type alert_type : Specifies the type of the alert. alert_type is the user-defined alert type. For example, Communications Alarm, Environmental Alarm, Equipment Alarm, Indeterminate Integrity Violation Alarm, Operational Violation Alarm, Physical Violation Alarm, Processing Error Alarm, Quality of Service Alarm, Security Service Alarm, Mechanism Violation Alarm, or Time Domain Violation Alarm.

• annotation annotation_name : Specifies the annotation to attach to the alerts. annotation_name is the name of the annotation.

• value annotation_value : Specifies the annotation value. annotation_value is the value of the annotation.

The following example configures an alert, which is triggered when the percentage of Unified Data Management (UDM) responses is less than the specified threshold limit.

Example:

	config terminal
		alerts rules group BNGUDMchk_incr
		interval-seconds 300
		rule BNGUDMchk_incr
		expression "sum(increase(bng_restep_http_msg_total{nf_type=\"udm\", message_direction=\"outbound\", response_status=~\"2..\"}[3m])) /  sum(increase(smf_restep_http_msg_total{nf_type=\"udm\", message_direction=\"outbound\"}[3m])) < 0.95"
		severity major
		type "Communications Alarm"
		annotation summary
		value "This alert is fired when the percentage of UDM responses is less than threshold“
		exit
	exit
exit

You can view the configured alert using the show running-config alerts command.

Example:

The following example displays the alerts configured in the running configuration:

	show running-config alerts
		interval-seconds 300
		rule SMFUDMchk_incr
		expression "sum(increase(smf_restep_http_msg_total{nf_type=\"udm\", message_direction=\"outbound\", response_status=~\"2..\"}[3m])) /  sum(increase(smf_restep_http_msg_total{nf_type=\"udm\", message_direction=\"outbound\"}[3m])) < 0.95"
		severity major
		type "Communications Alarm"
		annotation summary
		value "This alert is fired when the percentage of UDM responses is less than threshold“              
		exit
	exit
exit

Use the following commands to configure or enable SNMP Traps.

config 
   snmp-trapper enable true 
   snmp-trapper { v2c-target target | v3-target target |  
   v3-engine-id source_engine_id } 
      community [ community_string ] 
      port [ port ] 
      exit 
   snmp-trapper source-ip-routes [ vip_options ] 
   exit 

config 
  no snmp-trapper enable 
  exit 

NOTES:

• snmp-trapper enable true : Enables the SNMP trapper parameters.

• v2c-target|v3-target [ target ] : Specifies the list of SNMP v2c and v3 trap receivers.

• community [ community_string ] : Specifies the SNMP trap receiver community.

• v3-engine-id source_engine_id : Specifies the source engine ID for the v3 traps. source_engine_id must be an hexagonal string. For instance, 80004f.

• port [ port ] : Specifies the SNMP trap receiver port. port must be an integer in the range of 0 through 65535. The default value is 162.

• source-ip-routes [ vip_options ] : Enables binding to source IP for SNMP routing. vip_options specifies the virtual IP (VIP) address. The different options for virtual IP addresses include:

  • default-external-vip : Specifies the default external VIP for source IP routing.

  • internal-vip : Specifies the internal VIP for source IP routing.

  • source-external-vips : Specifies the external VIP per namespace.

• no snmp-trapper enable : Disables SNMP traps.