HA 2.0 Traps, Syslogs, and Netflow configuration

11/8/2018 9:57 PM

1/12/2021 10:35 AM

This requires that your traps, syslogs and netflow configuration must be sent to your HA VIP or Domain instead of the IP or Hostname of your polling engine. 

Netflow Traffic Analyzer

HA 2.0 brought support for a multi-subnet environment. If you are using a multi-subnet structure (pool), you might need to adjust the configuration of your traps, syslogs, and NetFlow. See Multi-subnets in What is High Availability.

For traps, syslogs, and NetFlow, you can use the hostname or virtual hostname. Some Cisco devices will allow the hostname. For more information, see the Flexible NetFlow Configuration Guide (© 1992-2017 Cisco, available at https://www.cisco.com, obtained on January 24, 2018.).

If your devices support hostname as the destination, use the virtual hostname as the destination address for your traps, syslogs, and NetFlow. See What is a virtual hostname in When do I use a VIP?

If your devices don't support hostname, you need to provide an IP address as the destination and thus configure two destinations (both servers within a pool) for traps, Syslog and NetFlow. Packets will be accepted on the Active server and dropped on the Standby server. It doubles the size of the traffic on the network, and half of that traffic is dropped.