BFD between Nexus 3500 and Juniper MX Router.

Has anyone gotten BFD to work between these too?

We have tried lots of settings on the Juniper side.

Originally tried the following.

 bfd-liveness-detection { minimum-interval 2000; } 

Below is current state.

Using the defaults on the Nexus 3500 the minRX/minTX are 2000ms, hold timer is 6000ms, and multiplier 3.

Session state is Down and not using echo function Session type: Singlehop Local Diag: 0, Demand mode: 0, Poll bit: 0, Authentication: None MinTxInt: 2000000 us, MinRxInt: 2000000 us, Multiplier: 3 Received MinRxInt: 2000000 us, Received Multiplier: 3 Holdown (hits): 6000 ms (4), Hello (hits): 2000 ms (22062) Rx Count: 18813, Rx Interval (ms) min/max/avg: 101/282/2040 last: 1887 ms ago Tx Count: 22062, Tx Interval (ms) min/max/avg: 1743/1743/1743 last: 1545 ms ago Registered protocols: bgp Downtime: 0 days 10 hrs 40 mins 8 secs Last packet: Version: 1 - Diagnostic: 0 State bit: Down - Demand bit: 0 Poll bit: 1 - Final bit: 0 Multiplier: 3 - Length: 24 My Discr.: 23 - Your Discr.: 0 Min tx interval: 2000000 - Min rx interval: 2000000 Min Echo interval: 0 - Authentication bit: 0 Hosting LC: 1, Down reason: No Diagnostic, Reason not-hosted: None 

On the Juniper side we have the following.

bfd-liveness-detection { version 1; minimum-receive-interval 2000; multiplier 3; transmit-interval { minimum-interval 2000; threshold 6000; } session-mode automatic; } 

​

Address State Interface Time Interval Multiplier 172.17.113.237 Down ge-4/1/1.0 0.000 2.000 3 Client BGP, TX interval 2.000, RX interval 2.000 Local diagnostic None, remote diagnostic None Remote state AdminDown, version 1 Replicated Session type: Single hop BFD Min async interval 2.000, min slow interval 2.000 Adaptive async TX interval 2.000, RX interval 2.000 Local min TX interval 2.000, minimum RX interval 2.000, multiplier 3 Remote min TX interval 0.000, min RX interval 0.000, multiplier 0 Local discriminator 23, remote discriminator 0 Echo mode disabled/inactive, no-absorb, no-refresh Session ID: 0x551b 

Any help would be greatly appreciated.