OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Sina Mirtorabi (sinaCISCO.COM)
Date: Wed Jul 04 2001 - 01:13:15 CDT

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Umesh

    Umesh_MS wrote:

    > Heloo..
    >
    > According to RFC 2328, section 16.1.1, there are two case for
    > calculating next hop. The second case is for network. In that case I
    > didn't get that how to calculate next hop and outgoing interface..
    > can anybody explain this..(with the help of a figure)
    >
    > regards..
    >
    >
    > Umesh

    In the second case, the parent vertex is a network that
                directly connects the calculating router to the destination
                router. The list of next hops is then determined by
                examining the destination's router-LSA. For each link in
                the router-LSA that points back to the parent network, the
                link's Link Data field provides the IP address of a next hop

                router. The outgoing interface to use can then be derived
                from the next hop IP address (or it can be inherited from
                the parent network).

    R1 R2 R3
    | | |
    ---------------------------

    imagine R1 is root and R2 is the DR further R2 is the parent of R3
    if R2 was a router node and R1 didn't have a direct connection through a
    transit network to R3 in this case R3 will just inherit the outgoing
    interface and next hop from its parent ( R2 )
    here R2 is a transit node so as stated we check if R3 announce a link
    back to its parent ( R2 ) and the Link data field will give us the next
    hop address
    for outgoing interface it can be inherited from its parent ( R2 ) or
    found directly since we have an common interface with the next hop IP
    address

    Sina