[j-nsp] Fwd: OSPF Sham link question

[Sergio D.]

resending to the group.

David,

It was quite a while ago, and I don't have the details of it. All I remember
is that it worked :). I however have it currently set up with an all Cisco
environment, and is working as well.  I am pretty sure that a "show ospf
neighbor" for that instance will show the pe as a neighbor with interface as
the sham-link

R2#show ip ospf sham-links
Sham Link OSPF_SL1 to address 200.200.200.200 is up
Area 0 source address 100.100.100.100
  Run as demand circuit
  DoNotAge LSA allowed. Cost of using 1 State POINT_TO_POINT,
  Timer intervals configured, Hello 10, Dead 40, Wait 40,
    Hello due in 00:00:08
    Adjacency State FULL (Hello suppressed)
    Index 2/2, retransmission queue length 0, number of retransmission 0
    First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
    Last retransmission scan length is 0, maximum is 0
    Last retransmission scan time is 0 msec, maximum is 0 msec�

R2#show ip ospf neighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface
200.200.200.200   0   FULL/  -           -        200.200.200.200 OSPF_SL1�

BTW, the CE loopbacks do show up as type-1 LSA on the remote sides :)

HTH


- Show quoted text -


On Dec 7, 2007 9:13 AM, David Ball <davidtball at gmail.com> wrote:

>  Sergio,
>
>   In your tests, what indication did you see that the sham link was
> up and working as expected?  Did it appear as an OSPF neighbor in 'sh
> ospf neigh instance <name>' ?  did something specific occur in your
> log file (if you enabled one) that indicated 'sham link up!'.  I
> suppose one of the difficulties I'm having is that I don't know what I
> should expect to see from the sham link, nor can I tell if it's up or
> down.
>
> David
>
>
> On 07/12/2007, Sergio D. <sdanelli at gmail.com> wrote:
> > If this becomes an inter-area type-3 LSA, the remote PE-CE will always
> > prefer the on-demand back-up link. If this is correct, then I don't see
> the
> > point of a sham-link.
> > >From my tests this has worked as designed, if all routers are
> configured
> > with the same area with a sham-link between PE-PE then the LSA stays as
> a
> > type-1.
> >
> > http://www.juniper.net/techpubs/software/junos/junos84/swconfig84-vpns/id-10939238.html#id-10939238
>
> >
> > On Dec 7, 2007 3:13 AM, Daniel Lete <daniel.lete at heanet.ie> wrote:
> >
> > > Hello Sergio,
> > > In the PE where the CE is connected to, LSA Type-1 from CE should be
> seen
> > > as
> > > LSA Type-1
> > >
> > > In the remote PE, LSA Type-1 from that same CE should be seen as LSA
> > > Type-3
> > > (inter-area)
> > >
> > > Daniel
> > >
> > > Sergio D. wrote:
> > > > But you should at least be learning the loopbacks from each side as
>  a
> > > > type-1 LSA.
> > > > How are these routes showing on the PEs "show route protocol ospf
> table
> > > > sham-link-test"  ? I think I missed that output or sorry if it was
> > > already
> > > > mentioned.
> > > >
> > > >
> > > >
> > > > Message: 4
> > > > Date: Thu, 06 Dec 2007 15:04:03 +0000
> > > > From: Daniel Lete <daniel.lete at heanet.ie>
> > > > Subject: Re: [j-nsp] OSPF Sham link question
> > > > To: David Ball <davidtball at gmail.com>
> > > > Cc: juniper-nsp at puck.nether.net
> > > > Message-ID: < 47580F63.10905 at heanet.ie>
> > > > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> > > >
> > > > Hello David,
> > > > Your comment below:
> > > >  > (NB: is it normal that the routes PE2 is learning from the m10
> are
> > > > 'Extern' ?)
> > > >
> > > > may not be related at all with sham links or even with
> rfc2547/rfc4364.
> > > If
> > > > you
> > > > are injecting prefixes into OSPF (redistribute in Cisco or export in
> > > > Juniper)
> > > > in your CE, then those prefixes will appear as LSA Type-5 (external
> if
> > > you
> > > > want).
> > > >
> > > > Daniel
> > > >
> > > >
> > > >
>