Added two test cases of LAG testing (on t1-lag topology)

[antonpatenko]

1. VM LAG members traffic testing
2. LACP rate verifying on VMs and DUT

Note: there is also an issue with SSH connection to VMs, so sometimes, when running cisco scripts, the test can hang.

Full LAG test plan is available here:
https://github.com/Azure/SONiC/wiki/LAG-test-plan

[stcheng]

this test assumes that each lag has two members, need to check if the test bed type is t1-lag or not before running the test.

[antonpatenko]

You mean automatic topology type checking performed by the test itself?

[stcheng]

i wonder about it, or if we pass the testbed type as an extra argument and just check the argument's value?

[antonpatenko]

Well, I can make test checking the topology type, but I'm not sure it makes sense. Test assumes, that the user (who runs this test) guarantees that topology type is T1-LAG. But I can change that approach if we really need that.

[liatgrozovik]

i dont think we should. lag test should run only on the relevant topology. you should not run it on non lag topology Best regards, Liat Grozovik +972-54-923-7674 Sent from my Samsung Galaxy smartphone.

-------- Original message -------- From: antonpatenko <[email protected]> Date: 3/15/17 17:56 (GMT+02:00) To: Azure/sonic-mgmt <[email protected]> Cc: Subscribed <[email protected]> Subject: Re: [Azure/sonic-mgmt] Added two test cases of LAG testing (on t1-lag topology) (#129) @antonpatenko commented on this pull request.

________________________________ In ansible/roles/test/tasks/lag_vm_ports_test.yml<#129 (comment)>:

+# 1.2) Verify all the traffic goes through another LAG member and no packets lost.

+# +# @ params: login_creds - credentials for Arista VM +# @ params: vm_name +# @ params: lag_ip - LAG interface IP address +# @ params: lag_member_0 - First LAG member on VM +# @ params: lag_member_1 - Second LAG member on VM +# @ params: iface_behind_lag_member_0 - PTF docker iface, connected to LAG VM +# @ params: iface_behind_lag_member_1 - PTF docker iface, connected to LAG VM +# @ params: not_behind_lag_iface - PTF docker interface that is connected to non-LAG VM (meaning eth31) +# @ params: vm_ip - VM mgmt IP; taken from lag_link_flap_vars.yml +# @ params: num_of_pkts - number of packets to send while PTF test. +#--------------------------------------------------------- + + # --- TEST FIRST LAG MEMBER --- +- block: Well, I can make test checking the topology type, but I'm not sure it makes sense. Test assumes, that the user (who runs this test) guarantees that topology type is T1-LAG. But I can change that approach if we really need that. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#129 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AQ8YX9z6N_QB-lb6wa-AbUJtli16e7fpks5rmAo-gaJpZM4MI7ze>.