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.

Quick start for subscriber management

Set up and configure basic components to prepare the MAG-c for subscriber management.

Configuration overview

This overview describes the components and steps required to configure the MAG-c for subscriber management.

The following table lists the main components and links to the specific configuration step that you must complete to prepare the MAG-c for subscriber management.

Table 1. MAG-c configuration components and quick-start steps
Configuration component	Configuration task
Configure MAG-c system resources.	Step 1
Configure IP connectivity between MAG-c and BNG-UP.	Step 2
Configure the PFCP association.	Step 3
Configure the IBCP and network realm (default PFCP session) for fixed-access sessions. Configure control plane communication for fixed wireless access (FWA) sessions.	Step 4
Configure the local IP address pool.	Step 5
Configure the APN and network realm.	Step 6
Configure the authentication database (ADB).	Step 7
Configure the BNG entry point for fixed access sessions. Configure the incoming APN/DNN for FWA sessions.	Step 8

Configuring MAG-c

These quick-start instructions provide the basic steps required to configure the MAG-c for subscriber management, including references to additional topics for users who want more information.

Identify the name of the IES or VPRN service used to host subscriber sessions on the BNG-UP; see Service selection.
Ensure the BNG-UP is configured; see the 7750 SR and VSR BNG CUPS User Plane Function Guide, "PFCP association" and "Session management", for more information.

This procedure describes the minimal configuration required to create subscriber sessions on the MAG-c.

Configure the system resources.
The values specified in the following example are for a MAG-c with a single VM instance. The assumption is the resource pool, gateway, card, and group are already configured. See CP session state and VM resilience for information about different VM resiliency models.
System resource configuration with a single VM instance
```
A:MAG-c>config>mobile>system# info
----------------------------------------------
            resource-pool 1 redundancy many-to-many gateway 1
                card 2
            exit
            group 1 resource-pool 1
                no shutdown
            exit
----------------------------------------------
```
Configure IP connectivity between the MAG-c and BNG-UP.
The following example shows a MAG-c directly connected to a BNG-UP. Connectivity to the system interface is also required for basic MAG-c functionality. See the7450 ESS, 7750 SR, 7950 XRS, and VSR Interface Configuration Guide for information about IP routing configuration.
IP connectivity between the MAG-c and BNG-UP
```
A:mag-c>config>router# info
----------------------------------------------
    interface "system"
        address 1.1.1.1/32
        no shutdown
    exit
    interface "to-BNG-UP1"
        address 192.168.1.1/24
        port 1/2/1
        no shutdown
    exit
----------------------------------------------
```

Create a PDN instance and under it, configure the PFCP association between the MAG-c and the BNG-UP.

The following example shows a minimal configuration required to form a PFCP association between the MAG-c and the BNG-UP. See PFCP association and path for more information.

PFCP association between the MAG-c and the BNG-UP

A:mag-c>config>mobile# info
----------------------------------------------
    profile
        pfcp
            pfcp-association-peer-list "peers"
                    pfcp-peer 192.168.50.84
                    pfcp-peer 192.168.50.83
                    pfcp-peer 192.168.50.82
                exit
            up-peer-list "ups"
                peer 192.168.50.84
                peer 192.168.50.83
                peer 192.164.50.82
            exit
        exit  
    exit
    pdn 1
        instance-type control
        pfcp-node-id-type ip
        epc-node 001.01.magc.nokia.1.1
        sx-n4 "default"
            interface
                pfcp "to-BNG-UP1"
            exit
            pfcp-association-list "peers"
            signaling
                pfcp
                    profile "default"
                exit
            exit
        up-peer-list "ups"
        no shutdown
    exit
----------------------------------------------

Configure a fixed-access or FWA session.
- For fixed-access sessions, configure IBCP to allow tunneling of IPoE sessions.
  The default IBCP tunnel supports tunneling of control packets from the BNG-UP to the MAG-c. The following example configures IPoE-based tunneling sessions. See In-band control plane and BNG-UP selection for more information about IBCP.
IPoE-based tunneling configuration for the IBCP tunnel
```
A:MAG-c>config>mobile>pdn#info
----------------------------------------------
        sx-n4 "default"
            interface
                ibcp "to-BNG-UP1"
            exit
            signaling
                ibcp
                    triggers ipoe-dhcp ipoe-dhcpv6 ipoe-router-solicit
                exit
            exit
----------------------------------------------
```
- For 4G FWA sessions, configure the S11 and S5 endpoints to enable control plane communication toward the MME.
  The following example shows a 4G FWA configuration for control plane traffic toward the MME. You require the S5 interface, even though it is an internal interface over which no messages are sent.
  
  Note: 5G FWA sessions follow similar steps but require more groundwork to enable Service Based Interface (SBI) communications. See Configuring Service Based Interfaces for the specific quick-start procedure.
  
  Note: See 4G and 5G NSA option 3 sessions and 5G standalone sessions for more information about configuring 4G and 5G sessions.
4G FWA configuration for control plane traffic toward the MME
```
A:MAG-c>config>mobile>pdn#info
----------------------------------------------
            s5 "default"
                interface
                    gtp-c "system" interface-realm "to_ran"
                exit
            exit
            s11 "default"
                interface
                    gtp-c "system" interface-realm "to_ran"
                exit
            exit
            sx-n4 
----------------------------------------------
```

Configure a local address pool for IP address assignment.

The following example shows a simple address pool configuration that uses the prefix 192.168.2.0/24 for an IP address assignment. Other methods can also be used. See Local address assignment for more information about IP address assignment.

Local address pool configuration for IP address assignment

A:MAG-c>config>mobile>pdn# info
----------------------------------------------
    local-address-assignment
        network-realm "realm-01"
            pool "pool-01"
                ipv4
                    default-gateway first-address
                    micro-net-length 24
                    prefix 192.168.0.0/16
                exit
                ipv6
                    pd
                        micro-net-length 48
                        prefix 2001::/37
                        prefix 192.168.2.0/24
                    exit
                exit
            exit
        exit
    exit
----------------------------------------------

Configure a network realm for the APN.

Configure the network realm for the APN to match the service name of the IES or VPRN service used to host the subscriber session on the BNG-UP. See Service selection for more information about network-realm configuration.

Network-realm configuration for the APN

A:MAG-c>config>mobile>pdn# info
----------------------------------------------
        apn "apn-01"
            network-realm "realm-01"
        no shutdown
----------------------------------------------

For FWA sessions, provision the APN in the UP peer list created in step 3, for the BNG-UPs that can provide service for this APN. The following example shows this configuration.

APN configuration in the UP peer list for FWA sessions

A:MAG-c>config>mobile>profile>pfcp# info
----------------------------------------------
                up-peer-list "ups"
                    peer 192.168.50.84
                        apn “apn-01”
                        exit
                    exit
                    peer 192.168.50.83
                        apn “apn-01”
                        exit
                    exit
                    peer 192.168.50.82
                        apn “apn-01”
                        exit
                    exit
                exit
----------------------------------------------

Configure the ADB.

The ADB configuration determines the authentication process and address assignment method, and also retrieves attributes associated with the subscriber session. The following example uses the ADB to provide the address assignment and the subscriber and SLA profiles for the subscriber session. The address pool refers to the local-address assignment configured in step 5. See Authentication database for more information.

ADB configuration

A:MAG-c>config>mobile>profile# info
----------------------------------------------
    authentication-database "auth-db-01"
        match 1 attribute username
            optional
        exit
        entry "default"
            address-assignment
                local-dynamic
                    ipv4-pool "pool-01"
            apn "apn-01"
            ip-anti-spoof true
            subscriber-mgmt
                sla-profile "cup-prof"
                sub-profile "cup-prof"
            exit
            no shutdown
        exit
        no shutdown
    exit
----------------------------------------------

Configure a fixed-access or FWA session.
- For fixed-access sessions, configure the BNG entry point.
  The BNG entry point informs the MAG-c about the authentication flow and other aspects of fixed-subscriber session management and setup. See BNG entry point for more information. The following example shows a simple configuration that refers to the ADB configured in step 7.
BNG entry point configuration
```
A:MAG-c>config>mobile>profile#
----------------------------------------------
    bng
        entry-point "bng-entry-01"
            match 1 attribute up-ip
                optional
            exit
            entry "1"
                ipoe
                    authentication-flow
                    adb "auth-db-01"
                exit
            exit
        match
            up-ip 192.168.50.84
        exit
        no shutdown
        exit
        no shutdown
        exit
    exit
----------------------------------------------
```
- For FWA sessions, configure the incoming APN/DNN, according to the GTP Session Establishment Request (4G) or Nsmf_PDUSession_CreateSMContextRequest (5G) messages. This APN informs the MAG-c about the authentication flow used for FWA sessions. The following example shows a simple configuration that refers to the ADB configured in step 7.
  Note: If the incoming APN and service APN are the same, it is not necessary to provide the APN via the ADB.
FWA incoming APN configuration
```
A:MAG-c>config>mobile>pdn#
----------------------------------------------
            apn "fwa.mnc01.mcc001.gprs"
                fixed-wireless-access
                    authentication-flow
                        adb "auth-db-01"
                    exit
                    no shutdown
                exit
                no shutdown
            exit
----------------------------------------------
```

Configuring Service Based Interfaces

These quick-start instructions provide the basic steps required to configure the MAG-c to support Service Based Interfaces (SBI) communication, with references to additional topics for users who want more information.

Configure the MAG-c for basic session management; for more information, see the Configuring MAG-c quick start topic.
Administratively disable the MAG-c PDN configuration using the following command.
```
configure mobile-gateway pdn shutdown
```

This procedure describes the minimal configuration required to set up SBI communication for a MAG-c. This includes setting up the MAG-c as an SMF SBI server and as an SBI client toward the NRF, AMF, UDM, PCF, and CHF peer network functions (NFs). This configuration assumes an NRF is used to discover any NFs and is used by the NFs to discover the MAG-c.

Configure an interface that is used for communication to SBI services.
The following example shows a single interface that is used throughout this quick-start procedure for all SBI services, but it is possible to specify a different interface for each service.
Interface for SBI communication
```
A:MAG-c>config>mobile>pdn# /configure router interface "to_sbi"
A:MAG-c>config>router>if# info
----------------------------------------------
            address 192.0.2.1/24
            port 1/1/1
            ipv6
                address 2001:db8:1:1::1/64
            exit
            no shutdown
----------------------------------------------
```

Configure the NF instance ID that the MAG-c uses to identify itself toward other NFs, and the slices that the MAG-c is serving.

The following example uses a randomly generated universally unique ID (UUID) as NF instance ID. Nokia recommends that you should generate a new and unique UUID when configuring a new system. See NF registration for more information about these parameters.

MAG-c NF instance ID and slice configuration

A:MAG-c>config>mobile>profile>list# info
----------------------------------------------
                slice-instance-list "fwa_inst"
                    slice-instance "fwa_inst"
                exit
                slice-list "fwa_slices"
                    slice "fwa_slice" sst 1 sd 000001
                        slice-instances fwa_inst
                    exit
                exit
----------------------------------------------
A:MAG-c>config>mobile>pdn# info
----------------------------------------------
            slices
                slice-list "fwa_slices"
            exit
            nf-profile-attributes
                nf-instance-id "ce23c7c3-b710-49ac-9e3c-764849a012fa"
            exit
----------------------------------------------

Configure the SMF SBI server service to allow the setup of 5G FWA sessions.
In the following example:
- the MAG-c communicates with the AMF using the common "to_sbi" interface
- the FWA-UP terminates GTP-u traffic using the "to_ran" service. This matches the service used on the S11 and S5 interface as described in Configuring MAG-c.
Note: For more information about 5G Session management and the SMF service, see 5G standalone sessions.
SMF server configuration
```
A:MAG-c>config>mobile>pdn>sba-server-services# info
----------------------------------------------
                    nsmf-pdusession "fwa_smf"
                        n3-interface-realm "to_ran"
                        interface "to_sbi" port 80
                    exit
----------------------------------------
```

Configure the NRF SBI client to allow the MAG-c to register itself with the NRF as an SMF NF, and discover other peer NFs.

The following example configures the MAG-c with a single NRF identified by the configured UUID, listening on a single IP. The NRF is the only SBI NF that always requires local configuration. Other NFs can subsequently be discovered through the NRF. See NF peer discovery for more information.

The configuration of the example allows the MAG-c to automatically register itself with the NRF as an SMF using the provided UUID and any configured APNs. For more information about registration parameters and their provisioning, see NF registration.

NRF client configuration

A:MAG-c>config>mobile>profile>list# info
----------------------------------------------
                prioritized-ip-address-list "nrfs"
                    address 192.168.40.1
                exit
                nf-id-list "nrfs"
                    nf-prof-id 1
                        prioritized-address-list "nrfs"
                        uuid AB61220B-F589-40D4-978B-D9C9F5AB742E
                        enable
                    exit
                exit
A:MAG-c>config>mobile>pdn>sba-client-services>nrf-client# info
----------------------------------------------
                    nnrf-nfm "nrf_client"
                        nf-id-list "nrfs"
                        interface "to_sbi"
                    exit
                    nnrf-disc "nrf_disc_client"
                        nf-id-list "nrfs"
                        interface "to_sbi"
                    exit
----------------------------------------------

Configure the SBI client for all other required SBI services.

The following example shows SBI client configuration for AMF, UDM, PCF, and CHF services using SBI-based discovery. For more information about each service, see the following topics:

AMF: AMF client communication service configuration
UDM: UDM function configuration
PCF: PCF-based policy management
CHF: CHF charging

AMF, UDM, PCF, and CHF client configuration

A:MAG-c>config>mobile>pdn>sba-client-services# info
----------------------------------------------
                amf-client
                    namf-comm "amf_comm_client"
                        interface "to_sbi"
                    exit
                exit
                chf-client
                    nchf-convergedcharging "chf_client"
                        interface "to_sbi"
                    exit
                exit
                pcf-client
                    npcf-smpolicycontrol "pcf_client"
                        interface "to_sbi"
                    exit
                exit
                udm-client
                    nudm-sdm "sdm_client"
                        interface "to_sbi"
                    exit
                    nudm-uecm "uecm_client"
                        interface "to_sbi"
                    exit
                exit
----------------------------------------------

Configure a service realm and add all SBI server and client services to enable all services.

SBA service realm configuration

A:MAG-c>config>mobile>pdn# info
            sba-service-realm "fwa_realm"
                server-service nsmf-pdusession service-instance "fwa_smf"
                client-service nnrf-nfm service-instance "nrf_client"
                client-service nnrf-disc service-instance "nrf_disc_client"
                client-service namf-comm service-instance "amf_comm_client"
                client-service npcf-smpolicycontrol service-instance "pcf_client"
                client-service nudm-sdm service-instance "sdm_client"
                client-service nudm-uecm service-instance "uecm_client"
                client-service nchf-convergedcharging service-instance "chf_client"
            exit

Enable the PDN to start using the SBI services.
```
configure mobile-gateway pdn no shutdown
```