[j-nsp] OSPF NBMA

Harry Reynolds harry at juniper.net
Fri Mar 27 14:48:56 EDT 2009


I would try adding the multipoint keyword under the interface unit, and
also add mapping for each remote dlci. The latter is needed due to lack
of inarp response (if that is still the case).

 unit 0 {
<<<<<multipoint;
      dlci 100;
      family inet {
          address 10.0.2.5/30{
	<<<<<<	multipoint-destination 10.0.2.6 dlci 100;
	 }
    }
 }

At both ends.


HTHs



-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Sean Clarke
Sent: Friday, March 27, 2009 9:48 AM
To: Aamir Saleem
Cc: Juniper Puck
Subject: Re: [j-nsp] OSPF NBMA


If I were you I'd turn on some OSPF traceoptions ... it might tell you
why it's not working

cheers
Sean


On 3/27/09 11:58 AM, Aamir Saleem wrote:
> Hi All,
>
> I am having problem to established NBMA relationship between two P2P 
> SONET interfaces with frame-relay encapsulation. Can anyone tell me 
> what is wrong with the following interface and ospf configuration or 
> what else need to be added to have neighbor established. I am able to 
> ping P2P ips and NBMA is working fine on multipoint interface
configuration.
>
> *A-END Configuration*
>
> LAB1<r at LAB1># show interfaces so-0/2/1 hold-time up 30 down 30; 
> encapsulation frame-relay; lmi {
>      n391dte 1;
>      n392dte 2;
>      n393dte 3;
>      t391dte 15;
>      lmi-type itu;
> }
> unit 0 {
>      dlci 100;
>      family inet {
>          address 10.0.2.5/30;
>      }
> }
> [edit]
> LAB1<r at LAB1># show protocols ospf
> area 0.0.0.0 {
>      interface so-0/2/1.0 {
>          interface-type nbma;
>          neighbor 10.0.2.6 eligible;
>      }
> }
> [edit]
> LAB1<aamir at LAB1>#
>
> *B-END Configuration*
> **
> LAB2<r at LAB2># show interfaces so-0/2/1 dce; hold-time up 30 down 30; 
> encapsulation frame-relay; lmi {
>      n392dce 2;
>      n393dce 3;
>      t392dce 25;
>      lmi-type itu;
> }
> unit 0 {
>      dlci 100;
>      family inet {
>          address 10.0.2.6/30;
>      }
> }
> [edit]
> LAB2<r at LAB2># show protocols ospf
> area 0.0.0.0 {
>      interface so-0/2/1.0 {
>          interface-type nbma;
>          neighbor 10.0.2.5 eligible;
>      }
> }
> [edit]
> LAB2<aamir at LAB2>#
>
>
> some ospf outputs
>
> LAB1<r at LAB1># run show ospf interface
> Interface           State   Area            DR ID           BDR ID
> Nbrs
> so-0/2/1.0          DR      0.0.0.0         10.0.5.1
> 0.0.0.0            0
> so-0/2/1.0          DR      0.0.0.0         10.0.5.1
> 0.0.0.0            1
> [edit]
> aamir at LAB1# run show ospf neighbor
> Address          Interface              State     ID               Pri
Dead
> 10.0.2.6         so-0/2/1.0             Down      0.0.0.0            0
0
> 10.0.2.6         so-0/2/1.0             Attempt   0.0.0.0            0
0
> [edit]
> aamir at LAB1#
>
> Why we have two interface and neighbor entries in "show ospf 
> interface" and "show ospf neighbor"?
>
>
>
> Regards.
> Aamir
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
>    

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


More information about the juniper-nsp mailing list