How to convert BlueXP Connector service manager from SM1 to SM2
Applies to
- BlueXP Connector
- Service Manager (SM) version 1
Description
-
BlueXP connectors running SM1 to follow this procedure before End of Support of SM1 in Dec 2025 to move connectors to SM2 as SM1 no longer receives updates.
-
Service Manager(SM) is essential for BlueXP Connector setup. It is the boot strap service that helps set up all the containers on the connector. All new features and security enhancements are built for SM2, such as support for Podman, vault, certs, dynamic connector configurations, the ability to disable data services, and alerting.
- BlueXP connector with SM1 can be identified as below:
- SSH to connector IP
sudo docker ps --format '{{.Image}}' | grep -e service_manager -e forwarder
- SSH to connector IP
If service_manager version shows 2.0.0.x and/or if forwarder container service is present - it indicates SM1.
Example :
BlueXPconnector> sudo docker ps --format '{{.Image}}' | grep -e service_manager -e forwarder
cloudmanagerinfraprod.azurecr.io/service_manager:2.0.0.1681625478565
cloudmanagerinfraprod.azurecr.io/cloudmanager_forwarder:7e59e2e-44-S
- Also check if service-manager folder present
ls /opt/application/netapp
=> Does not show service-manager-2 folder
- Download ASUP from Connector UI if unable to log into connector:
In BlueXP Connector AutoSupport logs find the SERVICE-MANAGER .LOG and search for string Current version:
[2024-03-18 00:00:00,248] [INFO] [com.cloudmanager.infra.servicemanager.actor.ServiceManagerUpdaterBehavior] [] - Checking for new updates, current version 2.0.0 (build time - 1681625478565) {akkaAddress=akka://service-manager, akkaSource=akka://service-manager/user/service-updater, sourceActorSystem=service-manager}
Version 2.0.0 indicates that the Connector is still running the old Service Manager 1
- In case of any further assistance needed for moving to SM2, Please contact ng-sm1-assistance@netapp.com and reference this article with the BlueXP account id and system id of the connector.
