SpectroSERVER Corba Timeouts after 100% Activation
search cancel

SpectroSERVER Corba Timeouts after 100% Activation

book

Article ID: 422980

calendar_today

Updated On:

Products

Spectrum

Issue/Introduction

After starting the Primary SpectroSERVER and reaching 100% activation CORBA::TIMEOUT errors are constantly written in the VNM.OUT


$SPECROOT/SS/VNM.OUT


--------------------------------------------------------------------------------

Dec 16 07:28:56 Model activation status - 1263279/1263281 activated( 99% ), 0 problematic.
currently processing 2 model activate triggers
Model 0x10632a8  "xxxxxxxxxxxxxxxx"/SwCiscoIOS - 181HsysUpTimeMonitor -101 seconds
Model 0x10b10dc  "xxxxxxxxxxxxxxxxxxxxxxxx"/SwCiscoIOS - 181HsysUpTimeMonitor - 64 seconds
--------------------------------------------------------------------------------

          Percentage of models activated: 100%
Dec 16 07:30:38  ERROR TRACE at CsCorbaMgr.cc(1271): Exception: CORBA::TIMEOUT
              Minor: 1447165959
              Completion Status: NO

Dec 16 07:31:23  ERROR TRACE at CsCorbaMgr.cc(1271): Exception: CORBA::TIMEOUT
              Minor: 1447165959
              Completion Status: NO

Dec 16 07:32:08  ERROR TRACE at CsCorbaMgr.cc(1271): Exception: CORBA::TIMEOUT
              Minor: 1447165959
              Completion Status: NO



Cause


The Fault Tolerant (FT) landscape had just been decomissioned but was still up and active while the primary was no longer able to resolve the FT landscapes name. The FT was
    connecting to the Primary but the Primary was unable to respond.

Resolution


Prevent the decomissioned server from being able to connect and remove it from the landscape map.

- update the .hostrc file on ALL SpectroSERVERs removing the decomissioned landscapes name

      $SPECROOT/.hostrc
      (delete the FT landscape name)

- On the MLS remove the FT Secondary from the map

     cd $SPECROOT/SS-Tools/
     ./MapUpdate -remove <landscape Handel> -p <precedence>


The removal of the host from the .hostrc file should prevent it from making a Corba connection and repopulating into the landscape map. Ideally one should
   update the $SPECROOT/LS/.locrc file on a server being decomissioned and set the main location server to itself to prevent it from connecting out.