Hi Matthew,
You must always specify the transit area when configuring a virtual link. So
use following command on both area border routers:
area transit-area virtual-link ip-address
The configs on page 310 are not correct, since the transit area in the
picture seems to be area 1. Moreover "are
Hi all,
I am studying the Cisco text "CCNP Routing" Exam Certification Guide and on
page 310 there is an example configuration:
Router Jack
interface loopback 0
ip address 10.10.10.33 255.255.255.0
router ospf 100
network 172.16.20.128 0.0.0.7 area 0
network 172.16.20.8 0.0.0.7 area 1
area 0 rang
As far as joining discontiguous nonzero areas, I would be interested to see
the configs...
-Jeremy
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Chuck
Sent: Thursday, April 25, 2002 6:29 PM
To: [EMAIL PROTECTED]
Subject: Re: OSPF Virtual-links [7:42565
In the world of OSPF, the virtual link end points are the router RID's This
is defined in the RFC.
with virtual links, the hello packet has the V bit set to 1. I believe that
the TTL of the IP packet transporting the VL hello is set to 255. In any
case, virtual link hellos are forwarded until suc
I think the VL must be defined on both routers using each others RID not
just any arbitraray interface) In your case maybe the time it worked just
happened to be when you defined the link with the RID.
Anthony Pace
""Jeremy"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> My qu
My question is regarding OSPF and virtual links. As you can see, I have
created an area 23 between R2 and R3 such that R3 will need a virtual link
defined in order to have a connection to Area 0. My question is, does R3
have to peer with an interface in R2 that is a member of area 0? I have
not
funny how this "quick fix" holds a such a place of prominence in the
standard ;->
Chuck
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 03, 2001 6:03 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: [Doyle on OSPF - Vir
,blah,blah.
1 of 48
Subj: RE: [Doyle on OSPF - Virtual Links [7:21658]
Date: Tue, 2 Oct 2001 8:35:54 PM Eastern Daylight Time
From: "Chuck Larrieu"
To: [EMAIL PROTECTED]
er 02, 2001 7:36 AM
To: [EMAIL PROTECTED]
Subject: Re: [Doyle on OSPF - Virtual Links [7:21658]
This is referring to the fact that the virtual-link is being treated as a
Demand Circuit. I don't believe that Doyle spoke much about this in his
book,
but I could be wrong. A Demand Circuit is us
: Tuesday, October 02, 2001 10:36 AM
To: [EMAIL PROTECTED]
Subject: Re: [Doyle on OSPF - Virtual Links [7:21658]
This is referring to the fact that the virtual-link is being treated as a
Demand Circuit. I don't believe that Doyle spoke much about this in his
book,
but I could be wrong. A Demand Ci
Sorry, I meant to say that it is a requirement for a router that
supports demand circuits to always attempt to make virtual-
links act as demand circuits.
> It is a
> requirement for a router that supports virtual-links to always try to make
it
> a demand circuit, so Cisco routers will always att
This is referring to the fact that the virtual-link is being treated as a
Demand Circuit. I don't believe that Doyle spoke much about this in his
book,
but I could be wrong. A Demand Circuit is used for low-bandwidth links such
as ISDN to limit the uptime required for the link, this is done in t
Hi.
On Routing TCP/IP's page 555 there is an output of "show ip ospf
virtual-link"
That has these two info:
1. DoNotAge LSA not allowed
2. Adjacency State FULL (Hello suppressed)
Can someone please explain why these show up in the virtual link info?
I must have missed the significance so
Looks like you have E0 of dogbert (area 1) in the same ethernet broadcast
domain as E3
of aspen (Area 0).
The only reason you are not seeing a similar message in dogbert is cause
your console
logging level is differnet in dogbert
DaveC
Shahid Muhammad Shafi wrote:
> Hi Guys.
> I am conf
Hi Guys.
I am configuring a virtual link between two OSPF
routers but it is not working at all. I am sending u
the configuration and diagram here;. Any help and
pinters will be appreciated.
Regards
Shahid
=
Shahid Muhammad Shafi
MSc Telecommunications Candidate
University of Colorado Boulder
rface command.
>From: "Arthur Simplina" <[EMAIL PROTECTED]>
>Reply-To: "Arthur Simplina" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: OSPF virtual links
>Date: Sun, 08 Apr 2001 20:15:15 -0400
>
>My c
My comments follow below. Please let me know how it worked out.
---
> >OSPF virtual links. Here's my configs: > >R2503 - backbone router
> >hostname r2503 >!
> >router ospf 100 &
At 03:59 PM 4/7/01 -0400, Fred Danson wrote:
>interface Serial0
>ip address 192.1.1.1 255.255.255.0
>no ip directed-broadcast
>ip ospf interface-retry 0 < see CCO link below
>no ip mroute-cache
>no fair-queue
http://www.cisco.com/warp/public/104/28.shtml
Stefan
__
ter configs and sh commands as well as the
capture of the successful ping, but I'll reserve posting them
to save bandwidth until I hear if you rebooted and cleaned up
the configs and your problem still exist.
Stefan
>Hey group,
>
>I am in the middle of Lab #30 from the CCIE Lab Stu
Hey group,
I am in the middle of Lab #30 from the CCIE Lab Study Guide which involves
OSPF virtual links. Here's my configs:
R2503 - backbone router
hostname r2503
!
!
ip subnet-zero
!
!
!
interface Loopback0
ip address 1.1.1.1 255.255.255.0
no ip directed-broadcast
!
interface Ethernet0
eu
Cc: Bryant Andrews
Subject: Revisted - OSPF Virtual Links and RIDs
Chuck,
I finally got a chance to mock this up in the lab and I've
got
some pretty cool resultsFirst of all when I did this using pretty much
the same scenario the virtual link never went down at
ea or
is connected by the same process a virtual-link
Just some observations..
Any thoughts...!
This is some really cool stuff.
Nigel.
- Original Message -
From: Chuck Larrieu <[EMAIL PROTECTED]>
To: CCIE_Lab Groupstudy List <[EMAIL PROTECTED]>
Sent: Sunday, December 2
22 matches
Mail list logo
