You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 29, 2021. It is now read-only.
We need to check the case of the remote connection of kernerl-forwarder and vppagent-forwarder via vxlan remote mechanism.
Test steps
Deploy nsmgr on node1. //force select vxlan remote mechanism
Deploy vppagent-forwarder on node1.
Deploy nsmgr on node2. //force select vxlan remote mechanism
Deploy kernel-forwarder on node2.
Deploy nse1 on node2
Deploy nsc1 on node1
Check ping from nsc1 to nse1.
Deploy nse2 on node1
Deploy nsc2 on node2.
Check ping from nsc2 to nse2
Expected: ping is a success in steps: 7, 10.
The text was updated successfully, but these errors were encountered:
denis-tingaikin
changed the title
Add test for remote connection between kernernel-forwarder and vppagent-forwarder
Add test for remote connection between kernel-forwarder and vppagent-forwarder
Mar 4, 2020
This issue has been automatically marked as stale because it has not had activity in 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
Motivation
We need to check the case of the remote connection of
kernerl-forwarder
andvppagent-forwarder
viavxlan
remote mechanism.Test steps
Expected: ping is a success in steps: 7, 10.
The text was updated successfully, but these errors were encountered: