This object sets, from 3 to 20, how many consecutive BFD messages can be missed from the peer before the session is declared down and upper-layer protocols like OSPF, IS-IS, or PIM are notified, defaulting to 3. Admins tune this to balance false-positive avoidance against fast failure detection: a lower multiplier reacts faster but risks flapping on transient loss, a higher one is more tolerant but slower to detect real failures. Setting this to 3 with a 100 ms interval means a BFD session using this template is declared down after roughly 300 ms of missed packets.