If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
SSL is some distance away from campus; in fact, they didn't lose power on 7 March, although their network connectivity was cut off due to the problem on campus.
So what's the current problem? Well it isn't an electrical outage, or at least not a widespread one. The SSL router (inr-60) is located at SSL, and it's fine, so SSL has electrical power. But all of the SSL subnets (not just S@H) are currently unreachable.
We don't know much more right now, since my group (Communications and Network Services) doesn't manage the network within SSL. (SSL is what we call a "private net"; we manage the backbone up to their router interface; they handle everything else within their buildings). At this point all I can say for sure is that there's an equipment failure of some sort at SSL.
As my colleague George Kaplan has mentioned, we (from campus) can't reach anything beyond inr-60, which is phyically located at SSL. inr-60 is reachable, and all of its interfaces are functioning properly, but the next hop beyond it (which is not the seti server, by the way, it's a firewall) is not responding. Because of that, traceroute keeps bumping the TTL and trying the next hop, which of course doesn't reply, and so on, until traceroute gives up after some arbitrary number of hops (often 30 or 60).
There's not much we can do about the current problem, other than try to get in touch with the SSL system admins (by phone, of course; email is somewhat problematic here), which we have been trying to do.
Comment