000025207 - Cannot run log monitor on a replica when the primary is down

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000025207
Applies ToRSA ACE/Server 5.0 (no longer supported as of 8-15-2004)
Microsoft Windows NT 4.0
UNIX (AIX, HP-UX, Solaris)
Remote Administration
IssueCannot run log monitor on a replica when the primary is down
If the primary is down, then it is not possible to connect to a replica with Remote Administration.        
CauseThe Remote Administration program does not fail over when authenticating.   It only attempts to authenticate to the Primary Server as defined in the sdconf.rec file.
ResolutionIt is possible to work around the problem by creating a second sdconf.rec file with a replica as the primary server.

On the primary server, back up the sdconf.rec file in the data directory.   Run "sdsetup -config".   Change the Primary RSA ACE Server to be the replica.   Copy that sdconf.rec file and the server.cer file from the replica and put it on the floppy diskette.   Put the original sdconf.rec back in the data directory on the Primary.

On the remote administration PC, run setup from the aceserv/nt_i386 folder.   Point to the floppy diskette for the sdconf.rec and server.cer file.    The installation GUI will offer to add another server for remote administration, make sure only this option is checked.   The remote administrator can choose the replica if connection to the primary server fails.   The replica is still read only, but the administrator can view the log monitor from remote administration.
Legacy Article IDa6168