[alcatel-nsp] Question: VPRN service: "auto-bind ldp" andSDPbindings

[SMITH Anton]

Kila,

RSVP signalled paths will be preferred over LDP signalled paths.

Therefore, you can keep using auto-bind ldp, and if you specify an RSVP based sdp in your VPRN, then it will be preferred for traffic to the remote PE. All other traffic will use LDP signalled LSPs.

Hope this is helpful.

Regards,
Anton


-----Ursprungligt meddelande-----
Från: alcatel-nsp-bounces at puck.nether.net genom Kila Hsu
Skickat: on 2009-01-28 23:38
Till: alcatel-nsp at puck.nether.net
Ämne: [alcatel-nsp] Question: VPRN service: "auto-bind ldp" andSDPbindings
 
Hi,

I have a similar question about VPRN auto-bind ldp.
Say, I have several PEs in my VPRN service, and now I'm using auto-bind ldp for my core. And assume now I want to specify one "special" path that goes from PE1 to PE2, for which I would like to use an RSVP-signaled LSP so I can specify some TE parameters.

For routes between the other PEs, I don't really mind and would just keep using the LDP signaled paths.

The question is 

1. Can I only bind this LSP to an SDP and specify Spoke SDP for this one, while keeping all the others auto-bind ldp? 

or 

2. Do I need to disable auto-bind ldp, manually create the LDP-signalled SDPs and specify Spoke SDP for all these as well, in addition to the RSVP signalled SDP I'm interested in? 

I would prefer the first one since it would be a lot of work to create all these extra LDP- signalled SDPs. According to Wim's answer to the previous question, this would be solved by the new version by specifying auto-bind MPLS. However if there is already some solution other than creating extra SDPs I would be really happy.

thanks for your help.
Kila Hsu



      

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/alcatel-nsp/attachments/20090129/f8ece193/attachment.html>