Re: How to remove the offset-list in RIP?? Seriously..

Thanks for your comment. This is what I expected but I got someting else. I play on different platfom. I can't put "no offset-list in|out", see:

R1(config-router)#no off ?
  <0-99> Access list of networks to apply offset (0 selects all networks)
  <1300-1999> Access list of networks to apply offset (expanded range)

R1(config-router)#no off in
% Incomplete command.

However I can do "no off 0 in|out" since 0 means all networks. But why can we remove OL with named ACL using the same command with non-existent ACL 1 or 1000, ... ? :-)

It's a bug. I expect there a "NAME" option right after "no off". But this is only a visage problem. The worse one is with 3560 - If you have an access to 3560 with recent IOS, try to put a multiline "vacant-message" in "line con" mode. The switch will reboot.. :-)) I did it on two different boxes.

Regards,
Miroslav

On Jan 6, 2010, at 1:14 PM, GAURAV MADAN wrote:

> I understand your point .. u can call this is cli bug .. but there are
> so many places ..
> lemme explain how to look at this :
>
>
> Point 1
> =========
> I guess u will agree to point that there can b 1 and only 1 offset
> list on rip procedure .
>
> Point 2
> ======
> If u apply a offset-list say "test" and then apply offset-list "new"
> .. the OL "new" overwrites "test"
>
> C2900(config-router)#do sh run | sec rip
> router rip
> offset-list test in 15
> network 10.0.0.0
> C2900(config-router)#
> C2900(config-router)#offset-list new in 14
> C2900(config-router)#do sh run | sec rip
> router rip
> offset-list new in 14
> network 10.0.0.0
> C2900(config-router)#
>
>
> Point 3
> =======
> Since there can be 1 and only 1 offset list that can be applied to rip
> process ; while removing this ; CLI should not give any option .
> i.e following makes more sense
>
> router rip
> no offset-list {in|out} ?
> <cr>
>
> This shd take care of removing offset list in IN / OUT direction.
> although this is not the implementation ( rightly caught ) .. but one
> shd not get confused ..
>
> Hence
> if u have "offset-li in TEST 15" applied
> and you say
>
> no offset-list in NEW
>
> it will take away your TEST
>
>
> HTH
> Gaurav Madan
> CCIE
> On Wed, Jan 6, 2010 at 5:34 PM, Miroslav Kosut <miroslav.kosut_at_me.com> wrote:
>> Hello,
>>
>> just in case someone is interested ...
>>
>> I've been playing with RIP for a while and I found a small CLI bug. I configured the offset-list with named ACL. I got the expected behaviour, no problem with that. Then I was to remove the offset list, but here is what I found:
>>
>> R2(config-router)#no offset-list ?
>> <0-99> Access list of networks to apply offset (0 selects all networks)
>> <1300-1999> Access list of networks to apply offset (expanded range)
>>
>> R2(config-router)#no offset-list
>>
>> Oops :-) The funny thing is that you are still able to remove the offset-list with named-ACL using a CLI with "no offset-list 0" command, even "1" worked fine. I hope I won't be facing a similar issue during the lab :-)
>>
>> Here is my config and IOS version if someone is interested:
>>
>> R2(config-router)#do s run | be router rip
>> router rip
>> timers basic 10 30 30 40
>> passive-interface default
>> no passive-interface FastEthernet0/0
>> no passive-interface FastEthernet0/1
>> offset-list LOOPBACK-ACL out 1
>> network 2.0.0.0
>> network 10.0.0.0
>>
>> R2(config-router)#do s ver | i mz
>> System image file is "flash:c2600-entservicesk9-mz.124-15.T9.bin"
>>
>> Have a nice day!
>>
>> Regards,
>> Miroslav
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Wed Jan 06 2010 - 13:25:34 ART