[identity profile] compsth.livejournal.com posting in [community profile] techrecovery
What NOT to do when setting up a new server in a data center:

1) Assign the server a static IP on the subnet ending in .1
2) Assign a totally bogus gateway
3) Continually reboot the new server, not understanding why it won't work

Today, a member of our server group did all that he shouldn't have. As luck would have it, the .1 IP just so happened to be a distribution core. It's always fun seeing server after server drop off the map....

Date: 2007-02-28 04:21 am (UTC)
From: [identity profile] sneezypb.livejournal.com
Ah, yeah, back in the good 'ole days everything went dead early one morning. Web, email, DNS, everything. Turns out of the Unix server guys did #1 & 2. He didn't reboot continually. Once people got in a tizzy, he realized the problem and pulled the network plug. He normally came into work no earlier than 11 AM, but his boss wanted him coming in at 8AM "like all the other staff."

Date: 2007-03-03 03:05 pm (UTC)
From: [identity profile] fuzzyr.livejournal.com
I'm not understanding why an address ending in .1 is bad.

#2 and #3, I get, but I have machines that are network address +1. Is it just that that address was already used on the subnet?

Profile

techrecovery: (Default)
Elitist Computer Nerd Posse

April 2017

S M T W T F S
      1
2345678
91011121314 15
16171819202122
23242526272829
30      

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Mar. 20th, 2026 03:39 am
Powered by Dreamwidth Studios