From: Joe Harris (joeh@xxxxxxxxxxxxxxxxx)
Date: Fri Apr 28 2000 - 12:50:45 GMT-3
Wyan:
Clifton is correct in the fact that the (area 1 virtual-link <RID address> mess
age-digest-key <key> md5 <key name>) is needed on both router R2 and
R3. Also you will need to add to R3, under your (router ospf #) this command:
(area 0 authentication message-digest).
Router 3, (with the virtual-link command enabled) is "directly" connected to ar
ea0. Although it does not technically have any area's in area0, it is exchangin
g
updates with area0, not area1. This, with the md5 enabled on your virtual-link
will solve your problem.
-Joe
"6 days left till the big dance in RTP"
*********** REPLY SEPARATOR ***********
On 4/28/00 at 12:55 AM Clifton Stewart wrote:
>Wyan,
>
>On your statement area 2 virtual link (md5 authentication) is needed.
>Try enabling authentication on both sides of the virtual link, then
>issue debug ip ospf packet. This should resolve your problem.
>
>Clifton Stewart-CCNA, CCIE Candidate
>
>wyan@ca.ibm.com wrote:
>>
>> Hi, there,
>>
>> I tried to config the following network but couldn't get the virtual link
>> up.
>>
>> R1--Area0--- R2---Area1---R3---Area3----R4
>>
>> Area 0 using MD5
>> Virtual link between R2/R3
>>
>> Looks like R2 is checking incoming hello from R3 with MD5(type 2) but
>> couldn't make
>> R3 to talk in MD5. Have tried enabling MD5 in area1 and/or area3 but R3
>> still sent
>> type 0 hello to R2 on the virtual link. R2 is version 11.2 and R3 is 12.05.
>>
>> Any help would be appreciated. Thanks.
>>
>> Weidong Yan
>>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:16 GMT-3