Install Juniper BNG CUPS
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 Kubernetes cluster that consists of multiple nodes.
The BNG CUPS Controller can be installed on a single Kubernetes cluster or on a multiple geographical, multiple cluster setup. The installation requirements and installation process for these two types of setups are different. See the followings sections for your BNG CUPS Controller setup:
BNG CUPS Controller Installation Requirements
To install BNG CUPS Controller, you need the hardware and software requirements listed in this section.
- BNG CUPS Controller Requirements for a Single Geographically Located Setup
- BNG CUPS Controller Requirements for a Multiple Geographically Located Setup
- Additional Requirements
BNG CUPS Controller Requirements for a Single Geographically Located Setup
BNG CUPS Controller installs on a Kubernetes cluster that consists of physical or virtual machines. For availability, you must have at least three nodes in the cluster.
BNG CUPS Controller requires the minimal resources listed in Table 1, from the Kubernetes cluster.
Category | Details |
---|---|
Jump host |
The jump host must be running Ubuntu version 22.04 LTS or
later and have the following resources allocated to it:
If you are using a Red Hat OpenShift Container Platform cluster, you must have the OpenShift CLI installed. |
Node specification (minimum of 3 nodes) | A node is a Linux system (either virtual or physical system)
that has a management address and a domain name. The nodes must
meet the following requirements:
Note:
To create the cluster, you can use either of the following applications:
|
BNG CUPS Controller Requirements for a Multiple Geographically Located Setup
A geographically redundant, multiple cluster BNG CUPS Controller setup consists of three separate Kubernetes clusters. Each of the three clusters is geographically separated, so that service impacting events affecting one cluster do not affect the other clusters. The clusters which comprise the multiple cluster setup take on specific roles.
One cluster takes on the role of the management cluster and the other two clusters take on the role of workload clusters. The workload clusters provided a redundant platform where most of BNG CUPS Controller application runs. The management cluster runs software that monitors the health of the workload clusters and determines whether BNG CUPS Controller should switchover from one workload cluster to the other.
Each Kubernetes cluster in the multiple cluster consists of physical or virtual machines (VMs).
BNG CUPS Controller requires the minimal resources listed in Table 1, from the Kubernetes cluster.
Category | Details |
---|---|
Jump host—The jump host must have connectivity to the management and workload clusters. |
The jump host must be running Ubuntu version 22.04 LTS or later and have the following resources allocated to it:
|
Management Cluster—The management cluster requires the following:
|
A node is a Linux system (either virtual or physical system) that has a management address and a domain name. The hybrid nodes must meet the following requirements:
|
Workload Cluster—Two workload clusters are required (primary and backup). The workload cluster requires the following:
|
A node is a Linux system (either virtual or physical system) that has a management address and a domain name. The hybrid nodes must meet the following requirements:
|
In a single geography BNG CUPS Controller setup, you can make some basic assumptions about the cluster's parameters, therefore you can use a quick start tool like BBE Cloudsetup. But the construction of a production environment BNG CUPS Controller setup with multiple geographies and multiple clusters requires much more input from you to build.
We recommend that you use Rancher's RKE2 distribution for building the clusters that will be part of the multiple cluster setup. Also, Kubernetes 1.28.6 or later is required.
Additional Requirements
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/.
Confirm that you have a juniper.net user account with permissions to download the BNG CUPS Controller software package. Download and install the BNG CUPS Controller software from a machine that will not be part of the Kubernetes cluster.
Install a Single Geographically Located Juniper BNG CUPS Controller
Use the procedures in this section to install a single geographically located Juniper BNG CUPS Controller for the first time.
Before you begin, confirm that you have met the requirements for the BNG CUPS Controller installation (see Table 1).
You have the following two options for creating the Kubernetes cluster that you can install BNG CUPS Controller on:
-
BBE Cloudsetup—For installation instructions, see BBE Cloudsetup Installation Guide.
Note:BBE Cloudsetup is a utility that you can use to quickly get started with using BNG CUPS Controller. It is not a life cycle tool for the cluster. You cannot expand the width of the cluster, perform node maintenance, upgrade infrastructure components, and so on. A Kubernetes cluster for production purposes should be designed and constructed with the requirements of the production environment and with appropriate support to maintain its life cycle.
-
Red Hat OpenShift Container Platform—For installation instructions, see the Red Hat OpenShift Container Platform documentation.
Before starting the BNG CUPS Controller installation, make sure that you have the following information:
- Container registry details:
-
If you are using a BBE Cloudsetup created cluster:
-
External registry address
-
External registry port number (usually 5000)
-
-
If you are using a Red Hat OpenShift Container Platform cluster:
-
External registry (FQDN)
-
Internal (Docker) registry address
-
Internal (Docker) registry port number
-
-
- Syslog server details—Syslog server information is required if you are
planning to export BGN CUPS Controller logs to an external syslog collector.
Note:
If BBE Event Collection and Visualization is detected running on the target cluster, the address and port values of the ECAV deployment will be suggested as the default.
-
Syslog server address
-
Syslog server port number
-
Install the BNG CUPS Controller Application (single).
Start BNG CUPS Controller in a Single Geographically Located Setup
Use this procedure to configure and to start BNG CUPS Controller in a single geographically located setup.
Install Juniper BNG CUPS Controller in a Multiple Geographically Located Setup
Use the installation procedures in this section for a BNG CUPS Controller setup that consists of multiple BNG CUPS Controllers that are located in different geographical locations.
Before you begin, confirm that you have met the requirements for the BNG CUPS Controller installation (see Table 2).
Before starting the BNG CUPS Controller installation, make sure that you have the following information:
You must collect the information listed below for all three clusters.
-
The cluster context names of the workload clusters, the management cluster's karmada context and the management cluster's working context
-
Karmada kubeconfig secret name—The name of the secret used to interface with the Karmada context's REST API
- Container registry details for each cluster:
-
External registry address
-
External registry port number (usually 5000)
-
- Syslog server details—Syslog server information is required if you are
planning to export BGN CUPS Controller logs to an external syslog collector.
Note:
If BBE Event Collection and Visualization is detected running on the target cluster, the address and port values of the ECAV deployment will be suggested as the default.
-
Syslog server address
-
Syslog server port number
-
Install the BNG CUPS Controller Application (multiple geographically located setup).
Start BNG CUPS Controller in a Multiple Geographically Located Setup
Use this procedure to configure and to start BNG CUPS Controller in a multiple geographically located setup.
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 Junos® OS Software Installation and Upgrade Guide.