BRI interfaces status check

Yes. Any NMS worthy of the description should do this. As an example, I use Zabbix to poll the ifOperStatus of interfaces I'm interested in.

You do not have to, as you could send remote syslog and have your syslog server alert you when it sees an up/down message. However, SNMP is the cross-platform standard way of doing this so will probably be easier.

As for performance, it's impossible to measure something without affecting it, but so long as you're not polling every 5 seconds or something silly like that you shouldn't notice. You can also have a device send an SNMP 'trap' to inform you of the interface changing status.

And finally, for a higher-level overview of how things are working, you can poll the next hop of a particular route with SNMP to see which way traffic is flowing, although this may not apply to your network topology.

Thank you for your time and information, Alexd. I'm thinking of trying MRTG.

Giorgos

ce be affected by

ance be affected by

MRTG can for sure do the job but I suspect that it is no longer in development (years ago now) and that you might be better investing your time in something else.

I have not used it but Cacti seems to be recommended.

Strange comment. The latest release of MRTG is from 20-Jan-2010.

However, it's more a measurement tool than alerting. I measure traffic on a whole pile of BRIs with it, but for notification there are a number of SNMP tools, including your suggestion of Cacti.

Hmm. Appears I was completely wrong. Sorry.

I recall looking at MRTG a few years ago and for some reason decided that development had been stopped.

I mentioned MRTG, because I'm already using it on some of our routers to check the speed utilization. It would be great if I set it up to include the BRI interfaces as well. Though it will take lots of time and research to setup all those MIBs and OIDs, it would be very interesting. Alerting is not on my plans yet, that's why MRTG would be one of the best solutions.

Thanks again!

Giorgos

Not at all, it only requires that you add the BRI interfaces to the mrtg.cfg the same way you add all other interfaces.

Make sure you don't use the numerical interface number as that is going to change.

Something like this will work:

Target[router.20]: \BRI1/0\:1:public@router SetEnv[router.20]: MRTG_INT_IP="" MRTG_INT_DESCR="BRI1/0:1" (plus the remainder of a normal entry in mrtg.cfg)

From IOS 12.1 one can use: snmp-server ifindex persist may apply globally or at the interface level