OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Alex Zinin (azininNEXSI.COM)
Date: Tue Sep 04 2001 - 18:02:33 CDT

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

    sdf,

      To clarify, the fwd address indeed describes a
      router in another AS, but, at the same time, the
      address needs to belong to a subnet within the
      local OSPF domain so other routers can calculate
      a path to it.

    --
    Alex Zinin
    

    Thursday, August 02, 2001, 11:22:14 PM, sdf sdaf wrote:

    > Hi...

    > According to RFC2328 16.5 case:1

    > if the router is an area border router attached > to one or more transit areas, the calculation in > Section 16.3 must be run again for the single > destination. If the results of these calculations > have changed the cost/path to an AS boundary router > (as would be the case for a Type 4 summary-LSA) or to > any forwarding addresses, all AS-external-LSAs will > have to be reexamined by rerunning the calculationin > Section 16.4.

    > But in RFC 2328 section 12.4.4.1.. > "Note that when the forwarding address field is non- > zero, it should point to a router belonging to > another Autonomous System"

    > Actually in inter area calculation we can find out > destination inside AS. > can anybody explain how we can find out the change in > forwarding address in in inter area calculation..

    > thanks in advance..

    > kannan

    > __________________________________________________ > Do You Yahoo!? > Make international calls for as low as $.04/minute with Yahoo! Messenger > http://phonecard.yahoo.com/