One more AP

[94:44:52:a4:fe:4e]
brand = belkin
wan_hostname = chromeos3-row4-rack4-host3
bss = 94:44:52:a4:fe:4e
wan mac = 94:44:52:a4:fe:4f
model = f7d2301 v1_1
class_name = BelkinF9KAPConfigurator
admin_url = http://chromeos3-row4-rack4-host3:8080
admin_ip = http://172.22.39.63:8080

chromeos3-row4-rack2-host2 Done
The AP is reset and able to reach the admin page of the AP.

chromeos3-row4-rack4-host3 Done
This Belkin AP is not able reachable after reset, not able to ping this AP at all. I tried to factory reset this AP by holding down the reset button and still failed to reset. This AP seems that it needs to be replaced with new one. 

This host has the same AP:
chromeos3-row4-rack2-host8

[94:44:52:62:bd:81]
brand = belkin
wan_hostname = chromeos3-row4-rack2-host8
bss = 94:44:52:62:bd:81
wan mac = 94:44:52:62:bd:82
model = f7d1301 v1_2
class_name = BelkinF9KAPConfigurator
admin_url = http://chromeos3-row4-rack2-host8:8080
admin_ip = http://172.22.39.28:8080

Paul, can you check if this AP is pingable? Since there are 2 of the same model AP, if the chromeos3-row4-rack4-host3 is broken, we could potentially remove it from our inventory or replace it.

chromeos3-row4-rack2-host8
This host is pingable.
Should we replace the AP in chromeos3-row4-rack4-host3 or replace it with new one or different kind?


root@chromeos3-chaosvmmaster:~# ping 172.22.39.28
PING 172.22.39.28 (172.22.39.28) 56(84) bytes of data.
64 bytes from 172.22.39.28: icmp_seq=1 ttl=64 time=0.626 ms
64 bytes from 172.22.39.28: icmp_seq=2 ttl=64 time=0.398 ms
64 bytes from 172.22.39.28: icmp_seq=3 ttl=64 time=0.369 ms
64 bytes from 172.22.39.28: icmp_seq=4 ttl=64 time=0.369 ms

Nice! Bindu, what do you think? I'm fine with either ordering the same AP model to replace the bad one or using this spot for another AP model.

If the AP in chromeos3-row4-rack2-host8
 is in good condition and running, we should let it be. It might be worth ordering a new one to replace the broken one(of the same model).

Please let me know when the new replacement AP is available.

brand = belkin
wan_hostname = chromeos3-row4-rack2-host2
This AP is not still pingable afre reset the through USB ethernet dongle with chromebook.

tienchang@ - have you placed an order for the new AP?

chromeos3-row4-rack2-host2 is pingable after disabling the ICMP blocking.


jongkyuj@jongkyuj0:~$ ping chromeos3-row4-rack2-host2
PING chromeos3-row4-rack2-host2.cros.corp.google.com (172.22.39.22) 56(84) bytes of data.
64 bytes from 172.22.39.22: icmp_seq=1 ttl=62 time=0.592 ms
64 bytes from 172.22.39.22: icmp_seq=2 ttl=62 time=0.593 ms
64 bytes from 172.22.39.22: icmp_seq=3 ttl=62 time=0.556 ms
64 bytes from 172.22.39.22: icmp_seq=4 ttl=62 time=0.514 ms

chromeos3-row4-rack2-host8 is pingable after disabling the ICMP blocking.
ongkyuj@jongkyuj0:~$ ping chromeos3-row4-rack2-host8
PING chromeos3-row4-rack2-host8.cros.corp.google.com (172.22.39.28) 56(84) bytes of data.
64 bytes from 172.22.39.28: icmp_seq=1 ttl=62 time=0.601 ms
64 bytes from 172.22.39.28: icmp_seq=2 ttl=62 time=0.597 ms
64 bytes from 172.22.39.28: icmp_seq=3 ttl=62 time=0.582 ms
64 bytes from 172.22.39.28: icmp_seq=4 ttl=62 time=0.568 ms

chromeos3-row4-rack4-host3 is pingable after disabling the ICMP blocking.
jongkyuj@jongkyuj0:~$ ping chromeos3-row4-rack4-host3 
PING chromeos3-row4-rack4-host3.cros.corp.google.com (172.22.39.63) 56(84) bytes of data.
64 bytes from 172.22.39.63: icmp_seq=1 ttl=62 time=0.522 ms
64 bytes from 172.22.39.63: icmp_seq=2 ttl=62 time=0.632 ms
64 bytes from 172.22.39.63: icmp_seq=3 ttl=62 time=0.560 ms