Revocation List Timers - High Availability not working
Originally Published: 2009-07-15
Article Number
Applies To
Microsoft Windows 2003
Solaris 10
ADAM High Availability
Sun One High Availability
Issue
Configured RSA CM 6.8 with external LDAP. RCM is not able to generate CRL automatically when configured through Revocation List Timer - High Availability.
The basic installation (with internal Secure Directory) it works fine.
Cause
The host name used to configure primary and/or secondary instance on Revocation List Timers - High Availability configuration page did not match with the host name RSA CM detected internally.
Resolution
1. Configure CRL timers for a CA through System Configuration workbench -> Configure Revocation List Timers
2. Configure the primary instance hostname (FQDN and not IP address) and secure port through System Configuration -> Revocation List Timers - High Availability (see Note below to obtain a tool to determine the hostname RCM detects internally)
3. Restart RCM instances.
Notes
C:\> gethostname
gethostname retrieved rsatestbox
Calling gethostbyname with rsatestbox
Function returned:
Official name: rsatestbox.internal.rsa.net
Address type: AF_INET
Address length: 4
IP Address #1: 123.12.12.123
IP Address #2: 192.168.123.123
IP Address #3: 192.168.234.1
IP Address #4: 192.168.345.1
C:\> gethostname ?
usage: gethostname
or
gethostname ipv4address
or
gethostname hostname
For example:
to detect local host name
gethostname
to return the host based on IP
gethostname 127.0.0.1
to return the IP addresses for a host
gethostname www.rsa.com
Related Articles
Cloud Access Service - Clusters, High Availability, and Backups 20Number of Views Configure High Availability OTP 42Number of Views Configure High Availability for Cloud Access Service Deployments 104Number of Views Fully Resynchronize High Availability Tokencodes 57Number of Views High Availability OTP 56Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?