Hi Krzysztof, I am using MX router with version 15.1F6-S5.6 and the options you referred are not existing in the software :(
[edit protocols mpls label-switched-path Juniper-Huawei] Juniper# set oam bfd-liveness-detection ? Possible completions: + apply-groups Groups from which to inherit configuration data + apply-groups-except Don't inherit configuration data from these groups > detection-time Detection-time options > failure-action Action to take when BFD session goes down minimum-interval Minimum transmit and receive interval (1..255000 milliseconds) minimum-receive-interval Minimum receive interval (1..255000 milliseconds) multiplier Detection time multiplier (1..255) no-adaptation Disable adaptation > transmit-interval Transmit-interval options version BFD protocol version number Regards, Gokhan On Sun, May 28, 2017 at 8:21 AM, Krzysztof Grzegorz Szarkowicz < kszarkow...@gmail.com> wrote: > Hi, > > Please check following knobs: > > *no-router-alert-option* > *use-ip-ttl-1* > *bfd-port* > > root@PE1# set protocols mpls label-switched-path PE1-->PE4 primary PATH-1 > oam bfd-liveness-detection ? > W21: Sat 2017-05-27T10:12:07 PDT (UTC-0700) > Possible completions: > + apply-groups Groups from which to inherit configuration data > + apply-groups-except Don't inherit configuration data from these groups > > detection-time Detection-time options > > failure-action Action to take when BFD session goes down > minimum-interval Minimum transmit and receive interval (1..255000 > milliseconds) > minimum-receive-interval Minimum receive interval (1..255000 > milliseconds) > multiplier Detection time multiplier (1..255) > no-adaptation Disable adaptation > * no-router-alert-option Do not set Router-Alert options in IP header > for MPLS-BFD. <=================* > > transmit-interval Transmit-interval options > *use-ip-ttl-1 Set TTL value to 1 in IP header for MPLS-BFD > <=================* > version BFD protocol version number > > root@PE1# set protocols mpls label-switched-path PE1-->PE4 primary PATH-1 > oam bfd-port ? > W21: Sat 2017-05-27T10:30:34 PDT (UTC-0700) > Possible completions: > + apply-groups Groups from which to inherit configuration data > + apply-groups-except Don't inherit configuration data from these groups > + import Import policy > > — Krzysztof > > On 2017-May-26, at 16:52, Gökhan Gümüş <ggu...@gmail.com> wrote: > > Hi Steinar, > > Thanks for reply. Actually, i have been looking for BFD at MPLS LSP level > instead of ISIS level. > Are you using BFD at LSP level between Juniper and Huawei? > > Kind regards, > Gokhan > > On Fri, May 26, 2017 at 2:39 PM, <sth...@nethelp.no> wrote: > > I am trying to establish a RSVP-OAM between a Juniper and Huawei device. > > > Possibly not directly relevant to your case - but we have lots of BFD > sessions for IS-IS between Juniper and Huawei. Nothing special, it > just works. Lightly edited example below. > > Steinar Haug, Nethelp consulting, sth...@nethelp.no > > ---------------------------------------------------------------------- > > ar1.xxx> show configuration interfaces xe-10/0/2 > mtu 9114; > unit 0 { > family inet { > address 10.1.1.87/31; > } > family iso; > family mpls; > } > > ar1.xxx> show configuration protocols isis interface xe-10/0/2.0 > ldp-synchronization { > hold-time 600; > } > point-to-point; > bfd-liveness-detection { > minimum-interval 50; > multiplier 3; > } > > interface GigabitEthernet0/1/0 > mtu 9100 > undo shutdown > ip address 10.1.1.86 255.255.255.254 > isis enable 1 > isis circuit-type p2p > isis circuit-level level-2 > isis ldp-sync > isis bfd enable > isis bfd min-tx-interval 50 min-rx-interval 50 > mpls > mpls te > mpls rsvp-te > mpls ldp > > _______________________________________________ > 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