Comment 6 for bug 1637649

From the debug session with Junaid, the issue is the MTU size. From the plumgrid-gateway node it cannot ping the plumgrid-director node with MTU size 1580 (1580 is the requirements).

pomeroy is the plumgrid-gateway node.

# ping plumgrid-director node with 1552 does not work
ubuntu@pomeroy:/var/lib/plumgrid/plumgrid-data/conf/pg$ ping -c 4 -s 1552 -M do 10.245.1.102
PING 10.245.1.102 (10.245.1.102) 1552(1580) bytes of data.

# ping plumgrid-director node with 1452 works
ubuntu@pomeroy:/var/lib/plumgrid/plumgrid-data/conf/pg$ ping -c 4 -s 1452 -M do 10.245.1.102
PING 10.245.1.102 (10.245.1.102) 1452(1480) bytes of data.
1460 bytes from 10.245.1.102: icmp_seq=1 ttl=64 time=0.406 ms
1460 bytes from 10.245.1.102: icmp_seq=2 ttl=64 time=0.399 ms
1460 bytes from 10.245.1.102: icmp_seq=3 ttl=64 time=0.382 ms
1460 bytes from 10.245.1.102: icmp_seq=4 ttl=64 time=0.331 ms

ubuntu@pomeroy:/var/lib/plumgrid/plumgrid-data/conf/pg$ cat ifcs.conf
br-eth0 = fabric_core host
eth1 = access_phys
ubuntu@pomeroy:/var/lib/plumgrid/plumgrid-data/conf/pg$ cat plumgrid.conf
plumgrid_ip=10.245.1.102 #plumgrid-director IP
plumgrid_port=8001
mgmt_dev=br-eth0
label=pomeroy
plumgrid_rsync_port=2222
plumgrid_rest_addr=0.0.0.0:9180
fabric_mode=host
plumgrid_syslog_ng_ip=
plumgrid_syslog_ng_port=
plumgrid_monitor_interval=
start_plumgrid_iovisor=yes
start_plumgrid=`/opt/pg/scripts/pg_is_director.sh $plumgrid_ip`
location=

From plumgrid-edge node, we are able to ping plumgrid-director node:
ubuntu@sirrush:~$ ping -c 4 -s 1552 -M do 10.245.1.102
PING 10.245.1.102 (10.245.1.102) 1552(1580) bytes of data.
1560 bytes from 10.245.1.102: icmp_seq=1 ttl=64 time=0.350 ms
1560 bytes from 10.245.1.102: icmp_seq=2 ttl=64 time=0.371 ms
1560 bytes from 10.245.1.102: icmp_seq=3 ttl=64 time=0.378 ms