All:

  One more small note here. When ever OSPF adjacency
  between R1 and R2 toggles, R2 should revisit all
  the External LSAs and change the Forwarding Address
  accordingly (either R1 interface address or 0.0.0.0)

Venkata.

-> Venkata,
->
-> Section 2.3 RFC2328 last paragraph, seems to suggest
-> something like what you
-> said.
->
-> Figure-16 is just used to give an example for AS-External
-> LSA's, however I
-> guess
->
-> Note that when the forwarding address
-> field is non-
-> zero, it "should" point to a router belonging to
-> another Autonomous System.
->
-> can be made to
-> Note that when the forwarding address
-> field is non-
-> zero, it "may" point to a router belonging to
-> another Autonomous System.
->
-> Also I guess(or I couldn't find it) nowhere in the RFC does
-> it say the link
-> can't be P2P, for the example in figure-16 though, it would
-> be helpful only
-> when the interface is of type broadcast.
->
-> Probably someone else will clarify on this too.
->
-> Thanks,
-> Vishwas
->
-> -----Original Message-----
-> From: Igor Miroshnik [mailto:IgorMRADLAN.CO.IL]
-> Sent: Sunday, February 17, 2002 11:07 AM
-> To: OSPFDISCUSS.MICROSOFT.COM
-> Subject: Re: Forwarding Address Issue
->
->
-> Venkata,
->
-> In the topology under consideration, how can R2 know that R1
-> has a link to
-> P? I reckon, R1 would not advertise P unless it was ASBR.
->
-> Igor
->
-> -----Original Message-----
-> From: Naidu, Venkata [mailto:Venkata.NaiduMARCONI.COM]
-> Sent: Sunday, February 17, 2002 1:18 AM
-> To: OSPFDISCUSS.MICROSOFT.COM
-> Subject: Forwarding Address Issue
->
->
-> All:
->
-> I have a doubt (just thinking about this issue) regarding
-> below statement in RFC2328.
->
-> Note that when the forwarding address field is non-
-> zero, it should point to a router belonging to
-> another Autonomous System.
->
-> For example, take below configuration.
->
-> (P)--//--(R1)------(R2)------(R3)
-> | |
-> ------------------
->
-> Conditions:
-> * All are P2P links with equal cost in same area.
-> * R2 is an ASBR exporting Prefix P with
-> next hop address as R1
-> * R1-R2-R3 are all fully adjacent.
->
-> 1. First, is it valid to have R1 as the forwarding address
-> in R2's ASE LSA to reach prefix P?
->
-> I think, it is valid to have forwarding address pointing
-> to R1 - because R3 can reach R1 directly with out
-> going an extra hop (R2) to reach destination P.
->
-> 2. If so, then the above statement in RFC2328 is not valid.
-> Because R1 is in the same AS.
->
-> 3. More over, note that there is no Broadcast network in the
-> topology (contrary to RFC2328 Figure 16)
->
-> Am I missing something here? ;-)
->
-> Venkata.
->

This e-mail and any attachments are confidential. If you are not the
intended recipient, please notify us immediately by reply e-mail and then
delete this message from your system. Do not copy this e-mail or any
attachment, use the contents for any purposes, or disclose the contents to
any other person: to do so could be a breach of confidence.

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