Setup
VMware-vRealize-Log-Insight-4.8.0-13036238_OVF10.ova
VCSA 6.7 Build 14368073

It took 5 hours to deploy the OVA (remote site) and you fat fingered any of the network card settings. You don’t want to spend another 5 hours.

You shut down the VM. Config / Settings / vApp Options and set the vami.ip0.VMware_vCenter_Log_Insight Network 1 IP Address from 192.168.0.243 to 192.168.0.249

  • Issue – The OS does not pick up the new IP address upon boot.

 

  1. Login to the VM console as root since root login via SSH is blocked by default.
    Run
    /opt/vmware/share/vami/vami_config_net 
  2. Hit 6 to change the IP address (or any other config you may have fat fingered)
  3. Hit 0 to validate or 1 to exit.
  4. The web client shows the new IP pulling from VM tools. Validate via the https url.
  5. I rebooted for grins and the new IP stuck.

 

Situation

Setup
VMware-vRealize-Log-Insight-4.8.0-13036238_OVF10.ova
VCSA 6.7 Build 14368073

It took 5 hours to deploy the OVA (remote site) and you fat fingered any of the network card settings. You don’t want to spend another 5 hours.

You shut down the VM. Config / Settings / vApp Options and set the vami.ip0.VMware_vCenter_Log_Insight Network 1 IP Address from 192.168.0.243 to 192.168.0.249

  • Issue – The OS does not pick up the new IP address upon boot.

 

Fix
  1. Login to the VM console as root since root login via SSH is blocked by default.
    Run
    /opt/vmware/share/vami/vami_config_net 
  2. Hit 6 to change the IP address (or any other config you may have fat fingered)
  3. Hit 0 to validate or 1 to exit.
  4. The web client shows the new IP pulling from VM tools. Validate via the https url.
  5. I rebooted for grins and the new IP stuck.

 

Menu