DS Installer prompts for lockbox.zip during upgrade

Products

• Network Observability

Issue/Introduction

When performing an upgrade to NCM version 25.4.x in a distributed environment, the Device Server (DS) upgrade script prompts for the location of a lockbox.zip file. The user may find that this file does not exist on the Application Server or Device Server by default.

Environment

Smarts NCM 25.4.2 and above.

Cause

Starting with NCM 25.x, the installer requires a manual sync of the security lockbox during the upgrade of remote components. The lockbox.zip is not automatically generated by the App Server upgrade process; it must be prepared by the administrator to ensure the DS can authorize with the AS post-upgrade.

Resolution

The lockbox.zip file must be manually created from the Application Server (AS) and transferred to the Device Server (DS) during the installation process.

1. On the Application Server:
   • Navigate to the $VOYENCE_HOME/data directory.
   • Locate the active lockbox files (typically lockb.clb and, if using Standard Security, lockb.ekey).
   • Create a compressed archive named lockbox.zip containing these files.
     
     
2. On the Device Server:
   • Launch the DS upgrade/installation script.
   • When prompted for the lockbox.zip file, provide the path to the file created in Step 1.
     
     
3. Verification:
   • After the upgrade completes, verify that the files have been extracted to the DS $VOYENCE_HOME/data directory.
   • Restart services using systemctl restart vcmaster and confirm the DS status in the NCM Console.