Good to know. Since I replied to a number of people privately about LFM in 
JUNOS, I should also mention that we ran into a major issue with LFM last 
Friday. Just spent the last 5 days working with ATAC and Engineering on this. 
Short story is, do not deploy LFM if you have the following combination in your 
network:

1. VRF using vrf-table-label
2. M320 PE with a 1-port 10GE XENPAK PIC used as an upstream interface
3. I-Chip FPC for the above mentioned 10GE PIC

If you have this combo, either remove vrf-table-label, or don't deploy LFM. 
This is broke in all JUNOS versions. :)

Regards,
-Jeff

On Aug 16, 2011, at 10:06 AM, <david....@orange-ftgroup.com> 
<david....@orange-ftgroup.com> wrote:

> 
> ________________________________________
> De : juniper-nsp-boun...@puck.nether.net 
> [juniper-nsp-boun...@puck.nether.net] de la part de Rafael Rodriguez 
> [packetjoc...@gmail.com]
> Date d'envoi : vendredi 29 juillet 2011 22:08
> À : Daniel Verlouw
> Cc : Juniper Puck
> Objet : Re: [j-nsp] ECMP vs LAG and OAM vs BFD
> 
> FYI list,
> 
> OAM LFM (802.3ah) appears to be supported in Junos 11.1 for Trio/MPC (I've
> yet to test this).
> 
> http://www.juniper.net/techpubs/en_US/junos11.1/information-products/topic-collections/release-notes/11.1/index.html?topic-53312.html#jd0e1736
> 
> 
> On Sat, Jul 23, 2011 at 7:22 AM, Daniel Verlouw <dan...@shunoshu.net> wrote:
> 
>> On Fri, Jul 22, 2011 at 22:14, Stefan Fouant
>> <sfou...@shortestpathfirst.net> wrote:
>>> Regarding BFD's capabilities to determine member state of individual
>> member
>>> links, this is not currently supported by BFD.  Take a look at IETF Draft
>>> 'Bidirectional Forwarding Detection (BFD) for Interface' which was just
>>> released a few weeks ago. It is designed to meet these requirements -
>>> http://tools.ietf.org/html/draft-chen-bfd-interface-00
>> 
>> IOS XR (at least on the ASR9k) supports BFD over individual member
>> links. Saw it in the lab, seemed to work fine. Not sure if it's
>> implementation is based on this draft though, or if it's a proprietary
>> one.
>> 
>> --Daniel.
>> 
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
> 
> ********************************************************************************
> IMPORTANT.Les informations contenues dans ce message electronique y compris 
> les fichiers attaches sont strictement confidentielles
> et peuvent etre protegees par la loi.
> Ce message electronique est destine exclusivement au(x) destinataire(s) 
> mentionne(s) ci-dessus.
> Si vous avez recu ce message par erreur ou s il ne vous est pas destine, 
> veuillez immediatement le signaler  a l expediteur et effacer ce message 
> et tous les fichiers eventuellement attaches.
> Toute lecture, exploitation ou transmission des informations contenues dans 
> ce message est interdite.
> Tout message electronique est susceptible d alteration.
> A ce titre, le Groupe France Telecom decline toute responsabilite notamment s 
> il a ete altere, deforme ou falsifie.
> De meme, il appartient au destinataire de s assurer de l absence de tout 
> virus.
> 
> IMPORTANT.This e-mail message and any attachments are strictly confidential 
> and may be protected by law. This message is
> intended only for the named recipient(s) above.
> If you have received this message in error, or are not the named 
> recipient(s), please immediately notify the sender and delete this e-mail 
> message.
> Any unauthorized view, usage or disclosure ofthis message is prohibited.
> Since e-mail messages may not be reliable, France Telecom Group shall not be 
> liable for any message if modified, changed or falsified.
> Additionally the recipient should ensure they are actually virus free.
> ********************************************************************************
> 
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp


_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to