[alcatel-nsp] alcatel-nsp Digest, Vol 72, Issue 3

Tue Sep 13 11:26:53 EDT 2016

That's not considered good design. If you absolutely must have a topology
like this then use an OSPF virtual link. I really wouldn't go down this
road if I was you.

If you wanted to go completely mad you could use hybrid ports on NE2 (both
sides)
NE1 --network-------hybrid--NE2--hybrid--------network--NE3
Use an epipe on the hybrid ports of NE2 for the NE1 to NE3 connectivity and
use and put a router interface on another subinterface:

|------------------------------ospf etc ---------------|
NE1 --.1q 100 ------- NE2epipe --------.1q 100 NE3
|--------.1q 200 -------NE2 network
|-----ospf etc----------------|

quite hard to explain with ascii :)

My advice, redesign your topology.

On Tue, 13 Sep 2016 at 16:20 Youness Meklati <youness.meklati at gmail.com>
wrote:

> Hello all
>
> Thank you for your support, I use network interface to create router, ldp,
> mpls and ospf interface in my network, but in this case i can't use a
> network interface, the scenario is:
>
> NE1<----->NE2<------->NE3 : physicaly NE3 is not directly connected to NE1
> NE1 is the ABR in the area 0 (backbonne) and is belong also to area4 with
> NE2 :
> --area0-->NE1<---area4(stub)-->NE2
>
> NOW I need to add NE3 to an new area 5 (nssa) with NE1 and run ospf, mpls
> and ldp in this interface between NE1 and NE3 ( NE3 is not directly
> connectd to NE1 it pass NE2)
>
> to solve to ospf issue, i create an vpls between NE2 and NE1 and bind the
> this vpls the ies in NE1
>
> the configuration is as below:
>
> NE2# configure>servise>vpls>
> sap 2/2/2:3 (the port connected to NE3)
> sdp 1:3 (the sdp to NE1)
> .....
>
> in NE1
> NE1# configure>servise>vpls>
> allow-ip-int-binding
> sdp 2:3 (the sdp to NE2)
>
> and i give the ies NE1 and the port in NE3 the address IP /30 and the ospf
> was ok
>
> but when I add this the interface to mpls and ldp it give my this error.
> *Cannot configure LDP on service interface*
>
> Can you help me please.
>
>
> 2016-09-11 16:13 GMT+01:00 Keith Humphreys <thecandymancan at gmail.com>:
>
>> If you want to run protocols over a VPRN service interface you need to
>> specify its as a network interface within the service.  Doing CSC? Specify
>> that in the config as well.  Something like this
>>
>>             carrier-carrier-vpn
>>             network-interface "blah" create
>>                 address 10.1.1.1/24
>>                 port 1/1/5
>>                 no shutdown
>>
>> last time I checked LDP was not supported for CSC, only BGP can signal
>> labels.
>>
>> On Sat, 10 Sep 2016 at 17:00 <alcatel-nsp-request at puck.nether.net> wrote:
>>
>>> Send alcatel-nsp mailing list submissions to
>>>         alcatel-nsp at puck.nether.net
>>>
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>         https://puck.nether.net/mailman/listinfo/alcatel-nsp
>>> or, via email, send a message with subject or body 'help' to
>>>         alcatel-nsp-request at puck.nether.net
>>>
>>> You can reach the person managing the list at
>>>         alcatel-nsp-owner at puck.nether.net
>>>
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of alcatel-nsp digest..."
>>>
>>>
>>> Today's Topics:
>>>
>>>    1. Re: Cannot configure LDP on service interface
>>>       (Johnson, Alastair (Nokia - US))
>>>
>>>
>>> ----------------------------------------------------------------------
>>>
>>> Message: 1
>>> Date: Fri, 9 Sep 2016 17:01:30 +0000
>>> From: "Johnson, Alastair (Nokia - US)" <alastair.johnson at nokia.com>
>>> To: ?ukasz Dudzi?ski <lukasz at dudzinscy.org>, "Youness Meklati"
>>>         <youness.meklati at gmail.com>, "alcatel-nsp at puck.nether.net"
>>>         <alcatel-nsp at puck.nether.net>
>>> Subject: Re: [alcatel-nsp] Cannot configure LDP on service interface
>>> Message-ID: <1BCCBA22-4191-43A6-BE1C-A0E2F8788F01 at nokia.com>
>>> Content-Type: text/plain; charset="utf-8"
>>>
>>> You can also use hybrid mode for ports that need to support access (SAP)
>>> interfaces and network functionality.
>>>
>>>
>>> From: alcatel-nsp <alcatel-nsp-bounces at puck.nether.net> on behalf of
>>> ?ukasz Dudzi?ski <lukasz at dudzinscy.org>
>>> Date: Friday, September 9, 2016 at 8:24 AM
>>> To: Youness Meklati <youness.meklati at gmail.com>, "
>>> alcatel-nsp at puck.nether.net" <alcatel-nsp at puck.nether.net>
>>> Subject: Re: [alcatel-nsp] Cannot configure LDP on service interface
>>>
>>> Hi,
>>>
>>> You need to config interface in "/configure router" context and set port
>>> to "ethernet network" mode instead of "access mode". Mpls is not supported
>>> on service (access) interfaces.
>>> --
>>> ?ukasz
>>> On September 9, 2016 5:04:45 PM GMT+02:00, Youness Meklati <
>>> youness.meklati at gmail.com> wrote:
>>> Hello
>>>
>>> I have configured an ies to be an Interface in ospf area and then used
>>> for ldp and mpls, but the ospf is ok but when i want to add this interface
>>> as an ldp interface i got this error:Cannot configure LDP on service
>>> interface.
>>>
>>> Can some one help me.
>>>
>>> Youness
>>>
>>> ________________________________
>>>
>>> alcatel-nsp mailing list
>>> alcatel-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/alcatel-nsp
>>> -------------- next part --------------
>>> An HTML attachment was scrubbed...
>>> URL: <
>>> https://puck.nether.net/pipermail/alcatel-nsp/attachments/20160909/73d2a42f/attachment-0001.html
>>> >
>>>
>>> ------------------------------
>>>
>>> Subject: Digest Footer
>>>
>>> _______________________________________________
>>> alcatel-nsp mailing list
>>> alcatel-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/alcatel-nsp
>>>
>>>
>>> ------------------------------
>>>
>>> End of alcatel-nsp Digest, Vol 72, Issue 3
>>> ******************************************
>>>
>>
>> _______________________________________________
>> alcatel-nsp mailing list
>> alcatel-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/alcatel-nsp
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/alcatel-nsp/attachments/20160913/226b7b50/attachment-0001.html>