I would like to create as IP SLA for our remote Internet circuits that will trigger an alert when not working. This way we will be alerted even if the Outside interface remains up and pingable. The architecture is such that if the Internet is down at a remote site, all Internet traffic from that site will traverse the WAN pipe.So, we might never find out that the Internet is down at the remote site.
Should I create an IP SLA that is constantly pinging an address and trigger an alert when that IP SLA fails?
If so, would it be bettter to ping a known public IP address (184.108.40.206) or one of our own and configure the IP SLA operation only to ping the address via the Internet circuit?
The bgp neighborship could be up - and internet still down, I'm not sure but enabling bgp trap may not work in this case. I think we want to achieve full internet connectivity monitoring from the sites not just bgp specific events.
Please rate useful posts & remember to mark any solved questions as answered. Thank you.
Hello Pat, this is a good idea, however perhaps one small problem which you may have thought about already.
Lets say we have site A with internet circuits, bgp peering with ISP etc... If you have a backup route for all your internet traffic through your WAN, in theory the ping will never stop working even when the internet links are broken along the path.
So I would possibly do this...
create a static route to 220.127.116.11 via the bgp peer which is recommended or static out the interface connecting to the ISP BGP peer.
Create IP SLA to ping at 18.104.22.168
You have couple of options - EEM script, syslogs, SNMP Traps to trigger the alert.
One problem with the static route though pointing towards your bgp peer, if the interface was to go down, I believe that the static route will no longer be in the routing table, so this is a down side. But then one would assume you are monitoring the interfaces themselves. Therefor you have the option of pointing the static route at the interface for exit point.
R1(config)#ip route 22.214.171.124 255.255.255.255 x.x.x.x name ##IPSLA-VIA-BGP##
R1(config)#ip sla 1
R1(config-ip-sla)# icmp-echo 126.96.36.199
R1(config-ip-sla-echo)# frequency 5
R1(config)#ip sla schedule 1 life forever start-time now
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...