:-) New Job - NOC Technician!! :-)

Hi Everybody,
I have been offered a new job as a NOC Technician, its late night and i am supposed to monitor systems and prepare tickets for the engineers to resolve. Can anyone here tell me what to expect from the job? I presume its going to be a great spring board and i wont be working late nights forever.

Insight?

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

kohr-ah

When I worked in a NOC.
Monitor systems. - Get tickets when stuff goes wrong.
When something goes down (if you have access) see if you can see why it went down.
Call someone higher up to go fix it or if for a customer inform the customer that it is down.

Good entry level experience for networking. A lot of sh ip eigrp neighbors, sh ip protocols, sh logs, so you learn to troubleshoot well.

Sometimes during days I got sent to replace switches, routers, etc.

Downtime studied and labs

networker050184

You can expect pretty much what you described. Getting alarms from monitoring systems, figure out who handles the issue, create/escalate ticket. Depending on the NOC you might have more troubleshooting responsibilities.

Congrats on the new gig!

coffeeluvr

Congrats on the new job!!

DoubleNNs

Congrats on the new job!! Update us how it is after the first few weeks

bermovick

My overnight NOC job was pretty much what was listed above; if a monitored circuit dropped, I'd determine if it was a power outage or an actual circuit failure. If a failure, I'd find out who the carrier was and get a ticket open with them for testing. I'd also open carrier tickets day shift left for me for excessive circuit errors or bounces that happened during the day.

We were also a VoIP provider so I'd also occasionally get 'larger' MAC changes that would take a while to do or were disruptive, but there were plenty of nights where I . did . not . do . a . thing. (except study or play games)

YFZblu

Congrats!

DoubleNNs

bermovick wrote: »

but there were plenty of nights where I . did . not . do . a . thing. (except study or play games)

I kinda want a job like that right now, to work on my skills and/or certs during the downtime. I don't have that opportunity at my current job. =/

Ivanjam

@Node Man - congrats on your new job - make use of the opportunity to get some experience and new certs!

@networker050184 @bermovick - can you guys provide some insight as to the locations of such jobs to people like DoubleNNs and me, who are actively searching for NOC positions?

Mike-Mike

kohr-ah wrote: »

When I worked in a NOC.
Monitor systems. - Get tickets when stuff goes wrong.
When something goes down (if you have access) see if you can see why it went down.
Call someone higher up to go fix it or if for a customer inform the customer that it is down.

Good entry level experience for networking. A lot of sh ip eigrp neighbors, sh ip protocols, sh logs, so you learn to troubleshoot well.

Sometimes during days I got sent to replace switches, routers, etc.

Downtime studied and labs

I never replaced any devices, but other than that, this sounds spot on like my NOC experience. Great chance to learn

gbdavidx

you just have ccent too?

bermovick

Ivanjam wrote: »

@Node Man - congrats on your new job - make use of the opportunity to get some experience and new certs!

@networker050184 @bermovick - can you guys provide some insight as to the locations of such jobs to people like DoubleNNs and me, who are actively searching for NOC positions?

Mine was in St Louis, but the work environment was actually TERRIBLE. Abusive coworkers, etc. If I hadn't worked remotely, due an arrangement I'd made with the NOC supervisor at the time, I don't know if I could have worked there as long as I did.

JDMurray

Make sure you always obey the org's change management procedures. If you make changes to system or device without first having proper permission, paperwork, and a scheduled change window, and your changes interrupt production, you could easily find yourself looking for your next NOC job toot sweet.

Ivanjam

@bermovick - thanks for that insight! I am wondering if the Texas and Atlanta IT jobs mecca is fact or fiction...

DoubleNNs

I know I was thinking about moving to Austin, TX spring 2014. I checked their craigslist postings and it was pretty barren. So barren, that the site actually had to format the page differently.

I don't know whether that's an indication of the actual IT job market down there or not. Regardless, I think the attention Google fiber is bringing to Austin would spark the IT sector there.

gadav478

Congrats. Definitely keep us updated. I myself have a second interview for a NOC tech job tomorrow... Definitely excited.

Node Man

CCENT is my only cert. But I have 2.5 years experience as a VOIP provisioner and voip troubleshooter in the teleco industry.

Thanks everyone, I will keep you posted as things happen. I dont start for a few weeks.

gbdavidx

what were you before that? i am trying to get into a noc environment, any suggestions? im currently studying for ccna

JDMurray

NOCs are always looking for people with Unified Communications (VoIP, video streaming, IM, call center, collaboration, etc.) knowledge and expertise. If you favor those areas as a specialty then you will be in demand.

gbdavidx

JDMurray wrote: »

NOCs are always looking for people with Unified Communications (VoIP, video streaming, IM, call center, collaboration, etc.) knowledge and expertise. If you favor those areas as a specialty then you will be in demand.

what do you mean? Like someone who has had a job in a call center? I currently do phone support for a hospital, does that count?

Dakinggamer87

Congrats on the new job let us know how it goes!!

instant000

gbdavidx wrote: »

what do you mean? Like someone who has had a job in a call center? I currently do phone support for a hospital, does that count?

You appear to be talking about the person who uses that solution. He's talking about the person who designs, implements, manages that type of solution. He's talking about the person you contact when the phone system isn't acting right or the DMS (an expensive Cisco solution, didn't they drop it?) is on the fritz.

Hope this helps.