Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

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