[f-nsp] TE for the same VLL peers

[Tomasz Szewczyk]

Hi,

We also requested this feature quite long time ago - just after this functionality became available for VPLS. The disadvantage of using VPLS
is not only cam size (becasue it can be easily adopted) but loops created by/in end user network. Such  loops impacts control plane (even
when cpu protection is enabled).
The disadvantage of using LSP and CoS mapping is that you must use this in entire network - just like QoS policy, because by default it also
puts the traffic in appropriate queue (please note I'm not saying it is something bad :-)

I think before acquisition by Brocade Foundry was more flexible in this field ;-)


Cheers

Tomek
 
W dniu 2011-03-31 23:02, Romain DEGEZ pisze:
> Hi
>
> There is another way if I remember well : define a COS value in the LSP configuration and use the same cos for the vll. (the cos is an
> optional parameter at vll creation)
>
> That way, the vll will use the first LSP to destination that match its COS.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5846 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20110407/546c8257/attachment.p7s>