Rev 1.2
12
Mellanox Technologies
Note: Replace interface names in the commands below as appropriate. See
3,“Test Set-up Architecture” on page 9
Step 2.
Verify connectivity and link speed for all six interfaces on all four servers. You may use ethtool
to query the link state and/or ping to test connectivity. Example:
4.1.3 IP Routing Topology
Step 1.
Turn on IP forwarding on both gateway servers:
Step 2.
Add routes between all three subnets:
Step 3.
Verify forwarding connectivity between the two servers. At this point, traffic is neither
encrypted nor encapsulated:
[root@server-a ~]# ifconfig ens1 192.168.8.2/24 up
[root@server-a ~]# ip addr add 192.168.8.3/24 dev ens1
[root@server-a ~]# ip addr add 192.168.8.4/24 dev ens1
[root@gateway-c ~]# ifconfig ens1 192.168.8.1/24 up
[root@gateway-c ~]# ifconfig ens2 192.168.7.2/24 up
[root@gateway-d ~]# ifconfig ens2 192.168.7.9/24 up
[root@gateway-d ~]# ifconfig ens1 192.168.9.1/24 up
[root@server-b ~]# ifconfig ens1 192.168.9.2/24 up
[root@server-b ~]# ip addr add 192.168.9.3/24 dev ens1
[root@server-b ~]# ip addr add 192.168.9.4/24 dev ens1
[root@server-a ~]# ping 192.168.8.1
[root@gateway-c ~]# echo 1 > /proc/sys/net/ipv4/ip_forward
[root@gateway-d ~]# echo 1 > /proc/sys/net/ipv4/ip_forward
[root@server-a ~]# ip route add 192.168.7.0/24 via 192.168.8.1
[root@server-a ~]# ip route add 192.168.9.0/24 via 192.168.8.1
[root@gateway-c ~]# ip route add 192.168.9.0/24 via 192.168.7.9
[root@gateway-d ~]# ip route add 192.168.8.0/24 via 192.168.7.2
[root@server-b ~]# ip route add 192.168.7.0/24 via 192.168.9.1
[root@server-b ~]# ip route add 192.168.8.0/24 via 192.168.9.1
[root@server-a ~]# ping 192.168.9.2
[root@server-b ~]# ping 192.168.8.2
