Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > HA 2.0 Traps, Syslogs, and Netflow configuration

HA 2.0 Traps, Syslogs, and Netflow configuration

Updated January 25, 2018


This article provides information about High Availability (HA) 2.0 Traps, Syslogs, and NetFlow configurations.


  • HA 2.0


For Traps, Syslogs, and NetFlow, you can use the host name or virtual host name. Some Cisco devices will allow the host name. For more information, see the Flexible NetFlow Configuration Guide (© 1992-2017 Cisco, available at, obtained on January 24, 2018.).

Most devices require configuration with an IP address, which will require to configure two destinations (both servers within a pool) of the Traps, Syslog, and NetFlow. Packets will be accepted on the Active server and dropped on the Standby server. This will double the size of the traffic on the network and half of that traffic will be dropped.



Last modified