Generic Procedure Failure Logs
The following are the synopsis of the Generic Procedure Failure logs to trigger session management policies towards the SMF:
-
During the termination scenario, each Procedure Failure log turns on the EndProcedure.
-
During the failure scenario, the Error Code returns to the SMF Infra indicating whether the procedure was a success or a failure.
-
On failure, a Generic Transaction log (common to all procedures) with level warning is used to dump the session details as the following:
-
Transaction ID
-
Procedure Name
-
Detailed Error—It contains failure reason or cause, disconnect reason (if applicable) and failure metrics.
-
-
The Generic Procedure Failure LogTag is common to all procedures.
-
When a specific procedure failure LogTag is disabled and a Generic Procedure Failure LogTag is enabled, then the SMF doesn't print the Event Trace.
-
The Event Trace is printed, only when a specific procedure failure LogTag gets enabled.
-
The Transaction ID gets printed in a procedure failure logs to align with the logs and call flow.
-
The Detailed errors note gets printed in the generic procedure failure logs. It helps in understanding the problem, the actual error cause, disconnect reason (if applicable), and failure metrics.
Logging a Message for Generic Procedure Failure Logs
The following is a sample example of a LogTag for Generic Procedure Failure logs:
2023/01/15 10:58:01.171 [WARN] [smf-service.smf-app.procfailure] [Txn :1]Procedure=[PDN Connect [LTE]],
PduState=[IDLE], Rat-Type=[rat_type_unknown], FailureReason=[udm_subscribe_notify_failure],
DisconnectReason=[disc_pdnsetup_udm_sub_notify_resp_failed]