Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Log & Event Manager (LEM) > SolarWinds LEM 6.3 User Guide > Advanced LEM configurations > Configure connectors

Configure connectors

After you configure the manager connectors, configure the sensor and actor connectors for each agent associated with the manager. Use the connector configuration form to connect each agent connector to any supported product that is either installed on, or remotely forwarding log messages to the agent computer. Once you configure the agent connectors, the manager can monitor and interact with the products and devices on that computer.

Agent connectors run locally to monitor local log files and data logged to the agent computer from remote devices that cannot run an agent. The active response connectors (actors) allow the agent to receive instructions from the manager and perform active responses locally on the agent computer, such as sending pop-up messages or detaching USB devices.

Connectors grid icons

The following table describes the icons used in the Connectors grid.

Icon Description

File:Success_Center/New_Articles/LEMUserGuide_MT/0B0/020/Icon-BlueTool_24x24.png

A product sensor. The sensor displays the name of the product it is designed to monitor.

File:Success_Center/New_Articles/LEMUserGuide_MT/0B0/020/Icon-OrangeTool_25x24.png

A product actor that performs an active response. The actor displays the name of the product it is designed to interact with.

File:Success_Center/New_Articles/LEMUserGuide_MT/0B0/020/Icon-SensorTool_27x27.jpg

A configured instance of a sensor connector. The Status column displays Stopped File:Success_Center/New_Articles/LEMUserGuide_MT/0B0/020/Icon-Stop_13x13.png or Running File:Success_Center/New_Articles/LEMUserGuide_MT/0B0/020/Icon-Play_13x13.png for each instance.

File:Success_Center/New_Articles/LEMUserGuide_MT/0B0/020/Icon-ActorInstance_27x27.jpg

A configured instance of an actor connector. The Status column displays Stopped File:Success_Center/New_Articles/LEMUserGuide_MT/0B0/020/Icon-Stop_13x13.png or Running File:Success_Center/New_Articles/LEMUserGuide_MT/0B0/020/Icon-Play_13x13.png for each instance.

Configure manager connectors (general procedure)

Follow this procedure to configure manager connectors (sensors and actors). It lets the manager monitor and interact with supported security products and devices that are either installed on, or remotely forwarding log messages to the manager computer.

  1. Start the LEM Console.
  2. Open the Manage > Appliances view.
  3. Add and configure each manager you will use in your network.
  4. Log on to the manager.
  5. Open the Connector Configuration for [Manager] form.
  6. Add a connector instance for each product event log source.
  7. When you are finished, start the connector instance.
  8. Repeat Steps 6 and 7 for each product or device that is forwarding log messages to the manager computer.
  9. Repeat Steps 4 through 8 for each manager until you have configured connectors for each point on your network.

Configure agent connectors (general procedure)

Follow this procedure to configure the connectors (sensors and actors) used by the agent to monitor and interact with each network security product and device running on the agent computer.

  1. Open the Manage > Nodes view.
  2. Search for the IP address or host in the Nodes grid.
  3. Click File:Success_Center/New_Articles/LEMUserGuide_MT/0B0/020/Button-Gear_17x14.png beside the hostname or IP address and select Connectors.
  4. In the Refine Results pane, enter a search term that describe the connector you need.
  5. Click File:Success_Center/New_Articles/LEMUserGuide_MT/0B0/020/Button-Gear_17x14.png beside your targeted connector and select New.
  6. Complete the connector information form, and then click Save.

    Some connectors require the exact path to the Windows log, while others just read the Windows Event Viewer logs.

  7. When you are finished, start the connector instance.
  8. Repeat steps 3 through 7 for each product or device the agent is monitoring on the agent computer.

    If you are not using connector profiles, repeat steps 2 through 7 for each agent until you finish configuring the connectors for each point on your network. If you are using connector profiles, you can use a configured agent as a template for a connector profile.

Use connector profiles to configure multiple agents

Most agents in a network include a few different connector configurations. You can streamline your connector configuration process by creating connector profiles.

  • A connector profile is a group of agents that share the same connector configuration. You can use the profile to configure a set of standardized connector settings, and then apply those settings to all agents assigned to that profile. Once applied, every agent in the profile will have the same connector settings.
  • Connector profiles maintain all agents in a profile by updating only the profile connector configuration. The system then propagates your changes to all of the agents in the profile.
  • Using Connector Profiles, you can streamline the process of connecting your network security products to LEM. If you decide not to use connector profiles, you must create at least one connector instance for every product that you intend to integrate with LEM, and then repeat this process for each agent.
  • A well-planned set of connector profiles provides you with a versatile and efficient method for configuring and maintaining your agent connector configurations.

Configure email active response connectors

Configure the email active response connector on your LEM manager to enable the manager to send automated emails to console users when a rule fires. This connector specifies the mail host that your manager uses to send emails. When required, it also provides the server credentials.

The email active response connector requires:

  • An email server that allows the LEM manager to relay email messages through it
  • IP address or hostname of your email server
  • A return email address for bounced messages and replies
  • User credentials for your email server (only if your email server requires internal users to authenticate to send email)

Configure the connector

  1. Open the LEM console.
  2. Click Manage > Appliance.
  3. Log in to the LEM manager that requires an email active response connector.
  4. Click File:Success_Center/New_Articles/LEMUserGuide_MT/0B0/020/Button-Gear_17x14.png next to your LEM manager and select Connectors.
  5. Enter Email Active Response in the search box on the Refine Results pane.
  6. Click File:Success_Center/New_Articles/LEMUserGuide_MT/0B0/020/Button-Gear_17x14.png next to the master connector and select New.
  7. Complete the Email Active Response connector form.

    If you use a hostname for the Mail Host value, your manager must be able to resolve it.

  8. Enter a valid email address in the Test E-mail Address field. After the connector is saved and started, your manager sends a test email to the email address.
  9. Click Save.
  10. Locate the new connector instance in the Nodes grid.
  11. Click File:Success_Center/New_Articles/LEMUserGuide_MT/0B0/020/Button-Gear_17x14.png and select Start.

    A green icon in the Status column indicates the connector is running.

  12. Test the connector.

Test the connector

Click Test Email to test your settings. If the test email is successful, you receive an email. If the test email is unsuccessful, the LEM Internal Events filter displays the following information:

  • Event Name: InternalInfo
  • Event Info: Email notification failed
  • Extraneous Info: Information about the failure. For example, server not reachable, authentication issue, etc.

If required, modify the connector configuration to make sure you are using the correct information.

 
Last modified
14:48, 23 Mar 2017

Tags

Classifications

Public