From: Williams, Glenn (WILLIAMSG@xxxxxxxxxxxxx)
Date: Fri Nov 30 2001 - 12:20:22 GMT-3
Yes the Ethernets are in a switch on different vlans. I'll disconnect the
Ethernets and give a keepalive of 0 on them and see what happens. Though it
sounds like I'm the switch is where you think it should be. Thanks for the
reply.
GW
-----Original Message-----
From: Jim Brown [mailto:Jim.Brown@CaseLogic.com]
Sent: Friday, November 30, 2001 9:10 AM
To: 'Ajaz Nawaz'; Williams, Glenn; 'routerkid'
Cc: ccielab@groupstudy.com
Subject: RE: Lab 4 vlinks
Are all of the routers Ethernet interfaces plugged into a switch?
Have the interfaces been segmented into different VLANs?
This could be due to noise the interface is hearing related to an
unsegmented switch. I might be hearing hello from a different area and this
is why it is complaining about a virtual link.
Check the VLAN configuration.
-----Original Message-----
From: Ajaz Nawaz [mailto:anawaz@cisco.com]
Sent: Friday, November 30, 2001 7:27 AM
To: Williams, Glenn; 'routerkid'
Cc: ccielab@groupstudy.com
Subject: RE: Lab 4 vlinks
This is interesting. Normal OSPF operation on p2p links is no DR/BDR
election. If your lab questions involves forcing DR/BDR election on p2p then
that might be one reason ' ip ospf network broadcast ' was used in the
answers that you have. BTW I havn't tried this - I was just trying to add
some logic to why one would set the net type on p2p to broadcast.
You may already know and anyone will tell you that it's pointless having
DR/BDR on p2p link since there are only two interfaces talking to one
another.
jaz
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Williams, Glenn
Sent: 30 November 2001 13:17
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