What’s new in AMCOP 3.2

Aarna Networks has recently released a new version of its open source orchestration platform, the Aarna Networks Multi Cluster Orchestration Platform (AMCOP) v3.2. This platform aims to solve management complexity for edgenative and 5G network services, providing orchestration, lifecycle management, and real-time policy, closed-loop automation capabilities. This blog post covers the new features, enhancements, and additions in this latest version of AMCOP.

I. New Feature Addition

One of the new features of AMCOP v3.2 is the startup config push from SMO (Service Management Orchestrator) to RAN (Radio Access Network) elements. This feature automatically pushes configuration to a new device when it connects for the first time. To use this feature, the desired startup config must be added to SMO via a REST API before connecting the device. SMO provides APIs to manage (add/view/delete) the desired configuration.

Another new feature is the cell setup/active/inactive capability. SMO will perform cell setup to DU (Distributed Unit) or cell active/inactive to CU (Central Unit) based on the synchronization-state change of the RU (Radio Unit).

AMCOP v3.2 also includes RU carrier activation, which performs active or inactive to all the carriers of the respective RU based on the cell status (in-service/out-of-service) netconf notification from CU/DU.

II. Additional Capabilities on Observability and Monitoring

AMCOP v3.2 has added new capabilities on observability and monitoring. It now includes ELK (Elasticsearch, Logstash, Kibana) integration, which provides centralized logging to identify problems with servers or applications. It allows you to search all the logs in a single place and helps to find issues in multiple servers by connecting logs during a specific time frame. To use this feature, you need to have a separate K8s cluster up and running to deploy the ELK stack.

AMCOP v3.2 also includes Prometheus and Grafana Orchestration, which enables telemetry service for target cluster monitoring. Prometheus federate (scrape approach) is used for target Kubernetes cluster and host server resource monitoring.

III. Addition of a new northbound interface (SOL-005)

AMCOP v3.2 now supports ETSI SOL005 Interface, which is related to network service management and VNF (Virtual Network Function) onboarding towards OSS/BSS (Operations Support System/Business Support System). SOL005 Interface fulfills the requirements defined in ETSI NFV IFA013.

IV. Greater Stability

AMCOP v3.2 has been stabilized for production readiness. Several fixes have been made to harden this version and make it ready for deployment in the production stage. The platform now has better fault management, alarm generation, failure handling, smooth migration, and service deletion.

In conclusion, the latest release of Aarna Networks Multi Cluster Orchestration Platform (AMCOP) v3.2 includes new features and enhancements that enable greater automation, observability, and stability for edge native and 5G network services. The addition of new capabilities on observability and monitoring, as well as the support for a new northbound interface, makes AMCOP v3.2 a more complete and robust platform for managing network services.

Learn more about ACMOP and request a free trial.

We use cookies to enhance site navigation, analyze site usage, and assist in our marketing efforts. For more information, please see the Aarna Networks Cookie Policy.
Accept cookies