Mavenir AUSF Operations Management Guide
Mavenir AUSF Operations Management Guide
Commercial in Confidence
© Copyright 2021, Mavenir
AUSF Operations and Management
DISCLAIMER
© Copyright 2021, Mavenir. All rights reserved. This document is protected by international copyright law and may not be reprinted, reproduced,
copied or utilised in whole or in part by any means including electronic, mechanical, or other means without the prior written consent of Mavenir.
Whilst reasonable care has been taken by Mavenir to ensure the information contained herein is reasonably accurate, Mavenir shall not, undera
any circumstances be liable for any loss or damage (direct, indirect or consequential) suffered by any party as a result of the contents of this
publication or the reliance of any party thereon or any inaccuracy or omission therein. The information in this document is therefore provided on
an "as is" basis without warranty and is subject to change without further notice and cannot be construed as a commitment by Mavenir.
The products mentioned in this document are identified by the names, trademarks, service marks and logos of their respective companies or
organizations and may not be used in any advertising or publicity without the prior written consent of those companies or organizations and
Mavenir.
www.mavenir.com
AUSF Operations and Management
Table of Contents
1. Purpose ...............................................................................................................................1
1.1. Acronyms .......................................................................................................................1
1.2. Standard References .....................................................................................................2
1.3. Mavenir References.......................................................................................................2
2. Performance Management.................................................................................................3
2.1. Authentication Server Function (AUSF) Performance Counters....................................4
2.1.1. AUSF Labels..........................................................................................................4
2.1.2. AUSF Service Operation Counters ........................................................................4
2.1.2.1 AUSF Generic Counters ......................................................................................4
2.1.2.2 AUSF Authentication Counters ............................................................................5
2.1.2.3 Registration Counters ..........................................................................................9
2.1.2.4 De-register Counters ..........................................................................................10
2.1.2.5 EAP AKA Authentication Counters ....................................................................10
2.1.2.6 5G AKA Authentication Counters .......................................................................12
2.1.2.7 EAP TLS Authentication Counters .....................................................................13
2.1.2.8 UE Authentication Confirmation Counters .........................................................14
2.1.2.9 UPU Protection Group Counters ........................................................................15
2.1.2.10 SOR Protection Group Counters .....................................................................16
2.1.2.11 AUSF NRF Interface Group Counters ..............................................................17
2.1.2.12 AUSF UDSF Interface Group Counters ...........................................................18
2.1.2.13 AUSF UDM Interface Group Counters .............................................................19
2.1.2.14 AUSF UEAUTH Interface Group Counters ......................................................21
3. Alarms Overview...............................................................................................................23
3.1. About Alarms ...............................................................................................................23
3.1.1. Alarms Types .......................................................................................................23
3.1.2. Alarm Severity Levels ..........................................................................................23
3.1.3. Alarm Parameters ................................................................................................24
3.1.4. Color Coded Alarm Severity Levels .....................................................................25
3.2. CMS Fault Management ..............................................................................................26
3.2.1. Fault Presentation................................................................................................26
3.2.2. Fault Management UI ..........................................................................................26
3.3. Authentication Server Function (AUSF) Alarms and Events........................................28
3.3.1. UDM Interface......................................................................................................28
3.3.2. UDSF Interface ....................................................................................................28
4. Authentication Server Function (AUSF) Show and Execute Commands....................30
4.1. Document conventions ................................................................................................30
4.1.1. Text formatting conventions.................................................................................30
4.1.2. Command syntax conventions.............................................................................30
4.2. AUSF Show and Exec Commands ..............................................................................31
4.2.1. get_ausf_version..................................................................................................31
www.mavenir.com i
AUSF Operations and Management
www.mavenir.com ii
AUSF Operations and Management
1 Purpose
This document describes the Alarms, Counters and KPIs and the Show&Exec commands
supported by the Mavenir Authentication Server Function (AUSF) in 5G Core.
1.1 Acronyms
Table 1 lists the acronyms used in this guide.
Table 1: Acronyms
Acronyms Description
www.mavenir.com 1
AUSF Operations and Management
Acronyms Description
• 3GPP TS 23.501 v16.4.0: System Architecture for the 5G System (5GS); Stage2
www.mavenir.com 2
AUSF Operations and Management
2 Performance Management
The Performance Management subsystem provides standard compliant (3GPP, IETF)
performance counters for all application functions.
Performance Management (PM) data collection is activated by default, and data is collected and
stored in periodic and daily registers. Performance data is stored in flat files and can be uploaded
to an external system for display, data analysis and/or post-processing purposes. The operator
can query the PM database by node, by PM measurement groups, PM data type, and date and
time to display basic PM reports in tabular formats.
• Perfmon data - generic data (not application-specific) that shows the health of an application,
and the CPU, memory and disk usage of the application. CMS retrieves Perfmon data from the
VNFs to display on the Dashboard
• Raw counters (also called TMMs) - are specific to each NF. These values are updated
periodically based on the configuration (5, 10, or 15 minutes). There can be several groups of
counter data for each NF that are arranged based on the functionality. For example, system
counters and interface counters. These counters are uploaded to a system that generates Key
Performance Indicators (KPIs) using basic formulas. These counters are collected by CMS
from the VNFs using Netconf and normally uploaded to an analytics system such as Analytics
(aka MSIS) for KPI reports.
• Transaction Logs (TRLs) - Transaction logs are generated at the end of each session and can
be used to identify problems in the network. Like CDRs, Transaction logs are streamed by the
VNF onto Analytics via a REST interface.These log files are collected by Analytics from the
VNFs using REST and can be used for troubleshooting or customer care queries on subscriber
activities or specific/persistent problems. They can also be used for big data analytics to
analyze long term trends in the network.
Presentation
www.mavenir.com 3
AUSF Operations and Management
Table 2: Labels
Serial No. Labels Description
4. serviceName The name of service AUSF, deducted from env. variable AUSF_SERVICE and
values can be:
• ausf-auth
• ausf-sorprotect
• ausf-upuprotect
5. nfId The identificator of consumer, taken from http2 headers: x-forwarded-for or x-
real-ip. Used only for AUSF_NAUSF_OCI_COUNT:
6. iface The name of interface - N12 or N13. Used only for AUSF_NAUSF_O-
CI_COUNT: x
www.mavenir.com 4
AUSF Operations and Management
www.mavenir.com 5
AUSF Operations and Management
www.mavenir.com 6
AUSF Operations and Management
www.mavenir.com 7
AUSF Operations and Management
www.mavenir.com 8
AUSF Operations and Management
www.mavenir.com 9
AUSF Operations and Management
www.mavenir.com 10
AUSF Operations and Management
www.mavenir.com 11
AUSF Operations and Management
www.mavenir.com 12
AUSF Operations and Management
www.mavenir.com 13
AUSF Operations and Management
www.mavenir.com 14
AUSF Operations and Management
www.mavenir.com 15
AUSF Operations and Management
www.mavenir.com 16
AUSF Operations and Management
www.mavenir.com 17
AUSF Operations and Management
www.mavenir.com 18
AUSF Operations and Management
www.mavenir.com 19
AUSF Operations and Management
www.mavenir.com 20
AUSF Operations and Management
www.mavenir.com 21
AUSF Operations and Management
www.mavenir.com 22
AUSF Operations and Management
3 Alarms Overview
An alarm indicates the fault types generated within 5G Core that requires attention. Alarm
information is displayed in an intuitive, easy-to-use manner. Fault Management (FM) provides
basic built-in alarm correlation capabilities to identify the root cause of alarms. Fault Management
is able to generate a single alarm of a faulty resource and any number of all physical / logical
resources affected by fault, which facilitates root cause analysis and alarm clearing. When a fault
is cleared, the fault management clears the alarms associated with the repaired faults.
A color-coded control panel shows the number of alarms per severity type, and dynamically
updates the screen as alarms are received and cleared.
You can view mCMS alarms from the mCMS Fault Management screen.
Communication Alarm A communication alarm is associated with the procedures and/or processes
that convey information from one point to another.
Quality of Service Alarms A Quality of Service alarm indicates a degradation in the Quality of Service.
Processing Error Alarms A Processing Error alarm indicates a software or processing fault
Equipment Alarms An Equipment Alarm indicates an equipment fault.
Environmental Alarms An environmental alarm indicates a condition relating to an enclosure where
the equipment resides.
Clear Indicates the system cleared one or more previously reported alarms. A cleared
status indicates the performed functions, as follows:
• Cleared all alarms for a managed object with the same alarm type, including:
• the probable cause.
• specific problems (if given)
Note: Using the Correlated notifications parameter, multiple associated
notifications may also be cleared.
Indeterminate Indicates the system cannot determine the severity level.
www.mavenir.com 23
AUSF Operations and Management
Critical Indicates an active service affecting condition occurred that requires an immediate
corrective action.
Note: A critical status occurs when a managed object goes out of service and
its capability must be restored.
Major Indicates an active service affecting condition developed that requires urgent cor-
rective action. This severity level applies when there is a severe degradation in the
capability of the managed object and its capability must be restored.
Minor Indicates a non-service affecting fault condition and that corrective action should
be taken in order to prevent a more serious fault.
Note: A minor status occurs when a detected alarm condition is not currently
degrading the capacity of the managed object.
Warning Indicates the detection of a potential or impending service affecting the fault before
any significant effects have occurred.
Note: Further action should be taken to diagnose and correct the problem (if
necessary) prevent it from becoming a more serious affecting fault.
Information Indicates the detection of an informational event that has occurred.
www.mavenir.com 24
AUSF Operations and Management
Probable Cause None Indicates a brief description of probable cause of this event
Specific Problem None A brief description of the specific cause of the event
Acknowledgment • ACK_YES Indicates whether the alarm or event has been acknowl-
• ACK_NO edged or not
Snmp Oid None Indicates the SNMP ID of the application process / thread
which originated the event
Component Label None Indicates the label or name of NFS / NFSI generating the
alarm
Comment None A brief comment on the event
Comment By None Details of who added the comment for the event
Changed Timestamp None Indicates the timestamp when the changes are made
Clear Event Name None Indicates the name of the event that can clear the alarm
Clear Snmp Id None Indicates the OID of the clear event
Ns ID None Indicates UUID of NF Service
Ns Service None Indicates the user label or name of the NF Service
NF Id None Indicates UUID of Network Function
Fault Event Data None Provides the complete Fault VES data received for that
alarm/event
Network Element Type • CNF Indicates the network element type
• CMS
Product None Indicates the product for which the alarm was raised
NF Service None Indicates the unique identifier (UUID) of the NF service that
is assigned by MTCIL
NF Id None Indicates the unique identifier (UUID) of the NF Id that is
assigned by MTCIL
IP Address None Indicates the IP address of the element causing the alarm
or event
Red Critical
Yellow Major
Teal Green Minor
Green Clear
www.mavenir.com 25
AUSF Operations and Management
CMS enables to configure several northbound SNMP alarm collection points. Whenever a new
northbound alarm collection end point is added, CMS iterates through the active alarm list of all
managed nodes and within CMS, and sends them as SNMP traps towards the new northbound
alarm collection point.
CMS supports re-generation of active alarms (alarm re-sync) of CMS, of each VNF separately or
together ("All nodes").
As an alternative option to SNMP, CMS can forward alarms and events received to northbound via
a VES interface.
T he F aul t M an age me nt su bsyst em su ppo rts f ive ba sic cat ego ries of al arm type s:
Communications, Quality of Service, Processing, Equipment and Environmental. Refer to
section Alarms Types for more information on the alarm type.
The Fault Management subsystem supports alarm severity levels: Critical, Major, Minor, Warning
and Clear. Refer to section Alarm Severity Levels for more information on the alarm severity levels.
SNMP Traps are used to inform the NBI of an alarm or event. Events are alarms collected by CMS
GUI and displayed in a tabular format. The alarm display is updated dynamically as new alarms
are received and existing alarms are cleared.
CMS supports to re-sync all active alarms to OSS, if OSS drops connection with CMS.
www.mavenir.com 26
AUSF Operations and Management
The following filter options are available in CMS fault management window:
• display based on Alarm severity: Critical, Major, Minor, Info (or Warning)
www.mavenir.com 27
AUSF Operations and Management
1. MAJOR EID_PEER_UDM_INTERFACE_UNAVAILABLE
Type COMMUNICATION
Repair Action Verify the following:
• If there is any network connectivity issue towards peer UDM,
or
• If the peer UDM interface server is down
Probable Cause Either the peer UDM interface is down or there is a network
issue.
Peer UDM service interface IP: <IP address>
Specific Problem Peer UDM interface is unavailable
AUSF clears the outstanding alarm when the peer UDM interface unavailability issue is resolved.
2. CLEAR EID_PEER_AUSF_INTERFACE_UNAVAILABLE_CLEARED
Type COMMUNICATION
Repair Action None
Probable Cause Peer UDM interface server unavailability issue is resolved
Specific Problem None
1. MAJOR EID_PEER_UDSF_INTERFACE_UNAVAILABLE
Type COMMUNICATION
Repair Action Verify the following:
• If there is any network connectivity issue towards peer UDSF,
or
• If the peer UDSF interface server is down
Probable Cause Either the peer UDSF interface is down or there is a network
issue.
Peer UDSF service interface IP: <IP address>
Specific Problem UDSF interface is unavailable
www.mavenir.com 28
AUSF Operations and Management
AUSF clears the outstanding alarm when the peer UDSF interface unavailability issue is resolved.
2. CLEAR EID_PEER_UDSF_INTERFACE_UNAVAILABLE_CLEARED
Type COMMUNICATION
Repair Action None
Probable Cause Peer UDSF interface server unavailability issue is resolved
Specific Problem None
www.mavenir.com 29
AUSF Operations and Management
Format Description
Convention Description
www.mavenir.com 30
AUSF Operations and Management
4.2.1 get_ausf_version
Retrieves the build and version information of the queried AUSF instance.
Syntax
get_ausf_version
Parameters
None
HTTP Method
GET
Execution Path
/ausf-man/v1//version
Usage Guidelines
Use this command to retrieve the build and version information of the queried AUSF instance.
Example
mCMS Output
www.mavenir.com 31
AUSF Operations and Management
The following example provides a sample output of the build and version information of the
queried AUSF instance.
CLI Output
The following CURL command provides a sample output of the build and version
information of the queried AUSF instance.
curl -v -X GET "http://172.16.230.44/ausf-man/v1/version”
www.mavenir.com 32
AUSF Operations and Management
4.2.2 get_ausf_svc_info
Retrieves NF focused information of AUSF instance.
Syntax
get_ausf_svc_info
Parameters
None
HTTP Method
GET
Execution Path
/ausf-man/v1/svc-info
Usage Guidelines
Example
mCMS Output
The following example provides a sample output of the NF focused information of AUSF
instance.
www.mavenir.com 33
AUSF Operations and Management
CLI Output
The following CURL command provides a sample output of the NF focused information of
AUSF instance.
curl -v -X GET "http://172.16.230.44/ausf-man/v1/svc-info”
www.mavenir.com 34
AUSF Operations and Management
4.2.3 get_ausf_stats
Retrieves platform informations AUSF instance is running on.
Syntax
get_ausf_stats
Parameters
None
HTTP Method
GET
Execution Path
/ausf-man/v1/stats
Usage Guidelines
Use this command to retrieve platform informations AUSF instance is running on.
Example
mCMS Output
The following example provides a sample output of the platform informations AUSF instance is
running on.
CLI Output
The following CURL command provides a sample output of the platform informations AUSF
instance is running on.
www.mavenir.com 35
AUSF Operations and Management
www.mavenir.com 36
AUSF Operations and Management
4.2.4 get_ausf_alarms
Retrieves statuses of alarms in AUSF instance.
Syntax
get_ausf_alarms
Parameters
None
HTTP Method
GET
Execution Path
/ausf-man/v1/alarms
Usage Guidelines
Example
mCMS Output
The following example provides a sample output of the statuses of the retrieved alarms in
AUSF instance.
www.mavenir.com 37
AUSF Operations and Management
CLI Output
The following CURL command provides a sample output of the statuses of the retrieved
alarms in AUSF instance.
curl -v -X GET "http://172.16.230.44/ausf-man/v1/alarms”
www.mavenir.com 38
AUSF Operations and Management
4.2.5 get_ausf_supi
Retrieves data of UE context stored in UDSF for AUSF.
Syntax
get_ausf_supi
Parameters
HTTP Method
GET
Execution Path
/ausf-man/v1/supi/{supi}
Usage Guidelines
Use this command to retrieve data of UE context stored in UDSF for AUSF.
Example
mCMS Output
The following example provides a sample output of the retrieved data of UE context stored
in UDSF for AUSF.
www.mavenir.com 39
AUSF Operations and Management
CLI Output
The following CURL command provides a sample output of the retrieved data of UE
context stored in UDSF for AUSF.
curl -v -X GET "http://172.16.230.44/ausf-man/v1/supi/{supi}”
www.mavenir.com 40
AUSF Operations and Management
4.2.6 del_ausf_supi
Cancels UE from authentication - delete context from UDSF.
Syntax
del_ausf_supi
Parameters
HTTP Method
DELETE
Execution Path
/ausf-man/v1/supi/{supi}
Usage Guidelines
Example
mCMS Output
The following example provides a sample output of the canceled UE from authentication.
CLI Output
www.mavenir.com 41
AUSF Operations and Management
The following CURL command provides a sample output of the canceled UE from
authentication.
curl -v -X GET "http://172.16.230.44/ausf-man/v1/del_ausf_supi”
www.mavenir.com 42
AUSF Operations and Management
Traces are activated from the Management System. Trace content is sent to the Trace Collection
Entity.
• N12
• N13
www.mavenir.com 43