Creating Device configuration snippets
[CREATED] dut: initial,routing,bgp,bgp.policy
[CREATED] customer: initial,bgp,bgp.policy
[CREATED] peer: initial,bgp,bgp.policy
[CREATED] upstream: initial,bgp,bgp.policy
[CREATED] bad: initial,bgp,bgp.policy
[CREATED] good: initial,bgp,bgp.policy
[CREATED] legacy: initial,bgp
Config Deploying device configurations
 [INFO] Executing initial configuration for node dut (namespace clab-
          ml-17-dut)
 [INFO] Executing initial configuration for node customer
 [INFO] Executing initial configuration for node peer
 [INFO] Executing initial configuration for node upstream
 [INFO] Executing initial configuration for node bad
 [INFO] Executing initial configuration for node good
 [INFO] Executing initial configuration for node legacy
 [INFO] Executing bgp configuration for node peer
 [INFO] Executing bgp configuration for node legacy
 [INFO] Executing bgp configuration for node good
 [INFO] Executing bgp configuration for node bad
 [INFO] Executing bgp configuration for node customer
 [INFO] Executing bgp configuration for node upstream
 [INFO] Executing bgp.policy configuration for node peer
 [INFO] Executing bgp.policy configuration for node bad
 [INFO] Executing bgp.policy configuration for node customer
 [INFO] Executing bgp.policy configuration for node good
 [INFO] Executing bgp.policy configuration for node upstream

Results of configuration script deployments
================================================================================
dut              Script:  initial
customer         Script:  initial,bgp,bgp.policy
peer             Script:  initial,bgp,bgp.policy
upstream         Script:  initial,bgp,bgp.policy
bad              Script:  initial,bgp,bgp.policy
good             Script:  initial,bgp,bgp.policy
legacy           Script:  initial,bgp


Test RFC 9234 BGP roles on EBGP sessions: provider/customer and peer/peer
sessions (including route-leak prevention), and strict-mode role mismatch
handling when another session on the same router has incompatible roles.