Bfd Ospf Three Devs

Test to check BFD protocol in OSPF with three devices.

../../../_images/bfdospfthreedevs.svg

Test Connection With Three Devices

Description

Tests connection between three devices with BFD in OSPF by checking if they are each others peers and their status is up.

Scenario

Step 1: Set the following configuration in DUT0 :

set interfaces dummy dum0 address 10.0.0.1/24
set interfaces ethernet eth0 address 192.168.1.1/24
set interfaces ethernet eth0 ip ospf bfd
set interfaces ethernet eth0 ip ospf network point-to-point
set interfaces ethernet eth1 address 192.168.2.1/24
set interfaces ethernet eth1 ip ospf bfd
set interfaces ethernet eth1 ip ospf network point-to-point
set protocols ospf area 0 network 10.0.0.0/24
set protocols ospf area 0 network 192.168.1.0/24
set protocols ospf area 1 network 192.168.2.0/24
set protocols ospf parameters router-id 1.1.1.1
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 10.0.0.2/24
set interfaces ethernet eth0 address 192.168.1.2/24
set interfaces ethernet eth0 ip ospf bfd
set interfaces ethernet eth0 ip ospf network point-to-point
set interfaces ethernet eth2 address 192.168.3.2/24
set interfaces ethernet eth2 ip ospf bfd
set interfaces ethernet eth2 ip ospf network point-to-point
set protocols ospf area 0 network 10.0.0.0/24
set protocols ospf area 0 network 192.168.1.0/24
set protocols ospf area 2 network 192.168.3.0/24
set protocols ospf parameters router-id 2.2.2.2
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 3: Set the following configuration in DUT2 :

set interfaces dummy dum0 address 10.0.0.3/24
set interfaces ethernet eth1 address 192.168.2.3/24
set interfaces ethernet eth1 ip ospf bfd
set interfaces ethernet eth1 ip ospf network point-to-point
set interfaces ethernet eth2 address 192.168.3.3/24
set interfaces ethernet eth2 ip ospf bfd
set interfaces ethernet eth2 ip ospf network point-to-point
set protocols ospf area 0 network 10.0.0.0/24
set protocols ospf area 1 network 192.168.2.0/24
set protocols ospf area 2 network 192.168.3.0/24
set protocols ospf parameters router-id 3.3.3.3
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Note

Check connectivity

Step 4: Ping the IP address 192.168.1.2 from DUT0:

admin@DUT0$ ping 192.168.1.2 count 1 size 56 timeout 1
Show output
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=1.55 ms

--- 192.168.1.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.546/1.546/1.546/0.000 ms

Step 5: Ping the IP address 192.168.2.3 from DUT0:

admin@DUT0$ ping 192.168.2.3 count 1 size 56 timeout 1
Show output
PING 192.168.2.3 (192.168.2.3) 56(84) bytes of data.
64 bytes from 192.168.2.3: icmp_seq=1 ttl=64 time=3.93 ms

--- 192.168.2.3 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 3.933/3.933/3.933/0.000 ms

Step 6: Ping the IP address 192.168.1.1 from DUT1:

admin@DUT1$ ping 192.168.1.1 count 1 size 56 timeout 1
Show output
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.655 ms

--- 192.168.1.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.655/0.655/0.655/0.000 ms

Step 7: Ping the IP address 192.168.3.3 from DUT1:

admin@DUT1$ ping 192.168.3.3 count 1 size 56 timeout 1
Show output
PING 192.168.3.3 (192.168.3.3) 56(84) bytes of data.
64 bytes from 192.168.3.3: icmp_seq=1 ttl=64 time=0.628 ms

--- 192.168.3.3 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.628/0.628/0.628/0.000 ms

Step 8: Ping the IP address 192.168.2.1 from DUT2:

admin@DUT2$ ping 192.168.2.1 count 1 size 56 timeout 1
Show output
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.295 ms

--- 192.168.2.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.295/0.295/0.295/0.000 ms

Step 9: Ping the IP address 192.168.3.2 from DUT2:

admin@DUT2$ ping 192.168.3.2 count 1 size 56 timeout 1
Show output
PING 192.168.3.2 (192.168.3.2) 56(84) bytes of data.
64 bytes from 192.168.3.2: icmp_seq=1 ttl=64 time=0.313 ms

--- 192.168.3.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.313/0.313/0.313/0.000 ms

Note

Check that they are each other’s neighbors

Step 10: Run the command protocols ospf show neighbor on DUT0 and check whether the output contains the following tokens:

2.2.2.2
3.3.3.3
Show output
Neighbor ID     Pri State           Up Time         Dead Time Address         Interface                        RXmtL RqstL DBsmL
2.2.2.2           1 Full/-          6.617s            35.802s 192.168.1.2     eth0:192.168.1.1                     0     0     0
3.3.3.3           1 Full/-          1.649s            38.348s 192.168.2.3     eth1:192.168.2.1                     1     0     0

Step 11: Run the command protocols ospf show neighbor on DUT1 and check whether the output contains the following tokens:

1.1.1.1
3.3.3.3
Show output
Neighbor ID     Pri State           Up Time         Dead Time Address         Interface                        RXmtL RqstL DBsmL
1.1.1.1           1 Full/-          6.731s            33.267s 192.168.1.1     eth0:192.168.1.2                     0     0     0
3.3.3.3           1 Full/-          1.764s            38.234s 192.168.3.3     eth2:192.168.3.2                     1     0     0

Step 12: Run the command protocols ospf show neighbor on DUT2 and check whether the output contains the following tokens:

1.1.1.1
2.2.2.2
Show output
Neighbor ID     Pri State           Up Time         Dead Time Address         Interface                        RXmtL RqstL DBsmL
1.1.1.1           1 Full/-          1.898s            33.132s 192.168.2.1     eth1:192.168.2.3                     1     0     0
2.2.2.2           1 Full/-          1.898s            35.553s 192.168.3.2     eth2:192.168.3.3                     1     0     0

Note

Check that they are each other’s peers and that their status is up (the BFD session has been successfully established)

Step 13: Run the command protocols bfd show peers on DUT0 and check whether the output contains the following tokens:

192.168.1.2
Status: up
192.168.2.3
Status: up
Show output
BFD Peers:
peer 192.168.1.2 local-address 192.168.1.1 vrf default interface eth0
ID: 3256260521
Remote ID: 934781387
Active mode
Status: up
Uptime: 5 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
Transmission interval (actual with jitter): 228ms
Detection timeout: 900ms
Echo receive interval: 50ms
Echo transmission interval: disabled
Remote timers:
Detect-multiplier: 3
Receive interval: 300ms
Transmission interval: 300ms
Echo receive interval: 50ms

peer 192.168.2.3 local-address 192.168.2.1 vrf default interface eth1
ID: 3369148969
Remote ID: 1713111031
Active mode
Status: up
Uptime: 0 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
Transmission interval (actual with jitter): 300ms
Detection timeout: 900ms
Echo receive interval: 50ms
Echo transmission interval: disabled
Remote timers:
Detect-multiplier: 3
Receive interval: 300ms
Transmission interval: 300ms
Echo receive interval: 50ms

Step 14: Run the command protocols bfd show peers on DUT1 and check whether the output contains the following tokens:

192.168.1.1
Status: up
192.168.3.3
Status: up
Show output
BFD Peers:
peer 192.168.1.1 local-address 192.168.1.2 vrf default interface eth0
ID: 934781387
Remote ID: 3256260521
Active mode
Status: up
Uptime: 5 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
Transmission interval (actual with jitter): 297ms
Detection timeout: 900ms
Echo receive interval: 50ms
Echo transmission interval: disabled
Remote timers:
Detect-multiplier: 3
Receive interval: 300ms
Transmission interval: 300ms
Echo receive interval: 50ms

peer 192.168.3.3 local-address 192.168.3.2 vrf default interface eth2
ID: 2714594555
Remote ID: 498251803
Active mode
Status: up
Uptime: 0 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
Transmission interval (actual with jitter): 237ms
Detection timeout: 900ms
Echo receive interval: 50ms
Echo transmission interval: disabled
Remote timers:
Detect-multiplier: 3
Receive interval: 300ms
Transmission interval: 300ms
Echo receive interval: 50ms

Step 15: Run the command protocols bfd show peers on DUT2 and check whether the output contains the following tokens:

192.168.2.1
Status: up
192.168.3.2
Status: up
Show output
BFD Peers:
peer 192.168.2.1 local-address 192.168.2.3 vrf default interface eth1
ID: 1713111031
Remote ID: 3369148969
Active mode
Status: up
Uptime: 0 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
Transmission interval (actual with jitter): 279ms
Detection timeout: 900ms
Echo receive interval: 50ms
Echo transmission interval: disabled
Remote timers:
Detect-multiplier: 3
Receive interval: 300ms
Transmission interval: 300ms
Echo receive interval: 50ms

peer 192.168.3.2 local-address 192.168.3.3 vrf default interface eth2
ID: 498251803
Remote ID: 2714594555
Active mode
Status: up
Uptime: 0 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
Transmission interval (actual with jitter): 246ms
Detection timeout: 900ms
Echo receive interval: 50ms
Echo transmission interval: disabled
Remote timers:
Detect-multiplier: 3
Receive interval: 300ms
Transmission interval: 300ms
Echo receive interval: 50ms