Cisco routers will send a trap on BGP peering changes. The following is an example config: snmp-server community private RW 1 snmp-server community public RO 2 snmp-server trap-authentication snmp-server enable traps envmon snmp-server enable traps bgp snmp-server enable traps frame-relay snmp-server host XXX.XXX.XXX.XXX public tty frame-relay isdn envmon bgp snmp You must enable traps for BGP events and then define the SNMP console "host" to receive those traps and list the traps you want sent to that host. Hope this helps, Chad ------------------------------------------ Chad Skidmore VP Operations & Engineering Data Source, L.L.C. http://www.dsource.com cskidmore@dsource.com
-----Original Message----- From: Curtis Generous [SMTP:generous@uucom.com] Sent: Thursday, June 05, 1997 7:07 AM To: nanog@merit.edu Subject: Loss of BGP peering monitoring via SNMP
We have been caught several times lately with some of our border routers loss of BGP peering going undetected for sometime. Is there a way to enable BGP peering loss monitoring via SNMP from a CISCO router? I've looked at both the public and private MIBS but haven't found anything.
I am aware of the 'nocol' package but really was hoping for an SNMP based approach to tie into our net-mgmt packages (sunnet and hpov).
TIA
--curtis -- Curtis Generous generous@uucom.com Phone: (703) 461-1350 UUcom Inc., Suite 250, 4875 Eisenhower Avenue, Alexandria, VA 22304-0797