Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Install Juniper BNG CUPS

SUMMARY This section describes installation procedures and system requirements for Juniper BNG CUPS.

Juniper BNG CUPS disaggregates the broadband network gateway (BNG) function running in Junos OS into separate control plane and user plane components. The control plane is a cloud-native application that runs in a Kubernetes environment. The user plane component continues to run on Junos OS on a dedicated hardware platform.

The installation instructions in this guide are for the disaggregated control plane component of the Juniper BNG CUPS solution. In the Juniper BNG CUPS solution, the control plane is referred to as Juniper BNG CUPS Controller (BNG CUPS Controller). The BNG CUPS Controller component requires a multi-node Kubernetes cluster.

Before You Begin

Before you begin installing and running BNG CUPS Controller, make sure you have the following:

  • A juniper.net user account with permissions to download the Juniper BNG CUPS software package.

  • A Linux host (jump host) running Ubuntu 22.04 LTS (or later) required for running the junos-bng-cups-controller installation. The jump host must have the following resources allocated to it:

    • CPU cores—2

    • RAM—8 GB

    • Disk space—128 GB of free disk storage

  • The cluster must have at least three worker nodes (either virtual or physical machines). A node is a Linux system running Ubuntu 22.04 LTS (or later) that has a management address and a domain name. The nodes must meet the following system requirements:

    • CPU cores—8 (hyperthreading preferred)

    • RAM—64 GB

    • Disk space—512 GB of free disk storage in the root partition

      We recommend that you partition your disk storage accordingly:

      • 128 GB to the root (/) partition for the operating system

      • 128 GB to /var/lib/docker for the Docker cache

      • 256 GB to /mnt/longhorn for the application data. This is the default location, you can specify a different location during configuration.

    • All cluster nodes must have a user account with sudo access.

    • You must have root-level SSH access from the jump host, using key-based authentication, to all nodes.

To use Juniper BNG CUPS, you must purchase a license for both the Juniper BNG CUPS Controller (control plane) and the Juniper BNG User Planes (user planes) associated to the Juniper BNG CUPS Controller. For information about how to purchase a software license, contact your Juniper Networks sales representative at https://www.juniper.net/in/en/contact-us/.

The MX Series devices that you are using in your Juniper BNG CUPS environment also require their own separate licenses. For information about how to purchase hardware, contact your Juniper Networks sales representative at https://www.juniper.net/in/en/contact-us/.

Install Juniper BNG CUPS Controller

SUMMARY Use this procedure to install Juniper BNG CUPS Controller.

Before you begin, confirm that you have met the requirements for the BNG CUPS Controller installation.

Note:

See the BBE Cloudsetup Installation Guide for instructions on installing the BBE Cloudsetup facility and building the Kubernetes cluster. Use the dbng setup [--bbecloudsetup] to install and to build your cluster. All the defaults align with BBE Cloudsetup if you use the bbecloudsetup option. If you don't use the bbecloudsetup option with setup, then you need to have the following information when you start the BNG CUPS Controller installation:

  • Kubernetes registry location
  • Registry name
  • Registry port
  • Syslog server/BBE Event Collection and Visualization address and syslog server port

Install the BNG CUPS Controller Application

  1. Download the Juniper BNG CUPS software package from Juniper Networks software download page, and save it to the jump host.

    BNG CUPS Controller is available as a compressed tarball image (.tgz). The filename includes the release number as part of the name. The release number has the format:m.nZb.s

    For example, the software release number 23.4R1.5 maps to the following format:

    • m is the main release number of the product (for example, 23).

    • n is the minor release number of the product (for example, 4).

    • Z is the type of software release (for example, R for FRS or maintenance release).

    • b is the build number of the product (for example, 1, indicating the FRS release, rather than a maintenance release).

    • s is the spin number of the product (for example, 5).

  2. Unpack the BNG CUPS Controller tarball (.tgz) file on the jump host by entering:
  3. Run the loader script after you unpack the tarball.
  4. Use the sudo -E dbng link --context context-name --version software-release command to link to the cluster. The link command associates the loaded BNG CUPS Controller software package to the cluster in preparation for the setup.

    • context context-name—The Kubernetes context name.

    • version software-release—The BNG CUPS Controller software version, as displayed from the bng_loader output.

  5. If you are using a secure registry (as would be created on a BBE Cloudsetup created cluster), authenticate with the registry by issuing a docker login as the system user (the system user supplied in the BBE Cloudsetup configuration file) to the cluster's registry transport address (the FQDN supplied as the system address in the BBE Cloudsetup configuration file).
  6. Run dbng setup to configure your installation.

    • context context-name—The Kubernetes context name.

    • update—You will only be prompted for missing values during setup.

    • bbecloudsetup—Uses the default values used when BBE Cloudsetup created the Kubernetes cluster.

    • ssh host:port—A hostname or IP address of the cluster (any of the cluster’s nodes) and open port used for SSH access to the CLI.

    The setup command does the following:

    • Collects information about the cluster environment such as; Names of storage class or persistent volumes, location of a container registry, container/pod name of registry, any TLS key information, and so on.

    • Initializes the BNG CUPS Controller configuration.

      If you did not use the bbecloudsetup option with the setup command, you need to complete these prompts during the setup:

      • Docker registry address and port number

      • CPi Config storage class name and size

      • CPi Core storage class name and size

      • Scache Core storage size

  7. Verify the BNG CUPS Controller installation by running the dbng version command.

    • context context-name—The Kubernetes context name.

    • detail—Displays all available software versions.

Start BNG CUPS Controller

SUMMARY Use this procedure to configure and to start BNG CUPS Controller.

  1. Enter rollout to start the BNG CUPS Controller installation. The BNG CUPS Controller utility allows you to roll out different software versions for all microservices that are part of BNG CUPS Controller. You need to use the rollout command with sudo as root. The rollout command also validates that all the values needed for the new releases are present and loads the new release container images to the registry. Use sudo -E dbng rollout --context context-name --version software-release --service service-name to start BNG CUPS Controller services. For example:

    • context-name—The Kubernetes context.

    • service service-name—The microservice name to rollout (for example, scache and cpi-).

    • version software-release—The software release to rollout (defaults to the release that links to the cluster).

    Note:

    On the first rollout -–service is not required. The -–service is used with the –-version to rollout (upgrade) specific versions of specific services.
    Note:

    By default, BNG CUPS Controller starts from factory-default. The configuration is reset to its initial state. Any persistent state and any persistent logs are cleared.

  2. Enter dbng status --detail --context context-name to verify that the BNG CUPS Controller services are up and running. For example:
    Note:

    Collect the logs for a service and contact the Juniper Networks Technical Assistance Center (JTAC) when either of the following occurs:

    • The service is not running.

    • The service’s uptime compared with other services indicates that it has restarted.
  3. You must add a control plane instance (CPi) to your BNG CUPS Controller. Run the CPi add command.

    • context context-name—The Kubernetes context name. Enter the name of the context.

    • version software-release—The software release for the new CPi pod. Enter a release.

    • cpi-label—Specify a label that is used for CPi commands.

  4. Verify that the CPi micro service is running, by using the dbng status command.

    • context context-name—The Kubernetes context name.

    • detail—Displays detailed information.

Install a BNG User Plane

The BNG User Planes that you use as part of Juniper BNG CUPS are the MX Series routers that you have installed in your network. BNG User Planes (MX Series routers) run Junos OS. If you need to install a BNG User Plane, see the following: Junos® OS Software Installation and Upgrade Guide.