DX NetOps NCM Scheduled or manual jobs fail to execute

Products

• VMware Smart Assurance
• Network Observability

Issue/Introduction

An inspection of the commmgr (Communications Manager) log confirmed no activity was being recorded other than routine service restarts, indicating a breakdown in the job processing flow

 

By tracing the NCM job flow, the identified point of failure: the ssxfrcgi daemon. This daemon was throwing an error regarding the unavailability of the master.addr file, which is critical for communication between the Device Server (DS) and the Application Server (AS).

Environment

 

• Application: Broadcom Network Configuration Manager (formerly Voyence NCM)

• Version: 25.4.x

 

Resolution

Restoring master.addr 

1. Navigated to the Device Server directory: /opt/voyence/data/devserver.

2. Manually created the missing master.addr file.

3. Populated the file with the IP address of the Application Server (AS).

4. Corrected the file ownership and permissions to match NCM requirements.

 

Rebuilding Device Server Identity Files 

1. Navigated back to /opt/voyence/data/devserver.

2. Created a new file named our.idx.

3. Inserted the value 1000 into the file, which corresponds to the POPID (Point of Presence ID) of the Device Server.

4. Corrected the ownership and permissions for the new our.idx file.

5. Deleted the hidden .rhttps file located in /opt/voyence/data/ to force the system to rebuild its secure connection states.

6. Restart the vcmaster service.