@ David/Joe: What range of static IP's we would be assigning to the packet captures? 
p.s. This if for the dhcp change

+Joe

Which hosts would this be for so I can direct to the correct IP range?


Joe


Joe Ashur |  Lab Admin |  jashur@gmail |  847-525-3036

The ones marked in yellow in the following spreadsheet.

https://docs.google.com/spreadsheets/d/174X-oYFi5ypAgFCRVj1Z4YUoEaz6bc0JeITTEf-chh8/edit?ts=56df1c0e#gid=0

I added space for you in the following CL
https://chrome-internal-review.googlesource.com/#/c/261025/2

Please make any necessary changes to the hostname when you add the mac
addresses if needed.


Joe Ashur |  Lab Admin |  jashur@gmail |  847-525-3036

@David/Joe: As suggested by Bindu n Tien, I am going to add a pcap dhcp entry for each cell in 1758 sequentially. Do you guys see any issues implementing it,  like running out  of IP address or some other issues?  

8 racks, 4 cells per rack = 32 additional IP's. 

I thought you only needed space for 8?


Joe Ashur |  Lab Admin |  jashur@gmail |  847-525-3036

This is to future proof it. If we need to make a change, we don't have to move  IP's everytime.

In total, you will need 128 addresses is this correct?

Yes, in total. 32 additional IP's.

Your current starting spot is android1758-row4-rack1-host1 100.107.127.70

this block ends at android1758-row4-rack8-host4-servo 100.107.127.166

then there is another block starting with

android1758-row4-rack7-host1-chameleon 100.107.127.167

and ends with android1758-row4-rack8-host4-chameleon 100.107.127.174

After this there are 26 addresses before x.x.x.200. You may use these 26 addresses to keep everything in a block and sequential. However, in order to use these 26 addresses

android1758-shelf2-host8-femtocell  100.107.127.178
android1758-row3-rack2-power-test-router 100.107.127.179

will need to be relocated

This will give you 26 of the 32. The other 6 can be taken by moving up your starting address to 100.107.127.64

This will mean android1758-row4-rack1-host1 will now be 100.107.127.64.

android1758-row4-rack1-host1-router   100.107.127.65
android1758-row4-rack1-host1-servo    100.107.127.66
android1758-row4-rack1-host1-pcap     100.107.127.67

android1758-row4-rack1-host2          100.107.127.68
android1758-row4-rack1-host2-router   100.107.127.69
android1758-row4-rack1-host2-servo    100.107.127.70
android1758-row4-rack1-host2-pcap     100.107.127.71

Until you get to 
android1758-row4-rack7-host1              100.107.127.xx
android1758-row4-rack7-host1-router       100.107.127.xx
android1758-row4-rack7-host1-servo        100.107.127.xx
android1758-row4-rack7-host1-pcap         100.107.127.xx
android1758-row4-rack7-host1-chameleon    100.107.127.xx

The host with the chameleon in them will need a switch. I have spares so I can provide this hardware.

android1758-shelf2-host8-femtocell  100.107.127.178 can be moved to 100.107.127.62 ( coordinate with Harpreet )
android1758-row3-rack2-power-test-router 100.107.127.179 can be moved to 100.107.127.63 ( I think this is possibly Ang's device so probably coordinate with his team on this change )

Also, rack1 through rack6 will need to have an additional ethernet cable added to it's setup.

I have a CL ready ( just need to add mac address for packet capture )and started from 100.107.127.61.   I will move WiFi unrelated devices to the end of the block instead of start otherwise, I will have to revise the whole thing again. 

@Ang The following change will affect android1758-row3-rack2-power-test-router  
https://chrome-internal-review.googlesource.com/#/c/262235/

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/4f23510bf6b524c77bfb6a5cf70892f79d6de675

commit 4f23510bf6b524c77bfb6a5cf70892f79d6de675
Author: aashutosh <aashutoshk@google.com>
Date: Thu Jun 02 23:52:57 2016