CUPS UP configuration quick start

For a CUPS deployment scenario, configure the CUPS user plane (UP) for subscriber management using fixed access or fixed wireless access (FWA) sessions, in conjunction with the MAG-c control plane (CP).

See the following for information about the configuration tasks:

Configuration overview provides a summary of the CUPS UP configuration tasks.
The MAG-c Control Plane Function Guide provides information about configuring the MAG-c CP.

Configuration overview

The following table lists the main tasks required to configure the CUPS UP for subscriber management.

Table 1. Tasks for configuring the CUPS UP
Configuration component	Configuration task
Configure the basic system components, including cards, ports, users, and configuration modes.	See the following guides: 7450 ESS, 7750 SR, 7950 XRS, and VSR Basic System Configuration Guide 7450 ESS, 7750 SR, 7950 XRS, and VSR Interface Configuration Guide
Configure the IP connectivity from the CUPS UP to the MAG-c.	See Configuring the CUPS UP for subscriber management, step 1.
Configure the PFCP association.	See Configuring the CUPS UP for subscriber management, step 2.
Configure the fixed access or FWA services.	See Configuring the CUPS UP for subscriber management, step 3.
Configure the network services.	See Configuring the CUPS UP for subscriber management, step 4.
Configure the profiles and templates for subscribers, SLAs, SAPs, and group interfaces.	See Configuring the CUPS UP for subscriber management, step 5.

Configuring the CUPS UP for subscriber management

Ensure the basic system components are configured, including the cards, ports, users, and configuration modes. See the 7450 ESS, 7750 SR, 7950 XRS, and VSR Basic System Configuration Guide.
Familiarize yourself with the steps and examples for configuring IP connectivity in the base router and VPRNs. See the 7450 ESS, 7750 SR, 7950 XRS, and VSR Interface Configuration Guide for more information.
Familiarize yourself with the steps and examples for configuring the MAG-c CP. See the MAG-c Control Plane Function Guide for more information.

To configure the CUPS UP for subscriber management (in conjunction with the MAG-c CP), using fixed access or FWA sessions, you must configure IP connectivity, PFCP association, access and network services, subscriber and SLA profiles, and SAP and group interface templates.

Perform all the steps in the order specified. These steps include links to additional topics, if applicable, for users who require more detailed information.

Configure IP connectivity to the MAG-c function.

The CUPS UP requires an interface (preferably a loopback interface), in the base router instance or a VPRN, to terminate and originate PFCP traffic with the MAG-c.

The following example displays a loopback interface named "pfcp_endpoint" in the base router configuration that uses the IPv4 address 192.0.2.1 for PFCP communication.
Loopback interface configuration with IPv4 address for PFCP communication
```
[ex:/configure router "Base"]
A:admin@UP-West# info
    interface "pfcp_endpoint" {
        loopback
        ipv4 {
            primary {
                address 192.0.2.1
                prefix-length 32
            }
        }
    }
```
Configure the PFCP association.

The PFCP association manages all communication-related subscriber states between the UP and the CP.

The following example displays the connection to a MAG-c listening on IP 1.1.1.1, using the interface configured in step 1. The node-id command is configured to identify this UP on the MAG-c.

See PFCP association for more information about the PFCP configuration.
PFCP association configuration for connection to the MAG-c
```
[ex:/configure subscriber-mgmt pfcp association "MAG-c"]
A:admin@UP-West# info
    admin-state enable
    node-id {
        fqdn "up-west"
    }
    interface {
        router-instance "Base"
        name "pfcp_endpoint"
    }
    peer {
        ip-address 1.1.1.1
    }
```
Configure the access services.
- Fixed access sessions
  The access service is a VPLS with capture SAPs configured for the port, and the VLAN contexts in which subscribers are terminated.
  See Fixed access sessions for more information.
- FWA sessions
  The access service is a VPRN or the base router. In the VPRN, an interface (preferably a loopback interface) terminates GTP-u traffic. GTP-u traffic is sent with a source IP address of this interface, and follows regular routing. You must also configure a forwarding path extensions (FPE) construct in the same access service to terminate FWA subscribers.
  See Fixed wireless access sessions for more information.
Access services configuration for a fixed access session
This example displays the following configurations:
- A single capture SAP terminates subscribers on port 1/1/c1/1.
- The capture SAP uses wildcards for the S‑tag and C‑tag to allow any S‑tag and C‑tag.
- To start CUPS functionality and avoid treating the sessions like integrated BNG sessions, the capture SAP is linked to the PFCP association created in step 2 .
- The trigger-packet configuration determines which packet is sent to the CP for initial session setup.
```
[ex:/configure service vpls "fixed_access"]
A:admin@UP-West# info
    admin-state enable
    customer "1"
    capture-sap 1/1/c1/1:*.* {
        pfcp {
            association "MAG-c"
        }
        trigger-packet {
            dhcp true
            dhcp6 true
            pppoe true
            rtr-solicit true
        }
    }
```
Access services configuration for an FWA session
This example displays the following configurations:
- GTP-u traffic terminates on an FPE linked to an internal PXC on MAC 1 and MAC 4 of card and MDA 1/1.
- Listening is configured on IPv4 172.20.1.2 or IPv6 2001:db8:2020::2 in a VPRN named "to_ran".
Other VPRN configurations, such as the interfaces to the RAN network, are not shown.
Note: The UP automatically balances FWA sessions over both PXCs.
See the 7450 ESS, 7750 SR, 7950 XRS, and VSR Interface Configuration Guide for more information about the following topics:
- See "Port cross-connect", for information about how to configure port cross-connects.
- See "FPE", for information about configuring FPEs.
```
[ex:/configure card 1 mda 1]
A:admin@UP-West# info
    xconnect {
        mac 1 {
            loopback 1 {
            }
        }
        mac 4 {
            loopback 1 {
            }
        }
    }

[ex:/configure port 1/1/m1/1]
A:admin@UP-West# info
    admin-state enable

[ex:/configure port 1/1/m4/1]
A:admin@UP-West# info
    admin-state enable

[ex:/configure port-xc]
A:admin@UP-West# info
    pxc 1 {
        admin-state enable
        port-id 1/1/m1/1
    }
    pxc 2 {
        admin-state enable
        port-id 1/1/m4/1
    }

[ex:/configure fwd-path-ext fpe 1]
A:admin@UP-West# info
    multi-path {
        path 1 {
            pxc 1
        }
        path 2 {
            pxc 2
        }
    }
    application {
        sub-mgmt-extension true
    } 

[ex:/configure service vprn "to_ran"] 
A:admin@UP-West# info
    gtp {
        upf-data-endpoint {
            interface "gtp_u_endpoint"
            fpe 1
        }
    }
    interface "gtp_u_endpoint" {
        loopback true
        ipv4 {
            primary {
                address 172.20.1.2
                prefix-length 32
            }
        }
        ipv6 {
            address 2001:db8:2020::2 {
                prefix-length 128
            }
        }
    }
```
Configure the network services.
Fixed access and FWA sessions use IES or VPRN services to provide VPRN connectivity. You do not require a specific subscriber-management configuration; the service must only exist and be referenced by the MAG-c when installing the session.

See IP gateway, services, and routing for more information about how to use these services.
Configure default profiles.
CUPS sessions require the following explicitly-configured profiles and templates:
- SLA profiles
- subscriber profiles
- SAP templates
- group‑interface templates
If the CP does not specify values for these profiles or templates, the UP automatically uses any profile or template configured with the name “default”. The following example displays default configuration settings for these profiles and templates.
See SAP and group interface templates and Subscribers, QoS, and filters for more information.
Note: The default SLA and subscriber profiles provide the minimal functionality to set up a subscriber. For actual deployments, tailor these profiles to the required use cases. See Overview of dynamic QoS based on PCC rules for information about profile configurations for FWA sessions with dynamic PCC rules.
Configuration of SLA and subscriber profiles and SAP and group-interface templates
```
[ex:/configure subscriber-mgmt]
A:admin@UP-West# info
    group-interface-template "default" {
    }
    sap-template "default" {
    }
    sub-profile "default" {
        control {
            cups true
        }
    }
    sla-profile "default" {
        control {
            cups true
        }
    }
```