Backhoe Bob strikes again!

[networkman]

Yeah, I got into work Tuesday at noon, and it turns out the construction guys on the road near our place, sliced through our T1 to the internet and both PRIs for our phone system! This affects not only the Service Center, but all 18 branches of our library system - no Internet access for public or staff, and no calls in or out on our Cisco VoIP system(internal calls only). :Q Then just when we figure it can't get any worse, they manage to slice through the analog lines too, thus taking out our fax lines and analog backups!

Now, the only way things can get worse is if they slice through the DS3 that connects all of our branches with the Service Center.. if that goes, we'll really be in a world of hurt, since much of our system is dependent on the Citrix servers we have in place.

Needless to say my boss is not pleased.

So, where's the FAQ on sneaker-netting WUs to remote PCs?

 

[amdskip]

Pics?

J/k, sounds like a real mess. Gives ya a little work to do instead of neffing it up

 

[Confused]

Dasm, that suxors

Hope the "construction" guys (hey, maybe they should be F2'd to "Destruction guys") get the wrap for this, and are charged the full whack of the repair costs :disgust:


Hope things get sorted out soon Robert!


Garry

 

[IsOs]

sneakernetting in linux

Ken_g6 HD-less SETI Sneakernet

From SoulAssassin reply to Need help getting SETI networked

<< Can anyone point me to instructions on sneakernetting SETI with a floppy?
I know there is a problem with starting a WU on one machine and finishing it on another. >>



I have a couple pc's crunching that don't have a net connection, I created two batch files, one that runs the client and another that calls out, then created a dir that has subdirs labeled 1-50..here's part of the one that runs the crunching:
copy c:\work_seti\user_info.sah c:\work_seti\1\cmd-0\1
copy c:\work_seti\seti.exe c:\work_seti\1\cmd-0\1
cd c:\work_seti\1\cmd-0\1
seti.exe -stop_after_process -cpu 0
del seti.exe

copy c:\work_seti\user_info.sah c:\work_seti\1\cmd-0\2
copy c:\work_seti\seti.exe c:\work_seti\1\cmd-0\2
cd c:\work_seti\1\cmd-0\2
seti.exe -stop_after_process -cpu 0
del seti.exe

And one that calls out..

copy c:\work_seti\user_info.sah c:\work_seti\1\cmd-0\1
copy c:\work_seti\seti.exe c:\work_seti\1\cmd-0\1
cd c:\work_seti\1\cmd-0\1
seti.exe -stop_after_xfer -cpu 0
del seti.exe

copy c:\work_seti\user_info.sah c:\work_seti\1\cmd-0\2
copy c:\work_seti\seti.exe c:\work_seti\1\cmd-0\2
cd c:\work_seti\1\cmd-0\2
seti.exe -stop_after_xfer -cpu 0
del seti.exe

I put the w/u's on via cd and can dump the w/u's to a floppys (use Winzip if necessary) and then call out, dump them back on cd, rinse and repeat . Yes, rather than manually creating each part of the batch file with the dir name I could use a for loop but I was lazy when I made it. You get the point.

Hope you can make it work

 

[ProviaFan]

Ugh, why can't these construction people actually read the freaking signs that are always put above critical cables to find out where they are? :|

I lost phone (and therefore, internet) service almost a whole day due to a similar incident last year. It sucks.

Here's wishes that they get it fixed, and SOON!

 

[JWMiddleton]

- Hope the splice crews are quick!!

 

[Coolkid]

Originally posted by: JWMiddleton
- Hope the splice crews are quick!!

 

[deerslayer]

That sucks! Hope it gets fixed soon!

 

[Starrider]

I used to work for a small communications company as a line splicer. Some of the smaller contractors just plain didn't care if they damage the underground cables or not. Our fees were quite steep if they failed to call for a cable locate before digging. Best one I ever had was an idiot that cut up a phone cable(several hundred pairs)one summer, and the same idiot cut the same cable the next summer in the exact same spot. He did learn to call for a cable locate AFTER he cut into an underground cross country electrical feed.

 

[Armitage]

Heh ... we used to call that a BISI: Backhoe Induced Service Interuption

 

[SoulAssassin]

What you guys don't have setiq's w POTS/cellular automated failover, a couple gigs of w/u's ready to go, and replication to a hot spare every 15 minutes in each of your sites uploading to a group of setiq's in a central location doing a dns round robin? How do you sleep knowing you could lose seconds, even minutes of processor time.

(somebody worked too late tonight, guess who)

threadjack: design a super redundant seti system for your workplace assuming a large but not overly ridiculous budget. No Sunfire 15k's for seti q's.