UPGRADE GUIDE. Log & Event Manager. Version 6.4

UPGRADE GUIDE Log & Event Manager Version 6.4 Last Updated: Friday, May 11, 2018

Copyright 2018 SolarWinds Worldwide, LLC. All rights reserved worldwide. No part of this document may be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the written consent of SolarWinds. All right, title, and interest in and to the software and documentation are and shall remain the exclusive property of SolarWinds and its respective licensors. SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. The SOLARWINDS and SOLARWINDS & Design marks are the exclusive property of SolarWinds Worldwide, LLC and its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks, registered or pending registration in the United States or in other countries. All other trademarks mentioned herein are used for identification purposes only and may be or are trademarks or registered trademarks of their respective companies. page 2

Table of Contents Prepare to upgrade LEM 4 Determine your upgrade path to the latest version of LEM 5 Best practices for LEM upgrades 6 Resize the LEM virtual appliance 6 Additional considerations for VMware vsphere 7 Clone the LEM virtual appliance 7 Upgrade LEM: complete steps 8 LEM upgrade options - Debian upgrade 8 Upgrade the virtual appliances 8 Troubleshoot errors during the appliance upgrade 9 Getting Help 10 Pull debugging information from your LEM virtual appliance 10 Send the log files to Customer Support 11 Upgrade the connectors 12 Upgrade connectors using the LEM console 12 Upgrade connectors using the CMC interface 12 Upgrade the consoles 13 Upgrade the reports console 14 Upgrade the agents 14 Upgrade agents from the virtual appliance using the LEM console 14 Upgrade LEM agents for Windows using the LEM console 15 Upgrade LEM agents for Windows using an installer 15 page 3

UPGRADE GUIDE: LOG & EVENT MANAGER Prepare to upgrade LEM The LEM upgrade process consists of upgrading the LEM appliance and related components: console, agents, and reports. The LEM 6.4 appliance upgrade package upgrades all components of LEM appliances running LEM version 6.3.1 and later. If you are running an earlier version of LEM or TriGeo SIM, see Upgrade paths for prior versions to review your required upgrade path. SolarWinds recommends this upgrade for all LEM components. The latest LEM agents are available both as stand-alone installers and as part of the LEM appliance upgrade package. For more information about this release, see the Release Notes. page 4

Determine your upgrade path to the latest version of LEM The LEM 6.4 appliance upgrade package upgrades LEM appliances running version 6.3.1 and later. If you need an upgrade package for an earlier version of LEM or TriGeo SIM, open a Customer Support ticket. The following table lists the full upgrade paths from all prior LEM versions to the latest version. LEM VERSION UPGRADE PATH 4.5.3 5.0.2 > 5.2.1 > 5.4 > 5.6 > 6.0.1 > 6.2.1 > 6.3.1 > 6.4 4.6 5.0.2 > 5.2.1 > 5.4 > 5.6 > 6.0.1 > 6.2.1 > 6.3.1 > 6.4 5.0.x 5.0.2 > 5.2.1 > 5.4 > 5.6 > 6.0.1 > 6.2.1 > 6.3.1 > 6.4 5.0.2 5.2.1 > 5.4 > 5.6 > 6.0.1 > 6.2.1 > 6.3.1 > 6.4 5.1.x 5.2.1 > 5.4 > 5.6 > 6.0.1 > 6.2.1 > 6.3.1 > 6.4 5.2.1 5.4 > 5.6 > 6.0.1 > 6.2.1 > 6.3.1 > 6.4 5.3 5.4 > 5.6 > 6.0.1 > 6.2.1 > 6.3.1 > 6.4 5.4 5.4 > 5.6 > 6.0.1 > 6.2.1 > 6.3.1 > 6.4 5.5 5.6 > 6.0.1 > 6.2.1 > 6.3.1 > 6.4 5.6 6.0.1 > 6.2.1 > 6.3.1 > 6.4 6.0 6.0.1 > 6.2.1 > 6.3.1 > 6.4 6.0.1 6.2.1 > 6.3.1 > 6.4 6.1 6.2.1 > 6.3.1 > 6.4 6.2 6.3.1 > 6.4 6.2.1 6.3.1 > 6.4 6.3.0 6.3.1 > 6.4 6.3.1 6.4 page 5

UPGRADE GUIDE: LOG & EVENT MANAGER Best practices for LEM upgrades Most standard LEM deployments upgrade a single virtual appliance. If you have multiple LEM 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. The upgrade will overwrite the system partition and cannot be interrupted or undone. Solarwinds recommends exporting (Hyper-V) or taking a snapshot of (vsphere) your LEM virtual appliance before running the upgrade. You can delete the snapshot upon confirmation of a successful upgrade. 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 for vsphere ESX /ESXi is 2TB. You can exceed the 2 TB limit with a fresh LEM deployment. page 6

The maximum virtualization platform disk size for Hyper-V: VHD - 2TB, for very old Hyper-V only. VHDX (recommended) - 2TB or more is supported. 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. page 7

UPGRADE GUIDE: LOG & EVENT MANAGER Upgrade LEM: complete steps When you upgrade your LEM appliances and components, upgrade the LEM appliances first. Upgrade your LEM appliances and components in the following order: Virtual appliances Connectors Consoles Reports console Agents When you perform a LEM upgrade, always reboot the LEM appliances. LEM upgrade options - Debian upgrade Upgrade 6.4 via network SMB share. If SMB1 is forbidden, the upgrade will not be able to reach the Windows shared drive. As an alternative, attach the upgrade ISO to the virtual machine CD-ROM from filesystem, datastore, etc. Custom changes made on any LEM appliance (by root) will not be preserved after the upgrade. Specifically, any unexpected configuration formats created outside of CMC. For example: Iptables custom rules Modified scripts Added scripts Modified chron scheduler Upgrade the virtual appliances During this process, the upgrade script disconnects the LEM virtual appliance from all LEM agents and consoles. 1. Prepare the upgrade media. a. Download the Upgrade Package for LEM Virtual ZIP file from the SolarWinds Customer Portal. b. Unzip the file. c. Open the SolarWinds Log & Event Manager 6.4 Upgrade folder. page 8

d. Copy the TriGeo and Upgrade folders to the root of a network share. The upgrade locates the two directories only when \\<server-ip>\<share-name> is specified. For example, for \\<server-ip>\<share-name>, the TriGeo and Upgrade directories are placed directly under <share-name>. 2. Connect to the LEM virtual appliance using the virtual console (vsphere or Hyper-V Manager) or an SSH client (such as PuTTY). If you are using an SSH client, use port 22 or 32022, and then log in with your CMC user credentials. 3. Access the CMC prompt. In vsphere, arrow down to Advanced Configuration, and then press Enter. In PuTTY, log in using your CMC credentials. 4. At the cmc> prompt, enter: upgrade 5. Follow the onscreen instructions to complete the LEM appliance upgrade. During the upgrade, the LEM will reboot automatically. Troubleshoot errors during the appliance upgrade If you encounter errors during the appliance upgrade, review the error message information below before you contact Customer Support. ERROR MESSAGE An error occurred during the upgrade. You must upgrade to 6.3.1 before upgrading to 6.4. The current host name is invalid. The database is not running. RESOLUTION Rerun the upgrade script. If the script returns the error again, pull debugging information and open a Customer Support ticket. See Upgrading from prior versions for the appropriate upgrade procedure. This error occurs when the host name for your LEM virtual appliance contains an underscore ( _ ) character. To resolve this issue: 1. Enter exit to return to the cmc> prompt. 2. At the cmc> prompt, enter appliance, and then press Enter. 3. At the cmc::acm prompt, enter hostname, and then press Enter. page 9

UPGRADE GUIDE: LOG & EVENT MANAGER ERROR MESSAGE RESOLUTION 4. Follow the onscreen instructions to change your LEM virtual appliance hostname to a name that does not contain the underscore character. When you change the host name, any agent of a syslog device that sends log data to the LEM host name will require configuration changes. 5. Rerun the upgrade script. If the script returns the error again, pull debugging information from your LEM appliance and open a Customer Support ticket. Additionally, perform these procedures to troubleshoot the following error: The database is not running. If the script returns the error again, open a Customer Support ticket. Getting Help Use the debug command on your LEM virtual appliance to pull log files from the appliance to send to Customer Support. These files contain debugging information used by Customer Support to troubleshoot your issue. Pull debugging information from your LEM virtual appliance 1. Connect to your LEM virtual appliance using the vsphere console view or an SSH client (such as PuTTY). If you are using an SSH client, log in to your LEM virtual appliance using your CMC credentials. 2. At the cmc> prompt, enter manager, and press Enter. 3. At the cmc::cmm prompt, enter debug, and press Enter. page 10

4. Specify whether you want to send the debugging files as an email or save the files to a network location. Some debugging files may be too large to send to Customer Support through email. To resolve this issue, save the files to a separate location, and then compress them into a ZIP file. When completed, email the file to yourself. If you receive the email with the attached debugging files, forward the file to Customer Support. 5. Follow the prompts on your screen to generate the files. 6. Verify that the script generated three files with the following extensions:.tgz.log.txt 7. Email these files to Customer Support. These files do not contain alert data or other data from your LEM database. 8. Enter exit and press Enter to return to the cmc> prompt. 9. Enter exit and press Enter to log out of your LEM virtual appliance. Send the log files to Customer Support 1. Save your debugging information in a compressed folder (such as a ZIP file). If your ZIP file is 10 MB or smaller, email the file directly to your existing support case or create a new case with Customer Support. If you established email communication with Customer Support about this issue, reply to the existing email thread. If your ZIP file is larger than 10 MB: a. Navigate to solarwinds.leapfile.com. b. Click Secure Upload. c. Enter support@solarwinds.net in the Recipient Email field. d. Click Start. e. Complete the Secure Upload form and click Select files to send (Regular Upload). f. Click Choose file and select a debug file to upload. g. Click Open. h. Repeat this procedure for all debug files you want to send to Customer Support. page 11

UPGRADE GUIDE: LOG & EVENT MANAGER 2. When completed, click Upload & Send. The ZIP file is sent to Customer Support. Customer Support is not automatically notified when you upload files to the Secure File Exchange website. If you established email communications with Customer Support about this issue, reply to the existing email thread to notify them that you uploaded the files. Otherwise, place a similar comment in your case. Upgrade the connectors Beginning in LEM 6.2.0, you can upgrade your connectors using the LEM console. For versions prior to 6.2.0, update your connectors using the CMC command interface. Upgrade connectors using the LEM console 1. Navigate to the Appliance grid on the Manage tab. 2. In the toolbar, click the Connector Updates drop-down menu and select Update now. A message displays, confirming the update was applied. Upgrade connectors using the CMC interface 1. Download the current Connector Update package from the LEM Additional Components page located on the SolarWinds Customer Portal. The download requires approximately 3.6 MB of disk space. 2. Prepare the update package. a. Unzip the Connector Update Package file. The directory structure uses approximately 100 MB of disk space. b. Open the SolarWinds-LEM-Connectors folder. c. Copy the LEM folder to the root of a network share. For example: \\<server-ip>\<share-name> The connector locates the LEM directory under the root of the share. 3. Connect to the LEM virtual appliance using a virtual console or SSH client. 4. Access the cmc> prompt. If you are using a virtual console, scroll down to Advanced Configuration and press Enter. If you are using an SSH Client, log in using your CMC credentials. page 12

5. Update the connectors. Press Enter after entering each command. a. At the cmc> prompt, enter manager. b. At the cmc::cmm# prompt, enter sensortoolupgrade. c. Press Enter to begin the upgrade process. d. Enter n (network) for your sensor tool updates location. e. Press Enter to continue. f. Enter your Windows destination share. For example: \\server\share: \\share\folder\ g. Enter y to confirm your share name. h. When prompted, enter your name, user name, and password. 6. Verify that the configured connectors restart after the update by monitoring the LEM console and searching for InternalToolOnline events in the default SolarWinds events filter. 7. When the update is completed, enter exit twice and press Enter twice to exit the CMC interface. Upgrade the consoles Upgrading the LEM appliance automatically updates the LEM web console. During the upgrade, you may be reconnected automatically. To ensure you are running the latest web console version, you can: Refresh the console in your browser. Close the console, reopen your browser, and reconnect. After you upgrade the LEM virtual appliance, upgrade the LEM desktop console to take advantage of the new features in this release. page 13

UPGRADE GUIDE: LOG & EVENT MANAGER 1. Uninstall the existing desktop console. 2. Run SolarWindsLEMConsole.air. 3. Complete the installation wizard. Both the LEM desktop console and the web console preserve all filters and other local settings from previous LEM console versions. Upgrade the reports console After you upgrade the LEM virtual appliance, upgrade the LEM reports application so it is compatible with the web or desktop console. Previously-scheduled reports will not run until you upgrade the reports application to the latest version. This is especially important when using Windows 8 and later operating systems. 1. Open the Reports folder from your unzipped upgrade download. 2. Copy setup.exe to the local drive on your Reports computer. The security settings in some Windows operating systems require the installer to be on the local hard drive prior to the launch. 3. Log in to the Reports computer. 4. Right-click setup.exe and select Launch to run as administrator. 5. Complete the installation wizard. If you are installing the update on systems running Microsoft Windows 8.1, Windows 10, or Windows 2012 R2, include Windows 7 compatibility for the installation. Upgrade the agents To take advantage of new enhancements such as Java Runtime Environment (JRE) and infrastructure updates, be sure to upgrade the LEM agents. If you selected the Enable Global Automatic Updates check box when you adjusted your Global Automatic Update setting, your LEM agents will update automatically. If you did not enable global automatic updates, you can manually upgrade the LEM agents by accessing the installer through the LEM console or using an installer downloaded directly from the SolarWinds Customer Portal. Upgrade agents from the virtual appliance using the LEM console Manually pushing agent upgrades from the virtual appliance is the fastest, easiest way to manually upgrade agents. page 14

1. In the LEM console, click Manage and select Nodes. 2. In the Nodes pane, select the LEM agent to upgrade. Press and hold <Ctrl> to select more than one agent. 3. Click Remote Updates, and then select Update. An Update Status icon for your selected agent opens, indicating the update procedure. When the update is completed, the Update Status icon changes back to the green Updated icon and displays the new agent version. A LEM agent upgrade does not require you to reboot the host computer. Upgrade LEM agents for Windows using the LEM console If your console is connected to the Internet, you can update your LEM agents through the LEM console. 1. In the LEM console, click Manage and select Nodes. 2. Click Add Node and select Agent node. 3. Select the appropriate installation type. Select Remote Installation to push LEM agents to Microsoft Windows hosts across your network. Select Local Installation to log in to the device and install the LEM agent. 4. Copy the setup.exe file to the local hard drive on the computer. The security settings in some Windows operating systems require the installer to be on the local hard drive prior to the launch. 5. Log in to the computer, right-click the installer, select Run as Administrator, and complete the installation wizard. When installing the upgrade on systems running Windows 8.1, Windows 10, or Windows 2012 R2, include Windows 7 compatibility for the installation. Upgrade LEM agents for Windows using an installer If your console is not connected to the Internet, you can update your LEM agents by downloading the agent installer from another computer with an Internet connection. Install your new LEM agents in the same folder as your existing LEM agents. This process allows the installer to update the LEM agent software while maintaining all other configuration settings. 1. Download the agent installer from the Additional Components page on the SolarWinds Customer Portal. 2. Extract the ZIP file contents to your desktop or another location. page 15

UPGRADE GUIDE: LOG & EVENT MANAGER 3. Copy the setup.exe file to the local hard drive on the computer. The security settings in some Windows operating systems require the installer to be on the local hard drive prior to the launch. 4. Log in to the computer, right-click setup.exe, select Run as Administrator, and complete the installation wizard. When installing on Windows 8.1, Windows 10, or Windows 2012 R2, include Windows 7 compatibility for the installation. 5. Run setup and complete the installation wizard. page 16