What do Sys Admins or Network Admins do when there are no fires to put out?

What are the daily responsibilities of Sys Admins or Network Admins? What do they do when there are no fires to put out?

Find more posts tagged with

Comments

Welly_59

Play water polo.

Seriously though, there's usually a bunch of changes that need some work completed. Failing that I just study.

scaredoftests

Study. Document the fire.

NetworkNewb

They make sure everything is setup and working correctly so you don't have many fires to put out.

Rakurai

Network diagrams, backup configurations (if there isn't a tool that automatically does that), IOS upgrades, port security for help desk swapping out equipment, prepping for ASI's, maintaining monitoring tools (if there isn't a separate group), hardware upgrades, network expansion/ new site standup's. Most importantly, answering to why things failed and/or if redundancy didn't work or was never implemented. Don't forget about more unimportant meetings that don't accomplish anything

Panther

How do you explain "studying" to HR or other management?
What do you study?

I think my immediate boss or even the dept. manager (depending on your relationship) wouldn't care so much if you're studying, as long as it's mainly work relevant.

But outside of them, "studying" could be you don't have enough to do?

Panther

There we go. Not having to explain why things failed and/or why redundancy didn't work or was never implemented. So when there's no fire, you focus on ensuring those things work. Got it.

That's what one could be "studying" for. Though, I like to say researching.

Rakurai wrote: »

Network diagrams, backup configurations (if there isn't a tool that automatically does that), IOS upgrades, port security for help desk swapping out equipment, prepping for ASI's, maintaining monitoring tools (if there isn't a separate group), hardware upgrades, network expansion/ new site standup's. Most importantly, answering to why things failed and/or if redundancy didn't work or was never implemented. Don't forget about more unimportant meetings that don't accomplish anything

scaredoftests

OOPS. I mean RESEARCHING. However, if it applies to my job (which covers all aspects..the studying is RESEARCHING!)

networker050184

Usually when you're not putting out a fire you'll be doing project type work. What those projects are depends of course and people here gave great examples.

Ismaeljrp

Rakurai wrote: »

Network diagrams, backup configurations (if there isn't a tool that automatically does that), IOS upgrades, port security for help desk swapping out equipment, prepping for ASI's, maintaining monitoring tools (if there isn't a separate group), hardware upgrades, network expansion/ new site standup's. Most importantly, answering to why things failed and/or if redundancy didn't work or was never implemented. Don't forget about more unimportant meetings that don't accomplish anything

This pretty much nails it.

Dakinggamer87

Research solutions and architect ways to improve the system back end infrastructure.

kriscamaro68

Automate putting the fires out. Automate everything else. Site back after everything is automated.

vanillagorilla3

Do something to create a new fire.

jibtech

Network and System Admins have two jobs:

1. Put fires out.

2. Create an environment where fires don't start.

If they aren't doing #1, they are doing #2. #2 can be configurations, improving network responsiveness, backups, automation, you name it.

But a big part of #2 is training. How is this done somewhere else? What are the best practices? How can it be done better? Call it studying, learning, training or researching. But, it is a core element of #2, not something done on the side.

When you dail at that aspect of #2, you tend to do a lot more of #1.

jdancer

Automate the sh*t out of everything, 'cuz you know, admins are lazy f*ckers. ( <- yeah, that's me! )

UnixGuy

images?q=tbn:ANd9GcRAYvDq2ETsHwMAkyKUCGByUOul3Z14pgU9cg43jv5Sm1YGKiOmpw

jelevated

ABL

Always Be Labbin'

Legacy User

Rakurai wrote: »

Network diagrams, backup configurations (if there isn't a tool that automatically does that), IOS upgrades, port security for help desk swapping out equipment, prepping for ASI's, maintaining monitoring tools (if there isn't a separate group), hardware upgrades, network expansion/ new site standup's. Most importantly, answering to why things failed and/or if redundancy didn't work or was never implemented. Don't forget about more unimportant meetings that don't accomplish anything

1+ this plus creating netflow reports on traffic usage for someone stating the network is slow for there pc and professional development (studying)

kohr-ah

Study
Work on making the environment better
Documentation
Learn how my current environment works fully inside and out (Corporate)