When running NCM from secondary SpectroSERVER, SPC-OCC-11538 TFTP directory not set correctly error is generated

Products

• Network Observability
• Spectrum

Issue/Introduction

When primary SpectroSERVER (SS) is failed over to secondary, and NCM is running on the secondary, it is failing with the following error;

SPC-OCC-10747: Error capturing configuration for host: SPC-OCC-11538: Default TFTP directory is not set correctly.
Please verify it is set to the root directory of your TFTP server;

Environment

DX NetOps Spectrum all currently supported releases

Cause

The default TFTP directory setting will be pointing to the primary SS host.

It will not assume that this directory is on the secondary.

Resolution

We don’t advise running NCM on secondaries as it will result in the data being overwritten next time the primary is up and syncs back to the secondary. However, if this is a requirement of operations, then the secondary SS needs to be able to connect to the TFTP server running on the primary as per the following: 

1. The primary landscape TFTP directory path is a remote directory for the Secondary, so the directory should be a shared/mounted one accessible by both servers. But this gets over-written during the next OLB and again needs to be reset.
   
   You will need to get your system administrators to set it up so that the default TFTP directory is a shared, mounted directory between both primary and secondary.
   
   
2. The only way to save the NCM data from the secondary is to stop both primary and secondary, take a backup of the secondary SSdb, then load it onto the primary with a precedence of 10 (by default, secondary has a precedence of 20). So you would have to do this as follows:
   
   a. Uncompress and copy the backup file to the directory :
   
   

   $SPECROOT/SS

   
   b. Goto the command line (In Windows, run bash -login), then run:
   
   

   cd $SPECROOT/SS

3. Then, from the $SPECROOT/SS directory, run;

   ../SS-Tools/SSdbload.exe -il -r20 <DB_SAVED_BACKUP>.SSdb

   
   If the above is not done, then the NCM data on the secondary will be overwritten the next time the primary syncs with it when the primary is operational again.

 

Additional Information

KB : Spectrum NCM running on Secondary SpectroSERVER