http://wiki.nesevo.com/index.php?action=history&feed=atom&title=Sonic-lab
Sonic-lab - Revision history
2026-05-30T12:00:33Z
Revision history for this page on the wiki
MediaWiki 1.35.1
http://wiki.nesevo.com/index.php?title=Sonic-lab&diff=2985&oldid=prev
PierreLancastre at 08:47, 29 October 2021
2021-10-29T08:47:37Z
<p></p>
<table class="diff diff-contentalign-left diff-editfont-monospace" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 08:47, 29 October 2021</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l26" >Line 26:</td>
<td colspan="2" class="diff-lineno">Line 26:</td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Once you're ready, please run the lab by launching "./start.sh"</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Once you're ready, please run the lab by launching "./start.sh"</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>The script :<del class="diffchange diffchange-inline"><div></div></del></div></td><td class='diff-marker'>+</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>The script :</div></td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del class="diffchange diffchange-inline"> </del>* launches the containers without Docket network features</div></td><td class='diff-marker'>+</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>* launches the containers without Docket network features</div></td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del class="diffchange diffchange-inline"> </del>* create network namespaces</div></td><td class='diff-marker'>+</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>* create network namespaces</div></td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del class="diffchange diffchange-inline"> </del>* build linux bridges to interconnect the containers</div></td><td class='diff-marker'>+</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>* build linux bridges to interconnect the containers</div></td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del class="diffchange diffchange-inline"> </del>* configure host IPs</div></td><td class='diff-marker'>+</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>* configure host IPs</div></td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del class="diffchange diffchange-inline"> </del>* launch startup sonic scripts into sonic devices</div></td><td class='diff-marker'>+</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>* launch startup sonic scripts into sonic devices</div></td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del class="diffchange diffchange-inline"> </del>* once devices started, checks + ping tests are run. If all BGP sessions are ok on spine + all ping are fine, the setup works well.</div></td><td class='diff-marker'>+</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>* once devices started, checks + ping tests are run. If all BGP sessions are ok on spine + all ping are fine, the setup works well.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The "start" script has several comments, perhaps without the right vocabulary, so please be tolerant :)</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The "start" script has several comments, perhaps without the right vocabulary, so please be tolerant :)</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
</table>
PierreLancastre
http://wiki.nesevo.com/index.php?title=Sonic-lab&diff=2978&oldid=prev
PierreLancastre: Created page with " <span><to be noted that those informations are included into the readme.md file into the archive></span> == Lab diagram == File:SONIC_LAB.jpg Lab archive [https://wiki...."
2021-10-29T08:34:39Z
<p>Created page with " <span><to be noted that those informations are included into the readme.md file into the archive></span> == Lab diagram == <a href="/index.php/File:SONIC_LAB.jpg" title="File:SONIC LAB.jpg">File:SONIC_LAB.jpg</a> Lab archive [https://wiki...."</p>
<p><b>New page</b></p><div><br />
<span><to be noted that those informations are included into the readme.md file into the archive></span><br />
<br />
== Lab diagram ==<br />
[[File:SONIC_LAB.jpg]]<br />
<br />
Lab archive [https://wiki.nesevo.com/images/0/0a/Sonic-lab-20201030.zip Sonic-lab-20201030.zip]<br />
<br />
This lab is a forked lab from many found on @, starting from Microsoft one : https://github.com/Azure/SONiC/wiki/SONiC-P4-Software-Switch<br />
<br />
The target of this lab is to simulate a simple IP/Fabric in SPINE/LEAF topology. Each Leaf provide local L2 connectivity + L3 gateways to hosts. Flows between hosts from different leaf are L3 routed, in a "node path" LEAF-SPINE-LEAF.<br />
<br />
Nothing complicated, but it allows to put a first foot into SONiC world :)<br />
<br />
For the moment, as far as we know, MC-LAG + EVPN/VXLAN features are only available on entreprise SONiC versions. Tests to come once physic switches in enterprise version will be available in our lab.<br />
<br />
The diagram of the architecture is into the zip file (SONIC_LAB.jpg)<br />
<br />
To run the lab you need :<br />
<br />
* to have installed docker by using ./install_docker_ovs.sh <br />
* to run the ./load_image.sh in order to get the Sonic image<br />
<br />
Note : don't change file / folders names of network devices (leafX, spineX)<br />
<br />
Once you're ready, please run the lab by launching "./start.sh"<br />
<br />
The script :<div></div><br />
* launches the containers without Docket network features<br />
* create network namespaces<br />
* build linux bridges to interconnect the containers<br />
* configure host IPs<br />
* launch startup sonic scripts into sonic devices<br />
* once devices started, checks + ping tests are run. If all BGP sessions are ok on spine + all ping are fine, the setup works well.<br />
The "start" script has several comments, perhaps without the right vocabulary, so please be tolerant :)<br />
<br />
If you want to stop the lab, please launch "./stop.sh"<br />
<br />
Below some useful commands to run for sonic containers :<br />
<br />
=== <span>run ping</span> ===<br />
<syntaxhighlight lang="bash"><br />
sudo docker exec -it <container> ping <ip><br />
</syntaxhighlight><br />
This command triggers ping into the targetted container :<br />
<syntaxhighlight lang="bash"><br />
plancastre@dockerhost:~/00.Projects/p4-version-pla$ sudo docker exec -it leaf1 ping 192.168.1.1<br />
PING 192.168.1.1 (192.168.1.1): 56 data bytes<br />
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=0.052 ms<br />
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.034 ms<br />
^C--- 192.168.1.1 ping statistics ---<br />
</syntaxhighlight><br />
<br />
=== <span>check bgp sessions</span> ===<br />
<syntaxhighlight lang="bash"><br />
sudo docker exec -it <container> vtysh -c "show ip bgp sum"<br />
</syntaxhighlight><br />
This command sollicitates the SONiC shell of the targeted container, in order to print the bgp status.<br />
Below, we run it on one spine, you should have 4 sessiosn UP (for the 4 leaves)<br />
<syntaxhighlight lang="bash"><br />
plancastre@dockerhost:~/00.Projects/p4-version-pla$ sudo docker exec -it spine1 vtysh -c "show ip bgp sum"<br />
BGP router identifier 10.1.0.1, local AS number 65001<br />
RIB entries 8, using 896 bytes of memory<br />
Peers 4, using 18 KiB of memory<br />
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd<br />
10.1.0.0 4 65101 6409 6411 0 0 0 01:46:46 3<br />
10.1.0.2 4 65102 6406 6410 0 0 0 01:46:44 3<br />
10.1.0.4 4 65103 6407 6410 0 0 0 01:46:44 4<br />
10.1.0.6 4 65104 6406 6412 0 0 0 01:46:46 1<br />
Total number of neighbors 4<br />
</syntaxhighlight><br />
<br />
=== <span>check ip route</span> ===<br />
<syntaxhighlight lang="bash"><br />
sudo docker exec -it <container> vtysh -c "show ip route"<br />
</syntaxhighlight><br />
This command sollicitates the SONiC shell of the targeted container, in order to print its routing table?<br />
<br />
<syntaxhighlight lang="bash"><br />
plancastre@dockerhost:~/00.Projects/p4-version-pla$ sudo docker exec -it spine1 vtysh -c "show ip route"<br />
Codes: K - kernel route, C - connected, S - static, R - RIP,<br />
O - OSPF, I - IS-IS, B - BGP, P - PIM, A - Babel,<br />
> - selected route, * - FIB route<br />
C>* 10.1.0.0/31 is directly connected, Vlan11<br />
C>* 10.1.0.2/31 is directly connected, Vlan21<br />
C>* 10.1.0.4/31 is directly connected, Vlan31<br />
C>* 10.1.0.6/31 is directly connected, Vlan41<br />
C>* 127.0.0.0/8 is directly connected, lo<br />
B>* 192.168.1.0/24 [20/0] via 10.1.0.0, Vlan11, 01:47:23<br />
B>* 192.168.2.0/24 [20/0] via 10.1.0.2, Vlan21, 01:47:21<br />
B>* 192.168.3.0/24 [20/0] via 10.1.0.4, Vlan31, 01:47:21<br />
B>* 192.168.4.0/24 [20/0] via 10.1.0.6, Vlan41, 01:47:23<br />
</syntaxhighlight><br />
For more commands check SONiC docs : https://github.com/Azure/sonic-utilities/blob/master/doc/Command-Reference.md<br />
<br />
To finish, below the output of the start.sh when all goes well<div></div><br />
plancastre@dockerhost:~/00.Projects/p4-version-pla$ ./start.sh <br />
---------------------------------------------------<br />
Creating the containers: starting<br />
---------------------------------------------------<br />
0b4bbb3c6cfc9895466ea13a9e940d1a176d66f45deee9752e9b4732d735bb03<br />
5ca9486baab3e8a5259062167132a944eee717875d3cc1ef29fe490cba3184c1<br />
46c9c09dba27a32715b9fbe0bc434a9284b9d59317d278df693f425cb669f037<br />
898e6afbcb2977115acbba2a69d069796cfd70fb90228b6c18e09ba4584365f7<br />
eb9b3ef6d14784c9ffe4d9d5df3e921a24559889cb8770d226263aad6761182a<br />
ae5f3b2c628da687eaabb331dc2cd989e71bcb386854e7a0be6ec587df99d49a<br />
122197bffd7566a01ce3b6565fdfb6eb893aab7d5236f14e5a9bbbe95037ced2<br />
a604520a080e2a2184598ad1d915c0c182d16e5185033373e95a4772d8978a67<br />
0c49e18d78b2aa7c8ef8e937b60285aa56ec0bf4a8530226285270a085e11d5c<br />
eb66336b8c6bd8333f1f4f685369e6cac973b817c35bb7126ac4d7ba72ef71bf<br />
---------------------------------------------------<br />
Retreiving PID from docker containers<br />
---------------------------------------------------<br />
---------------------------------------------------<br />
Creating network namespaces for containers<br />
---------------------------------------------------<br />
List of created namespaces<br />
ns_host4<br />
ns_host3<br />
ns_host2<br />
ns_host1<br />
ns_spine2<br />
ns_spine1<br />
ns_leaf4<br />
ns_leaf3<br />
ns_leaf2<br />
ns_leaf1<br />
---------------------------------------------------<br />
Creating network connectivity between containers<br />
---------------------------------------------------<br />
---------------------------------------------------<br />
Now assigning IPs to hosts (host1 to host4)<br />
---------------------------------------------------<br />
---------------------------------------------------<br />
Configuration of containers is now finished<br />
---------------------------------------------------<br />
---------------------------------------------------<br />
Now booting switches, please wait 2 minutes for switches to load<br />
---------------------------------------------------<br />
---------------------------------------------------<br />
2 minutes period is finished<br />
---------------------------------------------------<br />
---------------------------------------------------<br />
Now fixing the iptables<br />
---------------------------------------------------<br />
---------------------------------------------------<br />
Backend actions are now finished<br />
---------------------------------------------------<br />
---------------------------------------------------<br />
Now we'll check in 15 sec that BGP peers are all Up<br />
---------------------------------------------------<br />
---------------------------------------------------<br />
SPINE1 check BGP Sessions<br />
---------------------------------------------------<br />
BGP router identifier 10.1.0.1, local AS number 65001<br />
RIB entries 8, using 896 bytes of memory<br />
Peers 4, using 18 KiB of memory<br />
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd<br />
10.1.0.0 4 65101 94 97 0 0 0 00:01:28 4<br />
10.1.0.2 4 65102 95 97 0 0 0 00:01:28 5<br />
10.1.0.4 4 65103 95 97 0 0 0 00:01:28 5<br />
10.1.0.6 4 65104 95 97 0 0 0 00:01:28 5<br />
Total number of neighbors 4<br />
---------------------------------------------------<br />
SPINE2 check BGP Sessions<br />
---------------------------------------------------<br />
BGP router identifier 10.2.0.1, local AS number 65002<br />
RIB entries 8, using 896 bytes of memory<br />
Peers 4, using 18 KiB of memory<br />
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd<br />
10.2.0.0 4 65101 93 96 0 0 0 00:01:29 2<br />
10.2.0.2 4 65102 94 100 0 0 0 00:01:32 1<br />
10.2.0.4 4 65103 94 100 0 0 0 00:01:32 1<br />
10.2.0.6 4 65104 94 100 0 0 0 00:01:32 1<br />
Total number of neighbors 4<br />
---------------------------------------------------<br />
Now if all is ok, we'll do some ping tests<br />
---------------------------------------------------<br />
---------------------------------------------------<br />
host1 ping its gateway<br />
---------------------------------------------------<br />
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.<br />
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=17.6 ms<br />
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=9.14 ms<br />
--- 192.168.1.1 ping statistics ---<br />
2 packets transmitted, 2 received, 0% packet loss, time 1000ms<br />
rtt min/avg/max/mdev = 9.145/13.390/17.636/4.247 ms<br />
---------------------------------------------------<br />
host2 ping its gateway<br />
---------------------------------------------------<br />
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.<br />
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=23.6 ms<br />
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=6.21 ms<br />
--- 192.168.2.1 ping statistics ---<br />
2 packets transmitted, 2 received, 0% packet loss, time 1001ms<br />
rtt min/avg/max/mdev = 6.218/14.950/23.683/8.733 ms<br />
---------------------------------------------------<br />
host3 ping its gateway<br />
---------------------------------------------------<br />
PING 192.168.3.1 (192.168.3.1) 56(84) bytes of data.<br />
64 bytes from 192.168.3.1: icmp_seq=1 ttl=64 time=18.8 ms<br />
64 bytes from 192.168.3.1: icmp_seq=2 ttl=64 time=12.7 ms<br />
--- 192.168.3.1 ping statistics ---<br />
2 packets transmitted, 2 received, 0% packet loss, time 1001ms<br />
rtt min/avg/max/mdev = 12.716/15.764/18.812/3.048 ms<br />
---------------------------------------------------<br />
host4 ping its gateway<br />
---------------------------------------------------<br />
PING 192.168.4.1 (192.168.4.1) 56(84) bytes of data.<br />
64 bytes from 192.168.4.1: icmp_seq=1 ttl=64 time=17.7 ms<br />
64 bytes from 192.168.4.1: icmp_seq=2 ttl=64 time=4.46 ms<br />
--- 192.168.4.1 ping statistics ---<br />
2 packets transmitted, 2 received, 0% packet loss, time 1001ms<br />
rtt min/avg/max/mdev = 4.464/11.107/17.750/6.643 ms<br />
---------------------------------------------------<br />
host1 sends 3 ping the 3 other hosts<br />
---------------------------------------------------<br />
PING 192.168.2.2 (192.168.2.2) 56(84) bytes of data.<br />
64 bytes from 192.168.2.2: icmp_seq=1 ttl=61 time=16.0 ms<br />
64 bytes from 192.168.2.2: icmp_seq=2 ttl=61 time=19.5 ms<br />
64 bytes from 192.168.2.2: icmp_seq=3 ttl=61 time=16.1 ms<br />
--- 192.168.2.2 ping statistics ---<br />
3 packets transmitted, 3 received, 0% packet loss, time 2002ms<br />
rtt min/avg/max/mdev = 16.049/17.253/19.532/1.615 ms<br />
PING 192.168.3.2 (192.168.3.2) 56(84) bytes of data.<br />
64 bytes from 192.168.3.2: icmp_seq=1 ttl=61 time=15.5 ms<br />
64 bytes from 192.168.3.2: icmp_seq=2 ttl=61 time=14.3 ms<br />
64 bytes from 192.168.3.2: icmp_seq=3 ttl=61 time=16.9 ms<br />
--- 192.168.3.2 ping statistics ---<br />
3 packets transmitted, 3 received, 0% packet loss, time 2002ms<br />
rtt min/avg/max/mdev = 14.312/15.592/16.939/1.083 ms<br />
PING 192.168.4.2 (192.168.4.2) 56(84) bytes of data.<br />
64 bytes from 192.168.4.2: icmp_seq=1 ttl=61 time=16.0 ms<br />
64 bytes from 192.168.4.2: icmp_seq=2 ttl=61 time=20.7 ms<br />
64 bytes from 192.168.4.2: icmp_seq=3 ttl=61 time=16.8 ms<br />
--- 192.168.4.2 ping statistics ---<br />
3 packets transmitted, 3 received, 0% packet loss, time 2002ms<br />
rtt min/avg/max/mdev = 16.048/17.871/20.739/2.058 ms<br />
---------------------------------------------------<br />
host2 sends 3 ping the 3 other hosts<br />
---------------------------------------------------<br />
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.<br />
64 bytes from 192.168.1.2: icmp_seq=1 ttl=61 time=16.2 ms<br />
64 bytes from 192.168.1.2: icmp_seq=2 ttl=61 time=16.6 ms<br />
64 bytes from 192.168.1.2: icmp_seq=3 ttl=61 time=16.9 ms<br />
--- 192.168.1.2 ping statistics ---<br />
3 packets transmitted, 3 received, 0% packet loss, time 2002ms<br />
rtt min/avg/max/mdev = 16.222/16.583/16.924/0.286 ms<br />
PING 192.168.3.2 (192.168.3.2) 56(84) bytes of data.<br />
64 bytes from 192.168.3.2: icmp_seq=1 ttl=61 time=16.6 ms<br />
64 bytes from 192.168.3.2: icmp_seq=2 ttl=61 time=18.1 ms<br />
64 bytes from 192.168.3.2: icmp_seq=3 ttl=61 time=26.8 ms<br />
--- 192.168.3.2 ping statistics ---<br />
3 packets transmitted, 3 received, 0% packet loss, time 2002ms<br />
rtt min/avg/max/mdev = 16.620/20.549/26.887/4.524 ms<br />
PING 192.168.4.2 (192.168.4.2) 56(84) bytes of data.<br />
64 bytes from 192.168.4.2: icmp_seq=1 ttl=61 time=33.8 ms<br />
64 bytes from 192.168.4.2: icmp_seq=2 ttl=61 time=27.7 ms<br />
64 bytes from 192.168.4.2: icmp_seq=3 ttl=61 time=20.2 ms<br />
--- 192.168.4.2 ping statistics ---<br />
3 packets transmitted, 3 received, 0% packet loss, time 2002ms<br />
rtt min/avg/max/mdev = 20.216/27.259/33.818/5.566 ms<br />
---------------------------------------------------<br />
host3 sends 3 ping the 3 other hosts<br />
---------------------------------------------------<br />
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.<br />
64 bytes from 192.168.1.2: icmp_seq=1 ttl=61 time=14.5 ms<br />
64 bytes from 192.168.1.2: icmp_seq=2 ttl=61 time=19.5 ms<br />
64 bytes from 192.168.1.2: icmp_seq=3 ttl=61 time=15.5 ms<br />
--- 192.168.1.2 ping statistics ---<br />
3 packets transmitted, 3 received, 0% packet loss, time 2002ms<br />
rtt min/avg/max/mdev = 14.535/16.549/19.541/2.162 ms<br />
PING 192.168.2.2 (192.168.2.2) 56(84) bytes of data.<br />
64 bytes from 192.168.2.2: icmp_seq=1 ttl=61 time=16.4 ms<br />
64 bytes from 192.168.2.2: icmp_seq=2 ttl=61 time=14.6 ms<br />
64 bytes from 192.168.2.2: icmp_seq=3 ttl=61 time=18.2 ms<br />
--- 192.168.2.2 ping statistics ---<br />
3 packets transmitted, 3 received, 0% packet loss, time 2002ms<br />
rtt min/avg/max/mdev = 14.643/16.458/18.278/1.491 ms<br />
PING 192.168.4.2 (192.168.4.2) 56(84) bytes of data.<br />
64 bytes from 192.168.4.2: icmp_seq=1 ttl=61 time=15.3 ms<br />
64 bytes from 192.168.4.2: icmp_seq=2 ttl=61 time=14.1 ms<br />
64 bytes from 192.168.4.2: icmp_seq=3 ttl=61 time=13.1 ms<br />
--- 192.168.4.2 ping statistics ---<br />
3 packets transmitted, 3 received, 0% packet loss, time 2001ms<br />
rtt min/avg/max/mdev = 13.171/14.234/15.334/0.883 ms<br />
---------------------------------------------------<br />
host4 sends 3 ping the 3 other hosts<br />
---------------------------------------------------<br />
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.<br />
64 bytes from 192.168.1.2: icmp_seq=1 ttl=61 time=21.9 ms<br />
64 bytes from 192.168.1.2: icmp_seq=2 ttl=61 time=21.3 ms<br />
64 bytes from 192.168.1.2: icmp_seq=3 ttl=61 time=14.6 ms<br />
--- 192.168.1.2 ping statistics ---<br />
3 packets transmitted, 3 received, 0% packet loss, time 2001ms<br />
rtt min/avg/max/mdev = 14.619/19.284/21.932/3.310 ms<br />
PING 192.168.2.2 (192.168.2.2) 56(84) bytes of data.<br />
64 bytes from 192.168.2.2: icmp_seq=1 ttl=61 time=14.8 ms<br />
64 bytes from 192.168.2.2: icmp_seq=2 ttl=61 time=18.4 ms<br />
64 bytes from 192.168.2.2: icmp_seq=3 ttl=61 time=14.1 ms<br />
--- 192.168.2.2 ping statistics ---<br />
3 packets transmitted, 3 received, 0% packet loss, time 2002ms<br />
rtt min/avg/max/mdev = 14.148/15.786/18.409/1.879 ms<br />
PING 192.168.3.2 (192.168.3.2) 56(84) bytes of data.<br />
64 bytes from 192.168.3.2: icmp_seq=1 ttl=61 time=16.2 ms<br />
64 bytes from 192.168.3.2: icmp_seq=2 ttl=61 time=15.1 ms<br />
64 bytes from 192.168.3.2: icmp_seq=3 ttl=61 time=18.9 ms<br />
--- 192.168.3.2 ping statistics ---<br />
3 packets transmitted, 3 received, 0% packet loss, time 2001ms<br />
rtt min/avg/max/mdev = 15.117/16.788/18.962/1.612 ms<br />
---------------------------------------------------<br />
If bot spine have all BGP sessions and all ping succeeded, all works well<br />
Congrats ! please check readme file to find some details<br />
---------------------------------------------------</div>
PierreLancastre