| Topic List | Page List: 1 |
|---|---|
| Topic | Another late night network maintenance |
| CableZL 12/04/17 8:48:13 PM #4: | Yeah, being a network engineer is a whole new world. Exciting, sometimes frustrating, a few times nerve wracking, but... Yeah, entirely different. Then it's a whole new thing when you're the network engineer for a company vs a network engineer amongst a team of network engineers. At my old job, before they were bought out, we had 7 network engineers and I was the junior-most network engineer. By the time I left (post-buyout), I was one of 2 network engineers that had a CCNP route/switch certification. I could always rely on the other guys to cover my weak spots and ask questions. Now that I'm the sole network engineer at this job, it's way different. Way more responsibility, too. As a network operations engineer at a telecom, you have to know your stuff, but there's a lot of stuff you don't have to worry about. A lot of issues are the responsibility of the customer to fix. As the sole network engineer for a company, I have to worry about power configurations (making sure everything is on battery backup), cable management, redundancy, outage contingency plans, etc. I'm also the sole contact for bringing new internet/mpls connections in. Connecting and testing our backup voice MPLS circuit is what I'm doing tonight. --- ... Copied to Clipboard! |
| Topic List | Page List: 1 |
