I-Juniper NETWORKS 3.4.0 I-Juniper Address Pool Manager User Guide

Juniper Address Pool Manager (APM) is a cloud-native, container-based application running on a Kubernetes cluster that manages address pools in a network.
APM monitors the IPv4 address pools on broadband network gateways (BNGs) in the network.

When the free address utilization drops below a specified threshold on a BNG, APM adds unused prefixes from a centralized pool to the BNG’s address pool.
APM, in cooperation with the BNG, monitors and links address pools in support of dynamic address allocation mechanisms for subscribers.

Izinzuzo ze-APM zimi kanje:

Ithuthukisa ukusebenza kahle kokusetshenziswa kwamakheli

Yehlisa i-overhead nobunkimbinkimbi bokuqapha nokuhlinzeka ngokwenza ukuqapha nokuhlinzeka ngokuzenzakalelayo.
Ivumela ukubizwa kabusha kweziqalo ezingasetshenziswa kancane ukuze kusatshalaliswe kabusha kumachibi azidingayo.
Enables APM to work with the BNG CUPS Controller.
These release notes accompany Juniper Address Pool Manager Release 3.4.0

Ukufakwa

Address Pool manager 3.4.0 installation requires the minimum system requirements listed in this section.
QAPHELA: The system requirements listed in Table 1 on page 2 are for a single geographically located installation of Address Pool Manager (APM).
For the system requirements of a multiple geographically located, multiple cluster setup, see Address Pool Manager Installation Guide.
APM installs on a Kubernetes cluster comprised of physical or virtual machines (VMs).
APM has been qualified against the single geographical cluster described in Table 1.
For information on how to install APM, see Address Pool Manager Installation Guide.

Table 1: Single Geographical Cluster Specifications

Isigaba

Imininingwane

Iqoqo

A single cluster with 3 hybrid nodes.

Kubernetes node

The Kubernetes nodes require the following:

• For the operating system, you can use either of the following:

• Ubuntu 22.04 LTS (for a BBE Cloud setup cluster)

• Red Hat Enterprise Linux CoreOS (RHCOS) 4.15 or later (for an OpenShift Container Platform cluster)

• CPU: 8 or 16 cores.

Use a 16-core node if you plan on running other applications on the cluster (such as the BNG CUPS Controller application).

• Memory: 64 GB

• Storage: 512 GB storage partitioned as 128 GB root (/), 128 GB /var/lib/docker, and 256 GB /mnt/ longhorn(application data

• Kubernetes role: Control plane etcd function and worker node

This specification establishes a cluster that can run APM as well as its companion applications, such as BBE Event Collection and Visualization, and BNG CUPS Controller simultaneously.

Isigaba

Imininingwane

Yeqa umsingathi

The jump host requires the following:

• Operating system: Ubuntu version 22.04 LTS or later

• CPU: 2-core

• Memory: 8 gigabytes (GiB)

• Storage: 128 gigabytes (GiB)

• Installed software:

• Python3-venv

• Helm utility

• Docker utility

• OpenShift CLI. Required if you are using a Red Hat OpenShift Container Platform cluster.

Cluster software

The cluster requires the following software:

• RKE version 1.3.15 (Kubernetes 1.24.4)— Kubernetes distribution

• MetalLB version 0.13.7—Network load balancer

• Keepalived version 2.2.8—Kubelet HA VIP Controller

• Longhorn version 1.2.6—CSI

• Flannel version 0.15.1—CNI

• Registry version 2.8.1—Container registry

• OpenShift version 4.15+—Kubernetes Distribution for RHOCP. Uses compatible versions of Longhorn (CSI), MetalLB, OVN (CNI), and OpenShift Image Registry

Isigaba	Imininingwane
Jump host software	The jump host requires the following software: • Kubectl version 1.28.6+rke2r1—Kubernetes client • Helm version 3.12.3—Kubernetes package manager • Docker-ce version 20.10.21—Docker engine • Docker-ce-cli version 20.10.21—Docker engine CLI • OpenShift version 4.15+—Kubernetes distribution for RHOCP clusters.
Isitoreji	A storage class named jnpr-bbe-storage.
Network load balancer address	One for APMi.
Registry storage	Each APM release requires approximately 3 gigabytes (GiB) of container images.

Izidingo Ezengeziwe

The BNG is a Juniper Networks MX Series router running Junos or a Juniper BNG CUPS Controller (BNG CUPS Controller).

We recommend the following releases:

Junos OS Release 23.4R2-s5 or later
BNG CUPS Controller 24.4R1 or later
For APM, confirm that you have a juniper.net user account with permissions to download the APM software package.
Download and install the APM software from a machine that will not be part of the Kubernetes cluster.

Izici Ezintsha Neziguquliwe

We have introduced the following new feature in APM 3.4.0.
Support for geographic redundancy—Address Pool Manager can maintain continuous operation across multiple geographically distributed Kubernetes clusters.
By utilizing a multiple cluster architecture managed by Karmada for orchestration and Submariner for inter-cluster networking, APM can failover if a data center outage kwenzeka.

Vula Izinkinga

Learn about the open issues in Address Pool Manager 3.4.0
Deleting an entity-match entry does not completely clean up the show apm entity output. I-PR1874241
An in-service upgrade of the BBE-observer triggers a rollout. As part of an in-service upgrade of the observer microservice, it may appear as if all APM microservices are being upgraded.

The list of container images loaded or pushed in the rollout output indicates that all the microservices are being upgraded, but only the observer microservice is upgraded.
Other container images that are being loaded or pushed are not upgraded. I-PR1879715
Reverting network load balancer (MetalLB) annotations, followed by performing a rollout, does not reset the external IP address for the APMi.

Indlela yokusebenza:

When the external address of the APMi that is bound to a particular IPAddressPool through the network load balancer annotations needs to be reverted to use an auto-assign IPAddressPool by removing the annotations, a stop command, and then a rollout command of APM must be performed.
I-PR1836255

Icela Usekelo Lokusebenza

Ukusekelwa komkhiqizo wezobuchwepheshe kuyatholakala ngeJuniper Networks Technical Assistance Center (JTAC).
Uma uyikhasimende elinenkontileka yokusekela ye-Juniper Care noma i-Partner Support Services, noma ivikelwe ngaphansi kwewaranti, futhi udinga ukusekelwa kwezobuchwepheshe kwangemva kokuthengisa, ungafinyelela amathuluzi ethu nezisetshenziswa ku-inthanethi noma uvule icala nge-JTAC.
JTAC policies—For a complete understanding of our JTAC procedures and policies, review i-JTAC User Guide etholakala https://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.

Iziqinisekiso zomkhiqizo—For product warranty information, visit https://www.juniper.net/support/warranty/.
JTAC hours of operation—The JTAC centers have resources available 24 hours a day, 7 days a week, 365 days a year.

Amathuluzi Wokuzisiza Waku-inthanethi Nezinsiza

For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features.
Thola iminikelo ye-CSC: https://www.juniper.net/customers/support/
Cinga izimbungulu ezaziwayo: https://prsearch.juniper.net/

Thola amadokhumenti omkhiqizo: https://www.juniper.net/documentation/
Thola izixazululo futhi uphendule imibuzo usebenzisa i-Knowledge Base yethu: https://supportportal.juniper.net/s/knowledge
Landa izinguqulo zakamuva zesoftware bese uphindeview amanothi okukhululwa: https://www.juniper.net/customers/csc/software/

Sesha amanqampunqampu wezaziso zezingxenyekazi zekhompuyutha ezifanele kanye nesofthiwe: https://supportportal.juniper.net/s/knowledge
Joyina futhi ubambe iqhaza ku-Juniper Networks Community Forum: https://www.juniper.net/company/communities/
Dala isicelo sesevisi ku-inthanethi: https://supportportal.juniper.net/

Ukuze uqinisekise ukufaneleka kwesevisi ngenombolo yomkhiqizo womkhiqizo, sebenzisa Ithuluzi Le-Serial Number Entitlement (SNE) yethu: https://entitlementsearch.juniper.net/entitlementsearch/

Ukudala Isicelo Sesevisi nge-JTAC

Ungakha isicelo sesevisi nge-JTAC ku- Web noma ngocingo.
Vakashela https://support.juniper.net/support/requesting-support/

Call 1888314JTAC (18883145822 toll-free in the USA, Canada, and Mexico).
Ngezinketho zamazwe ngamazwe noma zokudayela ngokuqondile emazweni angenazo izinombolo zamahhala, bheka https://support.juniper.net/support/requesting-support/.
I-Juniper Networks, ilogo ye-Juniper Networks, i-Juniper, ne-Junos yizimpawu zokuthengisa ezibhalisiwe ze-Juniper Networks, Inc. e-United States nakwamanye amazwe.

All other trademarks, service marks, registered marks, or registered service marks are the property of their respective owners.
IJuniper Networks ayinaso isibopho sanoma yikuphi ukungalungi kulo mbhalo. I-Juniper Networks igodla ilungelo lokushintsha, ukulungisa, ukudlulisa, noma ukubuyekeza lokhu kushicilelwa ngaphandle kwesaziso.

imibuzo ejwayelekile ukubuzwa

Q: Yini okufanele ngiyenze uma ngihlangabezana nezinkinga phakathi nokufakwa?
- A: Refer to the Open Issues section in the user manual for troubleshooting tips or contact technical support for assistance.
Q: Can I run other applications on the same Kubernetes cluster as APM?
- A: Yes, you can run other applications on the cluster, but ensure to use a 16-core node as per the specifications.

Amadokhumenti / Izinsiza

Juniper NETWORKS 3.4.0 Juniper Address Pool Manager [pdf] Umhlahlandlela Womsebenzisi
APM-3-4-0, 3.4.0 Juniper Address Pool Manager, 3.4.0, Juniper Address Pool Manager, Address Pool Manager, Pool Manager, Manager

Izithenjwa

Imaniwali yosebenzisayo

Juniper NETWORKS 3.4.0 Juniper Address Pool Manager

Ulwazi Lomkhiqizo

Imiyalo yokusetshenziswa komkhiqizo

Isingeniso