[ospf_adj_dut] Check OSPF adjacencies with DUT [ node(s): r1 ]
[WAITING]      Waiting for OSPF adjacency process to complete (retrying for 40 seconds)
[PASS]         r1: Neighbor 10.0.0.1 is in state Full/-
[PASS]         Succeeded in 8.9 seconds
[PASS]         Test succeeded

[ospf_adj_r1]  Check OSPF adjacencies with R1 [ node(s): r2,rr2 ]
[PASS]         r2: Neighbor 10.0.0.10 is in state Full/-
[WAITING]      Waiting for OSPF adjacency process to complete (retrying for 10 seconds)
[PASS]         rr2: Neighbor 10.0.0.10 is in state Full/-
[PASS]         Succeeded in 1.3 seconds
[PASS]         Test succeeded

[session]      Check BGP sessions with DUT [ node(s): r1,r2,rr2,x1 ]
[PASS]         x1: Neighbor 172.16.3.1 (dut) is in state Established
[WAITING]      Wait for BGP sessions to be established (retrying for 30 seconds)
[PASS]         r1: Neighbor 10.0.0.1 (dut) is in state Established
[PASS]         r2: Neighbor 10.0.0.1 (dut) is in state Established
[PASS]         rr2: Neighbor 10.0.0.1 (dut) is in state Established
[PASS]         Succeeded in 11.8 seconds
[PASS]         Test succeeded

[prefix]       Check whether DUT1 propagates the external beacon prefix [ node(s): r1,r2,rr2 ]
[PASS]         r1: The prefix 172.42.42.0/24 is in the BGP table
[PASS]         r2: The prefix 172.42.42.0/24 is in the BGP table
[PASS]         rr2: The prefix 172.42.42.0/24 is in the BGP table
[PASS]         Test succeeded

[nhs]          Check next-hop handling on DUT [ node(s): r1,r2 ]
[PASS]         r1: The prefix 172.42.42.0/24 is in the BGP table with BGP next hop=10.0.0.1/32
[PASS]         r2: The prefix 172.42.42.0/24 is in the BGP table with BGP next hop=10.0.0.1/32
[PASS]         Test succeeded

[reflect]      Check route reflection on DUT [ node(s): r2 ]
[PASS]         r2: The prefix 172.0.42.0/24 is in the BGP table with BGP router ID=10.0.0.1
[PASS]         Test succeeded

[inact]        Check route reflection of inactive routes on DUT [ node(s): r2 ]
[FAIL]         r2: There is no path to 10.0.0.10/32 in the BGP table with BGP router ID=10.0.0.1
Returned result
================================================================================
paths:
- aspath:
    length: 0
    segments: []
    string: Local
  clusterList:
    list:
    - 10.0.0.43
  lastUpdate:
    epoch: 1723944017
    string: 'Sun Aug 18 01:20:17 2024

      '
  locPrf: 100
  metric: 0
  nexthops:
  - accessible: false
    afi: ipv4
    hostname: rr2
    importCheckEnabled: true
    ip: 10.0.0.10
    used: true
  origin: IGP
  originatorId: 10.0.0.10
  peer:
    hostname: rr2
    peerId: 10.0.0.2
    routerId: 10.0.0.2
    type: internal
  valid: false
  version: 0
prefix: 10.0.0.10/32
version: 0


[nhu]          Check next-hop handling of reflected routes [ node(s): r2 ]
[PASS]         r2: The prefix 172.0.42.0/24 is in the BGP table with BGP router ID=10.0.0.1,BGP next hop=10.0.0.10
[PASS]         Test succeeded

[cluster]      Check cluster-id attribute in the BGP update from RR [ node(s): r2 ]
[FAIL]         r2: Cannot find cluster ID 10.0.0.42 in the paths of prefix 172.0.42.0/24
Returned result
================================================================================
paths:
- aspath:
    length: 0
    segments: []
    string: Local
  clusterList:
    list:
    - 10.0.0.43
  lastUpdate:
    epoch: 1723944018
    string: 'Sun Aug 18 01:20:18 2024

      '
  locPrf: 100
  metric: 0
  nexthops:
  - accessible: true
    afi: ipv4
    hostname: rr2
    ip: 10.0.0.10
    metric: 10
    used: true
  origin: IGP
  originatorId: 10.0.0.1
  peer:
    hostname: rr2
    peerId: 10.0.0.2
    routerId: 10.0.0.2
    type: internal
  valid: true
  version: 3
- aspath:
    length: 0
    segments: []
    string: Local
  bestpath:
    bestpathFromAs: 0
    overall: true
    selectionReason: Cluster length
  lastUpdate:
    epoch: 1723944009
    string: 'Sun Aug 18 01:20:09 2024

      '
  locPrf: 100
  metric: 0
  nexthops:
  - accessible: true
    afi: ipv4
    ip: 10.0.0.10
    metric: 10
    used: true
  origin: IGP
  peer:
    peerId: 10.0.0.1
    routerId: 10.0.0.1
    type: internal
  valid: true
  version: 3
prefix: 172.0.42.0/24
version: 3


[FAIL]         Tests completed, validation failed