[1758] Cable 4th Ethernet Ports on rack1-5 and 8 |
|||
Issue descriptionThese six racks *do* have active DUTs in the wificells. I'd suggest working on one rack at a time in case this cannot be complete by end of Friday 6/24. There is no release testing on Friday. Because these DUTs run tests over the weekend, we need to be sure any changes don't affect devices (in other words, make sure hostnames are pingable) before Friday ends. We can always continue on Monday if needed. Equipment (Joe/David, please comment if the following are not available): Ethernet adapters (male & female) Long network cables (~7 ft) Short network cables (~3 ft) USB-Ethernet dongles On each wificell, please: Lock the hostname in cautotest. Add Ethernet adapter to outer panel of wificell. Add network cable from outer panel to switch. Add Ethernet adapter to inner panel of wificell. Add network cable from inner panel to Ethernet<->USB dongle (dongle <-> Whirlwind packet capture device). Make sure dongle MAC address is in Android Lab Overview spreadsheet. If there is no dongle, take note of the MAC address, add it to the spreadsheet according to the host, and HIGHLIGHT the entry. Joe or I will walk you through making DHCP changes after the cabling. If there were DHCP changes, verify device is pingable by hostname.
,
Jun 24 2016
I gave 6 Startech USB-Ethernet dongles to Paul, and we are looking for the female Ethernet connectors. David, would you be able to order more USB-Ethernet dongles? Also, would you & Joe be able to provide Ethernet switches?
,
Jun 24 2016
Installed 8 USB Ethernet devices and updated the MAC address to Android Lab overview under ChromeOS WiFi Test Cell Block. Row1 Host1 / Row1 Host2 Row2 Host3 / Row2 Host4 Row3 Host1 / Row3 Host2 / Row3 Host3 / Row3 / Host4 Still needs 8 additional USB Ethernet devices and 10 female Ethernet connectors to complete the testbed.
,
Jun 27 2016
Updates: To complete the task USB Ethernet needed: Total 7 rack4 host1 / rack4 host3 / rack4 host4 rack5 host2 / rack5 host3 / rack5 host4 rack8 host4 Female connectors needed: 5 rack4 host2 / rack4 host3 / rack4 host4 rack5 host2 / rack5 host3
,
Jun 27 2016
Added the type of testbeds in the spreadsheet.
,
Jun 28 2016
Installed 7 additional USB Ethernet devices and 5 female Ethernet connectors to complete the task. Also added the MAC address for new USB Ethernet devices in the spreadsheet. From rack5 host3-pcap, the MAC address got changed from the spreadsheet. Joe: Please help us to update the DNS server for changed MAC address. Old MAC: 80:3f:5d:08:20:9e New MAC: 58:6d:8f:59:41:5c
,
Jun 28 2016
,
Jun 28 2016
Add Ethernet adapter to outer panel of wificell. Done Add network cable from outer panel to switch. Done Add Ethernet adapter to inner panel of wificell. Done Add network cable from inner panel to Ethernet<->USB dongle (dongle <-> Whirlwind packet capture device). Done Make sure dongle MAC address is in Android Lab Overview spreadsheet. Done If there is no dongle, take note of the MAC address, add it to the spreadsheet according to the host, and HIGHLIGHT the entry. Joe or I will walk you through making DHCP changes after the cabling. Joe or Tien If there were DHCP changes, verify device is pingable by hostname. rack5 host3-pcap MAC address got changed. After update the DNS server, will verify to see if the hostname is pingable.
,
Jun 29 2016
ping android1758-row4-rack3-host1 PING android1758-row4-rack3-host1.cros.corp.google.com (100.107.127.93) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-93.mtv.corp.google.com (100.107.127.93): icmp_seq=1 ttl=60 time=1.39 ms 64 bytes from dhcp-100-107-127-93.mtv.corp.google.com (100.107.127.93): icmp_seq=2 ttl=60 time=1.34 ms ^C --- android1758-row4-rack3-host1.cros.corp.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 1.348/1.370/1.393/0.043 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack3-host1-servo PING android1758-row4-rack3-host1-servo.cros.corp.google.com (100.107.127.95) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-95.mtv.corp.google.com (100.107.127.95): icmp_seq=1 ttl=60 time=0.778 ms 64 bytes from dhcp-100-107-127-95.mtv.corp.google.com (100.107.127.95): icmp_seq=2 ttl=60 time=0.739 ms ^C --- android1758-row4-rack3-host1-servo.cros.corp.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 0.739/0.758/0.778/0.033 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack3-host1-router PING android1758-row4-rack3-host1-router.cros.corp.google.com (100.107.127.94) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-94.mtv.corp.google.com (100.107.127.94): icmp_seq=1 ttl=60 time=0.975 ms 64 bytes from dhcp-100-107-127-94.mtv.corp.google.com (100.107.127.94): icmp_seq=2 ttl=60 time=0.854 ms ^C --- android1758-row4-rack3-host1-router.cros.corp.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 0.854/0.914/0.975/0.067 ms ping android1758-row4-rack4-host1 PING android1758-row4-rack4-host1.cros.corp.google.com (100.107.127.109) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-109.mtv.corp.google.com (100.107.127.109): icmp_seq=1 ttl=60 time=0.797 ms ^C --- android1758-row4-rack4-host1.cros.corp.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.797/0.797/0.797/0.000 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack4-host1-servo PING android1758-row4-rack4-host1-servo.cros.corp.google.com (100.107.127.111) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-111.mtv.corp.google.com (100.107.127.111): icmp_seq=1 ttl=60 time=0.688 ms 64 bytes from dhcp-100-107-127-111.mtv.corp.google.com (100.107.127.111): icmp_seq=2 ttl=60 time=0.615 ms ^C --- android1758-row4-rack4-host1-servo.cros.corp.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 0.615/0.651/0.688/0.044 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack4-host1-router PING android1758-row4-rack4-host1-router.cros.corp.google.com (100.107.127.110) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-110.mtv.corp.google.com (100.107.127.110): icmp_seq=1 ttl=60 time=0.882 ms 64 bytes from dhcp-100-107-127-110.mtv.corp.google.com (100.107.127.110): icmp_seq=2 ttl=60 time=0.900 ms ^C64 bytes from dhcp-100-107-127-110.mtv.corp.google.com (100.107.127.110): icmp_seq=3 ttl=60 time=0.827 ms 64 bytes from dhcp-100-107-127-110.mtv.corp.google.com (100.107.127.110): icmp_seq=4 ttl=60 time=1.05 ms ^C --- android1758-row4-rack4-host1-router.cros.corp.google.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3000ms rtt min/avg/max/mdev = 0.827/0.915/1.053/0.089 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack5-host1 PING android1758-row4-rack5-host1.cros.corp.google.com (100.107.127.125) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-125.mtv.corp.google.com (100.107.127.125): icmp_seq=1 ttl=60 time=1.03 ms ^C --- android1758-row4-rack5-host1.cros.corp.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.035/1.035/1.035/0.000 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack5-host1-servo PING android1758-row4-rack5-host1-servo.cros.corp.google.com (100.107.127.127) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-127.mtv.corp.google.com (100.107.127.127): icmp_seq=1 ttl=60 time=0.783 ms ^C --- android1758-row4-rack5-host1-servo.cros.corp.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.783/0.783/0.783/0.000 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack5-host1-servo PING android1758-row4-rack5-host1-servo.cros.corp.google.com (100.107.127.127) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-127.mtv.corp.google.com (100.107.127.127): icmp_seq=1 ttl=60 time=0.752 ms ^C --- android1758-row4-rack5-host1-servo.cros.corp.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.752/0.752/0.752/0.000 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack2-host1 PING android1758-row4-rack2-host1.cros.corp.google.com (100.107.127.77) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-77.mtv.corp.google.com (100.107.127.77): icmp_seq=1 ttl=60 time=0.821 ms ^C --- android1758-row4-rack2-host1.cros.corp.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.821/0.821/0.821/0.000 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack2-host1-router PING android1758-row4-rack2-host1-router.cros.corp.google.com (100.107.127.78) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-78.mtv.corp.google.com (100.107.127.78): icmp_seq=1 ttl=60 time=0.916 ms ^C --- android1758-row4-rack2-host1-router.cros.corp.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.916/0.916/0.916/0.000 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack2-host1-servo PING android1758-row4-rack2-host1-servo.cros.corp.google.com (100.107.127.79) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-79.mtv.corp.google.com (100.107.127.79): icmp_seq=1 ttl=60 time=2.30 ms ^C --- android1758-row4-rack2-host1-servo.cros.corp.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 2.302/2.302/2.302/0.000 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack2-host1-pcap PING android1758-row4-rack2-host1-pcap.cros.corp.google.com (100.107.127.80) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-80.mtv.corp.google.com (100.107.127.80): icmp_seq=1 ttl=60 time=0.793 ms 64 bytes from dhcp-100-107-127-80.mtv.corp.google.com (100.107.127.80): icmp_seq=2 ttl=60 time=0.995 ms ^C --- android1758-row4-rack2-host1-pcap.cros.corp.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 0.793/0.894/0.995/0.101 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack1-host1-router PING android1758-row4-rack1-host1-router.cros.corp.google.com (100.107.127.62) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-62.mtv.corp.google.com (100.107.127.62): icmp_seq=1 ttl=60 time=0.639 ms ^C --- android1758-row4-rack1-host1-router.cros.corp.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.639/0.639/0.639/0.000 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack1-host1-servo PING android1758-row4-rack1-host1-servo.cros.corp.google.com (100.107.127.63) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-63.mtv.corp.google.com (100.107.127.63): icmp_seq=1 ttl=60 time=0.880 ms ^C --- android1758-row4-rack1-host1-servo.cros.corp.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.880/0.880/0.880/0.000 ms
,
Jun 29 2016
Make sure dongle MAC address is in Android Lab Overview spreadsheet. Done If there is no dongle, take note of the MAC address, add it to the spreadsheet according to the host, and HIGHLIGHT the entry. Joe or I will walk you through making DHCP changes after the cabling. Done If there were DHCP changes, verify device is pingable by hostname. Done |
|||
►
Sign in to add a comment |
|||
Comment 1 by jongkyuj@google.com
, Jun 24 2016