Please note there are different steps depending on the version you are running:
Aria Operations for Logs (formerly vRealize Log Insight) versions up until 8.12:
Important: Before applying the Resolution steps below, ensure that you update the IP address of the appliance if one has been specified in the vSphere Client under the vRealize Log Insight VM's Configure > Settings > vApp Options > Properties page. Please note the vApp options cannot be edited while the node is powered on.
Update the VM vApp configuration
- In the vSphere Web Client, select the VMware Aria Operations for Logs VM and navigate to Actions > Power > Shut Down Guest OS to shut down the guest OS gracefully
- Go to the Configure tab and choose vApp Options from Settings drop down
- Under Properties, select the key starting with vami.ip0 that describes Network 1 IP Address
- Click SET VALUE, enter the new IP address and click OK.
- Power on the VM from Actions > Power > Power On
Change the IP address of the node
- SSH to the vRealize Log Insight nodes as root
- Stop the Log Insight service
service loginsight stop
- Using a text editor, open the network configuration file located at /etc/systemd/network/10-eth0.network
- Replace the old IP with the desired address
- Save and exit the file
- Restart the network service
systemctl restart systemd-networkd
- SSH to the vRealize Log Insight node, using the new IP address
- Ensure the Log Insight service is not running
service loginsight status
Note: If the status output returned indicates that the service is running, stop it with service loginsight stop
- Copy the latest loginsight-config.xml# file (with the highest index number value) located in /storage/core/loginsight/config/, and increment the index number
Example: cp /storage/core/loginsight/config/loginsight-config.xml#11 /storage/core/loginsight/config/loginsight-config.xml#12
- Using a text editor, open the newly created xml file
- Update the IP address accordingly
- Save and exit the file
- Restart the VM from the vSphere Web Client to update the vCenter value with the new IP
Aria Operations for Logs (formerly vRealize Log Insight) version 8.14+:
Change the IP address of the node
- SSH to the Aria Operations for Logs node you wish to change the IP of, as root
- Stop the Log Insight service
systemctl stop loginsight
- List the contents of the config directory. In the output, note the file with the highest index number value at the end of its name
ls /storage/core/loginsight/config/
- Copy the latest loginsight-config.xml# file (with the highest index number value) and increment the index number in the new file
Example: cp /storage/core/loginsight/config/loginsight-config.xml#11 /storage/core/loginsight/config/loginsight-config.xml#12
Note: Replace loginsight-config.xml#11 in the above command with the filename of the highest index number you observed in step 3, and replace loginsight-config.xml#12 in the above command with the incremented index number (+1) of the number observed in step 3.
- Using a text editor, open the newly created xml file with the incremented index number, and update the IP address accordingly
- Save and exit the file
- Using a text editor, open the network configuration file located at /etc/systemd/network/10-eth0.network
- Replace the old IP address with the new one
- Save and exit the file
Update the VM configuration
- In the vSphere Web Client, select the VMware Aria Operations for Logs VM and navigate to Actions > Power > Shut Down Guest OS to shut down the guest OS gracefully
- Go to the Configure tab and choose vApp Options from Settings drop down
- Under Properties, select the key starting with vami.ip0 that describes Network 1 IP Address
- Click SET VALUE, enter the new IP address and click OK.
- Power on the VM from Actions > Power > Power On
Update and verify on other nodes
- SSH to the next node in the Aria Operations for Logs cluster as root
- Stop the Log Insight service:
systemctl stop loginsight
- Copy the new loginsight-config.xml# file (with the incremented index number) from the node with the changed IP address to /storage/core/loginsight/config directory on the current node
Example: scp root@nodeWithNewIP:/storage/core/loginsight/config/loginsight-config.xml#latest_number /storage/core/loginsight/config/
Note: Replace nodeWithNewIP in the above command with the IP address of the node which you have changed earlier in this article
- Start the Log Insight service
systemctl start loginsight
- Verify that the latest loginsight-config.xml# file contains the updated hosts
grep "daemon host=" "$(ls -1v /storage/core/loginsight/config/loginsight-config.xml* | tail -n 1)"
- restart Log Insight service on all remaining nodes one at a time to update Cassandra seeds:
systemctl restart loginsight
- Verify that the seeds are updated with the correct IPs:
grep "seeds" /storage/core/loginsight/cidata/cassandra/config/cassandra.yaml
- Repeat steps 5-7 on all nodes in the Aria Operations for Logs cluster.