Slashdot Mirror
Ask Slashdot: Designing a Telecom Configuration Center?
First time accepted submitter Big Jim Taters (1490261) writes "I have been tasked with helping move our config center from one location to our Headquarters. I have a small budget and no choice in location. I do, however, have an opportunity to design the space fresh (well, kinda.) What we will be configuring is routers, switches, firewalls, and other telecom related devices. What I cannot find is any "Best Practices" or "Lessons Learned" out there. So I ask you fine folks: What are some of the best and worst designs, practices, procedures, and work flows that you have encountered in sitting down to stage anywhere from 2 to 200 devices at once to get configured?"
Having done enough of this (both telco 25 to 600pr) and data networking) - I don't buy that logic. Having a cacophony of colors next to each other makes them visually more difficult to trace back.
I like the idea of separate colors for separate purposes. However, that requires that you purchase separate boxes of wire for each. Requiring that someone actually maintain that architecture... and, it makes it easier for someone to just cut the 'red' wires to kill a specific subset of your infrastructure. Bad idea.
My vote - one color - WHITE. Easy to label w/ a sharpie. Easy to see. Use over head cable management for network rather than under the floor. Ladder is easier to deal with than crawling in a hole. Put power under the floor as it's heavier and not moved as much.
I agree with the label both ends. Develop a grid system to denote where things goto. Use the floor tile layout as the demarcation of the grid. 1 -> n one axis, A-> zz on the other. Where's the server? Rack A7, Pos 55-57. Where does this cable go? Rack C8, Panel 3, Port 27 to Rack J27, Panel 5, Port 27.
If you have the $$ - dual power feeds - each at opposite ends of the room - with separate utility feeds (separate substations if you can do it). Also, a well-bonded ground grid that all Earth grounds get tied to. Lightning doesn't need to hit the building to destroy your gear... just like horseshoes and hand-grenades - close counts.
Be sure to purchase high-quality tools to handle your work. Nothing like a cheap tool to booger up a 250' cable run... that you have to redo.
Uptime Institute has a lot of good information on data-center designs and standards. Take some time and do some reading of what the 'experts' have to say.. not just us NOOBS out on /. :)
Enjoy.
FredInIT
You're seriously starting from scratch? Oh man... wish I could do that.
Lets see... #1 thing... when I started way-back-when, we had this giant display board that would show alarms on equipment. It looked neat, and made us look fancy. Don't do that... It was useless to those of us fixing stuff. The only people that looked at it were executives. Every hour or two some VP would come running over "Why is NewYork blinking red?!?!?!" "Because the gateways is down." "Is that bad?!?!" yada yada
Setup a wiki... make sure everyone has permissions to edit it. Make sure you have procedures in place for how and when to edit it.
I don't know what equipment you're using, but if you have a choice, try and go to a monoculture of one manufacturer if you can. We had a huge mess of every type of device you could imagine from every company on earth. Over in California we had 3 Juniper routers. Every time something "strange" happened with those we had to call the "Juniper guy" You should all be experts in everything you have and the easiest way to do that is to go with one vendor. It makes it easier to hire for. "We're a Cisco shop" or "We're a Juniper shop" whatever... That's up to you and how talented the people your managements willing to pay for. If they only will hire people green out of techschool like my old boss was, then this is likely a good idea.
Setup a centralized on-call list that charts whos responsible for what. One of the worst things that can happen during an outage is that you're screwing around calling Bob to get Toms number, because he has to change the firewall to let Tim into the device he needs to fix. This goes all the way down to your facilities people. I had an outage once that we couldn't address because the basement of the building was flooded and no-one knew who to call to get the pipes fixed.
Is everything you do software? Or will you be handing the equipment as well? Everything I did was via-remote. I rarely actually touched equipment, we had field techs for that. But my buddy that does the same job I did, now has a job where he actually unboxes the equipment and installs it personally. If you're going to do that I'd recomend a good printer, cable labeling templates... practice using both. TOOLS! Specifically "Easyouts" for stripped screws. A Small hammer. Hand-screw-drivers. Wire snips, etc...
Along those same lines, a benchtop with every type of OS that will pass through your stuff. We had Every version of Windows, MACs, Linux, etc... usually these were just to prove the vendor wrong... We'd submit a ticket for a bug and they'd say "Oh, that only happens with a MAC!!!" so we'd test it out "No it doesn't" etc...
I'm not sure if I got overly basic with you there, but that's how we did it.
For actually configuring devices, we'd have one of the leads write a script and then foist it off on "the new guy" to put it on every device. It's been about 5yrs since I've done a config though so things might not be as simple with all the modern GUI stuff.
and I like to get paid for my work. I expect most of my peers feel similar. So as unhelpful as you may find this, hire someone who's done it before, and ask them nicely to let you tag along and learn. Then you can become one of the professionals.
The above statement may sound condescending, but it's not meant that way. It takes years to learn the stuff you're asking, and differentiates the juniors from the seniors. Asking the seniors to train you for free isn't likely to be that well received by most of us.