I've recently begun utilizing ip sla monitoring and track statements on my routers to watch the availability of the next hop past my firewall. If the next hop is not available, the static route is updated per the following:
ip route 0.0.0.0 0.0.0.0 184.108.40.206 track 10
ip route 0.0.0.0 0.0.0.0 220.127.116.11 200 track 20
So when all is well and my local ISP is reachable, the 0.0.0.0 route points to my local firewall 18.104.22.168. If my local ISP is not reachable, the 0.0.0.0 route points to a different firewall located at 22.214.171.124. Because it has a higher administrative distance (200) if the primary comes back online, the primary takes over.
The question I have is there a way for me to send an SNMP trap or log to a syslog server if there is a change in what is considered to be the 0.0.0.0 route?
Searching these forums I learned that OID 126.96.36.199.188.8.131.52 will have all my route entries in it so I might be able to gather this from some sort of script but my preference would be to send a syslog or SNMP trap.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...