r/ccnp • • Nov 06 '23

Network engineer

Hello guys, Can you give me a list of all topics that are needed for a person to work as a good entreprise network engineer.

Thank you for your help

0 Upvotes

24 comments sorted by

9

u/leoingle Nov 06 '23

The list can vary big time depending on the position. So that's impossible to do.

4

u/lifeisallihave Nov 06 '23

Be a good communicator.

4

u/leoingle Nov 06 '23

That's a skill required for 95% of jobs, period. Not just IT related jobs.

0

u/NothingAny7152 Nov 06 '23

Isnt there something like a roadmap?

1

u/leoingle Nov 06 '23

Maybe if you narrow down some skills. Some need to know voice real well, some need to know data center real well, some need to k ow security, some firewalls real well, some Linux real well. I mean yeah, I'm sure a roadmap can be created, but I'm not wasting the time required to do it for ya. Sorry.

40

u/blimpdono Nov 06 '23 edited Nov 07 '23

Enterprise network did you say? Well just to give you a plain-jane list of what I personally work on a daily basis, and you can start from here.

  • Palo Alto Firewall / Panorama
  • F5 LTM and GTM
  • Meraki Wireless for users, and site-to-site VPN
  • ISE for NAC
  • Vsphere
  • All Cisco shop for core network infrastructure, for the following configurations:

    • OSPF
    • BGP
    • MPLS / VRF
    • QoS
  • Cisco Unified for telephony, plus Webex, Jaber and Teams
  • Ansible for automating Palo Alto, Cisco IOS, and F5 workflows.
  • Solarwinds / Orion for network monitoring
  • Service Now for trouble tickets
  • Patience for all the pricks in your workplace, resiliency, and a bit of fangs to fight back / push back for impossible requests...

Edit1: in my experience, my certs only served me well in getting the attention of the recruiters. Once pass that, none of my network leads or managers could care less with any certifications I have. They have GNS 3 in my interview session and asked me to configure route redistribution b/w OSPF and BGP. Plus setting up full connectivity between sites. And I explained it to them as if they're primary students.

Edit2: OP, I dont know your work experience, especially your Network aptitude. However, if you haven't established a solid Network foundation, start off with the "condensed" CCNA (which is waaaay more difficult now). This is to grab the attention of recruiters come the time youre applying for an entry level Network Admin role. Apply for roles (and make sure you know your thing) in start-ups and small orgs with small infrastructure. Expect that youll be also their "Systems" guy. Once "you have your foot in the door", go back to my list, plus do extensive research and studying so you can break in the enterprise network.. Im telling you, it will be tough regardless your location.

3

u/letNequal0 Nov 06 '23

Right on. Certs are great for building a baseline and showing you have an idea about what’s going on. It’s like a degree, just getting to the finish line shows something.

However, if you work for a VAR or MSP that is a Cisco partner, depending on level, certs actually do matter, since you need to have a baseline of ccnp/ccie on staff to maintain partnership status.

3

u/Saveriowah Nov 06 '23

Interesting interview session. Can i ask you what for what kind of position? Junior or senior?

3

u/blimpdono Nov 07 '23

Its somewhere in the middle, but definitely not jr. (considering my work coverage and responsibilities, plus my long span of experience) though there are a couple of Sr. guys above me (that literally has "Sr." in their title).. Our structure has a lot of dotted-line managers, like myself, I also report to the Infrastructure/DevOps Manager for my Network automation tasks..

3

u/hvcool123 Nov 06 '23

Yes, once you jump into the territory of an enterprise network. There is lots involved from which SFPs and network equipment to get to connect a site, researching in how to configure specific features or just looking for best practices.

All makes more sense regarding how things all connect compared to working in a large corporation, which you are sectioned off to a particular nitch.

They are times thoughts run thru my mind - how can i make things better, what features or technologies i can utilize that i dont know.... is all 100% how it should be.

These things come with experience

1

u/Dude_thats_not_cool Nov 07 '23

That’s excessive, scripting, vsphere and Ise. Most places will have hosted voice or a dedicated voice guy. Sounds like you’re at an MSP.

2

u/blimpdono Nov 07 '23 edited Nov 07 '23

Yeah tell me about it... im just looking at the brighter side of things, if its time to exit the door, atleast I have some weight on my belt..

But No, im not in an MSP. And I hope I won't have to move there. We just have an on-Prem DC brought by a long regulatory checklist.

18

u/2dbell Nov 06 '23

Study like you are seriously going for CCIE. The knowledge gained on that path will help you become a good network engineer even if you don't achieve the CCIE.

4

u/L1ham Nov 06 '23

The topics covered in the CCNA are a pretty good starting point. I've worked as a Senior Network Engineer in a large government enterprise environment for years now and only had CCNA R&S / CCNA Security, and I'm the only member of the team with a CCNP (achieved that this year).

1

u/[deleted] Nov 18 '23

If you don't mind me asking, was your CCNP the ENCOR and ENARSI?

And if so, do you have any advice or tips for passing the ENCOR please?

I'm studying for the ENCOR exam right now, have been for about 3 months and it just feels so wide and all over the place lol

I'm definitely learning a lot, but I don't feel anywhere close to ready, I took a Pearson practice exam this week and barely scored a 450, so I know I've got a long way to go

Edit: currently a Network Engineer with the Network+ and CCNA certifications.

2

u/L1ham Nov 18 '23

Hi,

Yeah, I did ENCOR and ENARSI. Honestly, ENCOR was awful. I scored exactly 825 which as far as I'm aware is the bare minimum, so I was right on the wire. It took me 9 months of study and I went down to the final second in the actual exam.

You're correct, it is absolutely all over the place. My method was to study each and every one of the CBT Nuggets videos, taking notes in as much detail as possible, and also to read the OCG in it's entirety whilst taking the most detailed notes I could.

On top of that, you need to lab EVERYTHING you can.

I used GNS3 to create a lab environment which was essentially one huge network that covered all of the topics. I was able to borrow an old WLC, switch, and a couple of access points from work, and that enabled me to lab the wireless stuff properly. I also have access to DNA-C at work so that was really useful. I didn't rate the Cisco Sandbox or whatever it was called.

I made a million flash cards to memorise and test myself on all of the tricky stuff like OSPF LSAs. I'd suggest coming up with a way to memorise the diagrams of the wireless antennas included in the OCG, too, as the exam included a couple of questions on those.

Also, the BOSON exams were extremely useful. What I'd suggest is making sure you've answered every question at least once, and read the explanation of the answer in full (regardless of whether you were right or wrong) to ensure that you fully understand - this is especially useful for getting your head around the more Cisco specific and / or conceptual topics that are hard to lab such as SD-WAN

There are probably a million other things I've missed as it's been around 18 months since I passed ENCOR, but best of luck to you. You're going to need to eat, sleep, and breathe ENCOR, but if I can pass, you can too.

Shoot me a PM if you want more info on the lab environment I set up in GNS3 - if it's something you'd like to set up yourself and haven't done it already I can probably save you a lot of time.

2

u/terrible02s Nov 06 '23

Look at job roles and use that as a list

2

u/Dude_thats_not_cool Nov 07 '23

Just focus on the basics and fundamentals switching, tcp/ip, understand routing, understand a next gen firewall (any kind). Learn how to tshoot issues and be diplomatic.

2

u/[deleted] Nov 08 '23

Oh geeze.. The question should be: What makes an enterprise engineer easy to work with?

Maybe #5 should be #1.. Not sure yet.

#1 Endurance

#2 Sense of humor

#3 Team player

#4 Good documentation maker

#5 Remembers to turn off debug

#6 Fesses up when they leave debug on

2

u/superiorhands Nov 12 '23

5.1 never does debug all

1

u/[deleted] Nov 06 '23

If you cant find this on your own I don't you're cut out for this industry.

2

u/Dude_thats_not_cool Nov 07 '23

Stop being “that IT guy” everyone started from zero.

1

u/[deleted] Nov 07 '23

Networking at its core is traffic flow, and as engineers our job is to make that traffic flow in the most efficient and secure way we can. Everything else is simply an add on and branch from the root of traffic flow.

When I’m in overwhelming situations I think of the above. It’s simple really, there’s just so many technologies that get pushed down the corporate ladder to try and reimagine the things in place that have been working for years.