New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 625275 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Email to this user bounced
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Add Whirlwind Packet Captures

Project Member Reported by bmahadev@chromium.org, Jul 1 2016

Issue description

Refer the whirlwind migration doc for the full list. But here are the handy hostnames:

android1758-row4-rack2-host4 Setzer
android1758-row4-rack3-host2	Lars
android1758-row4-rack3-host3	Samus
	
Conductive	
android1758-row4-rack4-host1	gandof

Steps:
1.Take an OTA/conductive whirlwind from crux
2.Connect it to the fourth ethernet port within the cell
3.Have David/Joe enable that port for us
4.Make a dhcp entry for the pcap device like: <host>-pcap
5.Make sure the pcap device is pingable 

Note: For the conductive one make suitable connection as in conductive setup.



 
Cc: krisr@chromium.org
android1758-row4-rack2-host4 Setzer
1.Take an OTA/conductive whirlwind from crux done
2.Connect it to the fourth ethernet port within the cell done
3.Have David/Joe enable that port for us done, Joe completed this morning.
4.Make a dhcp entry for the pcap device like: <host>-pcap done
5.Make sure the pcap device is pingable done

Status: Fixed (was: Assigned)
android1758-row4-rack3-host2	Lars     80:3f:5d:08:22:df
android1758-row4-rack3-host3	Samus    80:3f:5d:09:d2:df
	
Conductive	
android1758-row4-rack4-host1	gandof   94:10:3e:b7:db:75

Steps:
1.Take an OTA/conductive whirlwind from crux Done
2.Connect it to the fourth ethernet port within the cell Done
3.Have David/Joe enable that port for us Done
4.Make a dhcp entry for the pcap device like: <host>-pcap Joe will do it today
5.Make sure the pcap device is pingable After dhcp entry, will verify
Status: Verified (was: Fixed)
jongkyuj@jongkyuj0:~$ ping android1758-row4-rack3-host2-pcap
PING android1758-row4-rack3-host2-pcap.cros.corp.google.com (100.107.127.100) 56(84) bytes of data.
64 bytes from dhcp-100-107-127-100.mtv.corp.google.com (100.107.127.100): icmp_seq=1 ttl=60 time=1.11 ms
64 bytes from dhcp-100-107-127-100.mtv.corp.google.com (100.107.127.100): icmp_seq=2 ttl=60 time=1.01 ms
^C
--- android1758-row4-rack3-host2-pcap.cros.corp.google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 1.013/1.063/1.114/0.060 ms
jongkyuj@jongkyuj0:~$ ^C
jongkyuj@jongkyuj0:~$ ping android1758-row4-rack3-host3-pcap
PING android1758-row4-rack3-host3-pcap.cros.corp.google.com (100.107.127.104) 56(84) bytes of data.
64 bytes from dhcp-100-107-127-104.mtv.corp.google.com (100.107.127.104): icmp_seq=1 ttl=60 time=0.848 ms
^C
--- android1758-row4-rack3-host3-pcap.cros.corp.google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.848/0.848/0.848/0.000 ms
jongkyuj@jongkyuj0:~$ ping android1758-row4-rack4-host1-pcap
PING android1758-row4-rack4-host1-pcap.cros.corp.google.com (100.107.127.112) 56(84) bytes of data.
64 bytes from dhcp-100-107-127-112.mtv.corp.google.com (100.107.127.112): icmp_seq=1 ttl=60 time=0.676 ms
^C
--- android1758-row4-rack4-host1-pcap.cros.corp.google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.676/0.676/0.676/0.000 ms
Hi Bindu,

The spreadsheet has been updated.

Thanks,
Paul

Sign in to add a comment