Submit a ticketCall us

ebook60.pngHow to be a Cisco® ASA ace

Our eBook, Thou Shalt Not Pass…I Think?! can help you overcome the challenges of monitoring and managing Cisco ASA firewalls. This eBook is a great read if you’ve been frustrated with monitoring firewalls, managing ACL configs, and troubleshooting VPN connections.

Get your free eBook.

Home > Success Center > Log & Event Manager (LEM) > SolarWinds LEM Upgrade Guide > Best practices for LEM upgrades

Best practices for LEM upgrades

Most standard LEM deployments upgrade a single virtual appliance. If you have multiple LEM virtual appliances, including hardware and virtual appliances, SolarWinds recommends upgrading these appliances in the following order:

  1. Alert database appliances
  2. RAW nDepth appliances
  3. Manager appliances

If you have a High Availability (HA) system, upgrade the primary appliance first, followed by the secondary appliance. You can upgrade logging servers and network sensors at any time.

Resize the LEM virtual appliance

You can increase or decrease the LEM virtual appliance capacity by increasing the LEM virtual appliance size in your hypervisor or cloning the LEM virtual appliance. This process adds up to 15 minutes to the boot-up process to adjust the file systems.

See your hypervisor documentation for information about increasing the appliance size.

During the boot-up process, do not turn off or reboot the appliance until the startup is completed. Subsequent bootups and reboots do not require an additional amount of time.

To retain your log data for an extended amount of time, you may need to increase the LEM virtual appliance size. You can increase your LEM virtual appliance capacity by increasing the hard disk size in your VMWare vSphere or Microsoft Hyper-V client.

Always shut down the LEM virtual appliance before you reconfigure the vSphere or Hyper-V client disk.

When you increase the size of your virtual appliance, use the following guidelines:

  • The maximum virtualization platform disk size is 2040 GB for Hyper-V and 2 TB for vSphere ESX/ESXi.
  • After you increase the virtual disk size, you cannot decrease its size using the same methods. Cloning allows you to decrease the size, but not below the original disk size.
  • If you have VM snapshots, you cannot increase the size of your virtual appliance.

Additional considerations for VMWare vSphere

If you are running VMware and do not have snapshots, you can edit the VM settings and change the size of the disk. During startup, the virtual appliance recognizes the change in disk size and partitions and adjusts the file systems appropriately. If snapshots are available, the disk size field is disabled.

If you need to increase the size of your virtual appliance, delete all VM snapshots or increase the existing VM by cloning it onto a larger disk. See your vSphere documentation for more information about performing these tasks.

Clone the LEM virtual appliance

To increase or decrease the virtual appliance capacity, create a secondary hard disk for the virtual appliance in your vSphere or Hyper-V client. When completed, start the virtual appliance to automatically clone the existing disk to the secondary hard disk. The new disk must be large enough to accommodate all of the data on the existing disk, but it is not required to have the same maximum capacity.

After you clone a vSphere secondary hard drive, power on the LEM and take a snapshot of the new appliance.

For details about cloning a virtual appliance in vSphere or Hyper-V, see the documentation included with the software.

Last modified