I just looked around on the list and "sum for data center" flatlines all at once, so the new routers aren't in the cricket system yet, or aren't listed yet.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

I guess the Cricket changed to some other node after the network infrastructure upgrade. It's still at zero, despite uploads and downloads working.

I'm off to bed, so someone else can hunt down the new address.

I tried, but I can't find any data. Both inr-210/211 are silent: I tried 212 and up, but got "This page is temporarily out of service" - which may or may not mean "reserved for future expansion".
...

The ucb routers selection page still shows only inr-210/211 as being at the data center, and the sum of all datacenter traffic to the tier 2 routers inr-201/202 is also flat at zero.

I do hope that they intend to restore that data flow visibility, but perhaps there's a possibility they've decided to keep it hidden: reason for panic?

                                                                   Joe

I guess the Cricket changed to some other node after the network infrastructure upgrade. It's still at zero, despite uploads and downloads working.

I'm off to bed, so someone else can hunt down the new address.

I tried, but I can't find any data. Both inr-210/211 are silent: I tried 212 and up, but got "This page is temporarily out of service" - which may or may not mean "reserved for future expansion".
...

The ucb routers selection page still shows only inr-210/211 as being at the data center, and the sum of all datacenter traffic to the tier 2 routers inr-201/202 is also flat at zero.

I do hope that they intend to restore that data flow visibility, but perhaps there's a possibility they've decided to keep it hidden: reason for panic?

                                                                   Joe

I suspect they have been so busy with cables that the pretty up the page tasks are left to work days.

---

If they don't start splitting APs in a meaningful amount I will be crunching MBs in a few days much to my annoyance.

---

Can't say it's loading quickly around here. Pages that don't load fully, pages that load extremely slowly, pages that only half load. This page I am posting on hasn't loaded fully, it's still showing "transferring data from.." and "waiting for setiathome.berkeley.edu..."

---

I guess the Cricket changed to some other node after the network infrastructure upgrade. It's still at zero, despite uploads and downloads working.

I'm off to bed, so someone else can hunt down the new address.

I tried, but I can't find any data. Both inr-210/211 are silent: I tried 212 and up, but got "This page is temporarily out of service" - which may or may not mean "reserved for future expansion".
...

The ucb routers selection page still shows only inr-210/211 as being at the data center, and the sum of all datacenter traffic to the tier 2 routers inr-201/202 is also flat at zero.

I do hope that they intend to restore that data flow visibility, but perhaps there's a possibility they've decided to keep it hidden: reason for panic?

                                                                   Joe

As one who spends a lot of time keeping tabs on the Seti servers and their ups and downs, I should dearly miss the Cricket graphs if they are not brought back into service at some point. It is much more difficult to monitor things by looking at other statistics.
I do hope they point the Crickets in the right direction when they catch up from this weekend's major activities.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Ah well, that data center network upgrade, really turned into a downgrade. When I was on a dialup, my speed was much better than this.

Takes forever (several minutes at least) to load a page.

You might be one of the few or only having such a problem.
Everything this morning has been pretty snappy, including all of my stats pages.
No delays or problems here whatsoever.

Perhaps the change at the colo could be causing some DNS problems? I have made no changes, and all is very good here.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Takes forever (several minutes at least) to load a page.

Are you on DSL or Cable? You might try power off/power on the modem and router if using both.

My pages are loading instantly and have been since restoration of service yesterday.

---

"Sour Grapes make a bitter Whine." <(0)>

Took me 8 minutes to load page two of this thread (I've set 200 posts per page). On a 200Mbit connection on my side of the world, that's pretty damn slow. A 10 gigabit connection? Pah.

---

Took me 8 minutes to load page two of this thread (I've set 200 posts per page). On a 200Mbit connection on my side of the world, that's pretty damn slow. A 10 gigabit connection? Pah.

It just took me 3 seconds.....so, I don't believe it's the servers.
And I am not on anything special for a connection.
ATT DSL, 6Mb down, 512K up.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

As I recall the improvement was not going to improve the bandwidth for SETI just for inter-campus connectivity.

NOTE: this upgrade is largely to allow 10-gigabit connections between machines throughout the data center, which will speed up various campus services, but do nothing to speed up SETI@home traffic, or grant us more bandwidth. Nevertheless, as our servers are part of the data center, we are affected by the upgrade.

- Matt

---

"Sour Grapes make a bitter Whine." <(0)>

As I recall the improvement was not going to improve the bandwidth for SETI just for inter-campus connectivity.

Correct

Matt's other post in the outage thread

NOTE: this upgrade is largely to allow 10-gigabit connections between machines throughout the data center, which will speed up various campus services, but do nothing to speed up SETI@home traffic, or grant us more bandwidth. Nevertheless, as our servers are part of the data center, we are affected by the upgrade.

PS I am also having no problems with fourm loading and all caches are full, I am also watching streaming 720p video on my other monitor.

---

Since I made that post, I had to reload this thread 4 times to load it fully. 3 times it stuck loading at around Eric "Looking into it". The thread just times out.

I'm sure that after posting this it won't load again either, so I'm not going to try any further. Full attention back to ESO.

---

Looks as if it works from inside the U.S...

And the UK

---

Took me 8 minutes to load page two of this thread (I've set 200 posts per page). On a 200Mbit connection on my side of the world, that's pretty damn slow. A 10 gigabit connection? Pah.

Seems to be a problem from our part of the world, since both of us is on this side (Europe) part of the pond.

Looks as if it works from inside the U.S...

Crap nevertheless.

Maybe somebody there can do some ping tests and try to nail down the bottleneck.....

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Crickets.
Obvious they are working on those pages.

Hum, a traceroute to setiboinc.ssl.berkeley.edu no longer shows hops through a bunch of campus routers.

---

Well, I think we're closer to figuring out where the new cricket is going to be.

15 234 ms 240 ms * et3-47.inr-311-ewdc.Berkeley.EDU [128.32.0.103]

I just ran a tracert myself, and I came up with et3-47.inr-310.. so I'm not sure if 310 or 311 is going to be the primary, or if it does round-robin for load-balancing.

Regardless, "inr-310/11, 3_47" looks like probably maybe our new home, or really close to it. Unfortunately, the cricket summary pages for inr-310/11 are "temporarily out of service" at present, but based on the DNS name, those are definitely in the colo (ewdc - Earl Warren Data Center), which on the main page for the crickets, all of the entire EWDC section is gone. So.. that's progress, I think.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Tracing route to setiboinc.ssl.berkeley.edu [208.68.240.20]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms BTHUB5 [xxx.xxx.xxx.xxx]
2 5 ms 5 ms 5 ms 217.32.146.170
3 5 ms 5 ms 5 ms 217.32.146.222
4 6 ms 6 ms 5 ms 217.32.147.226
5 6 ms 6 ms 5 ms 217.41.168.15
6 6 ms 6 ms 6 ms 217.41.168.109
7 6 ms 6 ms 10 ms acc2-te0-4-0-11.l-far.21cn-ipp.bt.net 109.159.255.206]
8 6 ms 6 ms 6 ms core3-te0-12-0-20.faraday.ukcore.bt.net [109.159.249.145]
9 6 ms 7 ms 6 ms peer2-et-9-3-0.faraday.ukcore.bt.net [62.6.201.1
67]
10 6 ms 6 ms 6 ms 213.137.183.38
11 86 ms 85 ms 86 ms 166-49-208-123.eu.bt.net [166.49.208.123]
12 * * * Request timed out.
13 145 ms 148 ms 149 ms 10ge9-2.core1.pao1.he.net [184.105.213.177]
14 145 ms 145 ms 145 ms 64.71.140.42
15 149 ms 147 ms 148 ms 208.68.243.254
16 150 ms 148 ms 147 ms setiboinc.ssl.berkeley.edu [208.68.240.20]

Trace complete.

All good here

---

Tracing route to setiboinc.ssl.berkeley.edu [208.68.240.20]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms BTHUB5 [xxx.xxx.xxx.xxx]
2 5 ms 5 ms 5 ms 217.32.146.170
3 5 ms 5 ms 5 ms 217.32.146.222
4 6 ms 6 ms 5 ms 217.32.147.226
5 6 ms 6 ms 5 ms 217.41.168.15
6 6 ms 6 ms 6 ms 217.41.168.109
7 6 ms 6 ms 10 ms acc2-te0-4-0-11.l-far.21cn-ipp.bt.net 109.159.255.206]
8 6 ms 6 ms 6 ms core3-te0-12-0-20.faraday.ukcore.bt.net [109.159.249.145]
9 6 ms 7 ms 6 ms peer2-et-9-3-0.faraday.ukcore.bt.net [62.6.201.1
67]
10 6 ms 6 ms 6 ms 213.137.183.38
11 86 ms 85 ms 86 ms 166-49-208-123.eu.bt.net [166.49.208.123]
12 * * * Request timed out.
13 145 ms 148 ms 149 ms 10ge9-2.core1.pao1.he.net [184.105.213.177]
14 145 ms 145 ms 145 ms 64.71.140.42
15 149 ms 147 ms 148 ms 208.68.243.254
16 150 ms 148 ms 147 ms setiboinc.ssl.berkeley.edu [208.68.240.20]

Trace complete.

All good here

But that's not the SETI web page, but the "Scientific Linux Test Page"
We're at setiathome.berkeley.edu

Ever since the move to the colo I have never been able to ping the 169. ip address. I was just showing I can get to Berkeley with no problems,

If I ping "setiathome.berkeley.edu" it gives me 169.229.217.150, which fails, which by reasoning must be wrong as here I am posting.

Also of course if I try a tracert to that IP I get the same as you.

There is something stopping the ping and trace.

I always thought 169 IP addresses were used for something else.

I am sure someone will explain it!!

---

Well, I think we're closer to figuring out where the new cricket is going to be.

15 234 ms 240 ms * et3-47.inr-311-ewdc.Berkeley.EDU [128.32.0.103]

I just ran a tracert myself, and I came up with et3-47.inr-310.. so I'm not sure if 310 or 311 is going to be the primary, or if it does round-robin for load-balancing.

Regardless, "inr-310/11, 3_47" looks like probably maybe our new home, or really close to it. Unfortunately, the cricket summary pages for inr-310/11 are "temporarily out of service" at present, but based on the DNS name, those are definitely in the colo (ewdc - Earl Warren Data Center), which on the main page for the crickets, all of the entire EWDC section is gone. So.. that's progress, I think.

Thinking they used a logical numbering system for the routers around campus. I first tried cricket pages for 310 & 311 yesterday with the same results you have found. I later tried 200 to 399 also without any luck.

Given these graphs are provided for the "customers" of UC Berkeley Information Services and Technology (IST). I would imagine generating the new pages is on someones "to do" list, but as the priority of a heater repair person in the middle of summer.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[