Network settings are wiped out after RSA Authentication Manager 8.7 SP1 upgrade on Azure
a year ago
Originally Published: 2024-09-23
Article Number
000072847
Applies To
RSA Product Set: SecurID
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.7 SP1
Platform: SUSE Linux
O/S Version: Enterprise Server 15 Service Pack 3
Product Description: SecurID Appliance
Issue
After upgrading to 8.7 SP1, the primary server lost its IPv4 address on eth0. The VMs are hosted in Azure.
AdminServerWrapper.log shows:
INFO   | jvm 1    | main    | 2024/09/20 14:01:24 | <Sep 20, 2024 2:01:24,126 PM EDT> <Notice> <Security> <BEA-0090169> <Loading trusted certificates from the jks keystore file /opt/rsa/am/server/security/trust.jks.> 
INFO   | jvm 1    | main    | 2024/09/20 14:01:24 | <Sep 20, 2024 2:01:24,126 PM EDT> <Warning> <JMX> <BEA-149513> <JMX Connector Server stopped at service:jmk::iiop://192.168.0.20:7006/jndi/weblogic.management.mbeanservers.edit.>
INFO   | jvm 1    | main    | 2024/09/20 14:01:24 | <Sep 20, 2024 2:01:24,126 PM EDT> <Warning> <JMX> <BEA-149513> <JMX Connector Server stopped at service:jmk::iiop://192.168.0.20:7006/jndi/weblogic.management.mbeanservers.domainruntime.>
INFO   | jvm 1    | main    | 2024/09/20 14:01:24 | <Sep 20, 2024 2:01:24,126 PM EDT> <Warning> <JMX> <BEA-149513> <JMX Connector Server stopped at service:jmk::iiop://192.168.0.20:7006/jndi/weblogic.management.mbeanservers.runtime.>
INFO   | jvm 1    | main    | 2024/09/20 14:01:24 | <Sep 20, 2024 2:01:24,126 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
INFO   | jvm 1    | main    | 2024/09/20 14:01:24 | 
INFO   | jvm 1    | main    | 2024/09/20 14:01:24 | There are 1 nested errors:
INFO   | jvm 1    | main    | 2024/09/20 14:01:24 | 
INFO   | jvm 1    | main    | 2024/09/20 14:01:24 | java.io.IOException: [Server:002664] Failed to start Admin Channel AdminChannel.
INFO   | jvm 1    | main    | 2024/09/20 14:01:38 | 	at weblogic.server.channels.ServerSocketManager.createAndBindServerSockets (ServerSocketManager.java:132) 
INFO   | jvm 1    | main    | 2024/09/20 14:01:38 | 	at weblogic.server.channel
Noticed that the boot protocol changes from static to dhcpv4 in the network config file for eth0. The gateway is changed to none on the Operations Console and another DNS record is added on the OC as well.

[Expected]
rsaadmin@am87p:/etc/sysconfig/network> more ifcfg-eth0
STARTMODE=auto
BOOTPROTO=static
IPADDR=192.168.0.20
PREFIXLEN=27
LABEL=

[Actual]
rsaadmin@am87p:/etc/sysconfig/network> more ifcfg-eth0
# Created by cloud-init on instance boot automatically, do not edit.
#
BOOTPROTO=dhcp4
LLADDR=00:0d:3f:7b:9a:ef
STARTMODE=auto
Cause
Network settings on Azure change automatically after upgrading to 8.7 SP1 from 8.7 right after the automatic reboot.
Resolution

Prior to applying 8.7 SP1, retain the static IP network configuration by disabling cloud-init network config, which allows netconfig to control the network settings on reboot or not overridden by cloud-init.

Change in appliance as below:
1. Add  the following in /etc/cloud/cloud.cfg file:
network:
config: disabled

 

Please note that the lines should be added at the end of the file. Otherwise, server will lose its network settings.


2. Rebooted the appliance. Type:
Sudo reboot

3. If the upgrade was already progressed and encountered the network settings wiped out, then this can be resolved by manually configuring the appliance network settings with “configureNetwork.py” script as per KB 000043629:
https://community.rsa.com/s/article/Services-will-not-start-after-changing-IP-address-of-RSA-Authentication-Manager-8-x-from-command-line

Notes
Note that the fix is available in 8.7 SP1 Patch 2