Comprehensive and Detailed In-Depth Explanation:
To verify the correct answer, we need to analyze Bidirectional Forwarding Detection (BFD) behavior and the provided configuration.
1. Understanding BFD Configuration Parameters
BFD (Bidirectional Forwarding Detection) is a protocol used for fast failure detection between directly connected devices.
Key Configuration Parameters in BFD:
Peer IP (bind peer-ip)
This specifies the destination router’s IP address for the BFD session.
✅ Correctly configured on both R1 and R2.
Discriminator Local/Remote (discriminator local X / remote Y)
These values must match between the two routers.
✅ Correctly configured (R1: local 1, remote 2; R2: local 2, remote 1).
Min-TX Interval (min-tx-interval)
Defines the minimum transmit interval for BFD packets.
❌ Missing from R2’s configuration (could be a cause for mismatch).
Min-RX Interval (min-rx-interval)
Defines the minimum receive interval for BFD packets.
❌ Missing from R2’s configuration (could be a cause for mismatch).
2. Analyzing the Configuration on R1 and R2
✅ Configuration on R1 (Correct)
shell
CopyEdit
bfd tor2 bind peer-ip 10.0.12.2
discriminator local 1
discriminator remote 2
min-tx-interval 1500
min-rx-interval 1500
❌ Configuration on R2 (Incomplete)
shell
CopyEdit
bfd tor1 bind peer-ip 10.0.12.1
discriminator local 2
discriminator remote 1
3. Why the Answer is FALSE?
A BFD session does NOT go down due to mismatched timing parameters.
BFD dynamically negotiates timing values, meaning even if R2 is missing min-tx/min-rx values, the session should still establish.
However, the session will fail if the peer IP or discriminator values are incorrect (which they are NOT in this case).
The actual cause of failure in this case is likely the missing min-tx and min-rx settings on R2, NOT a mismatch between R1 and R2.
