This issue is resolved in vRealize Log Insight 8.1 and higher.
Workaround:
To workaround this issue, configure a network gateway before upgrading to vRealize Log Insight 8.0. If the upgrade has already been attempted, roll back to the snapshots taken before the upgrade, or follow the steps in
Manual rollback for a failed vRealize Log Insight 4.8 to 8.0 upgrade before proceeding.
Note: If no default gateway has been specified, the broadcast IP address of the network may show as the default gateway.
- Log into the vRealize Log Insight node as root via SSH or Console.
- Open /etc/sysconfig/network/routes in a text editor.
- Ensure the default gateway is configured correctly.
Example: default 192.168.0.1 - -
- Save and close the file.
- Open /etc/sysconfig/networking/devices/ifcfg-eth0 in a text editor.
- Ensure the default gateway is configured correctly on the GATEWAY line.
Note: If no GATEWAY line exists, add it to the end of the file.
Example:
DEVICE=eth0
BOOTPROTO='static'
STARTMODE='auto'
TYPE=Ethernet
USERCONTROL='no'
IPADDR='192.168.0.50'
NETMASK='255.255.255.0'
BROADCAST='192.168.0.255'
GATEWAY='192.168.0.1'
- Save and close the file.
- Repeat steps 1-7 on all vRealize Log Insight nodes in the cluster.
- Reboot vRealize Log Insight nodes and wait for services to start.