Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Network Performance Monitor (NPM) > Best practices for BGP Syslog alert

Best practices for BGP Syslog alert

Table of contents
Created by Malik Haider, last modified by MindTouch on Jun 23, 2016

Views: 44 Votes: 4 Revisions: 6

Overview

This article describes the best practices for BGP Syslog alert.

Environment

All NPM versions 

Detail

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 article 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

Last modified
21:48, 22 Jun 2016

Tags

Classifications

Public