Slashdot Mirror


Nine Traits of the Veteran Network Admin

snydeq writes "Born or made, network admins share certain defining characteristics. Deep End's Paul Venezia offers nine: 'I hope that this insight into the extremely logical, yet consistently dangerous world of the network admin has shed some light on how we work and how we think. I don't expect it to curtail the repeated claims of the network being down, but maybe it's a start. In fact, if you're reading this and you are not a network admin, perhaps you should find the closest one and buy him or her a cup of coffee. They could probably use it.'"

29 of 142 comments (clear)

  1. Will read later by Anonymous Coward · · Score: 5, Funny

    The network is down.

    1. Re:Will read later by Razgorov+Prikazka · · Score: 5, Funny

      Have you tried turning it off and on again?

      --
      rm -rf --no-preserve-root / ...and let /dev/null sort them out...
    2. Re: Will read later by nosfucious · · Score: 4, Insightful

      These "traits of" or "habits of" articles are the modern equivalent of horoscopes. Lots of feel good stuff, but not much actual advice. I can agree and disagree with every point to some extent.

      Nice article that generates a lot of page views. For real advice get 1 or more O'Reilly books, or better yet, find a competent admin and become his/her apprentice.

      --
      Q:I was listening to a CD in Grip and it sounded horrible! What's up? A:Perhaps you are listening to country music
    3. Re:Will read later by Anonymous Coward · · Score: 2, Funny

      Call to Admin: "Network is slower today than usual". Network Admin to caller: The weather is hot today, bits expand and it's harder for them to squeeze through thin wires.

    4. Re:Will read later by SuricouRaven · · Score: 3, Informative

      A proxy delivers whatever code the admin wants it to deliver. Squid returns 403 on ACL blocks, but it's trivial to alter.

    5. Re:Will read later by fuzzywig · · Score: 2
      "You could try straightening out your network cable, just go down behind your computer and massage out any kinks in it that might be slowing down the data."

      By the time they've finished doing that, you'll probably have worked out what was causing the slowdown, and either fixed it, or allowed it to fix it's self.

    6. Re:Will read later by RabidReindeer · · Score: 2

      Your admin blocks Infoworld articles? Thank him sometime for looking out for you.

      Thanks Mordac!

  2. The spice of life by cold+fjord · · Score: 4, Funny

    For many reasons there are few things add excitement to life like working with someone who habitually answers the phone with, "I didn't do it."

    --
    much of left-wing thought is a kind of playing with fire by people who don't even know that fire is hot - George Orwell
  3. Obligatory xkcd by vikingpower · · Score: 4, Funny
    --
    Religous speak to God. Insane are spoken to by God. When all shut up, one can finally hear Shostakovich in peace
    1. Re:Obligatory xkcd by L4t3r4lu5 · · Score: 2, Funny

      Holy fucking balls, you're such a moron! That's SYSTEMS! You know, the guys that make sure that the monkeys who think knowing PowerShell makes you some kind of IT god? NOTHING. They are FILTH.

      We're talking about Networks. Systems can do NOTHING without my massaging of the thinwire, caressing of the switch configuration. Systems are USELESS, DUMB without us. Systems is the heart of the network? Well, Networks is the vascular system. What is the heart without the blood vessels? Just another lump of useless meat.

      Excuse me for a moment. Latency just jumped three orders of magnitude on the fiber trunk to another building. I can hear the packets screaming already...

      I'll save you. I'll save you all.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    2. Re:Obligatory xkcd by Anonymous Coward · · Score: 2

      The REAL Sysadmin is the Network/Server/Software/Hardware person. A long time ago in a Galaxy far, far away.... You did everything and anything involved with IT. You even had to manage PBX and telco equipment, not just the routers and switches. You took care of the tape backups and user printers. You had to write code and compile kernels. And you had to know about electronics to repair outdated equipment critical to the workings of the company.

    3. Re:Obligatory xkcd by ixidor · · Score: 2

      and this would be a the job description of where i am now, add in gym tv repair man, light-fixture-changer, air-filter-changer, and 100's of other things.

    4. Re:Obligatory xkcd by zildgulf · · Score: 3

      In spite of all of the times I wired numerous double-wide and single-wide mobile units, big enough to hold 48 or 18 people respectively, the VoIP phones that trash their own firmware upon reboot, full recoveries in parking lots, fields, and any open spot after a hurricane or storm, all of the EIGRP and BGP failures, MPLS installations, numerous satellite equipment failures, bugs in switch, router, and firewall software, multicast software packages having dubious compatibility with firmware versions of our equipment, numerous firewalls each with its own way to make configurations and access lists, PBX systems going haywire, PRI, SIP, T1, and Fiber link outages, corrupted or destroyed MX and DNS records, e-mail services crapping out, lost connections to the cloud services, the DoS attacks, and such, there is nothing like being a field network engineer for disaster recovery. I LOVE my job!!!

  4. I RTFA by 19thNervousBreakdown · · Score: 5, Insightful

    Why do I feel like I just watched somebody jerk off?

    --
    <xml><I><am><so><damn>Web 2.0</damn></so></am></I></xml>
    1. Re:I RTFA by Anonymous Coward · · Score: 5, Insightful

      Because you can't handle the sheer awesomeness that is the veteran network admin!

    2. Re:I RTFA by evilviper · · Score: 4, Insightful

      They mostly come across as a bit OpenBSD-mailing-list if you see what I mean. They are defensive as hell, maybe their jobs make them that way.

      Imagine running your company's entire IT infrastructure off of a random assortment of Android cell phones... That's basically the job of a Network Administrator.

      Despite running the most critical piece of infrastructure, they can't peer into the base system at all, to see how it's going to behave in edge cases. The monitoring and management tools available are shockingly poor, and offer little utility.

      They're forced to use a random mix of different network hardware, which all behaves differently, and each has a list of errata 100 pages long. Updates are huge monolithic firmware blobs, guaranteed to have bugs, leading you to choose between dealing with the awful but barely manageable bugs you have now, or updating and dealing with a whole new set of bugs, and potentially some so bad they'll take the system down, and there's relatively little you can do to test this, even if you have a rather large testing network (which most do not).

      Software Defined Networking and OpenFlow look like they might finally start changing this, and Network Admins will be able to understand how these complex systems work, and even define the behavior they want. But in the mean time, your Network Admin remains the Prime Minister of the insane asylum.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    3. Re:I RTFA by BitZtream · · Score: 2

      If you think 'software defined networking' and OpenFlow are going to make it more understandable you completely fail to understand how any software works at all.

      Networks are ALREADY SOFTWARE DEFINED and ALWAYS HAVE BEEN.

      You seem to think running software on your software that runs on your hardware is magically and unintuitively going to work better than software on hardware.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  5. This is great! by Anonymous Coward · · Score: 5, Funny

    I just bought an MCSE or MSCE or whatever you call it and I was wondering how the fuck I could fool people into believing I actually knew what the fuck I was doing.

    Problem solved!

    Thanks a lot, InfoWorld!

    Captcha: "secured"

  6. Clarifying #4 by chill · · Score: 4, Insightful

    Notice he said "turning an interface on and off", not "rebooting".

    Nothing says "I'm a noon and came from a Windows world" like rebooting a switch or router to fix a problem.

    Logs on those devices are in memory. Rebooting clears the logs and you then can't troubleshoot. If you can't troubleshoot, you'll never know what really happened. If you don't know the root cause of the failure you can't prevent it from happening again.

    --
    Learning HOW to think is more important than learning WHAT to think.
    1. Re:Clarifying #4 by mysidia · · Score: 4, Insightful

      Logs on those devices are in memory

      Although they should be on the NMS and syslog servers too... and many Juniper M/T series devices, which are very frequently used by large carriers for core and edge routers, have a hard drive mounted on the /var filesystem, that the routers' syslogs get written to.

      Rebooting sounds like an act of desperation. It's almost never the cleanest way, and it almost always incurs additional downtime, causes more outages, or further lengthens the network downtime --- since you require 3 to 5 minutes for a reboot, then maybe 3 to 5 more minutes for routing protocols to reconverge.

      And god help your soul, if you reboot a Cisco device such as a 72xx or Catalyst 65xx running BGP with 3 or 4 copies of a full table, and with 8 or 9 total peers.

      That one weak moment, when reboot was chosen may result in 60 to 90 minutes of trying to coax the network back up gently.

    2. Re:Clarifying #4 by NatasRevol · · Score: 4, Insightful

      If you don't have a separate syslogd system, you're not doing your job well.

      --
      There are two types of people in the world: Those who crave closure
  7. Re:As someone who has worked in IT for 20 years... by AK+Marc · · Score: 2

    "Came clear during testing" is what I'd get for the "we fucked up, but we'll never admit to it" response.

  8. The BOFH knows the real traits of seasoned admins by dkleinsc · · Score: 5, Funny

    1. A complete disdain or hatred of lusers.
    2. A collection of blackmail materials.
    3. Homicidal rage.

    --
    I am officially gone from /. Long live http://www.soylentnews.com/
  9. Veteran network admin trait No. 10 by mwvdlee · · Score: 3, Insightful

    Veteran network admin trait No. 10: We like writing about how awesome we are
    Every once in a while we realize we're just glorified factory workers operating machines we know very little about. It is at times like these when we need to point out to ourselves how our brains are amazingly special for being able to navigate a maze of possibilities (completely unlike a delivery boy) and how we can handle the incredibly complex mathematics of subnet masks. It is to remind ourselves that restarting something and waiting for it to fix itself is actually a mental process reserved only for the enlightened few and we must publish such so the world may know of, though not quite comprehend, the extent of our genius.

    --
    Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
  10. Two traits : Cooperative and uncooperative by EmperorOfCanada · · Score: 4, Interesting

    Cooperative and uncooperative are the two primary traits of network admins. Seeing that most network admins are ignored when everything is going well and cursed when things are going badly it quickly becomes obvious to most network admins that saying no to most requests becomes a survival trait. But this often means that a network admin starts actively interfering with the actual business (unless the business is network administration)

    So take your average non IT company. The sales people want to switch from Blackberries to iPhones and Androids. The network admin has 4 certifications from RIM and recently set up a huge Blackberry server. Plus this particular admin hates all things touch screen. The usual scenario will be that the admin will pull out 9 whitepapers showing just how secure Blackberry is as compared to iOS and Android. Using techno babble he will explain how hackers will be running the company in under a week. The salesman on the otherhand say that they look like tools from the 90s with their blackberries. The network admin wins the battle but then he starts to get nervous as he notices traffic on his BB server is nearly zero. A quick investigation shows that nearly every Blackberry sits in a drawer and the Salesman have gone out and bought their own phones and swapped the SIM cards. The network admin sends out a memo saying this is against corporate policy which is ignored. His attempts to get a salesman fired(to set an example) for violating security fail. He then notices nearly everyone is using gmail instead of his highly secure MailMaster2000. Then sends out a memo indicating that this is against corporate policy. He then implements a 30 day mandatory password rotation. Internal file server traffic nearly drops to zero because everyone switched to dropbox. He then sends out a memo that dropbox is against corporate policy. He then starts blocking sites such as reddit and he notices that network traffic drops to nearly zero. But walking by a sales person's office he notices that they are on reddit. So he investigates and finds out the entire sales team has bought mobile data plans. He then sends out a memo saying that private data plans are against corporate policy.

    Then he comes to work only to find a contractor in his office. The contractor is there to "rationalize" IT seeing that after the IT guy insisted that all apps be developed for BB first the sales people have gone out on their own and developed 3 smartphone applications that have increased sales by 80% and that promotions via Reddit have sent corporate website visits through the roof. The company now works with clients via dropbox much more successfully than with the sftp system that merely served to confuse before. With mobile dataplans the salesforce has become much more effective.

    Now the IT guy is left filling out a resume where his two best features are many Novell certifications and many Blackberry certifications.

    IT people shouldn't cave into every whim of the week but I have seen so many that are stuck in the thinking of whatever year they became head of IT. IT is just one tiny department in so many companies yet I have seen IT somehow be able to treat senior managers of other departments like children. Seeing that they aren't children they often discover the virtues of outsourcing. The key benefit of outsourcing being that if the people they outsource to try pulling any crap they can be dropped in a second.

  11. Re:Trait #10 is certainly not by cold+fjord · · Score: 4, Funny

    Good administrators keep humility under control. Too much of it corrodes the equipment. There are sensors for it you know.

    --
    much of left-wing thought is a kind of playing with fire by people who don't even know that fire is hot - George Orwell
  12. Re:Who cares? by Anonymous Coward · · Score: 2, Interesting

    Honestly, I can say if someone came in for an interview with this type of an attitude, I would tell them to pound sand.

    I'm a network admin; not all of us act like tools like that. If your network admins are getting calls that something is down, then you need to redefine your processes and stop giving out your direct line like a toolbag and instead have users contact the help desk.

    I'd have called that article "9 traits of a crusty, worthless network admin". I'm seriously appalled someone even wrote that crap. :(

    And FYI, when I interview people, the first thing I do is make sure they're willing to admit they may be at fault and they know how to Google something. I generally will give them a situation of misconfiguration on our part and ask how they communicate that to a user. Be honest. You're human, you screwed up, and apologize for the inconvenience. I generally also ask "how do you solve a problem you've not run into, and how do you answer someone that asks you a question you don't know the answer to right off hand?" I have too many people say they've ran into every problem and they know the answers. There's no shame in admitting you don't know something and you need to Google the answer (or look it up on Cisco's/Juniper's/VendorX's website).

  13. Alternate Trait 1 by bobstreo · · Score: 2

    If you are good, you know when the network "isn't right" which is much better than UP/Down.

    This includes knowing things like a switch port has lost duplex on an ethernet connection,
    there is a broadcast storm in a building/site, one of your redundant links is down.

    Being right much much more often than being wrong in diagnosis/troubleshooting is also a good trait.

  14. Re:The BOFH knows the real traits of seasoned admi by dkleinsc · · Score: 3, Informative

    No it doesn't: packet sniffers.

    --
    I am officially gone from /. Long live http://www.soylentnews.com/