Mailing List Archive: nsp: foundry

VLL, VPLS and the point of configuring LSP's

Index | Next | Previous | View Threaded

remco at signet

May 10, 2012, 2:02 PM

Post #1 of 4 (598 views)
Permalink

VLL, VPLS and the point of configuring LSP's

Dear list,

At first, excuse my ignorance. I'm trying to get used to configuring MPLS on Brocade MLX/XMR series and all is working fine, but after reading through the manual i still have a question that is unanswered at the moment.
We are operating a network of 4 XMR routers in a ring topology with routed interfaces pointing to each-other. On these interfaces, i enabled ldp as follows :

router mpls
policy
traffic-eng ospf
mpls-interface ve9
ldp-enable
mpls-interface ve92
ldp-enable
!

Local, and remote VLL's are working perfectly. The manual is referring to configuring LSP's which you then use in the VPLS or VLL configuration to determine your path (vpls). I never used that before and it still is working. What is the actual advantage of configuring LSP's and using them in your VLL or VPLS configuration? I don't seem to understand it fully. If someone can explain it in a more basic way, i'd be very grateful.

Kind regards,

Remco Bressers

_______________________________________________
foundry-nsp mailing list
foundry-nsp [at] puck
http://puck.nether.net/mailman/listinfo/foundry-nsp

helmwork at ruraltel

May 10, 2012, 6:30 PM

Post #2 of 4 (572 views)
Permalink

Re: VLL, VPLS and the point of configuring LSP's [In reply to]

On 5/10/2012 4:02 PM, Remco Bressers wrote:
> Dear list,
>
> At first, excuse my ignorance. I'm trying to get used to configuring MPLS on Brocade MLX/XMR series and all is working fine, but after reading through the manual i still have a question that is unanswered at the moment.
> We are operating a network of 4 XMR routers in a ring topology with routed interfaces pointing to each-other. On these interfaces, i enabled ldp as follows :
>
> router mpls
> policy
> traffic-eng ospf
> mpls-interface ve9
> ldp-enable
> mpls-interface ve92
> ldp-enable
> !
>
> Local, and remote VLL's are working perfectly. The manual is referring to configuring LSP's which you then use in the VPLS or VLL configuration to determine your path (vpls). I never used that before and it still is working. What is the actual advantage of configuring LSP's and using them in your VLL or VPLS configuration? I don't seem to understand it fully. If someone can explain it in a more basic way, i'd be very grateful.
>

Traffic Engineering. LDP uses the IGP for path selection. TE using
manually defined LSPs can have explicitly defined paths among other
attributes/features.

/Eric
_______________________________________________
foundry-nsp mailing list
foundry-nsp [at] puck
http://puck.nether.net/mailman/listinfo/foundry-nsp

dspataro at corp

May 15, 2012, 8:40 AM

Post #3 of 4 (555 views)
Permalink

Re: VLL, VPLS and the point of configuring LSP's [In reply to]

Remco,

You can use LSPs configured with strict primary and secondary paths for the VPLS. This will allow you to control which way the VPLS traffic will flow over your network. You can also configure your LSP to use fast reroute for fast failover. Last time I checked you could not tell a VLL to use a defined LSP like you can do with a VPLS. I think a work around is to map a COS to the LSP and VLL.

Thanks,
Dan

-----Original Message-----
From: foundry-nsp-bounces [at] puck [mailto:foundry-nsp-bounces [at] puck] On Behalf Of Remco Bressers
Sent: Thursday, May 10, 2012 5:03 PM
To: foundry-nsp [at] puck
Subject: [f-nsp] VLL, VPLS and the point of configuring LSP's

Dear list,

At first, excuse my ignorance. I'm trying to get used to configuring MPLS on Brocade MLX/XMR series and all is working fine, but after reading through the manual i still have a question that is unanswered at the moment.
We are operating a network of 4 XMR routers in a ring topology with routed interfaces pointing to each-other. On these interfaces, i enabled ldp as follows :

router mpls
policy
traffic-eng ospf
mpls-interface ve9
ldp-enable
mpls-interface ve92
ldp-enable
!

Local, and remote VLL's are working perfectly. The manual is referring to configuring LSP's which you then use in the VPLS or VLL configuration to determine your path (vpls). I never used that before and it still is working. What is the actual advantage of configuring LSP's and using them in your VLL or VPLS configuration? I don't seem to understand it fully. If someone can explain it in a more basic way, i'd be very grateful.

Kind regards,

Remco Bressers

_______________________________________________
foundry-nsp mailing list
foundry-nsp [at] puck
http://puck.nether.net/mailman/listinfo/foundry-nsp

_______________________________________________
foundry-nsp mailing list
foundry-nsp [at] puck
http://puck.nether.net/mailman/listinfo/foundry-nsp

matthew at walster

May 16, 2012, 4:58 AM

Post #4 of 4 (555 views)
Permalink

Re: VLL, VPLS and the point of configuring LSP's [In reply to]

On 15 May 2012 16:40, Dan Spataro <dspataro [at] corp> wrote:
> Remco,
>
> You can use LSPs configured with strict primary and secondary paths for the VPLS. This will allow you to control which way the VPLS traffic will flow over your network. You can also configure your LSP to use fast reroute for fast failover. Last time I checked you could not tell a VLL to use a defined LSP like you can do with a VPLS. I think a work around is to map a COS to the LSP and VLL.

There is also the *dirty* way of doing it - create a new loopback
device, and do a new LSP between those two loopbacks, then set the VLL
to that loopback. It will then take the alternative route.

A manual way of steering of VLLs into certain LSPs would certainly be
welcomed from Brocade, however.

Matthew Walster

_______________________________________________
foundry-nsp mailing list
foundry-nsp [at] puck
http://puck.nether.net/mailman/listinfo/foundry-nsp

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads