Operate and maintain
Documents under this category provide functional descriptions and procedures for configuring, operating, and maintaining the MAG-c.
- Control Plane Function
  This guide describes the control plane function (CPF) for control and user plane separation (CUPS) solutions. The CPF is based on the packet forwarding control protocol (PFCP) interface as defined in 3GPP TS 29.244 for mobile 4G CUPS and 5G.
  - Getting started
    Find general information about this guide.
  - MAG-c configuration quick start
    The quick start steps configure the main components required to prepare the MAG-c for subscriber management or Service Based Interface (SBI) communication.
  - Session management
    Get a general overview of the session functionality and the address assignment protocols, and details on the IPoE and PPPoE fixed access and the fixed wireless access (FWA) session types.
  - Service Based Interfaces
    The 5G core network is a Service Based Architecture (SBA), which consists of multiple Network Functions (NFs). Each interface in the Service Based Interfaces (SBI) consists of one or more services that are used for the communication between the functions.
  - Address assignment
    Overview of the address assignment, and details on the supported local (ODSA) and AAA-based address assignment.
  - Authentication
    Configure authentication for a new MAG-c session, including the RADIUS authentication profile. Learn about the BNG EP and ADB lookup process.
  - PCF-based policy management
  - Accounting and charging
    Learn about the statistics collection from the BNG-UP, time-based and volume-based charging, RADIUS accounting configuration, and buffering of the RADIUS accounting messages for later retransmission.
  - Residential NAT
    Get information about NAT on BNG CUPS, learn about the functional split between MAG-c and BNG-UP, about configuring NAT, logging, and monitoring NAT resources.
  - Geo-redundancy
    Two MAG-c systems can be deployed in a geo-redundant configuration. If one system fails, the other system ensures uninterrupted service and minimizes the impact of failure for broadband clients.
  - Python support
    Customize the MAG-c behavior by applying user-defined Python scripts to inspect and modify control protocol packets.
  - BNG-UP resiliency
    The Nokia MAG-c supports a MAG-c-driven BNG-UP resiliency scheme. Learn about this resiliency scheme, the resiliency handling, and deployment use cases.
  - KPI and KCI performance monitoring
    The MAG-c supports periodic collection of Key Performance Indicator (KPI) and Key Capacity Indicator (KCI) statistics for control plane signaling and system resource usage. The MAG-c writes the KPI and KCI data as XML per collection interval.
  - Control Plane Function Guide PDF
- Control Plane Function Advanced Configuration
  This guide provides feature and configuration explanations, CLI descriptions, and overall solutions for the control plane function (CPF) for control and user plane separation (CUPS) solutions.
- Security Best Practices and Hardening
- SR OS User Plane Function

Storage and retrieval of KPI and KCI XML files

The MAG-c stores generated XML files in the local file system, from which an external management system can retrieve them using SFTP or FTP.

Nokia recommends using the CF2: card for storing the KPI and KCI XML files. This is because the system primarily uses the CF1: card to store configuration files and images. If the location is not defined, CF2: is the default location for accounting policies.

The system compresses the XML files using the gzip format and writes them temporarily in the local directory. After closing the files (rollover), the system moves them to a common directory for storage. After the rollover, an SNMP trap is sent to inform the external management system that a new set of files is available for retrieval.

October 30, 2025