Hi, Scott.
To monitor ospf adjancency or something like that, we usually have two
routers connected to each other via Ethernet interfaces in a normal
lab environment. In this case, before adjacency is built, old router
LSA lists the Ethenet interface's network as Link Type 3 - "connection
to a stub network" because no neighbor's found, but after adjacency
built, new router LSA lists it as Link Type 2 - "connection to a
transit network".
You can check this with "show ip ospf database router" before and
after ospf adjacency built.
http://www.isi.edu/in-notes/rfc2328.txt pp.207-208
Hope this helps
Regards
Jaeheon
On 10 Jan 2001 01:08:17 -0500, [EMAIL PROTECTED] (scott) wrote:
>Dear OSPF gurus:
>
>I am probably missing a very basic point here as I am somewhat new to
>OSPF. I have been debugging ospf adjacency, ospf events, ospf flood
>plus some others. After routers become adjacent, the flooding process
>starts. What I have noticed is that right after routers become
>adjacent, they create a new router LSA and add one to the sequence
>number. (The DR also sends out a network LSA.)
>
>My question is this: Does each router create this new instance of the
>LSA to trigger the flooding process itself or is there some other reason
>why a "new" LSA is created? *Why not just send out the original LSA to
>begin the flooding process?* Doesn't sending out a new LSA cause
>routers to recalculate their routing tables when, in fact, they just
>calculated them moments ago when they became adjacent using the original
>LSA?
>
>I understand the need for the flooding process. I don't understand the
>need for a new LSA.
>
>Thanks in advance,
>
>Scott Chapin
>
>_________________________________
>FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
