Re: Link state protocol

Cool! I just want to add as well that by shutting down the link on R2 -- On
R2 you will see the LSA go away, but on routers that R2 peered up with, the
route will be removed but the LSA will remain in the DB until the age
expires. You can see the LSA age in the command below as well in seconds.

On Thu, Sep 17, 2009 at 5:43 AM, jack daniels <jckdaniels12_at_gmail.com>wrote:

> Thanks joe :) got it now :)
>
> On Thu, Sep 17, 2009 at 3:06 PM, Joe Astorino <jastorino_at_ipexpert.com>wrote:
>
>> If the link is shut down you will not see it in the database...below you
>> see that I shutdown the serial link on R2 and as a result 2 of the 3 LSAs
>> went away (only the loopback remains)
>>
>> R2(config)#int s0/1/0
>> R2(config-if)#shutdown
>>
>> R2(config-if)#do sh ip ospf data router
>>
>> OSPF Router with ID (2.2.2.2) (Process ID 1)
>>
>> Router Link States (Area 0)
>>
>> LS age: 10
>> Options: (No TOS-capability, DC)
>> LS Type: Router Links
>> Link State ID: 2.2.2.2
>> Advertising Router: 2.2.2.2
>> LS Seq Number: 80000064
>> Checksum: 0xDFD6
>> Length: 36
>> Number of Links: 1
>>
>> Link connected to: a Stub Network
>> (Link ID) Network/subnet number: 2.2.2.2
>> (Link Data) Network Mask: 255.255.255.255
>> Number of TOS metrics: 0
>> TOS 0 Metrics: 1
>>
>>
>> On Thu, Sep 17, 2009 at 5:32 AM, jack daniels <jckdaniels12_at_gmail.com>wrote:
>>
>>> Hi,
>>>
>>> where is the state of the LINK ( up/down) in the output.
>>>
>>> Regards
>>>
>>> On Thu, Sep 17, 2009 at 3:00 PM, Joe Astorino <jastorino_at_ipexpert.com>wrote:
>>>
>>>> Check out the LSDB. Here is an example of a type-1 LSA stored in the
>>>> link-state database on a router
>>>>
>>>> R2#sh ip ospf data router
>>>>
>>>> OSPF Router with ID (2.2.2.2) (Process ID 1)
>>>>
>>>> Router Link States (Area 0)
>>>>
>>>> LS age: 498
>>>> Options: (No TOS-capability, DC)
>>>> LS Type: Router Links
>>>> Link State ID: 2.2.2.2
>>>> Advertising Router: 2.2.2.2
>>>> LS Seq Number: 80000063
>>>> Checksum: 0x1569
>>>> Length: 60
>>>> Number of Links: 3
>>>>
>>>> Link connected to: a Stub Network
>>>> (Link ID) Network/subnet number: 2.2.2.2
>>>> (Link Data) Network Mask: 255.255.255.255
>>>> Number of TOS metrics: 0
>>>> TOS 0 Metrics: 1
>>>>
>>>> Link connected to: another Router (point-to-point)
>>>> (Link ID) Neighboring Router ID: 6.6.6.6
>>>> (Link Data) Router Interface address: 150.100.100.2
>>>> Number of TOS metrics: 0
>>>> TOS 0 Metrics: 64
>>>>
>>>> Link connected to: a Stub Network
>>>> (Link ID) Network/subnet number: 150.100.100.2
>>>> (Link Data) Network Mask: 255.255.255.255
>>>> Number of TOS metrics: 0
>>>> TOS 0 Metrics: 0
>>>>
>>>>
>>>>
>>>> On Thu, Sep 17, 2009 at 5:15 AM, jack daniels <jckdaniels12_at_gmail.com>wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Thanks , but where can I see the output of Links State ( up/down ) in
>>>>> OSPF
>>>>> database or routing table .
>>>>>
>>>>> Regards
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Sep 17, 2009 at 1:48 PM, Abraham, Tharak <
>>>>> tharakabraham_at_gmail.com>wrote:
>>>>>
>>>>> > Flooding is the only method by which all the neighbors will have the
>>>>> same
>>>>> > database.
>>>>> >
>>>>> > One LSA is sent per each routers link with the details like
>>>>> >
>>>>> > 1. identifying the link --> network
>>>>> > 2. state of the link ---> up/down
>>>>> > 3. metric cost --> interface cost to the link
>>>>> > 4. any other links attached to that link --> neighbors on that link
>>>>> >
>>>>> >
>>>>> >
>>>>> > Best Regards,
>>>>> > Tharak Abraham Luke
>>>>> > Sent from Netherlands
>>>>> >
>>>>> > On Thu, Sep 17, 2009 at 9:25 AM, jack daniels <
>>>>> jckdaniels12_at_gmail.com>wrote:
>>>>> >
>>>>> >> Hi All,
>>>>> >>
>>>>> >> When we say Link state protocols flood link information to build to
>>>>> >> complete
>>>>> >> topology. >>>>
>>>>> >> Please help me in understanding what does it mens flood link
>>>>> >> information >>>>> as in OSPF or ISIS we see next hop cost .....but
>>>>> where
>>>>> >> is
>>>>> >> link states . Does link state mean Link State ( physicall state
>>>>> up/down)
>>>>> >>
>>>>> >> Regards
>>>>> >>
>>>>> >>
>>>>> >> Blogs and organic groups at http://www.ccie.net
>>>>> >>
>>>>> >>
>>>>> _______________________________________________________________________
>>>>> >> Subscription information may be found at:
>>>>> >> http://www.groupstudy.com/list/CCIELab.html
>>>>>
>>>>>
>>>>> Blogs and organic groups at http://www.ccie.net
>>>>>
>>>>> _______________________________________________________________________
>>>>> Subscription information may be found at:
>>>>> http://www.groupstudy.com/list/CCIELab.html
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>>
>>>> Joe Astorino - CCIE #24347 R&S
>>>> Technical Instructor - IPexpert, Inc.
>>>> Cell: +1.586.212.6107
>>>> Fax: +1.810.454.0130
>>>> Mailto: jastorino_at_ipexpert.com
>>>>
>>>
>>>
>>
>>
>> --
>> Regards,
>>
>> Joe Astorino - CCIE #24347 R&S
>> Technical Instructor - IPexpert, Inc.
>> Cell: +1.586.212.6107
>> Fax: +1.810.454.0130
>> Mailto: jastorino_at_ipexpert.com
>>
>
>

-- 
Regards,
Joe Astorino - CCIE #24347 R&S
Technical Instructor - IPexpert, Inc.
Cell: +1.586.212.6107
Fax: +1.810.454.0130
Mailto:  jastorino_at_ipexpert.com
Blogs and organic groups at http://www.ccie.net