Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

Supported Platforms

 

Related Documentation

 

loose-check (BGP BFD Authentication)

Syntax

loose-check ;

Hierarchy Level

[edit logical-systems logical-system-name protocols bgp bfd-liveness-detection authentication],[edit logical-systems logical-system-name protocols bgp group group-name bfd-liveness-detection authentication],[edit logical-systems logical-system-name protocols bgp group group-name neighbor address bfd-liveness-detection authentication],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp bfd-liveness-detection authentication],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name bfd-liveness-detection authentication],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address bfd-liveness-detection authentication],[edit protocols bgp bgp bfd-liveness-detection authentication],[edit protocols bgp group group-name bfd-liveness-detection authentication],[edit protocols bgp group group-name neighbor address bfd-liveness-detection authentication],[edit routing-instances routing-instance-name protocols bgp bfd-liveness-detection authentication],[edit routing-instances routing-instance-name protocols bgp group group-name bfd-liveness-detection authentication],[edit routing-instances routing-instance-name protocols bgp group group-name neighbor address bfd-liveness-detection authentication]

Release Information

Statement introduced in Junos OS Release 8.1.

Statement introduced in Junos OS Release 9.0 for EX Series switches.

Support for BFD authentication introduced in Junos OS Release 9.6.

Statement introduced in Junos OS Release 12.1 for the QFX Series.

Description

Specify loose authentication checking on the BFD session. Use loose authentication for transitional periods only when authentication might not be configured at both ends of the BFD session.

By default, strict authentication is enabled and authentication is checked at both ends of each BFD session. Optionally, to smooth migration from nonauthenticated sessions to authenticated sessions, you can configure loose checking. When loose checking is configured, packets are accepted without authentication being checked at each end of the session.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

 

Related Documentation

 

Published: 2013-01-22

Supported Platforms

 

Related Documentation

 

Published: 2013-01-22

Previous Page Next Page