Mobility Collector Deployment Upgrade Procedure

Introduction

This section provides the upgrade instructions for the Mobility Collector components. It is intended for deployment engineers responsible for maintaining production-grade Kubernetes (RKE2) environments using Helm for service management.

Prerequisites

Before beginning the upgrade, ensure that the updated Docker images, specifically the tags for the alertservice and OTEL transformer, have been mirrored to your local registry.

If these images are not yet available locally, follow the authentication and transfer workflow detailed in the Download Required Images section of Mobility Collector Installation. Verification of these images is required before proceeding to the Helm deployment.

Step 1: Unzip the Helm Chart Bundle

Unzip the bundle that contains the helm charts: Mobility Collector Controlled Availability Release (March 23rd, 2026)

Step 2: Update Credentials Configuration

Update credentials.json at /matrix/service-deployment/matrix-fm/alertservice/config/alertservice and add one entry under connections to enable HTTP push notifications from alertservice to matrix-of-otel-transformer-v2.
Important: Ensure you have two entries pointing to both the standard and v2 transformers.

Step 3: Deploy Helm Charts

Caution: Ensure you refer to the new images in the respective values.yaml files in the Helm charts. Helm will deploy the new versions of the services to the cluster using the updated image tags.

Important: This upgrade procedure involves the manual removal and re-deployment of specific services.

helm upgrade --install -n matrix-fm-analytics matrix-of-otel-transformer-v2 otel-transformer-0.1.2.tgz \\
  --set image.repository=gcr.io/npav-172917/matrix-of-otel-transformer \\ # Transformer image repository
  --set image.tag=<DOCKER_VER> \\ # Transformer image tag for this release
  --set env.DB_ENRICHMENT_ENABLED=true \\ # Enable FM DB-based enrichment
  --set env.DB_HOST=matrix-timescaledb.matrix-pm-analytics.svc.cluster.local \\ # TimescaleDB service host
  --set env.DB_PORT=5432 \\ # TimescaleDB service port
  --set env.DB_NAME=matrixdb \\ # Database name
  --set env.DB_USER=postgres \\ # Database user
  --set env.DB_TABLE=inventory_node \\ # Inventory source table
  --set env.DB_HOSTNAME_COLUMN=hostname \\ # Column mapped to host.name
  --set env.DB_NE_TYPE_COLUMN=node_type_name \\ # Column mapped to telco.network_function.name
  --set dbCredentials.secretName=matrix-timescaledb-credentials \\ # Kubernetes secret containing DB credentials
  --set dbCredentials.passwordKey=PATRONI_SUPERUSER_PASSWORD \\ # Secret key used as DB password
  --set env.LOGGING_LEVEL_COM_CISCO_MATRIX=DEBUG \\ # App package log level
  --set env.LOGGING_LEVEL_SPRING_WEB=DEBUG \\ # Spring web log level
  --set env.DB_SCHEMA=pca2 \\ # Database schema for inventory lookup
  --set 'imagePullSecrets[0].name=regcred' # Image pull secret for private registry

Caution: Ensure you refer to the new images in the respective values.yaml files in the Helm charts.

Deploy Alertservice

helm install matrix-of-alertservice alertservice/ -f /matrix/service-deployment/matrix-fm/alertservice/values.yaml --namespace matrix-fm-analytics --set image.repository=pm.app.cisco.com:5000/matrixcx-docker/matrix4/matrix-of-alertservice --set image.tag=0.16.0

# Deploy OTEL Transformer v2
helm install -n matrix-fm-analytics matrix-of-otel-transformer-v2 /matrix/service-deployment/matrix-fm/otel-transformer-0.1.1.tgz --set image.repository=pm.app.cisco.com:5000/matrixcx-docker/matrix4/matrix-of-otel-transformer --set image.tag=0.16.0
Mobility Collector FM Upgrade Procedure

Step 4: Validate via test traps

Verify all Pods are running and trigger test traps via the matrix-of-snmptrapd pod. (Note: For dual-stack deployments, verify the target IP and port 1162/UDP point to the Kubernetes service):

# Verify FM pods are in running state
kubectl get pods -n matrix-fm-analytics

# Verify PM pods are in running state
kubectl get pods -n matrix-pm-analytics

# Trigger Test Trap
kubectl --namespace matrix-fm-analytics exec -it deployment/matrix-of-snmptrapd -- bash
snmptrap -v 2c -c public 127.0.0.1:1162 '' .1.3.6.1.4.1.8164.2.1024 .1.3.6.1.4.1.8164.1.29.1.1.1 s "2" .1.3.6.1.4.1.8164.1.29.1.1.2 s "2" .1.3.6.1.4.1.8164.1.29.1.1.3 i 2