Best practices for BGP Syslog alert

This article describes setting up a BGP Syslog alert through configuring devices to forward Syslog messages to Orion.

The best practice is to configure your router to send Syslog if the status changes. This enables you to not miss any state changed once you have the Syslog in Orion. In the Syslog viewer, you can set up a rule for this specific Syslog. Then in the trigger actions tab, you can add an email action to be emailed when getting this Syslog.

If the neighbor description is in the message of the Syslog, then you should be able to put that in the email by the ${Message} variable. If it neighbor description is not in the message of the Syslog, then it would not be possible to add it in automatically and send it out.

Refer to the BGP Diagnostics section in the following article for more details:
http://www.cisco.com/en/US/prod/coll...p_osp_qos.html

Refer to the following article for the list of all variables that can be used with Syslogs.

http://www.solarwinds.com/NetPerfMon...tVariables.htm

Variables
http://www.solarwinds.com/NetPerfMon...eVariables.htm

Other Syslog variables
http://www.solarwinds.com/NetPerfMon...gVariables.htm

The following articles give more information on the BGP Alerting available.
http://thwack.solarwinds.com/message/135447#135447

http://thwack.solarwinds.com/message/168578#168578

http://thwack.solarwinds.com/thread/31248

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.