Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Log & Event Manager (LEM) > SolarWinds LEM 6.3 User Guide > Additional LEM Configuration and Troubleshooting Information > Output, nDepth Host, nDepth Port Fields

Output, nDepth Host, nDepth Port Fields

Table of contents
No headers
Created by Caroline Juszczak, last modified by Caroline Juszczak on Sep 21, 2017

Views: 20 Votes: 0 Revisions: 5

Note: Do not modify the Output, nDepth Host, or nDepth Port fields unless your LEM appliance has been configured to receive and store original log data in its own database, the RAW database, also called the nDepth database.

Your SolarWinds LEM appliance can store 100% of the original log data read by any SolarWinds LEM connector in addition to the data normalized and presented in your LEM Console. Original log data is stored in a separate database from the normalized data, and is can be separately searched. This database typically resides on the same appliance as the LEM Manager and alert database, but it can also reside on a dedicated LEM database or nDepth appliance.

The Output, nDepth Host, and nDepth Port fields in the tool configuration forms on your LEM Manager and Agents are reserved for implementations in which the LEM appliance has been configured to receive and store original log messages. If your LEM appliance is not configured appropriately, modifying these settings will cause all alert data to queue indefinitely, rather than being sent to the appropriate database.

For additional information about configuring your LEM appliance and tools to handle original log data, refer to Configuring your LEM Appliance Log Message Storage and nDepth Search.

Last modified
10:29, 21 Sep 2017