Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Log & Event Manager (LEM) > LEM Administrator's Guide > Apply a LEM connector update package

Apply a LEM connector update package

Updated: September 15, 2017

This topic documents different options for updating LEM connectors.

Enable global automatic connector updates

When enabled, this feature automatically updates Agents as they connect.

  1. Open the LEM console. See Log in to the LEM web console or Log in to the LEM desktop console for steps.

  2. Choose Manage > Appliances.

  3. Click the Settings tab in the Properties pane.

  4. Select "Enable Global Automatic Updates" under the Remote Updates heading.

Update connectors on-demand

  1. Open the LEM console. See Log in to the LEM web console or Log in to the LEM desktop console for steps.

  2. Choose Manage > Appliances.

  3. In the Appliances toolbar, click the Connector Updates drop-down menu and select Update now.


Update LEM connectors manually using the CMC interface

Customer Support occasionally provides stand-alone connector updates to address unmatched data alerts in your environment.

  1. Go to the SolarWinds Customer Portal and download the Connector Update package from the Additional Components page.
  2. Prepare the update package:
    1. Open the SolarWinds-LEM-Connectors folder.
    2. Copy the LEM folder to the root of a network share. For example: C:\share\LEM\.
  3. Open the CMC command line. See Log in to the LEM CMC command line interface for steps.

  4. At the cmc> prompt, enter manager.
  5. At the cmc::manager> prompt, enter sensortoolupgrade.
  6. Press the Enter key to start the upgrade process.
  7. Enter n to indicate that the update is located on the network.
  8. Press the Enter key to continue.
  9. Enter the path to the network share where the update package is located. Specify the path using the following UNC format: \\server\volume\file
  10. Enter y to confirm your entry.
  11. Enter the domain and user name for a user that can access the share. Use the following format: domain\user
  12. Enter yto confirm your entry.
  13. Enter the password for the user.
    Re-enter the password to confirm your entry.
  14. Enter 1 to start the update.

    The update will take several minutes.

    Verify that the configured connectors restart after they are updated by watching for InternalToolOnline alerts in the default SolarWinds Alerts filter in the LEM console.

  15. After the update is finished, type exit twice to exit the CMC interface.

Troubleshooting LEM connector upgrades

During the update process, the update script restarts all configured LEM connectors. In most cases, restarted connectors trigger one offline and one online alert in your LEM console.

An InternalWarning alert may appear, indicating that a connector started at the beginning of the corresponding log file. This alert may be caused by:

  • An unnecessary connector. For example, you could have an NT DNS connector configured on a server that is not running the DNS service.
  • A misconfigured connector. For example, you could have a connector pointing to the wrong location for the requisite log file.
  • The device associated with the connector rotated its logs while the connector was offline.

Below is the event information for the InternalWarning alert.

EventInfo: -1:Start location was -1. Init set to 'newest' record, record info: 1 - 193 (101 - 293) @ -1. InsertionIP: lab-vm-exc10.lab.exc Manager: lem DetectionIP: InsertionTime: 11:51:04 Thu Jun 16 2016 DetectionTime: 11:51:04 Thu Jun 16 2016 Severity: 2 ToolAlias: NT DNS InferenceRule: ProviderSID: FASTCenter normal error ExtraneousInfo: Component: FASTCenter:NT DNS Description: -1:Start location was -1. Init set to 'newest' record, record info: 1 - 193 (101 - 293) @ -1. Detail: StackTrace:
Last modified