RADIUS cannot be managed after rebooting RSA AM server running 7.1 SP4 full kit.
2 years ago
Originally Published: 2012-03-15
Article Number
000050992
Applies To
RSA Authentication Manager 7.1 SP4
RHEL Linux 5.8 64 bit
Cannot manage radius after rebooting the machine though all RSA services started.
Issue
RADIUS cannot be managed after rebooting RSA AM server running 7.1 SP4 full kit

 RSAAuthenticationManager/imsoc/ops-console.log shows below error:

@@@2012-03-14 12:42:05,544 ERROR [[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] GUILog.traceException(586) | exception:

javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://sacotpip02.sandisk.com:7082: Destination unreachable; nested exception is:

      javax.net.ssl.SSLKeyException: [Security:090504]Certificate chain received from sacotpip02.sandisk.com - 10.181.10.131 failed hostname verification check. Certificate contained sacotpip02.sdcorp.global.sandisk.com but check expected sacotpip02.sandisk.com; No available router to destination]


Cannot manage radius after rebooting the machine though all RSA services started.

Radius is configured with correct host name but after the configuration it shows a host name with incorrect domain suffix.