cMAG-c configuration quick start

The quick start steps configure the main components required to prepare the cMAG-c for subscriber management.

Configuring cMAG-c for subscriber management

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

Configuration overview

The cMAG-c basic configuration for subscriber management requires specific configuration tasks to be completed in a particular order.

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

Table 1. cMAG-c configuration components and quick-start steps
Configuration component	Configuration task
Configure a system name.	Step 1
Configure PFCP connectivity between the cMAG-c and MAG-u.	Step 2
Configure a service and network instance.	Step 3
Configure a local address pool for IP address assignment within the network instance.	Step 4
Configure the authentication database (ADB).	Step 5
Configure the entry point.	Step 6
Configure IBCP to terminate fixed access sessions.	Step 7

Configuring cMAG-c

These quick-start instructions provide the basic steps required to configure the cMAG-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 MAG-u; see Service selection.
Ensure the MAG-u is configured; see "PFCP association" and "Session management" in the 7750 SR and VSR BNG CUPS User Plane Function Guide for more information.

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

Optional: Configure a cMAG-c system name.
The cMAG-c system name is used as the hostname for the CLI session prompt and as the default value for any protocol that reflects a system identifier; for example, the NAS ID in RADIUS and the node ID in PFCP. Nokia recommends selecting a system name that is concise and adheres to the FQDN encoding rules.
System name configuration
```
# info from running /subscriber-management system-name
    subscriber-management {
        system-name cmag-c
    }
```

Configure PFCP connectivity between the cMAG-c and MAG-u.

The following example shows a cMAG-c connected to a MAG-u with node ID mag-u and IP 192.0.2.11.

PFCP connectivity between the cMAG-c and MAG-u

# info from running /subscriber-management ref-points up
    subscriber-management {
        ref-points {
            up {
                peer mag-u {
                    admin-state enable
                    address-resolution {
                        static-ip [
                            192.0.2.11
                        ]
                    }
                }
            }
        }
    }

Configure a service and network instance.
Sessions are assigned to a service, which maps to a network instance. A service is a generic concept describing the type of service a session receives; for example, high speed Internet, video, or voice. A network instance maps to a routing context on the UP. See Service selection for more information about network instance configuration.
Network instance configuration for the service
```
# info from running /subscriber-management services
    subscriber-management {
        services {
            network-instance hsi {
            }
            service hsi {
                network-instance hsi
            }
        }
    }
```

Configure a local address pool for IP address assignment within the network instance.

The following example shows a simple address pool configuration that uses the prefix 192.0.2.0/24 for IPv4 address assignment and 2001:db8:b00::/40 for IPv6 PD prefix assignment. Other methods can be used. See Local address assignment for more information about IP address assignment.

Local address pool configuration for IP address assignment

# info from running /subscriber-management services network-instance hsi pool hsi
    subscriber-management {
        services {
            network-instance hsi {
                pool hsi {
                    hold-time 300
                    ipv4 {
                        micro-net-length 28
                        prefix 192.0.2.0/24 {
                        }
                    }
                    ipv6 {
                        na {
                            micro-net-length 120
                            prefix 2001:db8:a00::/116 {
                            }
                        }
                        pd {
                            micro-net {
                                length 48
                            }
                            prefix 2001:db8:b00::/40 {
                            }
                        }
                        slaac {
                            micro-net-length 56
                            prefix 2001:db8:c00::/48 {
                            }
                        }
                    }
                }
            }
        }
    }

Configure the ADB.

The ADB configuration determines the authentication process and address assignment method, and 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 4. See Authentication database for more information.

ADB configuration

# info from running /subscriber-management authentication-database basic-adb
    subscriber-management {
        authentication-database basic-adb {
            admin-state enable
            match 1 {
                attribute c-vlan
                optional true
            }
            entry default {
                admin-state enable
                service-name hsi
                ip-anti-spoof true
                action {
                    accept
                }
                up-parameters {
                    sla-profile default
                    sub-profile default
                }
                address-assignment {
                    local-dynamic {
                        ipv4-pool hsi
                        ipv6-pd-pool hsi
                        ipv6-na-pool hsi
                    }
                }
            }
        }
    }

Configure the entry point.

The entry point informs the cMAG-c about the authentication flow and other aspects of 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 5.

Entry point configuration

# info from running /subscriber-management entry-point fixed-access
    subscriber-management {
        entry-point fixed-access {
            admin-state enable
            match 1 {
                attribute up-node-id
                optional true
            }
            entry default {
                admin-state enable
                ipoe {
                    authentication-flow {
                        authentication-database [
                            basic-adb
                        ]
                    }
                }
            }
        }
    }

Configure IBCP to terminate fixed access sessions.
For fixed access sessions, configure IBCP to allow tunneling of control plane messages.
The default IBCP tunnel supports tunneling of control packets from the MAG-u to the cMAG-c. The following example configures IBCP to terminate dual stack IPoE sessions. See In-band control plane and MAG-u selection for more information about IBCP.
Configuration for the IBCP tunnel
```
# info from running /subscriber-management ref-points up fixed-access
    subscriber-management {
        ref-points {
            up {
                fixed-access {
                    entry-point fixed-access
                    ibcp-triggers {
                        pppoe-discover true
                        ipoe-dhcp true
                        ipoe-dhcpv6 true
                        ipoe-router-solicit true
                    }
                }
            }
        }
    }
```