To those who work in a DNOC...Question

[SomeFknGuy]

I have a potential job oportunity to work in a DNOC for the company that just aquired us. I am currently 5 years in the technical support department for a local ISP, been promoted to manager 2 years after i started, installed/maintained business networks, our external network and infrastructure, all the usual tech support stuff, web authoring, pc repair...you name it... I am close to cluless as to what DNOC opps do... While i have a basic understanding, what can you guys tell me about normal dnoc activities and would my current work experience be sufficient for a DNOC position? If not, what can i cram to get my skills up as quickly as possible for it? Plz let me know if anyone can help me out, i am hoping this is my break to move up in the IT world

 

[delemorte]

I work in a NOC and it soudns like your skill set is right on. If you are set up like us you would be simply expanding your support role to a larger enviorment and back side support... instead of supporting local users we support our entire company and the infistructure that our company uses.

 

[ktwebb]

You'd really need to define what your job description would be. Working in a NOC could mean alot of things. Could be watching a plasma screen for alerts and contacting the actual support staff for instance.

 

[Sharaz Jek]

system backups and monitoring. server hardware is easy to work on, most systems these days dont require tools or inteligence to disassemble (most parts are designed for quick-release/hot-swap).

i would study up on databackups/system recovery. at my job im the only one with an intimate understanding of those concepts, and it makes me worth my weight in gold. practice up... borrow the software, and set up a practice/dev backup system of your home network.

 

[Malk-a-mite]

http://hotjobs.yahoo.com/jobs/IL/Chicago/Technology/J359612CE

Part of the above job link:

Day in the Life of a NOC Technician

* Execute multiple downloads for PB/BrokerTec
* Verify processes are running on multiple severs
* Storage Breakdowns on EMCs
* Storage utilization response on local server drives
* Re-run TWS jobs
* Reboots of servers
* Process kills/restarts on Linux/Windows
* Enable/Disable network access ports
* Event notifications (shadow, Bradmark)
* Vault Tapes
* Escort Vendors
* Replace drives on EMCs, Servers; hardware replacements on other servers
* Server/Rack checks post Site Management work
* End-user interaction (service requests)
* Vendor Feed issue coordination

Typical Troubleshooting Scenarios

* Sluggish server response
* Slow storage access
* File System Permissions
* Server/service up/down
* Automount/NIS issues
* Network link down/unstable (internal and vendor coordination)
* Potential node down situations, both server and network