Juniper NETWORKS 3.4.0 Xestor de agrupacións de enderezos de Juniper
Información do produto
Especificacións
- Categoría: Xestor do conxunto de enderezos
- Versión: 3.4.0
- Publicado: 2025-06-03
- Clúster: Single cluster with 3 hybrid nodes
- Nodo de Kubernetes: 16-core node for running APM and companion applications
- Almacenamento: almacenamento jnpr-bbe
- Enderezo do balanceador de carga de rede: One for APMi
- Requisito de almacenamento de imaxes de contedores: Approximately 3 gigabytes (GiB) per APM release
Instrucións de uso do produto
Instalación
- Address Pool Manager 3.4.0 installation requires the minimum system requirements listed in the user manual.
Requisitos adicionais
- Ensure to meet all additional requirements specified in the installation guide.
Configuración do clúster
- To set up a single geographical cluster for APM, follow the specifications provided in Table 1 of the user manual.
Configuración do nodo de Kubernetes
- Use a 16-core node for running APM and other companion applications concurrently.
Configuración de almacenamento
- Crea unha clase de almacenamento chamada jnpr-bbe-storage para o uso de APM.
Balanceador de carga de rede
- Configurar un enderezo de balanceador de carga de rede para APMi.
Almacenamento de imaxes de contedores
- Asegúrate de ter espazo de almacenamento suficiente para as imaxes dos contedores.
- Each APM release requires approximately 3 gigabytes (GiB) of storage.
Introdución
- 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.
Os beneficios de APM son os seguintes:
- Mellora a eficiencia na utilización do enderezo
- Reduce a sobrecarga e a complexidade da supervisión e do aprovisionamento automatizando a supervisión e o aprovisionamento.
- Permite a recuperación de prefixos infrautilizados para a súa redistribución aos pools que os necesiten.
- Enables APM to work with the BNG CUPS Controller.
- These release notes accompany Juniper Address Pool Manager Release 3.4.0
Instalación
- A instalación de Address Pool Manager 3.4.0 require os requisitos mínimos do sistema que se indican nesta sección.
- NOTA: 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
Categoría | Detalles |
Clúster | Un único clúster con 3 nodos híbridos. |
Nodo de Kubernetes | Os nodos de Kubernetes requiren o seguinte:
• 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 ou posterior (para un clúster de OpenShift Container Platform) • 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. |
Categoría | Detalles |
Saltar host | 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. |
Software de clúster | O clúster require o seguinte 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 |
Categoría | Detalles |
Software de aloxamento de salto | 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. |
Almacenamento | Unha clase de almacenamento chamada jnpr-bbe-storage. |
Enderezo do balanceador de carga de rede | Un para APMi. |
Almacenamento do rexistro | Each APM release requires approximately 3 gigabytes (GiB) of container images. |
Requisitos adicionais
- 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.
Funcións novas e modificadas
- 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 ocorre.
Asuntos Abertos
- 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.
Solución:
- 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
Solicitando soporte técnico
- O soporte técnico do produto está dispoñible a través do Centro de asistencia técnica de Juniper Networks (JTAC).
- Se es un cliente cun contrato de soporte activo de Juniper Care ou de servizos de soporte para socios, ou está cuberto pola garantía e necesita asistencia técnica posvenda, pode acceder ás nosas ferramentas e recursos en liña ou abrir un caso con JTAC.
- JTAC policies—For a complete understanding of our JTAC procedures and policies, review a Guía de usuario de JTAC situada en https://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.
- Garantías do produto—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.
Ferramentas e recursos de autoaxuda en liña
- 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.
- Atopar ofertas de CSC: https://www.juniper.net/customers/support/
- Busca erros coñecidos: https://prsearch.juniper.net/
- Atopar a documentación do produto: https://www.juniper.net/documentation/
- Busca solucións e responde preguntas usando a nosa base de coñecemento: https://supportportal.juniper.net/s/knowledge
- Descarga as últimas versións do software e review notas de publicación: https://www.juniper.net/customers/csc/software/
- Busca en boletíns técnicos notificacións de hardware e software relevantes: https://supportportal.juniper.net/s/knowledge
- Únete e participa no foro da comunidade de Juniper Networks: https://www.juniper.net/company/communities/
- Crea unha solicitude de servizo en liña: https://supportportal.juniper.net/
- Para verificar o dereito ao servizo mediante o número de serie do produto, use a nosa ferramenta de dereito ao número de serie (SNE): https://entitlementsearch.juniper.net/entitlementsearch/
Creando unha solicitude de servizo con JTAC
- Podes crear unha solicitude de servizo con JTAC na páxina Web ou por teléfono.
- Visita https://support.juniper.net/support/requesting-support/
- Call 1888314JTAC (18883145822 toll-free in the USA, Canada, and Mexico).
- Para obter opcións internacionais ou de marcación directa en países sen números gratuítos, consulte https://support.juniper.net/support/requesting-support/.
- Juniper Networks, o logotipo de Juniper Networks, Juniper e Junos son marcas rexistradas de Juniper Networks, Inc. nos Estados Unidos e noutros países.
- All other trademarks, service marks, registered marks, or registered service marks are the property of their respective owners.
- Juniper Networks non asume ningunha responsabilidade por calquera imprecisión neste documento. Juniper Networks resérvase o dereito de cambiar, modificar, transferir ou revisar esta publicación sen previo aviso.
- Copyright © 2025 Juniper Networks, Inc. Todos os dereitos reservados.
Preguntas frecuentes
- P: Que debo facer se teño problemas durante a instalación?
- A: Refer to the Open Issues section in the user manual for troubleshooting tips or contact technical support for assistance.
- P: Podo executar outras aplicacións no mesmo clúster de Kubernetes que APM?
- A: Yes, you can run other applications on the cluster, but ensure to use a 16-core node as per the specifications.
Documentos/Recursos
![]() |
Juniper NETWORKS 3.4.0 Xestor de agrupacións de enderezos de Juniper [pdfGuía do usuario APM-3-4-0, 3.4.0 Xestor de agrupacións de enderezos de Juniper, 3.4.0, Xestor de agrupacións de enderezos de Juniper, Xestor de agrupacións de enderezos, Xestor de agrupacións, Xestor |