[test] Add check neighbors health for SONiC neighbor devices

[Pterosaur]

Signed-off-by: Ze Gan ganze718@gmail.com

Description of PR

./run_tests.sh -E -n vms-kvm-t0 -d vlab-01 -c test_nbr_health.py -f vtestbed.csv -i veos_vtb -e "--neighbor_type=sonic"

Summary:
Add test for neighbor health if the neighbor devices are SONiC

Type of change

• Bug fix
• Testbed and Framework(new/improvement)
• Test case(new/improvement)

Approach

What is the motivation for this PR?

To check the neighbor health if the neighbor devices are SONiC

How did you do it?

Add a command argument of pytest to indicate the neighbor device type so that we can choose different flow when we check the neighbor health.

How did you verify/test it?

1. Build the SONiC neighbor testbed to follow the KVM Testbed Setup

./testbed-cli.sh -m veos_vtb -n 4 -k vsonic start-vms server_1 password.txt
./testbed-cli.sh -t vtestbed.csv -m veos_vtb -k vsonic add-topo vms-kvm-t0 password.txt
./testbed-cli.sh -t vtestbed.csv -m veos_vtb deploy-mg vms-kvm-t0 veos_vtb password.txt

2. Run neighbor health test

./run_tests.sh -n vms-kvm-t0 -d vlab-01 -c bgp/test_bgp_fact.py -f vtestbed.csv -i veos_vtb -e "--neighbor_type=sonic"

3. All test should be pass

Any platform specific information?

None

Supported testbed topology if it's a new test case?

None

Documentation

[wangxin]

Is there a way to detect the type of neighbor? Then the "--neighbor_type" option would be unnecessary. It would be easier to trigger tests.

[Pterosaur]

I don't have any elegant idea to check the type of neighbor.
In my mind, we can only get the type after we login the device, but the password and username is different between EOS and SONiC, so it requires that we need to know the type before we login the device.