From: Alexei Monastyrnyi (alexeim@orcsoftware.com)
Date: Mon Mar 20 2006 - 05:31:55 GMT-3
sorry, I actually misinterpreted the question, thinking that it was in
"why adj doesn't work" whereas it was "why it happens when it
shouldn't"... but it is good to go through a tricky wording :-)
A.
on 18/03/2006 00:13 Alexei Monastyrnyi wrote:
> a couple of side notes ...
> 1. unless you use a "neighbour" statement under OSPF process, R3 and
> R4 will try to use a link-local multicast, but you don't have
> "broadcast" keyword in your map statements...
> 2. IMO R5 will not work as reflector for OSPF adj between R3 and R4
> (reason is the same - local-link multicast, TTL=1), those two will
> never form an adj in such a topology.
>
> Please correct me if I miss something.
>
> Cheers,
> A.
>
> ----- Original Message ----- From: "John Matus" <John.Matus@tokiom.com>
> To: <ccielab@groupstudy.com>
> Sent: Friday, March 17, 2006 9:36 PM
> Subject: ospf adj problem
>
>
>> R3
>> int s0/1
>> ip address 183.1.0.3 255.255.255.0
>> encapsulation frame-relay
>> ip ospf network broadcast
>> ip ospf priority 0
>> frame-relay map ip 183.1.0.4 335
>> frame-relay map ip 183.1.0.5 335 broadcast
>> no frame-relay inverse-arp
>>
>> router ospf 1
>> log-adjacency-changes
>> network 183.1.0.3 0.0.0.0 area 0
>>
>>
>> R4
>> interface Serial0/0
>> ip address 183.1.0.4 255.255.255.0
>> encapsulation frame-relay
>> ip ospf network broadcast
>> ip ospf priority 0
>> frame-relay map ip 183.1.0.3 405
>> frame-relay map ip 183.1.0.5 405 broadcast
>> no frame-relay inverse-arp
>> frame-relay lmi-type cisco
>>
>> router ospf 1
>> log-adjacency-changes
>> network 183.1.0.4 0.0.0.0 area 0
>>
>>
>> Regards,
>>
>> John D. Matus
>> Technical Support / PAS
>> Fujitsu Consulting
>> 626-568-7716
>> John.Matus@tokiom.com
>> ========================================================================================================
>>
>> This e-mail is intended solely for the individual to whom
>> it is
>> addressed. The information contained in this transmission
>> contains
>> confidential and/or proprietary information or is otherwise
>> privileged. If
>> the reader of this message is not the intended recipient, please be
>> advised
>> that any dissemination, distribution or copying of this
>> transmission is
>> strictly prohibited. If you have received this e-mail in error,
>> please
>> notify us immediately by returning it to the sender and deleting
>> this copy
>> from your system. Thank you for your cooperation.
>> ========================================================================================================
>>
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Apr 01 2006 - 10:07:39 GMT-3