From: Williams, Glenn (WILLIAMSG@xxxxxxxxxxxxx)
Date: Fri Nov 30 2001 - 11:21:09 GMT-3
Thanks. I'm very comfortable with RIDs and neighbors, etc. What is odd is
that if I shut down R3 and R5 on the frame, the error message goes away.
The v-link from R2 to R1 shows up good in all cases (show ip ospf virt) and
I can see routes between areas 10,5,1 & 0 on R1 and R2. If I bring back in
R3 and R5 and issue the area 5 virtual-link 10.10.1.3 and 10.10.1.5 on R2
only, I stop getting the error message. I should only have to establish a
vlink between R1 and R2 right? Not R2 to R1, R2 to R3 and R2 to R5 should
I?????????????? Thought this was going to be cake. :(
Also, no matter whether or not I get the error message, everything is
working. I can see all routes. I just put in the two additional vlinks on
R2 only to stop the error messages.
GW
-----Original Message-----
From: Bill Hill [mailto:bhill@sgdata.com]
Sent: Friday, November 30, 2001 7:59 AM
To: Williams, Glenn
Subject: RE: Lab 4 vlinks
I also have had this problem and even though I told myself, no, it IS
setup right. Invariably it wasn't. I'm not saying that your isn't
right but usually taking a break and looking again fixed it for me. ;-)
Whenever I configure virtual-links, I always always always use show ip
ospf neighbor and use the rid there. Remember, even though your configs
may be indentical to the bootcamp scenario, the OSPF RID is the ip
address of the highest loopback if one exists or the highest ip address
of a physical up interface. If you per chance started ospf, then
created the loopbacks that are referenced in the RID's of the bootcamp,
then the virtual-link configuration will not match exactly. The RID is
generated when you start OSPF.
If this message doesn't help, feel free to ignore it and throw it away.
:-)
Otherwise, HTH.
-Bill
or you can send the configs to the group.
-----Original Message-----
From: Williams, Glenn [mailto:WILLIAMSG@PANASONIC.COM]
Sent: Friday, November 30, 2001 8:17 AM
To: 'routerkid'
Cc: 'ccielab@groupstudy.com'
Subject: RE: Lab 4 vlinks
Thanks, but this is not the issue. I can't see any difference in my
setup
and the lab answers except they were using an ip ospf broadcast network
on
the point to point R1-R2.
GW
-----Original Message-----
From: routerkid [mailto:routerkid@adelphia.net]
Sent: Friday, November 30, 2001 6:55 AM
To: Williams, Glenn
Subject: Re: Lab 4 vlinks
I have seen this a number of times.. Make sure you are using the RID of
the
other router in your virtual-link statements. You can identify the RIF
by
doing sh ip ospf prot on each router to gather that information. Then
use
the RID of the remote router when you configure the virtual link...
HTH...
----- Original Message -----
From: Williams, Glenn <WILLIAMSG@PANASONIC.COM>
To: <ccielab@groupstudy.com>
Sent: Thursday, November 29, 2001 10:00 PM
Subject: Lab 4 vlinks
> Hi,
>
> Has anyone had the problem where this message is received on lab 4, R2
>
> 00:22:07: %OSPF-4-ERRRCV: Received invalid packet: mismatch area ID,
from
> backbone area must be virtual-link but not found from 10.10.1.5,
Serial0
>
> 00:22:16: %OSPF-4-ERRRCV: Received invalid packet: mismatch area ID,
from
> backbone area must be virtual-link but not found from 10.10.1.3,
Serial0
>
> Area 5 is configured as a v link between R1 and R2 to the OSPF router
ids.
> I have done v links successfully in the past.
>
> The problem goes away when I issue this command on R2 only:
>
> R2(config-router)#area 5 virtual-link 11.1.1.5
>
> R2(config-router)#area 5 virtual-link 10.33.1.65
>
> Did I miss something big on v-links?
>
> I looked at ccbootcamp answers and could not see any difference in my
> configs on ospf or serial lines.
>
> Reboot or clear ip ospf proc does not work either.
>
>
> GW
>
> MCSE (worthless) CCNP - the paper is nice I guess
> I have nothing cute to say.
This archive was generated by hypermail 2.1.4 : Fri Jun 21 2002 - 06:45:27 GMT-3