Bfd Static Route
Tests to check BFD protocol in static routes.
Test Connection With Next Hop IPv4
Description
Tests connection between two devices with BFD in static routes using the gateway as the BFD peer, checking if they are each others peers and their status is up and installed.
Scenario
Step 1: Set the following configuration in DUT0 :
set interfaces ethernet eth0 address 10.10.0.100/24 set protocols static route 0.0.0.0/0 next-hop 10.10.0.200 bfd set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 2: Set the following configuration in DUT1 :
set interfaces ethernet eth0 address 10.10.0.200/24 set protocols static route 0.0.0.0/0 next-hop 10.10.0.100 bfd set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Note
Check connectivity
Step 3: Ping IP address 10.10.0.200 from DUT0:
admin@DUT0$ ping 10.10.0.200 count 1 size 56 timeout 1Show output
PING 10.10.0.200 (10.10.0.200) 56(84) bytes of data. 64 bytes from 10.10.0.200: icmp_seq=1 ttl=64 time=0.511 ms --- 10.10.0.200 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.511/0.511/0.511/0.000 ms
Step 4: Ping IP address 10.10.0.100 from DUT1:
admin@DUT1$ ping 10.10.0.100 count 1 size 56 timeout 1Show output
PING 10.10.0.100 (10.10.0.100) 56(84) bytes of data. 64 bytes from 10.10.0.100: icmp_seq=1 ttl=64 time=0.238 ms --- 10.10.0.100 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.238/0.238/0.238/0.000 ms
Note
Check that the operational command ‘protocols bfd show static route’ works, and shows that they are each other’s peers and that their status is installed, indicating that the next-hop router is reachable
Step 5: Run command protocols bfd show static route at DUT0 and check if output matches the following regular expressions:
10.10.0.200 status: installedShow output
Showing BFD monitored static routes: Next hops: VRF A IPv4 Unicast: VRF A IPv4 Multicast: VRF A IPv6 Unicast: VRF AP IPv4 Unicast: VRF AP IPv4 Multicast: VRF AP IPv6 Unicast: VRF B IPv4 Unicast: VRF B IPv4 Multicast: VRF B IPv6 Unicast: VRF BFD IPv4 Unicast: VRF BFD IPv4 Multicast: VRF BFD IPv6 Unicast: VRF BGP IPv4 Unicast: VRF BGP IPv4 Multicast: VRF BGP IPv6 Unicast: VRF G IPv4 Unicast: VRF G IPv4 Multicast: VRF G IPv6 Unicast: VRF LAN IPv4 Unicast: VRF LAN IPv4 Multicast: VRF LAN IPv6 Unicast: VRF LOC IPv4 Unicast: VRF LOC IPv4 Multicast: VRF LOC IPv6 Unicast: VRF MON IPv4 Unicast: VRF MON IPv4 Multicast: VRF MON IPv6 Unicast: VRF RED IPv4 Unicast: VRF RED IPv4 Multicast: VRF RED IPv6 Unicast: VRF TEST IPv4 Unicast: VRF TEST IPv4 Multicast: VRF TEST IPv6 Unicast: VRF VRF1 IPv4 Unicast: VRF VRF1 IPv4 Multicast: VRF VRF1 IPv6 Unicast: VRF VRF_LAN IPv4 Unicast: VRF VRF_LAN IPv4 Multicast: VRF VRF_LAN IPv6 Unicast: VRF VRF_TUN IPv4 Unicast: VRF VRF_TUN IPv4 Multicast: VRF VRF_TUN IPv6 Unicast: VRF VRF_WAN IPv4 Unicast: VRF VRF_WAN IPv4 Multicast: VRF VRF_WAN IPv6 Unicast: VRF WAN IPv4 Unicast: VRF WAN IPv4 Multicast: VRF WAN IPv6 Unicast: VRF default IPv4 Unicast: 0.0.0.0/0 peer 10.10.0.200 (status: installed) VRF default IPv4 Multicast: VRF default IPv6 Unicast: VRF test IPv4 Unicast: VRF test IPv4 Multicast: VRF test IPv6 Unicast: VRF test2 IPv4 Unicast: VRF test2 IPv4 Multicast: VRF test2 IPv6 Unicast:
Step 6: Run command protocols bfd show static route at DUT1 and check if output matches the following regular expressions:
10.10.0.100 status: installedShow output
Showing BFD monitored static routes: Next hops: VRF BFD IPv4 Unicast: VRF BFD IPv4 Multicast: VRF BFD IPv6 Unicast: VRF BGP IPv4 Unicast: VRF BGP IPv4 Multicast: VRF BGP IPv6 Unicast: VRF default IPv4 Unicast: 0.0.0.0/0 peer 10.10.0.100 (status: installed) VRF default IPv4 Multicast: VRF default IPv6 Unicast: VRF tenant1 IPv4 Unicast: VRF tenant1 IPv4 Multicast: VRF tenant1 IPv6 Unicast: VRF tenant2 IPv4 Unicast: VRF tenant2 IPv4 Multicast: VRF tenant2 IPv6 Unicast: VRF tenant3 IPv4 Unicast: VRF tenant3 IPv4 Multicast: VRF tenant3 IPv6 Unicast:
Note
Check that they are each other’s peers and that their status is up (the BFD session has beedn successfully established)
Step 7: Run command protocols bfd show peers at DUT0 and check if output matches the following regular expressions:
10.10.0.200 Status: upShow output
BFD Peers: peer 10.10.0.200 vrf default ID: 1134568321 Remote ID: 1092057133 Active mode Status: up Uptime: 2 second(s) Diagnostics: ok Remote diagnostics: ok Peer Type: dynamic RTT min/avg/max: 0/0/0 usec Local timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms Echo transmission interval: disabled Remote timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms
Step 8: Run command protocols bfd show peers at DUT1 and check if output matches the following regular expressions:
10.10.0.100 Status: upShow output
BFD Peers: peer 10.10.0.100 vrf default ID: 1092057133 Remote ID: 1134568321 Active mode Status: up Uptime: 2 second(s) Diagnostics: ok Remote diagnostics: ok Peer Type: dynamic RTT min/avg/max: 0/0/0 usec Local timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms Echo transmission interval: disabled Remote timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms
Test Connection With Next Hop And Interface IPv4
Description
Tests connection between two devices with BFD in static routes using the gateway as the BFD peer and an interface, checking if they are each others peers and their status is up and installed.
Scenario
Step 1: Set the following configuration in DUT0 :
set interfaces ethernet eth0 address 10.10.0.100/24 set protocols static route 0.0.0.0/0 next-hop 10.10.0.200 interface eth0 bfd set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 2: Set the following configuration in DUT1 :
set interfaces ethernet eth0 address 10.10.0.200/24 set protocols static route 0.0.0.0/0 next-hop 10.10.0.100 interface eth0 bfd set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Note
Check connectivity
Step 3: Ping IP address 10.10.0.200 from DUT0:
admin@DUT0$ ping 10.10.0.200 count 1 size 56 timeout 1Show output
PING 10.10.0.200 (10.10.0.200) 56(84) bytes of data. 64 bytes from 10.10.0.200: icmp_seq=1 ttl=64 time=0.876 ms --- 10.10.0.200 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.876/0.876/0.876/0.000 ms
Step 4: Ping IP address 10.10.0.100 from DUT1:
admin@DUT1$ ping 10.10.0.100 count 1 size 56 timeout 1Show output
PING 10.10.0.100 (10.10.0.100) 56(84) bytes of data. 64 bytes from 10.10.0.100: icmp_seq=1 ttl=64 time=0.292 ms --- 10.10.0.100 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.292/0.292/0.292/0.000 ms
Note
Check that the operational command ‘protocols bfd show static route’ works, and shows that they are each other’s peers and that their status is installed, indicating that the next-hop router is reachable
Step 5: Run command protocols bfd show static route at DUT0 and check if output matches the following regular expressions:
10.10.0.200 status: installedShow output
Showing BFD monitored static routes: Next hops: VRF A IPv4 Unicast: VRF A IPv4 Multicast: VRF A IPv6 Unicast: VRF AP IPv4 Unicast: VRF AP IPv4 Multicast: VRF AP IPv6 Unicast: VRF B IPv4 Unicast: VRF B IPv4 Multicast: VRF B IPv6 Unicast: VRF BFD IPv4 Unicast: VRF BFD IPv4 Multicast: VRF BFD IPv6 Unicast: VRF BGP IPv4 Unicast: VRF BGP IPv4 Multicast: VRF BGP IPv6 Unicast: VRF G IPv4 Unicast: VRF G IPv4 Multicast: VRF G IPv6 Unicast: VRF LAN IPv4 Unicast: VRF LAN IPv4 Multicast: VRF LAN IPv6 Unicast: VRF LOC IPv4 Unicast: VRF LOC IPv4 Multicast: VRF LOC IPv6 Unicast: VRF MON IPv4 Unicast: VRF MON IPv4 Multicast: VRF MON IPv6 Unicast: VRF RED IPv4 Unicast: VRF RED IPv4 Multicast: VRF RED IPv6 Unicast: VRF TEST IPv4 Unicast: VRF TEST IPv4 Multicast: VRF TEST IPv6 Unicast: VRF VRF1 IPv4 Unicast: VRF VRF1 IPv4 Multicast: VRF VRF1 IPv6 Unicast: VRF VRF_LAN IPv4 Unicast: VRF VRF_LAN IPv4 Multicast: VRF VRF_LAN IPv6 Unicast: VRF VRF_TUN IPv4 Unicast: VRF VRF_TUN IPv4 Multicast: VRF VRF_TUN IPv6 Unicast: VRF VRF_WAN IPv4 Unicast: VRF VRF_WAN IPv4 Multicast: VRF VRF_WAN IPv6 Unicast: VRF WAN IPv4 Unicast: VRF WAN IPv4 Multicast: VRF WAN IPv6 Unicast: VRF default IPv4 Unicast: 0.0.0.0/0 peer 10.10.0.200 (status: installed) VRF default IPv4 Multicast: VRF default IPv6 Unicast: VRF test IPv4 Unicast: VRF test IPv4 Multicast: VRF test IPv6 Unicast: VRF test2 IPv4 Unicast: VRF test2 IPv4 Multicast: VRF test2 IPv6 Unicast:
Step 6: Run command protocols bfd show static route at DUT1 and check if output matches the following regular expressions:
10.10.0.100 status: installedShow output
Showing BFD monitored static routes: Next hops: VRF BFD IPv4 Unicast: VRF BFD IPv4 Multicast: VRF BFD IPv6 Unicast: VRF BGP IPv4 Unicast: VRF BGP IPv4 Multicast: VRF BGP IPv6 Unicast: VRF default IPv4 Unicast: 0.0.0.0/0 peer 10.10.0.100 (status: installed) VRF default IPv4 Multicast: VRF default IPv6 Unicast: VRF tenant1 IPv4 Unicast: VRF tenant1 IPv4 Multicast: VRF tenant1 IPv6 Unicast: VRF tenant2 IPv4 Unicast: VRF tenant2 IPv4 Multicast: VRF tenant2 IPv6 Unicast: VRF tenant3 IPv4 Unicast: VRF tenant3 IPv4 Multicast: VRF tenant3 IPv6 Unicast:
Note
Check that they are each other’s peers and that their status is up (the BFD session has beedn successfully established)
Step 7: Run command protocols bfd show peers at DUT0 and check if output matches the following regular expressions:
10.10.0.200 Status: upShow output
BFD Peers: peer 10.10.0.200 vrf default interface eth0 ID: 1747612202 Remote ID: 3529072799 Active mode Status: up Uptime: 2 second(s) Diagnostics: ok Remote diagnostics: ok Peer Type: dynamic RTT min/avg/max: 0/0/0 usec Local timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms Echo transmission interval: disabled Remote timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms
Step 8: Run command protocols bfd show peers at DUT1 and check if output matches the following regular expressions:
10.10.0.100 Status: upShow output
BFD Peers: peer 10.10.0.100 vrf default interface eth0 ID: 3529072799 Remote ID: 1747612202 Active mode Status: up Uptime: 2 second(s) Diagnostics: ok Remote diagnostics: ok Peer Type: dynamic RTT min/avg/max: 0/0/0 usec Local timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms Echo transmission interval: disabled Remote timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms
Test Connection With Next Hop And Next Hop VRF IPv4
Description
Tests connection between two devices with BFD in static routes using the gateway as the BFD peer and a leaked route with a nexthop in the specified VRF ID, checking if they are each others peers and their status is up and installed.
Scenario
Step 1: Set the following configuration in DUT0 :
set interfaces ethernet eth0 address 10.10.0.100/24 set interfaces ethernet eth0 vrf VRF set protocols static route 0.0.0.0/0 next-hop 10.10.0.200 next-hop-vrf VRF bfd set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set system vrf VRF
Step 2: Set the following configuration in DUT1 :
set interfaces ethernet eth0 address 10.10.0.200/24 set interfaces ethernet eth0 vrf VRF set protocols static route 0.0.0.0/0 next-hop 10.10.0.100 next-hop-vrf VRF bfd set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set system vrf VRF
Note
Check connectivity
Step 3: Ping IP address 10.10.0.200 from DUT0:
admin@DUT0$ ping 10.10.0.200 count 1 size 56 timeout 1Show output
PING 10.10.0.200 (10.10.0.200) 56(84) bytes of data. 64 bytes from 10.10.0.200: icmp_seq=1 ttl=64 time=0.231 ms --- 10.10.0.200 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.231/0.231/0.231/0.000 ms
Step 4: Ping IP address 10.10.0.100 from DUT1:
admin@DUT1$ ping 10.10.0.100 count 1 size 56 timeout 1Show output
PING 10.10.0.100 (10.10.0.100) 56(84) bytes of data. 64 bytes from 10.10.0.100: icmp_seq=1 ttl=64 time=0.296 ms --- 10.10.0.100 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.296/0.296/0.296/0.000 ms
Note
Check that the operational command ‘protocols bfd show static route’ works, and shows that they are each other’s peers and that their status is installed, indicating that the next-hop router is reachable
Step 5: Run command protocols bfd show static route at DUT0 and check if output matches the following regular expressions:
10.10.0.200 status: installedShow output
Showing BFD monitored static routes: Next hops: VRF A IPv4 Unicast: VRF A IPv4 Multicast: VRF A IPv6 Unicast: VRF AP IPv4 Unicast: VRF AP IPv4 Multicast: VRF AP IPv6 Unicast: VRF B IPv4 Unicast: VRF B IPv4 Multicast: VRF B IPv6 Unicast: VRF BFD IPv4 Unicast: VRF BFD IPv4 Multicast: VRF BFD IPv6 Unicast: VRF BGP IPv4 Unicast: VRF BGP IPv4 Multicast: VRF BGP IPv6 Unicast: VRF G IPv4 Unicast: VRF G IPv4 Multicast: VRF G IPv6 Unicast: VRF LAN IPv4 Unicast: VRF LAN IPv4 Multicast: VRF LAN IPv6 Unicast: VRF LOC IPv4 Unicast: VRF LOC IPv4 Multicast: VRF LOC IPv6 Unicast: VRF MON IPv4 Unicast: VRF MON IPv4 Multicast: VRF MON IPv6 Unicast: VRF RED IPv4 Unicast: VRF RED IPv4 Multicast: VRF RED IPv6 Unicast: VRF TEST IPv4 Unicast: VRF TEST IPv4 Multicast: VRF TEST IPv6 Unicast: VRF VRF1 IPv4 Unicast: VRF VRF1 IPv4 Multicast: VRF VRF1 IPv6 Unicast: VRF VRF_LAN IPv4 Unicast: VRF VRF_LAN IPv4 Multicast: VRF VRF_LAN IPv6 Unicast: VRF VRF_TUN IPv4 Unicast: VRF VRF_TUN IPv4 Multicast: VRF VRF_TUN IPv6 Unicast: VRF VRF_WAN IPv4 Unicast: VRF VRF_WAN IPv4 Multicast: VRF VRF_WAN IPv6 Unicast: VRF WAN IPv4 Unicast: VRF WAN IPv4 Multicast: VRF WAN IPv6 Unicast: VRF default IPv4 Unicast: 0.0.0.0/0 peer 10.10.0.200 (status: installed) VRF default IPv4 Multicast: VRF default IPv6 Unicast: VRF test IPv4 Unicast: VRF test IPv4 Multicast: VRF test IPv6 Unicast: VRF test2 IPv4 Unicast: VRF test2 IPv4 Multicast: VRF test2 IPv6 Unicast:
Step 6: Run command protocols bfd show static route at DUT1 and check if output matches the following regular expressions:
10.10.0.100 status: installedShow output
Showing BFD monitored static routes: Next hops: VRF BFD IPv4 Unicast: VRF BFD IPv4 Multicast: VRF BFD IPv6 Unicast: VRF BGP IPv4 Unicast: VRF BGP IPv4 Multicast: VRF BGP IPv6 Unicast: VRF default IPv4 Unicast: 0.0.0.0/0 peer 10.10.0.100 (status: installed) VRF default IPv4 Multicast: VRF default IPv6 Unicast: VRF tenant1 IPv4 Unicast: VRF tenant1 IPv4 Multicast: VRF tenant1 IPv6 Unicast: VRF tenant2 IPv4 Unicast: VRF tenant2 IPv4 Multicast: VRF tenant2 IPv6 Unicast: VRF tenant3 IPv4 Unicast: VRF tenant3 IPv4 Multicast: VRF tenant3 IPv6 Unicast:
Note
Check that they are each other’s peers and that their status is up (the BFD session has beedn successfully established)
Step 7: Run command protocols bfd show peers at DUT0 and check if output matches the following regular expressions:
10.10.0.200 Status: upShow output
BFD Peers: peer 10.10.0.200 vrf VRF ID: 3565335410 Remote ID: 37945965 Active mode Status: up Uptime: 1 second(s) Diagnostics: ok Remote diagnostics: ok Peer Type: dynamic RTT min/avg/max: 0/0/0 usec Local timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms Echo transmission interval: disabled Remote timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms
Step 8: Run command protocols bfd show peers at DUT1 and check if output matches the following regular expressions:
10.10.0.100 Status: upShow output
BFD Peers: peer 10.10.0.100 vrf VRF ID: 37945965 Remote ID: 3565335410 Active mode Status: up Uptime: 1 second(s) Diagnostics: ok Remote diagnostics: ok Peer Type: dynamic RTT min/avg/max: 0/0/0 usec Local timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms Echo transmission interval: disabled Remote timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms
Test Connection With DHCP Interface IPv4
Description
Tests connection between two devices with BFD in static routes using a DHCP interface that supplies the next-hop IP address, checking if they are each others peers and their status is up and installed.
Scenario
Step 1: Set the following configuration in DUT0 :
set interfaces ethernet eth0 address dhcp set protocols static route 0.0.0.0/0 dhcp-interface eth0 bfd set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 2: Set the following configuration in DUT1 :
set interfaces ethernet eth0 address 10.10.0.200/24 set protocols static route 0.0.0.0/0 next-hop 10.10.0.150 bfd set service dhcp-server shared-network dhcpserver subnet 10.10.0.0/24 options default-router 10.10.0.200 set service dhcp-server shared-network dhcpserver subnet 10.10.0.0/24 start 10.10.0.150 stop 10.10.0.150 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Note
Check connectivity
Step 3: Ping IP address 10.10.0.200 from DUT0:
admin@DUT0$ ping 10.10.0.200 count 1 size 56 timeout 1Show output
PING 10.10.0.200 (10.10.0.200) 56(84) bytes of data. 64 bytes from 10.10.0.200: icmp_seq=1 ttl=64 time=0.401 ms --- 10.10.0.200 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.401/0.401/0.401/0.000 ms
Step 4: Ping IP address 10.10.0.150 from DUT1:
admin@DUT1$ ping 10.10.0.150 count 1 size 56 timeout 1Show output
PING 10.10.0.150 (10.10.0.150) 56(84) bytes of data. 64 bytes from 10.10.0.150: icmp_seq=1 ttl=64 time=0.310 ms --- 10.10.0.150 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.310/0.310/0.310/0.000 ms
Note
Check that the operational command ‘protocols bfd show static route’ works, and shows that they are each other’s peers and that their status is installed, indicating that the next-hop router is reachable
Step 5: Run command protocols bfd show static route at DUT0 and check if output matches the following regular expressions:
10.10.0.200 status: installedShow output
Showing BFD monitored static routes: Next hops: VRF A IPv4 Unicast: VRF A IPv4 Multicast: VRF A IPv6 Unicast: VRF AP IPv4 Unicast: VRF AP IPv4 Multicast: VRF AP IPv6 Unicast: VRF B IPv4 Unicast: VRF B IPv4 Multicast: VRF B IPv6 Unicast: VRF BFD IPv4 Unicast: VRF BFD IPv4 Multicast: VRF BFD IPv6 Unicast: VRF BGP IPv4 Unicast: VRF BGP IPv4 Multicast: VRF BGP IPv6 Unicast: VRF G IPv4 Unicast: VRF G IPv4 Multicast: VRF G IPv6 Unicast: VRF LAN IPv4 Unicast: VRF LAN IPv4 Multicast: VRF LAN IPv6 Unicast: VRF LOC IPv4 Unicast: VRF LOC IPv4 Multicast: VRF LOC IPv6 Unicast: VRF MON IPv4 Unicast: VRF MON IPv4 Multicast: VRF MON IPv6 Unicast: VRF RED IPv4 Unicast: VRF RED IPv4 Multicast: VRF RED IPv6 Unicast: VRF TEST IPv4 Unicast: VRF TEST IPv4 Multicast: VRF TEST IPv6 Unicast: VRF VRF1 IPv4 Unicast: VRF VRF1 IPv4 Multicast: VRF VRF1 IPv6 Unicast: VRF VRF_LAN IPv4 Unicast: VRF VRF_LAN IPv4 Multicast: VRF VRF_LAN IPv6 Unicast: VRF VRF_TUN IPv4 Unicast: VRF VRF_TUN IPv4 Multicast: VRF VRF_TUN IPv6 Unicast: VRF VRF_WAN IPv4 Unicast: VRF VRF_WAN IPv4 Multicast: VRF VRF_WAN IPv6 Unicast: VRF WAN IPv4 Unicast: VRF WAN IPv4 Multicast: VRF WAN IPv6 Unicast: VRF default IPv4 Unicast: 0.0.0.0/0 peer 10.10.0.200 (status: installed) VRF default IPv4 Multicast: VRF default IPv6 Unicast: VRF test IPv4 Unicast: VRF test IPv4 Multicast: VRF test IPv6 Unicast: VRF test2 IPv4 Unicast: VRF test2 IPv4 Multicast: VRF test2 IPv6 Unicast:
Step 6: Run command protocols bfd show static route at DUT1 and check if output matches the following regular expressions:
10.10.0.150 status: installedShow output
Showing BFD monitored static routes: Next hops: VRF BFD IPv4 Unicast: VRF BFD IPv4 Multicast: VRF BFD IPv6 Unicast: VRF BGP IPv4 Unicast: VRF BGP IPv4 Multicast: VRF BGP IPv6 Unicast: VRF default IPv4 Unicast: 0.0.0.0/0 peer 10.10.0.150 (status: installed) VRF default IPv4 Multicast: VRF default IPv6 Unicast: VRF tenant1 IPv4 Unicast: VRF tenant1 IPv4 Multicast: VRF tenant1 IPv6 Unicast: VRF tenant2 IPv4 Unicast: VRF tenant2 IPv4 Multicast: VRF tenant2 IPv6 Unicast: VRF tenant3 IPv4 Unicast: VRF tenant3 IPv4 Multicast: VRF tenant3 IPv6 Unicast:
Note
Check that they are each other’s peers and that their status is up (the BFD session has beedn successfully established)
Step 7: Run command protocols bfd show peers at DUT0 and check if output matches the following regular expressions:
10.10.0.200 Status: upShow output
BFD Peers: peer 10.10.0.200 vrf default interface eth0 ID: 4057981463 Remote ID: 1478498506 Active mode Status: up Uptime: 2 second(s) Diagnostics: ok Remote diagnostics: ok Peer Type: dynamic RTT min/avg/max: 0/0/0 usec Local timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms Echo transmission interval: disabled Remote timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms
Step 8: Run command protocols bfd show peers at DUT1 and check if output matches the following regular expressions:
10.10.0.150 Status: upShow output
BFD Peers: peer 10.10.0.150 vrf default ID: 1478498506 Remote ID: 4057981463 Active mode Status: up Uptime: 2 second(s) Diagnostics: ok Remote diagnostics: ok Peer Type: dynamic RTT min/avg/max: 0/0/0 usec Local timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms Echo transmission interval: disabled Remote timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms
Test Multihop Connection IPv4
Description
Tests multihop connection between two devices in different networks using a third device connected to both networks, checking if they are each others peers and their status is up and installed.
Scenario
Step 1: Set the following configuration in DUT0 :
set interfaces dummy dum0 address 1.1.1.1/24 set interfaces ethernet eth0 address 10.10.0.100/24 set protocols static route 2.2.2.0/24 next-hop 20.20.0.200 bfd multihop set protocols static route 20.20.0.0/24 next-hop 10.10.0.101 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 2: Set the following configuration in DUT1 :
set interfaces dummy dum0 address 2.2.2.1/24 set interfaces ethernet eth0 address 20.20.0.200/24 set protocols static route 1.1.1.0/24 next-hop 10.10.0.100 bfd multihop set protocols static route 10.10.0.0/24 next-hop 20.20.0.201 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Set the following configuration in DUT2 :
set interfaces ethernet eth0 address 10.10.0.101/24 set interfaces ethernet eth1 address 20.20.0.201/24 set protocols static route 1.1.1.0/24 next-hop 10.10.0.100 set protocols static route 2.2.2.0/24 next-hop 20.20.0.200 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Note
Check connectivity
Step 4: Ping IP address 20.20.0.200 from DUT0:
admin@DUT0$ ping 20.20.0.200 count 1 size 56 timeout 1Show output
PING 20.20.0.200 (20.20.0.200) 56(84) bytes of data. 64 bytes from 20.20.0.200: icmp_seq=1 ttl=63 time=0.426 ms --- 20.20.0.200 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.426/0.426/0.426/0.000 ms
Step 5: Ping IP address 10.10.0.100 from DUT1:
admin@DUT1$ ping 10.10.0.100 count 1 size 56 timeout 1Show output
PING 10.10.0.100 (10.10.0.100) 56(84) bytes of data. 64 bytes from 10.10.0.100: icmp_seq=1 ttl=63 time=0.429 ms --- 10.10.0.100 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.429/0.429/0.429/0.000 ms
Note
Check that the operational command ‘protocols bfd show static route’ works, and shows that they are each other’s peers and that their status is installed, indicating that the next-hop router is reachable
Step 6: Run command protocols bfd show static route at DUT0 and check if output matches the following regular expressions:
20.20.0.200 status: installedShow output
Showing BFD monitored static routes: Next hops: VRF A IPv4 Unicast: VRF A IPv4 Multicast: VRF A IPv6 Unicast: VRF AP IPv4 Unicast: VRF AP IPv4 Multicast: VRF AP IPv6 Unicast: VRF B IPv4 Unicast: VRF B IPv4 Multicast: VRF B IPv6 Unicast: VRF BFD IPv4 Unicast: VRF BFD IPv4 Multicast: VRF BFD IPv6 Unicast: VRF BGP IPv4 Unicast: VRF BGP IPv4 Multicast: VRF BGP IPv6 Unicast: VRF G IPv4 Unicast: VRF G IPv4 Multicast: VRF G IPv6 Unicast: VRF LAN IPv4 Unicast: VRF LAN IPv4 Multicast: VRF LAN IPv6 Unicast: VRF LOC IPv4 Unicast: VRF LOC IPv4 Multicast: VRF LOC IPv6 Unicast: VRF MON IPv4 Unicast: VRF MON IPv4 Multicast: VRF MON IPv6 Unicast: VRF RED IPv4 Unicast: VRF RED IPv4 Multicast: VRF RED IPv6 Unicast: VRF TEST IPv4 Unicast: VRF TEST IPv4 Multicast: VRF TEST IPv6 Unicast: VRF VRF1 IPv4 Unicast: VRF VRF1 IPv4 Multicast: VRF VRF1 IPv6 Unicast: VRF VRF_LAN IPv4 Unicast: VRF VRF_LAN IPv4 Multicast: VRF VRF_LAN IPv6 Unicast: VRF VRF_TUN IPv4 Unicast: VRF VRF_TUN IPv4 Multicast: VRF VRF_TUN IPv6 Unicast: VRF VRF_WAN IPv4 Unicast: VRF VRF_WAN IPv4 Multicast: VRF VRF_WAN IPv6 Unicast: VRF WAN IPv4 Unicast: VRF WAN IPv4 Multicast: VRF WAN IPv6 Unicast: VRF default IPv4 Unicast: 2.2.2.0/24 peer 20.20.0.200 (status: installed) VRF default IPv4 Multicast: VRF default IPv6 Unicast: VRF test IPv4 Unicast: VRF test IPv4 Multicast: VRF test IPv6 Unicast: VRF test2 IPv4 Unicast: VRF test2 IPv4 Multicast: VRF test2 IPv6 Unicast:
Step 7: Run command protocols bfd show static route at DUT1 and check if output matches the following regular expressions:
10.10.0.100 status: installedShow output
Showing BFD monitored static routes: Next hops: VRF BFD IPv4 Unicast: VRF BFD IPv4 Multicast: VRF BFD IPv6 Unicast: VRF BGP IPv4 Unicast: VRF BGP IPv4 Multicast: VRF BGP IPv6 Unicast: VRF default IPv4 Unicast: 1.1.1.0/24 peer 10.10.0.100 (status: installed) VRF default IPv4 Multicast: VRF default IPv6 Unicast: VRF tenant1 IPv4 Unicast: VRF tenant1 IPv4 Multicast: VRF tenant1 IPv6 Unicast: VRF tenant2 IPv4 Unicast: VRF tenant2 IPv4 Multicast: VRF tenant2 IPv6 Unicast: VRF tenant3 IPv4 Unicast: VRF tenant3 IPv4 Multicast: VRF tenant3 IPv6 Unicast:
Note
Check that they are each other’s peers and that their status is up (the BFD session has beedn successfully established)
Step 8: Run command protocols bfd show peers at DUT0 and check if output matches the following regular expressions:
20.20.0.200 Status: upShow output
BFD Peers: peer 20.20.0.200 multihop local-address 10.10.0.100 vrf default ID: 3946818365 Remote ID: 118734392 Active mode Minimum TTL: 2 Status: up Uptime: 1 second(s) Diagnostics: ok Remote diagnostics: ok Peer Type: dynamic RTT min/avg/max: 0/0/0 usec Local timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms Echo transmission interval: disabled Remote timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms
Step 9: Run command protocols bfd show peers at DUT1 and check if output matches the following regular expressions:
10.10.0.100 Status: upShow output
BFD Peers: peer 10.10.0.100 multihop local-address 20.20.0.200 vrf default ID: 118734392 Remote ID: 3946818365 Active mode Minimum TTL: 2 Status: up Uptime: 2 second(s) Diagnostics: ok Remote diagnostics: ok Peer Type: dynamic RTT min/avg/max: 0/0/0 usec Local timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms Echo transmission interval: disabled Remote timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms
Test DUT0 Source IP IPv4
Description
Captures BFD packets and verifies the source address is correct when packets are sent from DUT0.
Scenario
Step 1: Set the following configuration in DUT0 :
set interfaces ethernet eth0 address 10.10.0.100/24 set protocols static route 0.0.0.0/0 next-hop 10.10.0.200 bfd set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 2: Set the following configuration in DUT1 :
set interfaces ethernet eth0 address 10.10.0.200/24 set protocols static route 0.0.0.0/0 next-hop 10.10.0.100 bfd source-ip 10.10.0.100 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Note
Capture packets and show one to verify that the source address is 10.10.0.100:
Note
Source line:
Show output
7 2025-12-17 17:44:40.446440551 10.10.0.100 → 10.10.0.200 BFD Control 66 Diag: No Diagnostic, State: Down, Flags: 0x00
Test DUT1 Source IP IPv4
Description
Captures BFD packets and verifies the source address is correct when packets are sent from DUT1.
Scenario
Step 1: Set the following configuration in DUT0 :
set interfaces ethernet eth0 address 10.10.0.100/24 set protocols static route 0.0.0.0/0 next-hop 10.10.0.200 bfd source-ip 10.10.0.200 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 2: Set the following configuration in DUT1 :
set interfaces ethernet eth0 address 10.10.0.200/24 set protocols static route 0.0.0.0/0 next-hop 10.10.0.100 bfd set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Note
Capture packets and show one to verify that the source address is 10.10.0.200:
Note
Source line:
Show output
13 2025-12-17 17:44:54.621945368 10.10.0.200 → 10.10.0.100 BFD Control 66 Diag: No Diagnostic, State: Down, Flags: 0x00
Test Profile IPv4
Description
Checks that all BFD profile configured parameters are shown.
Scenario
Step 1: Set the following configuration in DUT0 :
set interfaces ethernet eth0 address 10.10.0.100/24 set protocols bfd profile PFL detect-multiplier 5 set protocols bfd profile PFL echo-interval 60 set protocols bfd profile PFL echo-mode set protocols bfd profile PFL passive-mode set protocols bfd profile PFL receive-interval 400 set protocols bfd profile PFL transmit-interval 400 set protocols static route 0.0.0.0/0 next-hop 10.10.0.200 bfd profile PFL set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 2: Set the following configuration in DUT1 :
set interfaces ethernet eth0 address 10.10.0.200/24 set protocols static route 0.0.0.0/0 next-hop 10.10.0.100 bfd set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Note
Check connectivity
Step 3: Ping IP address 10.10.0.200 from DUT0:
admin@DUT0$ ping 10.10.0.200 count 1 size 56 timeout 1Show output
PING 10.10.0.200 (10.10.0.200) 56(84) bytes of data. 64 bytes from 10.10.0.200: icmp_seq=1 ttl=64 time=0.544 ms --- 10.10.0.200 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.544/0.544/0.544/0.000 ms
Step 4: Ping IP address 10.10.0.100 from DUT1:
admin@DUT1$ ping 10.10.0.100 count 1 size 56 timeout 1Show output
PING 10.10.0.100 (10.10.0.100) 56(84) bytes of data. 64 bytes from 10.10.0.100: icmp_seq=1 ttl=64 time=0.389 ms --- 10.10.0.100 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.389/0.389/0.389/0.000 ms
Note
Check that they are each other’s peers and that their status is up (the BFD session has beedn successfully established). Check that all configured profile parameters are shown in DUT0
Step 5: Run command protocols bfd show peers at DUT0 and check if output matches the following regular expressions:
10.10.0.200 Status: up Detect-multiplier: 5 Echo receive interval: 60ms Echo transmission interval: 60ms Passive mode Receive interval: 400ms Transmission interval: 400msShow output
BFD Peers: peer 10.10.0.200 vrf default ID: 924009364 Remote ID: 2391562775 Passive mode Status: up Uptime: 2 second(s) Diagnostics: ok Remote diagnostics: ok Peer Type: dynamic RTT min/avg/max: 240/308/469 usec Local timers: Detect-multiplier: 5 Receive interval: 400ms Transmission interval: 400ms Echo receive interval: 60ms Echo transmission interval: 60ms Remote timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms
Step 6: Run command protocols bfd show peers at DUT1 and check if output matches the following regular expressions:
10.10.0.100 Status: upShow output
BFD Peers: peer 10.10.0.100 vrf default ID: 2391562775 Remote ID: 924009364 Active mode Status: up Uptime: 2 second(s) Diagnostics: ok Remote diagnostics: ok Peer Type: dynamic RTT min/avg/max: 0/0/0 usec Local timers: Detect-multiplier: 3 Receive interval: 300ms Transmission interval: 300ms Echo receive interval: 50ms Echo transmission interval: disabled Remote timers: Detect-multiplier: 5 Receive interval: 400ms Transmission interval: 400ms Echo receive interval: 60ms