[c-nsp] Object tracking

[Dean Smith]

Method 1) looks like this...

track 1 interface Fa0/0 line-protocol
track 2 list boolean
  object 1 not
ip route 1.1.1.1 255.255.255.255 null0 track 2

Dean
----- Original Message ----- 
From: "Dean Smith" <dean at eatworms.org.uk>
To: "Gary Roberton" <gary.ciscomail at gmail.com>; <cisco-nsp at puck.nether.net>
Sent: Thursday, May 29, 2008 4:24 PM
Subject: Re: [c-nsp] Object tracking


> Method 1)
>
> Create an object to track the interface state
> Create a boolean object to reverse the state of the first object.
> Add a /32 static route to Null0 for the Tunnel Destination IP dependant on 
> the 2nd object.
>
> If the interface is up Object 1 = True, Object 2 = False, Null0 route wont 
> be installed. Tunnel Stays up.
> If the interface is down, Object 1 = False, Object 2 = True, Static route 
> installed, Tunnel goes down.
>
> You'll need 12.4T I think to get all those bits.
>
> Method 2)
>
> Use the EEM to detect the interface down on the tracked interface - and 
> trigger a CLI action to shut the tunnel interface
> (and the reverse aswell)
>
> Dean
> ----- Original Message ----- 
> From: "Gary Roberton" <gary.ciscomail at gmail.com>
> To: <cisco-nsp at puck.nether.net>
> Sent: Thursday, May 29, 2008 4:01 PM
> Subject: [c-nsp] Object tracking
>
>
>> This one could be interesting...
>>
>> I have a tunnel interface that I only want to be up when the ethernet
>> interface on the router is up.  I don't want to relate the tunnel to the
>> address of the ethernet, I need these to be separate.
>>
>> So, does anyone know if I can shut the interface if the status of the 
>> object
>> changes?  If you have any example code that would be great...
>>
>> Thanks
>>
>> Gary
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>