Thanks Nick/James for the replies
Yes , I mean MPLS LDP router-id
I understand the simplicity of inter-as VPN options and I wish it was the case 
They requested BGP in order for future VPLS connections as well 
We are using BGP at the moment as we are advertising the router-ids (public 
loopbacks) and am sure we can replace that via static

What is werid for me till now , why the session is passive 
Meanwhile , I have tested it on Cisco and worked like a charm 

BR,
Mohammad

> From: [email protected]
> Date: Tue, 11 Aug 2015 18:44:34 +0100
> To: [email protected]
> Subject: Re: [c-nsp] MPLS router-ID
> 
> On 11 August 2015 at 14:39, Mohammad Khalil <[email protected]> wrote:
> > I have one of my PEs already configured with a router-id (which is my 
> > private loopback interface)
> 
> I assume you mean LDP router-id?
> 
> > Am trying to establish xconnect with my uplink provider (which uses Juniper)
> > The SP insisted to use public IP address for LDP neighborship , I cannot 
> > change my router-id as I will lose all of my active L2VPN sessions in my 
> > network (according to what I know , I cannot have expect for one ID for my 
> > router)
> > I configured a public IP address and advertised it into BGP to my SP and 
> > the MPLS LDP session is up , but the targeted LDP session is passive !
> 
> What you say configured a public IP, do you mean on the interface
> facing the provider and then used something like "discovery
> transport-address interface" to use the interface IP as your LDP
> router-id?
> 
> Also why have you originated it into BGP? If you are using the public
> on on the interface facing your provider they should know IP because
> its directly connected.
> 
> On paper this configuration works but I'm not 100% clear of your explentaion.
> 
> As Nick has said, just having something like a tagged sub-interface
> between you and your provider where the xconnect terminates would be a
> better idea, the L3 VPNs can be in other sub-int's.
> 
> Cheers,
> James.
> _______________________________________________
> cisco-nsp mailing list  [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
                                          
_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to