Juniper NETWORKS 3.4.0 Ntuziaka onye njikwa adreesị Juniper

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.

Uru nke APM bụ ndị a:

Na-emeziwanye arụmọrụ nke iji adreesị ozi-e

Na-ebelata oke na mgbagwoju anya nke nlekota na inye site na-akpaghị aka nlekota na inye.
Na-enye ohere iweghachite prefixes abaghị uru maka ikesa n'ọdọ mmiri ndị chọrọ ha.
Enables APM to work with the BNG CUPS Controller.
These release notes accompany Juniper Address Pool Manager Release 3.4.0

Nwụnye

Onye njikwa ọdọ mmiri Adreesị 3.4.0 nwụnye chọrọ sistemụ kacha nta achọrọ edepụtara na ngalaba a.
IHE: 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

Otu

Nkọwa

ụyọkọ

Otu ụyọkọ nwere ọnụ ngwakọ 3.

Kubernetes ọnụ

Ọnụ ụzọ Kubernetes chọrọ ihe ndị a:

• 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 ma ọ bụ karịa (maka ụyọkọ Platform OpenShift Container)

• 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.

Otu

Nkọwa

Malie onye ọbịa

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.

Akụrụngwa ụyọkọ

Ụyọkọ ahụ chọrọ ngwanrọ ndị a:

• 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

Otu	Nkọwa
Malite ngwa ngwa onye ọbịa	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.
Nchekwa	Klas nchekwa aha ya bụ jnpr-bbe-storage.
Adreesị nkwụnye ụgwọ netwọkụ	Otu maka API.
Nchekwa ndekọ	Each APM release requires approximately 3 gigabytes (GiB) of container images.

Ihe ndị ọzọ chọrọ

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.

Atụmatụ ọhụrụ na agbanwere

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 emee.

Okwu Mmeghe

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. 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. PR1879715
Reverting network load balancer (MetalLB) annotations, followed by performing a rollout, does not reset the external IP address for the APMi.

Usoro ọrụ:

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.
PR1836255

Arịrịọ nkwado nka nka

Nkwado ngwaahịa nka dị site na Juniper Networks Technical Assistance Center (JTAC).
Ọ bụrụ na ị bụ onye ahịa nwere nkwekọrịta nkwado Juniper Care ma ọ bụ Onye Mmekọ na-arụ ọrụ, ma ọ bụ kpuchie n'okpuru akwụkwọ ikike, ma chọọ nkwado teknụzụ mgbe ịre ahịa, ị nwere ike ịnweta ngwaọrụ na akụrụngwa anyị n'ịntanetị ma ọ bụ mepee ikpe na JTAC.
JTAC policies—For a complete understanding of our JTAC procedures and policies, review ntuziaka onye ọrụ JTAC dị na https://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.

Akwụkwọ ikike nke ngwaahịa—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.

Ngwaọrụ na akụrụngwa enyemaka onwe

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.
Chọta onyinye CSC: https://www.juniper.net/customers/support/
Chọọ maka ahụhụ amara: https://prsearch.juniper.net/

Chọta akwụkwọ ngwaahịa: https://www.juniper.net/documentation/
Chọta azịza wee zaa ajụjụ site na iji Ntọala Ọmụma: https://supportportal.juniper.net/s/knowledge
Budata ụdị ngwanrọ ọhụrụ kachasị ọhụrụ wee regharịaview ndetu ntọhapụ: https://www.juniper.net/customers/csc/software/

Chọọ akwụkwọ akụkọ teknụzụ maka ozi ngwaike na ngwanrọ dabara adaba: https://supportportal.juniper.net/s/knowledge
Soro ma sonye na ọgbakọ Juniper Networks Community Forum: https://www.juniper.net/company/communities/
Mepụta arịrịọ ọrụ n'ịntanetị: https://supportportal.juniper.net/

Iji gosi ntozu ọrụ site na nọmba nsoghere ngwaahịa, jiri ikike ikike nọmba Serial (SNE) anyị: https://entitlementsearch.juniper.net/entitlementsearch/

Mepụta arịrịọ ọrụ na JTAC

Ị nwere ike ịmepụta arịrịọ ọrụ na JTAC na Web ma ọ bụ site na ekwentị.
Gaa leta https://support.juniper.net/support/requesting-support/

Call 1888314JTAC (18883145822 toll-free in the USA, Canada, and Mexico).
Maka nhọrọ ọkpụkpọ oku nke mba ụwa ma ọ bụ ozugbo na mba na-enweghị ọnụọgụ akwụghị ụgwọ, hụ https://support.juniper.net/support/requesting-support/.
Juniper Networks, akara Juniper Networks, Juniper na Junos bụ ụghalaahịa edenyere n'akwụkwọ ikikere nke Juniper Networks, Inc. na United States na obodo ndị ọzọ.

All other trademarks, service marks, registered marks, or registered service marks are the property of their respective owners.
Juniper Networks anaghị ewere ọrụ maka ezighi ezi ọ bụla na akwụkwọ a. Netwọk Juniper nwere ikike ịgbanwe, gbanwee, nyefee, ma ọ bụ megharịa akwụkwọ a na-enweghị ọkwa.

Ajụjụ a na-ajụkarị

Ajụjụ: Gịnị ka m ga-eme ma ọ bụrụ na m zutere nsogbu n'oge echichi?
- A: Refer to the Open Issues section in the user manual for troubleshooting tips or contact technical support for assistance.
Ajụjụ: Enwere m ike ịme ngwa ndị ọzọ n'otu ụyọkọ Kubernetes dị ka APM?
- A: Yes, you can run other applications on the cluster, but ensure to use a 16-core node as per the specifications.

Akwụkwọ / akụrụngwa

Juniper NETWORKS 3.4.0 Onye njikwa adreesị Juniper [pdf] Ntuziaka onye ọrụ
APM-3-4-0.

Ntụaka

Akwụkwọ ntuziaka onye ọrụ

Juniper NETWORKS 3.4.0 Onye njikwa adreesị Juniper

Ozi ngwaahịa

Ntuziaka ojiji ngwaahịa

Okwu mmalite