Re: RIP MD5 follies

From: Chris McGuire (chris.mcguire333@gmail.com)
Date: Mon May 26 2008 - 22:14:49 ART


Also try removing the auth commands from the svi, delete and
reconfigure the key chain then after you have reconfigured the key
chain, add the auth commands to the svi. There are some order of
operation issues with this.

Hth
Chris

On May 26, 2008, at 5:59 PM, St Pancras <ccielab-groupstudy@mazehill.co.uk
> wrote:

> Could this be the perennial problem with "dead space" after the
> password??
> Go into config mode on BB2 and delete and re-enter the password to
> make sure there is no space there.
> Do the same for SW2.
>
> See if it works.
>
> Cheers
>
>
>
>
>
> Rik Guyler wrote:
>> I know I'm not the only one that despises MD5 authentication.
>> Seems like
>> there aren't too many other things in IOS-land that are as
>> unpredictable
>> when it comes to doing what it is supposed to be doing.
>>
>> I have SW2 and BB2 from an IE lab that are supposed to exchange RIP
>> routes
>> using MD5 authentication. I've reloaded both devices, verified the
>> configs
>> (yes, I cheated and looked at BB2 ;-) on both but the debugs on
>> both sides
>> continuously complain about the auth. I even checked the solution
>> guide and
>> my config is identical except the name of the key chain name.
>>
>> key chain RIP
>> key 1
>> key-string CISCO
>>
>> interface Vlan82
>> ip address 192.10.1.8 255.255.255.0
>> ip rip authentication mode md5
>> ip rip authentication key-chain RIP
>>
>> Anybody out there have a good method for clearing this type of mess
>> up?
>>
>> --
>> Rik
>>
>>
>> _______________________________________________________________________
 

>> Subscription information may be found at: http://www.groupstudy.com/list/CCIELab.html
>
>
> _______________________________________________________________________
 

> Subscription information may be found at: http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Mon Jun 02 2008 - 06:59:18 ART