Has anyone heard anything about the graphs yet?

I've been checking the index of the routers that are in the cricket system, and the co-lo doesn't appear in that list still. I'm fairly sure it will be inr-310 and 311, based on what traceroute shows along the way.

Thus far, Matt has been the only one to really provide any info about it in his occasional Tech News posts. At present, IT is still determining if they want to go with Cricket or something else.

---

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

...Not forgetting that the Crickets, or whatever replaces them, are provided by the Uni in the CoLo, and are thus outside the control of the project.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Just wondering out loud here....the kitties are curious.
I know that many like myself are still missing the Cricket graphs.

The software for the Cricket graphs appears to be available here under public license.

Would it be possible for Seti to host their own Cricket graph, monitoring only their own links?

Of course, other than the software, I do not know what else it takes to make it work, or how the data would be collected from the network.

Just a thought.

Meow?

---

"Time is simply the mechanism that keeps everything from happening all at once."

Data gets collected from the equipment via SNMP broadcast packets. Therefore, on the equipment itself, SNMP broadcasting not only consumes a tiny amount of network traffic by itself, but also some CPU overhead from having to keep track of things, and then put it into SNMP packets. Depending on the equipment itself, it may be configurable for only specific metrics on specific ports, or it's just an "all or nothing" kind of deal.

Since the equipment in question does not belong to S@H at all, they have no control over it, and the privilege of using it comes with the price of renting rack space.

I, too, miss the graphs, not so much because it allows for us to see when there might be a problem, but because I'm just nerdy and I like seeing metrics for things. It's like my older Linksys desktop switches that have three LEDs for every port (connected/activity, 100mbit, full duplex/collision).. I like those over the newer models that just have one LED for every port. I like having more metrics and statistics available to me.

The fact that the campus was gracious enough to have the graphs available to the general public was very generous of them and completely not required of them to do in the first place, but I, too, miss having it for our one port out of many.

---

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

Meowsigh....
Somehow I knew it wouldn't be as simple as just getting the software.
As to whether campus IT could be persuaded to turn the SNMP on just for the bit of equipment that handles Seti traffic....well, I doubt it.
But it wouldn't hurt to ask maybe?
One could only hope.........

---

"Time is simply the mechanism that keeps everything from happening all at once."

Data gets collected from the equipment via SNMP broadcast packets. Therefore, on the equipment itself, SNMP broadcasting not only consumes a tiny amount of network traffic by itself, but also some CPU overhead from having to keep track of things, and then put it into SNMP packets. Depending on the equipment itself, it may be configurable for only specific metrics on specific ports, or it's just an "all or nothing" kind of deal.

Since the equipment in question does not belong to S@H at all, they have no control over it, and the privilege of using it comes with the price of renting rack space.

I, too, miss the graphs, not so much because it allows for us to see when there might be a problem, but because I'm just nerdy and I like seeing metrics for things. It's like my older Linksys desktop switches that have three LEDs for every port (connected/activity, 100mbit, full duplex/collision).. I like those over the newer models that just have one LED for every port. I like having more metrics and statistics available to me.

The fact that the campus was gracious enough to have the graphs available to the general public was very generous of them and completely not required of them to do in the first place, but I, too, miss having it for our one port out of many.

I think the graphs are actually to provide information to their data center customers.

---

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

Data gets collected from the equipment via SNMP broadcast packets. Therefore, on the equipment itself, SNMP broadcasting not only consumes a tiny amount of network traffic by itself, but also some CPU overhead from having to keep track of things, and then put it into SNMP packets. Depending on the equipment itself, it may be configurable for only specific metrics on specific ports, or it's just an "all or nothing" kind of deal.

Since the equipment in question does not belong to S@H at all, they have no control over it, and the privilege of using it comes with the price of renting rack space.

I, too, miss the graphs, not so much because it allows for us to see when there might be a problem, but because I'm just nerdy and I like seeing metrics for things. It's like my older Linksys desktop switches that have three LEDs for every port (connected/activity, 100mbit, full duplex/collision).. I like those over the newer models that just have one LED for every port. I like having more metrics and statistics available to me.

The fact that the campus was gracious enough to have the graphs available to the general public was very generous of them and completely not required of them to do in the first place, but I, too, miss having it for our one port out of many.

I think the graphs are actually to provide information to their data center customers.

I suspect we may now be going through a router carrying traffic they might not wish the public at large to be able to monitor and know all the internal subnets. Remember we are now in the data center so much of the data center traffic may be on that router. Of course it is also possible the new router is not compatible with the software for the crickets.

Requests for it must come from Seti and Matt indicated there had been at least one contact on that point.

---

Data gets collected from the equipment via SNMP broadcast packets. Therefore, on the equipment itself, SNMP broadcasting not only consumes a tiny amount of network traffic by itself, but also some CPU overhead from having to keep track of things, and then put it into SNMP packets. Depending on the equipment itself, it may be configurable for only specific metrics on specific ports, or it's just an "all or nothing" kind of deal.

Since the equipment in question does not belong to S@H at all, they have no control over it, and the privilege of using it comes with the price of renting rack space.

I, too, miss the graphs, not so much because it allows for us to see when there might be a problem, but because I'm just nerdy and I like seeing metrics for things. It's like my older Linksys desktop switches that have three LEDs for every port (connected/activity, 100mbit, full duplex/collision).. I like those over the newer models that just have one LED for every port. I like having more metrics and statistics available to me.

The fact that the campus was gracious enough to have the graphs available to the general public was very generous of them and completely not required of them to do in the first place, but I, too, miss having it for our one port out of many.

I think the graphs are actually to provide information to their data center customers.

I suspect we may now be going through a router carrying traffic they might not wish the public at large to be able to monitor and know all the internal subnets. Remember we are now in the data center so much of the data center traffic may be on that router. Of course it is also possible the new router is not compatible with the software for the crickets.

Requests for it must come from Seti and Matt indicated there had been at least one contact on that point.

The router that SETI@home traffic is going through is already known to anyone that performs a route trace. So I wouldn't suspect that as being a security issue. The management of the network hardware shouldn't be accessible to any public networks anyway.
Matt has said they have their own internal software they are using to monitor things on their end. I imagine they are collecting the information from the servers via OS SNMP information.
Matt also inquired to the campus IST about the graphs & they stated they were evaluating options or something to that effect. Given that was at the end of the school year & a new semester starting soon. They may have a plan to implement a new service soon. Which may, or may not, be accessible to the whole of the internet.

---

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

Well, we'll just have to put it on the way back burner wish list, I guess.

It was a mighty handy tool for us coalmine canaries to detect when things were starting to go south and try to get somebody to head things off at the pass.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Well, now that we have had the great router reshuffle, is there any chance of getting to see our traffic on the crickets, or any other service?

---

Well, now that we have had the great router reshuffle, is there any chance of getting to see our traffic on the crickets, or any other service?

I was wondering that same thing. One thing that I was pretty sure I interpreted correctly is.. we're not using Hurricane Electronics anymore, right? We're using the campus' ISP now?

---

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

Well, now that we have had the great router reshuffle, is there any chance of getting to see our traffic on the crickets, or any other service?

No more than there was before.
It's up to the Uni IT dept.

---

Grant
Darwin NT

Well, now that we have had the great router reshuffle, is there any chance of getting to see our traffic on the crickets, or any other service?

I was wondering that same thing. One thing that I was pretty sure I interpreted correctly is.. we're not using Hurricane Electronics anymore, right? We're using the campus' ISP now?

Could be. I believe there was mention they had a plan to switch at some point in order to save money. I imagine if it has been switched we may not know until we get a "what has been happening" update post.

---

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

Well, now that we have had the great router reshuffle, is there any chance of getting to see our traffic on the crickets, or any other service?

I was wondering that same thing. One thing that I was pretty sure I interpreted correctly is.. we're not using Hurricane Electronics anymore, right? We're using the campus' ISP now?

Could be. I believe there was mention they had a plan to switch at some point in order to save money. I imagine if it has been switched we may not know until we get a "what has been happening" update post.

Seems some missed what Matt said.

Some big news is that campus is, for the first time in more than a decade, allowing SETI@home traffic back on the campus network infrastructure, thus obviating our need to pay for our own ISP. We are attempting this switchover tomorrow morning. Thus there will be more chaos and outages and DNS cache issues but this has been in the works for literal years so we're not stopping now. I apologize if this seems sudden but we weren't sure if this was actually going to happen until this past weekend.

So yes SETI@home is now on the Campus network, that was what the outage was for.

---

Well, now that we have had the great router reshuffle, is there any chance of getting to see our traffic on the crickets, or any other service?

I was wondering that same thing. One thing that I was pretty sure I interpreted correctly is.. we're not using Hurricane Electronics anymore, right? We're using the campus' ISP now?

Could be. I believe there was mention they had a plan to switch at some point in order to save money. I imagine if it has been switched we may not know until we get a "what has been happening" update post.

Seems some missed what Matt said.

Some big news is that campus is, for the first time in more than a decade, allowing SETI@home traffic back on the campus network infrastructure, thus obviating our need to pay for our own ISP. We are attempting this switchover tomorrow morning. Thus there will be more chaos and outages and DNS cache issues but this has been in the works for literal years so we're not stopping now. I apologize if this seems sudden but we weren't sure if this was actually going to happen until this past weekend.

So yes SETI@home is now on the Campus network, that was what the outage was for.

Yes, they mentioned the attempt, but I wasn't sure if it was actually successful.

---

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

Yes, they mentioned the attempt, but I wasn't sure if it was actually successful.

Tracert isn't going anywhere near HE @ Palo Alto any more. Instead, we're taking the 'cenic' route direct to Berkeley.

Yes, they mentioned the attempt, but I wasn't sure if it was actually successful.

Tracert isn't going anywhere near HE @ Palo Alto any more. Instead, we're taking the 'cenic' route direct to Berkeley.

I haven't seen HE in my trace routes since the hardware change at the colo.
I have been getting something like this since spring.
13 73 ms 74 ms 74 ms dc-oak-agg4--svl-agg4-100ge.cenic.net [137.164.46.144]
14 74 ms 73 ms 74 ms dc-oak-agg4--svl-agg4-100ge.cenic.net [137.164.46.144]
15 75 ms 74 ms 74 ms ucb--oak-agg4-10g.cenic.net [137.164.50.31]
16 75 ms 74 ms 75 ms et3-48.inr-311-ewdc.berkeley.edu [128.32.0.101]

---

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

Yes, they mentioned the attempt, but I wasn't sure if it was actually successful.

Tracert isn't going anywhere near HE @ Palo Alto any more. Instead, we're taking the 'cenic' route direct to Berkeley.

I haven't seen HE in my trace routes since the hardware change at the colo.
I have been getting something like this since spring.
13 73 ms 74 ms 74 ms dc-oak-agg4--svl-agg4-100ge.cenic.net [137.164.46.144]
14 74 ms 73 ms 74 ms dc-oak-agg4--svl-agg4-100ge.cenic.net [137.164.46.144]
15 75 ms 74 ms 74 ms ucb--oak-agg4-10g.cenic.net [137.164.50.31]
16 75 ms 74 ms 75 ms et3-48.inr-311-ewdc.berkeley.edu [128.32.0.101]

Depends on which IP you traced. The web server was always on campus lines, the upload/download servers were not. They are now on campus.

---

Yes, they mentioned the attempt, but I wasn't sure if it was actually successful.

Tracert isn't going anywhere near HE @ Palo Alto any more. Instead, we're taking the 'cenic' route direct to Berkeley.

I haven't seen HE in my trace routes since the hardware change at the colo.
I have been getting something like this since spring.
13 73 ms 74 ms 74 ms dc-oak-agg4--svl-agg4-100ge.cenic.net [137.164.46.144]
14 74 ms 73 ms 74 ms dc-oak-agg4--svl-agg4-100ge.cenic.net [137.164.46.144]
15 75 ms 74 ms 74 ms ucb--oak-agg4-10g.cenic.net [137.164.50.31]
16 75 ms 74 ms 75 ms et3-48.inr-311-ewdc.berkeley.edu [128.32.0.101]

Depends on which IP you traced. The web server was always on campus lines, the upload/download servers were not. They are now on campus.

Last I checked the addresses are setiboincdata.ssl.berkeley.edu for upload & boinc2.ssl.berkeley.edu for download. I did save the trace as boinc2.ssl.berkeley.edu.txt when we were trying to figure out where the new location of the bandwidth graphs might turn up. However I did truncate the output so it starts at the 5th line. So there is a chance I mislabeled it.

---

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

It's been awhile since frequented these threads, so I'll simply ask - Has anyone heard anything concerning the Cricket Graphs?

---

I don't buy computers, I build them!!