Re: Proactive monitoring of IP SLA with SNMP

The MIB to track IP SLA parameters are CISCO-RTTMON-MIB.
But remember that IP SLA and TRACK are too seperate things.

With IP SLA you can enable traps by using:
#ip sla monitor logging traps

And your SNMP with :
#snmp-server enable traps rtr
#snmp-server host {ip} traps {community}

The Track Statement by default loggs its status to the logging buffer.
This you have seen "%TRACKING-5-STATE: 1 interface Di1 ip routing Up->Down"
That can be sent to a server via syslog with "#logging {host-ip}"

Alternatively the logging buffer messages could be sent via SNMP traps too with
#snmp-server enable traps syslog.

HTH

On Wed, May 12, 2010 at 8:15 PM, Edouard Zorrilla <ezorrilla_at_tsf.com.pe> wrote:
> Good, let me test on.
>
> As a matter of fact, I have two types of primary intefaces, dialer and
> FastEthernet with dhcp. Even though primary BroadBand with DHCP is down, "snmp
> trap link-status " will show the interface always as UP, because the patch
> cord cable is always connected to the modem.
>
> Whit FasEthernet I have set up routers in the next motion :
>
> PE0267#track 1 ip sla 1
> PE0267#ip sla 1
> icmp-echo <Public GW.1> source-interface FastEthernet4
> frequency 6
> PE0267#ip sla schedule 1 life forever start-time now
>
> PE0267#sh run | i ip route 0.0.0.0
> ip route 0.0.0.0 0.0.0.0 FastEthernet4 <Public IP GW1> track 1
> ip route 0.0.0.0 0.0.0.0 Vlan2 <Public IP GW2> 100
> PE0267#
> PE0267#sh inventory
> NAME: "881", DESCR: "881 chassis,
>
> So, in this case, FastEthernet will never go down since it has L2 conectivity
> against the modem. Nevertheless, primary BroadBand line is already down with
> no ip address :
>
> PE0267#sh ip int brief | ex down
> Interface IP-Address OK? Method Status
> Protocol
> FastEthernet0 unassigned YES unset up up
> FastEthernet2 unassigned YES unset up up
> FastEthernet3 unassigned YES unset up up
> FastEthernet4 <Public IP1> YES DHCP up up
> Tunnel10 172.xx.117.67 YES manual up up
> Tunnel20 172.yy.117.67 YES manual up up
> Vlan1 10.xy.67.1 YES NVRAM up up
> Vlan2 <Public IP2> YES DHCP up up
> PE0267#
>
> In that case, the only chance that I have is to monitor primary is the
> message from track feature :
>
> "Apr 27 2010 01:56:50 PDT: %TRACKING-5-STATE: 1 ip sla 1 state Up->Down",
>
> Then default gateway will move from <Public IP GW1> to <Public IP GW2>.
>
> I will need to send this "%TRACKING-5-STATE: 1 ip sla 1 state Up->Down" as a
> trap to a snmp host and display a error here. So again the idea would be send
> snmp traps instead of polling from router. Would it be all right ?
>
> Thanks
>
> Regards
>
>
> ----- Original Message -----
> From: "eseosa" <eseosa.ehiwe_at_gmail.com>
> To: "Edouard Zorrilla" <ezorrilla_at_tsf.com.pe>
> Cc: <security_at_groupstudy.com>; <ccielab_at_groupstudy.com>
> Sent: Wednesday, May 12, 2010 10:49 AM
> Subject: Re: Proactive monitoring of IP SLA with SNMP
>
>
>> Hi Edouard ,
>>
>> Since the dialer interface is you primary interface you will be
>> interested in its line protocol status .
>>
>> rather than worrying about a tracking mib you can enable link status
>> traps on the dialer interface using the command below:
>> int dialer 1
>> snmp trap link-status
>>
>> and configure other snmp related commands(snmp-server community ,
>> snmp-server host etc)
>>
>>
>> HTH
>>
>>
>>
>>
>>
>> On 5/12/10, Edouard Zorrilla <ezorrilla_at_tsf.com.pe> wrote:
>>> Hello Guys,
>>>
>>> I hope you can help me with this. Here we have routers with two internet
>>> access (DMVPN Network), one is the principal and the other one is the back
>>> up.
>>>
>>> We have set up the router in this way :
>>>
>>> track 1 interface Dialer1 ip routing
>>> ip route 0.0.0.0 0.0.0.0 Dialer1 track 1
>>> ip route 0.0.0.0 0.0.0.0 Vlan2 dhcp 100
>>>
>>> PE0001#CA0269#sh ip int brief | ex down
>>> Interface IP-Address OK? Method Status
>>> Protocol
>>> Dialer1 <Public IP1> YES IPCP up
>>> up
>>> FastEthernet0 unassigned YES unset up
>>> up
>>> FastEthernet1 unassigned YES unset up
>>> up
>>> FastEthernet2 unassigned YES unset up
>>> up
>>> FastEthernet3 unassigned YES unset up
>>> up
>>> FastEthernet4 unassigned YES NVRAM up
>>> up
>>> Tunnel10 172.xx.117.69 YES NVRAM up
>>> up
>>> Tunnel20 172.yy.117.69 YES NVRAM up
>>> up
>>> Virtual-Access1 unassigned YES unset up
>>> up
>>> Vlan1 10.1xy.69.1 YES NVRAM up
>>> up
>>> Vlan2 <Public IP2> YES DHCP up
>>> up
>>> PE0001#
>>>
>>> PE0001#sh inventory
>>> NAME: "881", DESCR: "881 chassis.
>>>
>>>
>>> So, if dialer 1 get into a issue, default gateway move to be the secondary
>>> line. As soon as "track 1" senses that dialer is in a issue, it will show
> us
>>> a
>>> message :
>>>
>>> %TRACKING-5-STATE: 1 interface Di1 ip routing Up->Down
>>>
>>> My question is, how can I make that snmp take care of this message ? I
> want
>>> to
>>> respond to issues at the first sign of a problem, I mean when primary
>>> internet
>>> line is down. It would be very good that a Open Source solution (CACTI or
>>> Nagios ) could send me one email and show one alarm in monitor tab.
>>>
>>> But I do not know yet, how can I get the MIB for "track" feature on Cisco
>>> IOS.
>>> If I guess that If I am able to get the MIB for track command I would be
>>> able
>>> to monitor my cisco router when the primary line is down.
>>>
>>> Thanks a lot for your time,
>>>
>>> Regards
>>>
>>>
>>> Blogs and organic groups at http://www.ccie.net
>>>
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Warm Regards,
>>
>> Eseosa
>> CCIE #23782
>> Before God we are all equally wise - and equally foolish.
>> Albert Einstein
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>

-- 
<ruhann>
www.routing-bits.com
Blogs and organic groups at http://www.ccie.net