[action] [PR:6022] Added support for running T2 applicable tests using vsonic(KVM) for n… #11853
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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).
5 tasks
|
Original PR: #6022 |
|
/azp run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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"
BGP:
Interface up/down:
Interface name and numbering:
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