-
Notifications
You must be signed in to change notification settings - Fork 716
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added support for running T2 applicable tests using vsonic(KVM) for n… #6022
Conversation
This pull request introduces 1 alert when merging bad9a3177e129a72f4725b1aa5888945ca427fc5 into e33b228 - view on LGTM.com new alerts:
|
/easycla |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as comments
The pre-commit check detected issues in the files touched by this pull request. For old issues, it is not mandatory to fix them because they were not caused by this change. It is unfair to blame Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
cc @judyjoseph |
@sanmalho-git Can we close this soon. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
The pre-commit check detected issues in the files touched by this pull request. For old issues, it is not mandatory to fix them because they were not caused by this change. It is unfair to blame Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
Which topology was this ran in for this setup? Was it the t2-topo? |
T2 Toplogy |
Thanks. Was this a physical T2 setup with vSONIC KVM neighbors? |
The topology that we are using is T2_min with a physical chassis with 2 Linecards and 1 supervisor card and all eBGP peers being simulated using vsonic |
The pre-commit check detected issues in the files touched by this pull request. For old issues, it is not mandatory to fix them because they were not caused by this change. It is unfair to blame Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
fd575e5
to
3a4fd6d
Compare
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
/Azp run Azure.sonic-mgmt |
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
@judyjoseph I removed that section of the code as it is not related to this PR. All tests have passed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@mannytaheri PR conflicts with 202205 branch |
sonic-net#6022) * Added support for running T2 applicable tests using vsonic(KVM) for neighbors 1. Fix for test_lldp testcase: KVM neighbors do not advertise port ifname. They instead advertise 'descr'. We will use ifname for EosHost and descr for KVM 2. Fix for test_snmp_loopback testcase: snmpget command requires running in snmp docker 3. voq tests BGP: - Use vtysh for BGP configuration on vsonic Interface up/down: - Use shut/no shut commands Interface name and numbering: - Neighbors interface name is difference on vsonic vs Eos. - On Eos, inerfaces are named 'eth' (Ex. eth1) and portchannels are named po (Ex. po1). - On vsonic, interfaces are named Ethernet (Ex. Ethernet1) and portchannels are named PortChannel (PortChannel1).
sonic-net#6022) * Added support for running T2 applicable tests using vsonic(KVM) for neighbors 1. Fix for test_lldp testcase: KVM neighbors do not advertise port ifname. They instead advertise 'descr'. We will use ifname for EosHost and descr for KVM 2. Fix for test_snmp_loopback testcase: snmpget command requires running in snmp docker 3. voq tests BGP: - Use vtysh for BGP configuration on vsonic Interface up/down: - Use shut/no shut commands Interface name and numbering: - Neighbors interface name is difference on vsonic vs Eos. - On Eos, inerfaces are named 'eth' (Ex. eth1) and portchannels are named po (Ex. po1). - On vsonic, interfaces are named Ethernet (Ex. Ethernet1) and portchannels are named PortChannel (PortChannel1).
Cherry-pick PR to 202305: #11852 |
Cherry-pick PR to 202311: #11853 |
#6022) * Added support for running T2 applicable tests using vsonic(KVM) for neighbors 1. Fix for test_lldp testcase: KVM neighbors do not advertise port ifname. They instead advertise 'descr'. We will use ifname for EosHost and descr for KVM 2. Fix for test_snmp_loopback testcase: snmpget command requires running in snmp docker 3. voq tests BGP: - Use vtysh for BGP configuration on vsonic Interface up/down: - Use shut/no shut commands Interface name and numbering: - Neighbors interface name is difference on vsonic vs Eos. - On Eos, inerfaces are named 'eth' (Ex. eth1) and portchannels are named po (Ex. po1). - On vsonic, interfaces are named Ethernet (Ex. Ethernet1) and portchannels are named PortChannel (PortChannel1).
#6022) * Added support for running T2 applicable tests using vsonic(KVM) for neighbors 1. Fix for test_lldp testcase: KVM neighbors do not advertise port ifname. They instead advertise 'descr'. We will use ifname for EosHost and descr for KVM 2. Fix for test_snmp_loopback testcase: snmpget command requires running in snmp docker 3. voq tests BGP: - Use vtysh for BGP configuration on vsonic Interface up/down: - Use shut/no shut commands Interface name and numbering: - Neighbors interface name is difference on vsonic vs Eos. - On Eos, inerfaces are named 'eth' (Ex. eth1) and portchannels are named po (Ex. po1). - On vsonic, interfaces are named Ethernet (Ex. Ethernet1) and portchannels are named PortChannel (PortChannel1).
sonic-net#6022) * Added support for running T2 applicable tests using vsonic(KVM) for neighbors 1. Fix for test_lldp testcase: KVM neighbors do not advertise port ifname. They instead advertise 'descr'. We will use ifname for EosHost and descr for KVM 2. Fix for test_snmp_loopback testcase: snmpget command requires running in snmp docker 3. voq tests BGP: - Use vtysh for BGP configuration on vsonic Interface up/down: - Use shut/no shut commands Interface name and numbering: - Neighbors interface name is difference on vsonic vs Eos. - On Eos, inerfaces are named 'eth' (Ex. eth1) and portchannels are named po (Ex. po1). - On vsonic, interfaces are named Ethernet (Ex. Ethernet1) and portchannels are named PortChannel (PortChannel1). (cherry picked from commit 0a3acb7)
#6022) (#11905) * Added support for running T2 applicable tests using vsonic(KVM) for neighbors 1. Fix for test_lldp testcase: KVM neighbors do not advertise port ifname. They instead advertise 'descr'. We will use ifname for EosHost and descr for KVM 2. Fix for test_snmp_loopback testcase: snmpget command requires running in snmp docker 3. voq tests BGP: - Use vtysh for BGP configuration on vsonic Interface up/down: - Use shut/no shut commands Interface name and numbering: - Neighbors interface name is difference on vsonic vs Eos. - On Eos, inerfaces are named 'eth' (Ex. eth1) and portchannels are named po (Ex. po1). - On vsonic, interfaces are named Ethernet (Ex. Ethernet1) and portchannels are named PortChannel (PortChannel1). (cherry picked from commit 0a3acb7)
Description of PR
Added support for running T2 applicable tests using vsonic(KVM) for neighbors
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
To add support for vsonic/KVM commands on neighbors, as the commands are different from Eo
How did you do it?
Fix for test_lldp testcase:
KVM neighbors do not advertise port ifname. They instead advertise 'descr'. We will use ifname for EosHost and descr for KVM
Fix for test_snmp_loopback testcase:
snmpget command requires running in snmp docker
Eos Example:
ARISTA01T3#bash snmpget -v2c -c public 10.1.0.1 1.3.6.1.2.1.1.1.0
SNMPv2-MIB::sysDescr.0 = STRING: SONiC Software Version: SONiC.HEAD.291231-msft-2205-c679f2d - HwSku: Nokia-
IXR7250E-36x100G - Distribution: Debian 11.4 - Kernel: 5.10.0-12-2-amd64
vSonic Exmple:
admin@ARISTA01T1:~$ docker exec -it snmp snmpget -v2c -c public 10.1.0.1 1.3.6.1.2.1.1.1.0
iso.3.6.1.2.1.1.1.0 = STRING: "SONiC Software Version: SONiC.HEAD.291231-msft-2205-c679f2d - HwSku: Nokia-IXR7250E-
6x400G - Distribution: Debian 11.4 - Kernel: 5.10.0-12-2-amd64"
Fix for voq tests
BGP:
- Use vtysh for BGP configuration on vsonic
Interface up/down:
- Use shut/no shut commands
voq_helper
Interface name and numbering:
Fix for test_lag interface
There is no support for setting lacp rate in vsonic. So, skipping these tests.
How did you verify/test it?
Tested the code on a dut that uses Eos VM as it's neighbors in one setup and against vsonic neighbors in another setup.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation