Opened 12 years ago
Last modified 12 years ago
#142 new
unable to exchange Iperf tcp traffic between BT and VM in GPO rack
Reported by: | lnevers@bbn.com | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Experiment | Version: | SPIRAL5 |
Keywords: | Cc: | ||
Dependencies: |
Description
Created a sliver EG-MON-4-exp2 that includes 1 VM and one Bare Metal node. Able to exchange traffic between the two hosts, but am not able to exchange iperf TCP traffic it fails with a "No route to host" even though a route exists:
root@debian:~# /sbin/ifconfig eth1 eth1 Link encap:Ethernet HWaddr fe:16:3e:00:31:74 inet addr:172.16.1.2 Bcast:172.16.1.255 Mask:255.255.255.0 inet6 addr: fe80::fc16:3eff:fe00:3174/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:132 errors:0 dropped:0 overruns:0 frame:0 TX packets:2730 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:38496 (37.5 KiB) TX bytes:4008088 (3.8 MiB) root@debian:~# ping 172.16.1.1 -c 4 PING 172.16.1.1 (172.16.1.1) 56(84) bytes of data. 64 bytes from 172.16.1.1: icmp_req=2 ttl=64 time=0.497 ms 64 bytes from 172.16.1.1: icmp_req=3 ttl=64 time=0.365 ms 64 bytes from 172.16.1.1: icmp_req=4 ttl=64 time=0.328 ms --- 172.16.1.1 ping statistics --- 4 packets transmitted, 3 received, 25% packet loss, time 2999ms rtt min/avg/max/mdev = 0.328/0.396/0.497/0.076 ms root@debian:~# iperf -c 172.16.1.1 connect failed: No route to host root@debian:~#
Also tried iperf UDP, and it reports the "No route to host" failure, but it runs to completion:
root@debian:~# iperf -c 172.16.1.1 -t 10 -u ------------------------------------------------------------ Client connecting to 172.16.1.1, UDP port 5001 Sending 1470 byte datagrams UDP buffer size: 122 KByte (default) ------------------------------------------------------------ [ 3] local 172.16.1.2 port 42064 connected with 172.16.1.1 port 5001 read failed: No route to host [ 3] WARNING: did not receive ack of last datagram after 1 tries. [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 1.23 MBytes 1.03 Mbits/sec [ 3] Sent 893 datagrams
Note: See
TracTickets for help on using
tickets.
After re-creating the sliver, this just works... Strange! Will recreate the sliver sever times to determine how often the "No Route to Host" problem occurs.