Log events
Get a summary of the supported alarms and raising events and detailed descriptions per alarm and event object.
li
BootLIConfig
Property name | Value |
|---|---|
Application name |
li |
Event name | BootLIConfig |
Default severity | warning |
Message format string |
Lawful intercept (LI) bootup configuration status: LI_configuration_status; LI local save: LI_local_save_status; time of last system bootup: Date Time |
Cause | The system periodically reports the current status and the time of the last system bootup |
Effect | LI is in use and the current LI status is reported |
LIAdminDisable
Property name | Value |
|---|---|
Application name |
li |
Event name | LIAdminDisable |
Default severity | critical |
Message format string |
LI has changed to administrative disable state |
Cause |
Configuration update disables the LI administrative state |
Effect |
LI administrative state is disabled |
LIAdminEnable
Property name | Value |
|---|---|
Application name |
li |
Event name | LIAdminEnable |
Default severity | warning |
Message format string |
LI has changed to administrative enable state |
Cause |
Configuration update enables the LI administrative state |
Effect |
LI administrative state is enabled |
LIOperDown
Property name | Value |
|---|---|
Application name |
li |
Event name | LIOperDown |
|
Default severity | critical |
Message format string |
LI changed to the operational down state because of oper_down_reason |
|
Cause | LI mirror operational state changes from up to down |
|
Effect | LI operational state is down |
LIOperUp
Property name | Value |
|---|---|
Application name |
li |
Event name | LIOperUp |
|
Default severity | warning |
Message format string |
LI has changed to operational up state |
Cause | LI operational state changes from down to up |
Effect | LI operational state is up |
LISourceSubscriberProblemUP
Property name | Value |
|---|---|
Application name | li |
Event name |
LISourceSubscriberProblemUP |
Default severity | critical |
Message format string | Configuration of LI target subscriber LISubscriber_source under LI mirror source instance LISource_instance_name on the MAG-u failed with reason oper_down_reason; add the subscriber manually when the problem is fixed |
Cause | Error occurs in the LI session configuration between the MAG-c and MAG-u |
Effect | cMAG-c failed to configure and enable the LI session for the specific subscriber on the MAG-u; LI session is inactive |
LISourceSubscriberSessionActive
Property name | Value |
|---|---|
Application name | li |
Event name |
LISourceSubscriberSessionActive |
Default severity | notice |
Message format string | LI target subscriber LISubscriber_source under LI mirror source instance LISource_instance_name is online and under active LI |
Cause |
LI subscriber target is online and the LI session is active |
Effect |
Packets on the specified LI mirror source are mirrored toward the LI destination that is configured on the mirror destination |
LISourceSubscriberSessionStandby
Property name | Value |
|---|---|
Application name | li |
Event name |
LISourceSubscriberSessionStandby |
Default severity | notice |
Message format string | LI target subscriber LISubscriber_source under LI mirror source instance LISource_instance_name is offline and LI will resume when the target is back online |
Cause | LI session is inactive because the active subscriber target is offline; the session resumes when the active target is back online |
Effect | Specified LI mirror source is offline; packets are not mirrored toward the LI destination configured on the mirror destination |
LISubscriberAddUP
Property name | Value |
|---|---|
Application name |
li |
Event name | LISubscriberAddUP |
Default severity | debug |
Message format string |
LI target subscriber LISubscriber_source is added successfully to the LI mirror source instance LISource_instance_name on the MAG-u |
Cause | LI subscriber added successfully on the MAG-u |
Effect | Data packets are mirrored to the LI gateway when the subscriber comes online |
LISubscriberChangeUP
Property name | Value |
|---|---|
Application name | li |
Event name |
LISubscriberChangeUP |
Default severity | debug |
Message format string | Successfully changed configuration of LI target subscriber LISubscriber_source on LI mirror source instance LISource_instance_name on the MAG-u |
Cause | LI subscriber configuration changes successfully applied on the MAG-u |
Effect | LI data packets are mirrored successfully to the LI gateway when the subscriber comes online |
LISubscriberDeleteUP
Property name | Value |
|---|---|
Application name | li |
Event name |
LISubscriberDeleteUP |
Default severity | debug |
Message format string | Successfully removed LI target subscriber LISubscriber_source from the LI mirror source instance LISource_instance_name on the MAG-u |
Cause | LI subscriber is deleted successfully on the MAG-u |
Effect | LI subscriber is removed from the online MAG-u |
LISubscriberRetryUP
Property name | Value |
|---|---|
Application name | li |
Event name |
LISubscriberRetryUP |
Default severity | critical |
Message format string | cMAG-c cannot perform the operation LI_operation for LI target subscriber LISubscriber_source under LI mirror source instance LISource_instance_name and retries periodically |
Cause | cMAG-c fails to perform the LI operation for the LI target because the MAG-u is unreachable |
Effect | cMAG-c fails to perform the LI instruction and retries periodically |
management
ConfigurationApplyFailed
Property name | Value |
|---|---|
Application name | management |
Event name |
ConfigurationApplyFailed |
Default severity | warning |
Message format string | object: could not apply fields fields: reason |
Cause | Configuration fails |
Effect | Configuration is not applied; resolve the listed conflicts to allow the system to apply the configuration automatically, or apply a new configuration |
ConfigurationApplyFailureSolvedByApp
Property name | Value |
|---|---|
Application name | management |
Event name |
ConfigurationApplyFailureSolvedByApp |
Default severity |
informational |
Message format string | object: the configuration application failure is resolved |
Cause | Application accepts the new configuration |
|
Effect | Configuration successfully applied and configuration failure resolved |
ConfigurationApplyFailureSolvedByDelete
Property name | Value |
|---|---|
Application name | management |
Event name |
ConfigurationApplyFailureSolvedByDelete |
Default severity |
informational |
Message format string | object: the configuration application failure is resolved (object was deleted) |
Cause | Application accepts the object for deletion |
|
Effect | Object will be deleted and configuration failure resolved |
ConfigurationApplyFailureSolvedByUpdate
Property name | Value |
|---|---|
Application name | management |
Event name |
ConfigurationApplyFailureSolvedByUpdate |
Default severity |
informational |
Message format string | object: the configuration application failure is resolved (update request is canceled) |
Cause | New configuration overwrites the failing configuration |
Effect | No more pending configuration and configuration failure resolved |
ConfigurationDeleteFailed
Property name | Value |
|---|---|
Application name | management |
Event name |
ConfigurationDeleteFailed |
Default severity | warning |
Message format string | object: could not delete object: reason |
Cause | Configuration deletion fails |
Effect |
Configuration is not deleted; resolve the listed conflicts to allow the system to delete the configuration automatically, or restore the configuration to cancel the deletion |
ConfigurationDeleteFailureSolvedByApp
Property name | Value |
|---|---|
Application name | management |
Event name |
ConfigurationDeleteFailureSolvedByApp |
Default severity |
informational |
Message format string | object: the configuration delete failure is resolved |
Cause | Application deletes the object |
Effect |
Object deleted and configuration failure resolved |
ConfigurationDeleteFailureSolvedByUpdate
Property name | Value |
|---|---|
Application name | management |
Event name |
ConfigurationDeleteFailureSolvedByUpdate |
Default severity |
informational |
Message format string | object: the configuration delete failure is resolved (object need not be deleted anymore) |
Cause | New configuration cancels the pending delete |
|
Effect | Object not deleted and configuration failure resolved |
OperationalStateFetchFailed
Property name | Value |
|---|---|
Application name | management |
Event name |
OperationalStateFetchFailed |
Default severity | error |
Message format string | object: could not fetch operational state - reason |
Cause | Fetch of the operational state fails |
Effect |
Incorrect operational state returned |
OperationalStateFetchWarning
Property name | Value |
|---|---|
Application name |
management |
Event name | OperationalStateFetchWarning |
Default severity | warning |
Message format string |
object: warning while fetching operational state - reason |
|
Cause | Warning occurs while fetching operational state |
Effect |
Incorrect operational state may be returned |
odsa
MicroNetsAvailable
Property name | Value |
|---|---|
Application name | odsa |
Event name |
MicroNetsAvailable |
Default severity | informational |
Message format string | network-instance networkInstance, pool pool, address-assignment-type addressAssignmentType: micro-net(s) available again |
Cause |
Number of available micro-nets rises above zero |
Effect | Setup of new sessions no longer fails because of lack of addresses |
MicroNetsDepleted
Property name | Value |
|---|---|
Application name |
odsa |
Event name | MicroNetsDepleted |
Default severity | warning |
Message format string |
network-instance networkInstance, pool pool, address-assignment-type addressAssignmentType: no more micro-nets |
Cause | Number of available micro-nets reaches zero |
|
Effect | Setup of new sessions fails due to lack of addresses when a new micro-net is required. To resolve this, add subnets to the pool or clear sessions to free up micro-nets. |
MinimumFreeMicroNetsHigh
Property name | Value |
|---|---|
Application name | odsa |
Event name |
MinimumFreeMicroNetsHigh |
Default severity | informational |
Message format string | network-instance networkInstance, pool pool, address-assignment-type addressAssignmentType: number of micro-nets high enough again |
Cause |
Number of available micro-nets rises above the rising threshold and is above the wanted minimum |
Effect | None |
MinimumFreeMicroNetsLow
Property name | Value |
|---|---|
Application name |
odsa |
Event name | MinimumFreeMicroNetsLow |
Default severity | warning |
Message format string |
network-instance networkInstance, pool pool, address-assignment-type addressAssignmentType: running low on micro-nets |
Cause | Number of available micro-nets falls below the low threshold |
Effect | None |
python
PythonScriptCompilationFailure
Property name | Value |
|---|---|
Application name | python |
Event name |
PythonScriptCompilationFailure |
Default severity | warning |
Message format string | Python-script 'script' failed to compile: err |
Cause | Invalid Python script source code |
Effect |
Python script is operationally down and fails immediately when executed |
PythonScriptExecutionError
Property name | Value |
|---|---|
Application name | python |
Event name |
PythonScriptExecutionError |
Default severity | warning |
Message format string | Python-script 'script' terminated with an exception: err |
Cause | Python script terminates with an exception |
Effect | Python script uses the action-on-failure configuration to evaluate whether to continue the call flow |
PythonScriptOutput
Property name | Value |
|---|---|
Application name |
python |
Event name | PythonScriptOutput |
Default severity | debug |
Message format string |
Python-script 'script' output: output |
Cause |
Python script generated output |
Effect | Not applicable |
PythonScriptSourceLoadError
Property name | Value |
|---|---|
Application name | python |
Event name |
PythonScriptSourceLoadError |
Default severity | warning |
Message format string | Python-script 'script' failed to load: err |
Cause | Could not fetch the Python script source code from its location |
Effect | Python script is operationally down and fails immediately when executed |
radius
RadiusCoaDisconnectMsgSendError
Property name | Value |
|---|---|
Application name |
radius |
Event name | RadiusCoaDisconnectMsgSendError |
Default severity | warning |
Message format string |
Due to connectivity issues, a CoA reply message could not be sent. |
Cause |
CoA or Disconnect reply not sent because of connectivity issues |
Effect |
Reply is lost |
RadiusCoaDisconnectPacketDiscarded
Property name | Value |
|---|---|
Application name |
radius |
Event name | RadiusCoaDisconnectPacketDiscarded |
Default severity | warning |
Message format string |
A msgType request was discarded. |
Cause | Malformed CoA or Disconnect request |
Effect | CoA or Disconnect request discarded without performing the requested action |
RadiusCoaMessageHandlingFailed
Property name | Value |
|---|---|
Application name | radius |
Event name |
RadiusCoaMessageHandlingFailed |
Default severity | warning |
Message format string | A CoA Disconnect Request was not handled successfully. |
Cause | CoA or Disconnect request not processed |
|
Effect | Request is not executed or is executed incompletely |
RadiusCoaNackSent
Property name | Value |
|---|---|
Application name |
radius |
Event name | RadiusCoaNackSent |
Default severity | warning |
Message format string |
A CoA Request was not handled successfully. |
Cause | Unsuccessful CoA request |
Effect | Request is not executed or is executed incompletely |
RadiusDisconnectNackSent
Property name | Value |
|---|---|
Application name | radius |
Event name |
RadiusDisconnectNackSent |
Default severity | warning |
Message format string | A Disconnect Request was not handled successfully. |
Cause | Unsuccessful Disconnect request |
Effect |
Request is not executed or is executed incompletely |
session-manager
DHCPv4InvalidLeaseTimes
Property name | Value |
|---|---|
Application name |
session-manager |
Event name | DHCPv4InvalidLeaseTimes |
Default severity | warning |
Message format string |
Invalid DHCPv4 renew, rebind, lease time combination, fallback on default values |
Cause | Invalid DHCPv4 renew, rebind, and lease time combination |
Effect | Fallback to default DHCPv4 renew, rebind, and lease time; resolve by making the timers conform to the configuration rule, where each timer must be smaller than or equal to the next in the list |
DHCPv4RelayReplyDecodeFailure
Property name | Value |
|---|---|
Application name | session-manager |
Event name |
DHCPv4RelayReplyDecodeFailure |
Default severity | error |
Message format string | Could not decode DHCP message: errorMessage |
Cause | Invalid remote DHCPv4 server reply |
Effect |
Message drops |
DHCPv4RelayReplyMessageFailure
Property name | Value |
|---|---|
Application name |
session-manager |
Event name | DHCPv4RelayReplyMessageFailure |
Default severity | error |
Message format string |
Could not process DHCPv4 Relay server reply: errorMessage |
Cause |
Processing failure of remote DHCPv4 server reply |
Effect |
Message drops |
DHCPv4RelayReplySessionNotFoundFailure
Property name | Value |
|---|---|
Application name |
session-manager |
Event name | DHCPv4RelayReplySessionNotFoundFailure |
Default severity | error |
Message format string |
Could not find a session corresponding to the request: errorMessage |
|
Cause | corresponding session is not found for the reply received from the remote DHCPv4 server |
Effect | Message drops |
DHCPv6InvalidLifetimes
Property name | Value |
|---|---|
Application name | session-manager |
Event name |
DHCPv6InvalidLifetimes |
Default severity | warning |
Message format string | Invalid DHCPv6 t1, t2, IPv6 preferred and valid lifetime combination, fallback on default values |
Cause | Invalid DHCPv6 renew (T1), DHCPv6 rebind (T2), IPv6 preferred, and IPv6 valid lifetime combination |
Effect | Fallback to the default DHCPv6 renew, DHCPv6 rebind, IPv6 preferred, and IPv6 valid lifetime; resolve by making the timers confirm to the configuration rule, where each timer must be smaller than or equal to the next in the list |
DHCPv6RelayReplyDecodeFailure
Property name | Value |
|---|---|
Application name | session-manager |
Event name |
DHCPv6RelayReplyDecodeFailure |
Default severity | error |
Message format string | Could not decode DHCPv6 message: errorMessage |
Cause | Invalid remote DHCPv6 server reply |
Effect |
Message drops |
DHCPv6RelayReplyMessageFailure
Property name | Value |
|---|---|
Application name |
session-manager |
Event name | DHCPv6RelayReplyMessageFailure |
Default severity | error |
Message format string |
Could not process DHCPv6 Relay server reply: errorMessage |
Cause |
Processing failure of remote DHCPv6 server reply |
Effect |
Message drops |
DHCPv6RelayReplySessionNotFoundFailure
Property name | Value |
|---|---|
Application name |
session-manager |
Event name | DHCPv6RelayReplySessionNotFoundFailure |
Default severity | error |
Message format string |
Could not find session: errorMessage |
Cause | corresponding session is not found for the reply received from the remote DHCPv6 server |
Effect | Message drops |
IBCPMessageDecodeFailure
Property name | Value |
|---|---|
Application name | session-manager |
Event name |
IBCPMessageDecodeFailure |
Default severity | error |
Message format string | Could not decode IBCP message: errorMessage |
Cause | Incoming IBCP message with invalid encoding |
|
Effect | IBCP message drops; see the $errorMessage$ for more information and potential recovery actions |
IBCPMessageFailure
Property name | Value |
|---|---|
Application name |
session-manager |
Event name | IBCPMessageFailure |
Default severity | error |
Message format string |
Could not process IBCP message: errorMessage |
Cause |
IBCP message processing failure during a non-setup transaction (for example, because of unreachable MAG-u) |
Effect | IBCP message drops or returns with a failure status code, the transaction is not executed; see the $errorMessage$ for more information and potential recovery actions |
IBCPSessionSetupFailure
Property name | Value |
|---|---|
Application name | session-manager |
Event name |
IBCPSessionSetupFailure |
Default severity | error |
Message format string | IBCP session setup failure: errorMessage |
Cause | IBCP message fails to trigger a session setup (for example, because of failed authentication or unreachable MAG-u) |
Effect | IBCP message drops and session is not created; see the $errorMessage$ for more information and potential recovery actions |
LostHostConnectivity
Property name | Value |
|---|---|
Application name | session-manager |
Event name |
LostHostConnectivity |
Default severity | warning |
Message format string | Lost host connectivity |
Cause |
SHCV timeout |
Effect | Protocol stack or the session is removed |
PFCPSessionDeletionFailed
Property name | Value |
|---|---|
Application name | session-manager |
Event name |
PFCPSessionDeletionFailed |
Default severity | warning |
Message format string | PFCP session deletion failed for 15 minutes, session is deleted without informing the UPF |
Cause | PFCP session deletion fails for 15 minutes (for example, because of headless) |
Effect | Session is removed from the cMAG-c but not from the MAG-u; a PFCP audit is scheduled to synchronize the MAG-u and cMAG-c |
PFCPSessionReportFailure
Property name | Value |
|---|---|
Application name | session-manager |
Event name |
PFCPSessionReportFailure |
Default severity | error |
Message format string | PFCP Session Report failure: errorMessage |
Cause | PFCP session report from the MAG-u fails during processing (for example, an unsupported report type is received, or an inactivity report is received from a standby MAG-u) |
Effect | Report is not further processed and a response is sent to the MAG-u |
PPPTimerEventFailure
Property name | Value |
|---|---|
Application name | session-manager |
Event name |
PPPTimerEventFailure |
Default severity | error |
Message format string | Handling PPP timeout caused session failure: errorMessage |
Cause | A PPP protocol timer critical to the transaction expires (for example, LCP or IPCP timeout) |
Effect | Transaction (for example, session setup) fails and necessary protocol errors are signaled; see the $errorMessage$ for more information and potential recovery actions |
SessionCoAFailure
Property name | Value |
|---|---|
Application name |
session-manager |
Event name | SessionCoAFailure |
Default severity | error |
Message format string |
CoA failed: errorMessage |
Cause | Session CoA fails |
Effect | Changes are not applied and the CoA is NACKed |
SessionPFCPAuditFailure
Property name | Value |
|---|---|
Application name | session-manager |
Event name |
SessionPFCPAuditFailure |
Default severity | error |
Message format string | PFCP audit failed: errorMessage |
Cause | PFCP session audit message fails because the MAG-u rejects the message or because the message times out for longer than the configured headless timer |
Effect | Session is not audited; resolve by triggering a manual audit of the MAG-u that holds the session |
SessionsCleared
Property name | Value |
|---|---|
Application name |
session-manager |
Event name | SessionsCleared |
Default severity | informational |
Message format string |
Cleared numSessions sessions |
Cause | Clearing of sessions triggered by a clear command finishes |
Effect | Sessions are deleted |
SessionTimerFailure
Property name | Value |
|---|---|
Application name | session-manager |
Event name |
SessionTimerFailure |
Default severity | error |
Message format string | Timer event failed: errorMessage |
Cause | A transaction that is triggered by a session timer fails (for example, because of an unreachable peer) |
Effect | Timer event is ignored; the cMAG-c takes corrective actions or relies on a subsequent timer event for periodic timers (for example, RADIUS Interim Update messages); if the problem persists, see the $errorMessage$ for more information |
UPFResiliencyStandbyPFCPSessionFailure
Property name | Value |
|---|---|
Application name | session-manager |
Event name |
UPFResiliencyStandbyPFCPSessionFailure |
Default severity |
warning |
Message format string | PFCP session creation or modification failed on the standby UPF standbyUPFNodeID: failureReason |
Cause | PFCP session creation or modification fails on the standby MAG-u |
Effect | Standby MAG-u is not synchronized with the most recent session state; the cMAG-c automatically retries creation or modification toward the MAG-u to resolve this |
upf-manager
BaseFunctionFeatureSetNotSupported
Property name | Value |
|---|---|
Application name |
upf-manager |
Event name | BaseFunctionFeatureSetNotSupported |
Default severity | error |
Message format string |
Base function feature set not supported by UPF upfNodeId |
Cause |
MAG-u does not support the base function feature set |
Effect |
PFCP association with the MAG-u is not established or is not released; resolve this by upgrading the MAG-u to a version that supports all these features |
DynamicallySignaledL2AccessIdDeletedByTimeout
Property name | Value |
|---|---|
Application name | upf-manager |
Event name |
DynamicallySignaledL2AccessIdDeletedByTimeout |
Default severity |
informational |
Message format string | Dynamically signalled l2-access-id l2AccessId from UPF upfNodeId deleted by timeout |
Cause |
Dynamically-signaled Layer 2 access ID is deleted because the MAG-u no longer signals it |
Effect | Layer 2 access ID is no longer tracked, and the per l2-access-id tunnel is deleted |
NewDynamicallySignaledL2AccessIdDropped
Property name | Value |
|---|---|
Application name | upf-manager |
Event name |
NewDynamicallySignaledL2AccessIdDropped |
Default severity |
warning |
Message format string | New dynamically signalled l2-access-id l2AccessId from UPF upfNodeId dropped |
Cause | New dynamically-signaled Layer 2 access ID is ignored because the maximum limit is reached |
Effect | Health of the new Layer 2 access ID is not tracked and no per-port tunnel is established; resolve this by reducing the number of 'l2-access-id' entries on the MAG-u |
NewDynamicallySignaledNetworkInstanceDropped
Property name | Value |
|---|---|
Application name | upf-manager |
Event name |
NewDynamicallySignaledNetworkInstanceDropped |
Default severity |
warning |
Message format string | New dynamically signalled network instance networkInstance from UPF upfNodeId dropped |
Cause |
New dynamically-signaled network instances is ignored because the maximum limit is reached |
Effect | Network instance health is not tracked; resolve this by reducing the number of network-instances on the MAG-u |
PFCPAssociationFailure
Property name | Value |
|---|---|
Application name | upf-manager |
Event name |
PFCPAssociationFailure |
Default severity | error |
Message format string | PFCP pfcpMessage exchange with UPF upfNodeId failed: errorMessage |
Cause | PFCP association message exchange is unsuccessful |
Effect | MAG-u does not successfully process the message, refer to the $errorMessage$ for more details and potential recovery actions |
PFCPDefaultSessionFailure
Property name | Value |
|---|---|
Application name | upf-manager |
Event name |
PFCPDefaultSessionFailure |
Default severity | error |
Message format string | PFCP pfcpMessage exchange with UPF upfNodeId failed for default session with sessionID sessionId: errorMessage |
Cause | PFCP default session message exchange is unsuccessful |
Effect | MAG-u does not successfully process the message; refer to the $errorMessage$ for more information and potential recovery actions |
UpfAuditAbort
Property name | Value |
|---|---|
Application name |
upf-manager |
Event name | UpfAuditAbort |
Default severity | informational |
Message format string |
PFCP Audit with UPF upfNodeId aborted: cause |
Cause |
MAG-u audit aborts; for example, because of a signaling failure, bringing the PFCP association or PFCP path down, or a more recent audit request is received |
Effect | Ongoing MAG-u audit aborts; a newer audit starts or is scheduled if the PFCP association is up |
UpfAuditEnd
Property name | Value |
|---|---|
Application name |
upf-manager |
Event name | UpfAuditEnd |
Default severity | informational |
Message format string |
PFCP Audit with upfNodeId ended |
Cause | MAG-u audit ends |
Effect | All MAG-u sessions and fate sharing groups (FSGs) are audited |
UpfAuditEndFailure
Property name | Value |
|---|---|
Application name |
upf-manager |
Event name | UpfAuditEndFailure |
Default severity | error |
Message format string |
PFCP Audit with UPF upfNodeId not ended: errorMessage |
Cause |
Signaling the end message of a MAG-u PFCP audit fails |
Effect |
PFCP audit does not successfully complete; the audit is rescheduled, refer to the $errorMessage$ for more information and potential recovery actions |
UpfAuditInitiated
Property name | Value |
|---|---|
Application name |
upf-manager |
Event name | UpfAuditInitiated |
Default severity | informational |
Message format string |
PFCP Audit with UPF upfNodeId initiated: trigger trigger |
Cause |
MAG-u audit initiates |
Effect | All sessions and FSGs in the MAG-u are audited |
UpfAuditStartFailure
Property name | Value |
|---|---|
Application name | upf-manager |
Event name |
UpfAuditStartFailure |
Default severity | error |
Message format string | PFCP Audit with UPF upfNodeId not started: errorMessage |
Cause | Signaling the start message of a MAG-u PFCP audit fails |
Effect | PFCP audit does not start; audit is rescheduled, see $errorMessage$ for more information and potential recovery actions |
UpfPartialAuditAbort
Property name | Value |
|---|---|
Application name | upf-manager |
Event name |
UpfPartialAuditAbort |
Default severity | informational |
Message format string | PFCP Partial Audit with UPF upfNodeId aborted: cause |
Cause | Partial MAG-u audit aborts; for example, because of signaling failures or bringing the PFCP association or PFCP path down |
Effect | Ongoing partial MAG-u audit aborts; a full audit starts or is scheduled if the PFCP association is up |
UpfPartialAuditEnd
Property name | Value |
|---|---|
Application name |
upf-manager |
Event name | UpfPartialAuditEnd |
Default severity | informational |
Message format string |
PFCP Partial Audit with upfNodeId ended |
Cause |
Partial MAG-u audit ends |
Effect | All requested sessions in the MAG-u are audited |
UpfPartialAuditScheduledByAuditPod
Property name | Value |
|---|---|
Application name | upf-manager |
Event name |
UpfPartialAuditScheduledByAuditPod |
Default severity |
informational |
Message format string | PFCP Partial Audit with UPF upfNodeId started on audit pod request |
Cause | Audit pod initiates partial MAG-u audit |
Effect | A set of sessions that are potentially out-of-sync in the MAG-u are audited |
UpfPartialAuditStart
Property name | Value |
|---|---|
Application name | upf-manager |
Event name |
UpfPartialAuditStart |
Default severity | informational |
Message format string | PFCP Partial Audit with UPF upfNodeId initiated |
Cause | Partial MAG-u audit starts |
Effect |
A selection of sessions in the MAG-u are audited |
UpfResiliencyFsgUpfChange
Property name | Value |
|---|---|
Application name | upf-manager |
Event name |
UpfResiliencyFsgUpfChange |
Default severity | informational |
Message format string | UP group upGroup, FSG fsgID, active UPF activeUPFNodeID (health activeUPFHealth), standby UPF standbyUPFNodeID (health standbyUPFHealth), previous active UPF previousActiveUPFNodeID, previous standby UPF previousStandbyUPFNodeID |
|
Cause | Active or standby MAG-u of an FSG changes |
Effect |
If the active MAG-u changes, traffic associated with the FSG goes through the new active MAG-u, or if only the standby MAG-u changes, hot standby sessions are downloaded to the new standby MAG-U and removed from the old standby MAG-u |
UpfResiliencyFsgUpfError
Property name | Value |
|---|---|
Application name | upf-manager |
Event name |
UpfResiliencyFsgUpfError |
Default severity | error |
Message format string | UP group upGroup, FSG fsgID, PFCP SGRP operation failed on role UPF upfNodeID: failureReasondetailedFailureReason |
Cause | MAG-u reports an error in response to a PFCP SGRP create, modify, or delete request of an FSG |
Effect | MAG-u is placed in failure lockout, potentially changing its active/standby state, and cMAG-c automatically disables the lockout to allow the MAG-u to become active/standby again; if this repeats, investigate the error details to resolve the PFCP SGRP signaling issue |
UpfResiliencyFsgUpfHealthy
Property name | Value |
|---|---|
Application name | upf-manager |
Event name |
UpfResiliencyFsgUpfHealthy |
Default severity | informational |
Message format string | UP group upGroup, FSG fsgID, role UPF upfNodeID has become healthy |
Cause | MAG-u health rises above, or is equal to, the failure threshold health |
Effect | MAG-u is not considered fully failed |
UpfResiliencyFsgUpfNotHealthy
Property name | Value |
|---|---|
Application name | upf-manager |
Event name |
UpfResiliencyFsgUpfNotHealthy |
Default severity | informational |
Message format string | UP group upGroup, FSG fsgID, role UPF upfNodeID has become not healthy |
Cause | MAG-u health falls below the failure threshold health |
Effect | MAG-u is considered failed; If the MAG-u was active and non-revertive settings (active-change-without-failure false) are enabled, the MAG-u may now become standby |