Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

bgp and ospf going down to trigger map color change

Hello All

is there any way i can make ospf/bgp neighbors go down in one of the layer 3 nodes insides a map to trigger a map color to change from green to yellow or red ?

Find more posts tagged with

Accepted answers

All comments

mrkuwait

Very interesting. I would like to see this too.

CourtesyIT

Are you monitoring the LoopBack or Phyiscal Interface?

asherbersh

i am monitoring device loopback address , i am not sure but how this helps ?

cjfranca

If you to can remove and add one more time.

Removing you lost the date´s node.

CourtesyIT

A loopback address does not go down but a physical interface will.

superfly

A link can still show as up even if BGP goes down. Cause the link could be plugged into a NTU which is still up but in the meantime the network link is down. So if you have a remote sites with 2 links both links can still show up even though the primary link is no longer passing traffic.

To the OP, I'm not sure if you can make a link go yellow or red on BGP failure.

rschroeder

I like the discussion. Is it possible to use information from a trap or syslog message to trigger the map color change?

Keeping in mind that a remote device may not be able to send a trap or syslog message to NPM, or receive a poll from NPM, if its network path is down due to losing a BGP neighbor or OSPF relation. In this case you'd need to have the NPM server local to the router. Then the trap or syslog message will still make it to the NPM server.

Some other ideas, that don't involve changing icon colors (which I think is a pretty cool idea!) include:

Creating an automatic alert from Syslog to show your team immediately when BGP neighbor status or OSPF adjacency goes down
Creating a Critical Interfaces alert, then adding your most important interfaces to it. Some examples would be uplinks between switches, links on routers, etc. If you go this route, don't neglect to include the multiple physical ports that comprise a port-channel, since you'll want to know when some of your throughput and resilience has been lost due to one port in a multi-port port-channel being down. That's a reason why you shouldn't "only" monitor port-channels, but also their members.

superfly

rschroeder wrote:
I like the discussion. Is it possible to use information from a trap or syslog message to trigger the map color change?
Keeping in mind that a remote device may not be able to send a trap or syslog message to NPM, or receive a poll from NPM, if its network path is down due to losing a BGP neighbor or OSPF relation. In this case you'd need to have the NPM server local to the router. Then the trap or syslog message will still make it to the NPM server.

I would think that Solarwinds will always be able to see one end of the link, so syslogs from it will be received. If it could not see the remote end then it would mark it as being down regardless. The issue the OP describes occurs if there's 2 ways to a single destination. So everything remains as being up but the primary link is no longer passing traffic.

rschroeder wrote:
Some other ideas, that don't involve changing icon colors (which I think is a pretty cool idea!) include:
Creating an automatic alert from Syslog to show your team immediately when BGP neighbor status or OSPF adjacency goes down
Creating a Critical Interfaces alert, then adding your most important interfaces to it. Some examples would be uplinks between switches, links on routers, etc. If you go this route, don't neglect to include the multiple physical ports that comprise a port-channel, since you'll want to know when some of your throughput and resilience has been lost due to one port in a multi-port port-channel being down. That's a reason why you shouldn't "only" monitor port-channels, but also their members.

I already use syslog to send me BGP messages. You can also do this via Advanced Alert Manager but the problem I found with it is the delay on how often it checks the alert. So a flapping BGP link will not necessarily be picked up by the Alert, but syslog will send you all the messages so you know what's going on. That's how I currently tell if all links are operational or not.

It would be nice to be able to mark interfaces as critical or not. I only put in interfaces that I think are critical but every now and then I need to know throughput on a device but then I'll get alerts if the device goes up and down. Sounds like a good feature request!

rschroeder

You've got it in one. Both traps AND syslog are necessary when timely notification is of the essence. And nothing beats a great graphic, so the quest for a color change when BGP or OSPF changes is a good one.

sja

Big problem with SNMP TRAP it is not part of Advanced Alert Manager.

When you like to have a single "alert flow" that respect all the custom properties ,groups ....

some elements have okay mibs that you can poll the data you need...

but some don't .

THAT where I think your NMS software should help with "some kind of alert correlation"

/SJA

asherbersh

So basically you all agree it is a great idea but you say it is not available now right ?

CourtesyIT

Never say Never. You are going to have to look at a Normal operating situation and then a negitive operating situation then locate the deltas. Then reverse engineer the software to alert/notify you of the undesirable event.

Good luck, there is a solution there. By then end of the journey you will be teaching all of us.