Not enjoying studying CCNA. Should I still pursue it if I want to become a Sys Admin?
Posted by j1mmyava1on@reddit | sysadmin | View on Reddit | 150 comments
Currently working in Help Desk and I have the CompTIA trifecta. I've been trying to study for the CCNA for the past 2 months but I'm just not clicking with the material.
CCNA was a cert I wanted to get because I read how it helped a lot of people move from help desk to sys admin because it was well-known. But after 2 months of studying I'm just not enjoying the material or studying it altogether. I understand the importance of networking in IT but its just not an area that really piques my interests. I took a break from the CCNA to study for AZ-104 and I'm enjoying that much more than the CCNA.
Should I still try to go for CCNA to break out of help desk?
virtikle_two@reddit
You can't fake a CCNA cert, and it still shows a foundational level of knowledge that is heavily desired in the industry. I'm a current netadmin, former sysadmin, and in a past life I was on the help desk for a decade.
Concepts on the CCNA are fundamental, if you want to be a GOOD sysadmin. You can get away with not having the cert, but really learning that nitty gritty is gonna put you miles ahead of any team that has you. A network+ cert (I have that too) isn't really the same.
THAT SAID..... You should focus on your AZ-104 and maybe look at the CySA if you like security.
Mammoth_War_9320@reddit
It’s not required to understood deep networking to be a sysadmin, but I will admit I hate working with sysadmins who don’t understand networking. Kind of blows my mind that some people get the job without understanding basic CCNA levels of networking.
Not trying to burst your bubble, just my opinion. And I have that opinion because networking is the backbone of how ALL systems interact and communicate with one another.
SquizzOC@reddit
Just a random tangent, but software developers who don’t know the basics about troubleshooting their machines or even artists in the video game industry.
Blows my mind when they can’t figure out a basic driver issue or just to reboot the machine.
TheVillage1D10T@reddit
Yeah…someone in this sub tried to tell me the other day that it doesn’t matter if a developer has even a foundational understanding of how computers work…..
payterrrrrrrrr@reddit
It’s true! That way, we can keep our jobs 😂 am I annoyed that I gotta tell users that a restart’ll help them? Yes. Am I paid to do it? HEKC YEAAA
Case_Blue@reddit
One dev blamed the network when his API call was not working.
He was trying to call 127.0.0.1:xxxx to another machine...
VexingRaven@reddit
My favorite one is indie video game developers that act like they've never played another video game and end up with something that ignores ever single lesson learned by the industry before them.
rayjaymor85@reddit
yeah the company I work for didn't even have an IT team when we were a startup.
The thought process we had was that if you couldn't handle basic IT troubleshooting then you were useless to us.
nonResidentLurker@reddit
This is why we get “see your system administrator” error messages. The devs can’t figure out why their own app is crap.
DULUXR1R2L1L2@reddit
Right? If they don't know what an IP address or subnet mask is for, or if they don't know how packets flow through the network, then they really aren't good admins. How many times do you get told the firewall is blocking traffic between two hosts on the same subnet...
screampuff@reddit
I mean I've done a lot of networking and still found doing binary ip addresses and such to be a complete waste of time.
NotMedicine420@reddit
Binary is purely fundamental knowledge. You don't need to do them in practice, but you must know how these thing work.
Suitable-Hand-1059@reddit
I’ve known how CIDR works for the past 20 years, and have yet to need it to function.
So long as you know the gateway, mask and IP that you need to connect, and know how to use a calculator or spreadsheet, there is absolutely no reason to be learning binary.
Mammoth_War_9320@reddit
This is just horrible advice all around and tells me you’ve been stuck in the same spot for several years.
Suitable-Hand-1059@reddit
You can make whatever garbage assumptions you like, but you’re still wrong. Tell me one good reason anyone needs to understand the math behind subnetting. I’ll be happy to wait.
It’s all laid out in advance; you can literally just reference a chart or use a calculator.
Red_Pretense_1989@reddit
Because inevitably someone is going to screw it up and not understand why they are wrong.
Suitable-Hand-1059@reddit
It really doesn’t matter. All I need to know is that a /30 has a useable address, a /29 has 5, and so on. So long as I understand the network side of it, ie my “network” address will be the gateway of last resort for the subnet and that this restricts broadcast traffic between domains, and how it ties into VLANs.
In the sector I work in (manufacturing) there’s no real reason to segment a bunch of tiny subnets; we air gap older machines entirely with physical dual-NIC setups for transferring files to them and the rest can live on good old 255 subnets with no chance of ever running low on address space.
Unless you’re working in a data center for a FAANG company, and even there the use cases would be minimal, there is simply no need at all to convert to binary so long as you understand the relationships between number of hosts and number of network segments per octet.
Mammoth_War_9320@reddit
I mean you’re already wrong. A /30 has TWO usable addresses. Not one.
Suitable-Hand-1059@reddit
No. You have one host and one gateway address on a /30, one “useable” address.
Mammoth_War_9320@reddit
Lmao bruh so conifendtly incorrect it’s hilarious.
Suitable-Hand-1059@reddit
Holy shit, you fucking dingus… unless you’re literally creating one or two host subnets on a private network, you’re an ISP or consuming the services of an ISP. One of the two useable hosts is going on their modem / router. That leaves one host to actually use. The other two are broadcast and network. By gateway, I was referring to the IP that gets assigned to the ISP / routing device, ie gateway of last resort for a given network segment.
I’m so over a junior sitting here masturbating to himself talking, please just stfu and come back in a few years when you know the difference between theory and practice.
Red_Pretense_1989@reddit
Why would it be required for FAANG and nowhere else? weird comment.
And by the time you memorize all the shortcuts, you could have just learned how simple binary is.
Mammoth_War_9320@reddit
He’s wrong anyways. A /30 has two usable hosts and a /29 has 6 lol
Bro is sitting here arguing with me about why he doesn’t need to know the math because “spreadsheets” and then immediately is wrong lol
Red_Pretense_1989@reddit
Exactly.. lol
Mammoth_War_9320@reddit
Tell me you don’t know how to subnet without telling me you don’t know how to subnet.
screampuff@reddit
If you tell me you're using binary to create subnets and not a calculator, or memorization, I don't believe you.
Mammoth_War_9320@reddit
100% you can use charts, but this guy is trying to tell me that all you need to know is the subnet you’re connecting to. Which to me signals he’s never had to calculate a subnet in his life. Whether using a chart calculator or anything. Bro just expects the subnet to already exist.
KangarooSavings2745@reddit
I'm with you. Sysadmins need to know how things work. If subnets are a black box then you'll be in the dark a lot.
Mammoth_War_9320@reddit
Yea pretty shocked I’m eating downvotes for defending my claim that knowing how to subnet and how binary works is foundational sysadmin knowledge is mind boggling to me
Lot of shittysysadmins in here I guess lol
LegRepresentative418@reddit
Oh man, don't get me started on this nonsense. "192.168.1.25 cannot ping 192.168.1.26. Can you check the firewall?"
Nezgar@reddit
192.168.0.0/23 cant possibly be a valid host address.
neploxo@reddit
Windows firewall on the destination machine.
rayjaymor85@reddit
Fair, but the first thing I would check is if .26 is even turned on.
ocviogan@reddit
I just dealt working with a "Sr. Network Engineer" that could not do a fucking inch worth of networking, he could barely seem to understand his own computer. He also made the most money in the entire team while he kept trying to get me to help him to do his own job. I refused to, and of course my boss caught on and understood.
That network engineer only lasted 2 months. But that's two months of him doing nothing with only 2 tickets resolved under his name that he didn't really work on. The only thing he did was nuke our Meraki licenses for all our networks and fuck up the firewall management interface configuration, which I'd say is the most productive he ever was.
I have no idea how this guy qualified and made it past the interview process.
CandyR3dApple@reddit
This happened to us.
I’m a Sr Engineer with the most time in seat at my org so I am brought in on final interviews for potential Engineers. I don’t let them give vague answers so I’ll have them verbally configuring a router, site-to-site tunnel, etc.
This young lady nailed it. Best interview I’d seen in years. She started 2 weeks later and was let go on day 4. Total fraud. I’m guessing she was using AI. All final interviews are in-person now.
chory06@reddit
Wish i could land an interview like this....and these are pretty basic stuff.
CandyR3dApple@reddit
It’s mind blowing how many I see where it’s not basic. On the site-to-site IPsec tunnel, most quit somewhere during Phase 1 configuration.
Mammoth_War_9320@reddit
Lying and bullshitting his way through the interviews. Some people really are that good at it.
Have a friend who seems to be able to get every job he interviews for. Dude just crushes interviews somehow lol
okcboomer87@reddit
I got my Net plus but hate networking. Can't imagine getting the CCNA at this point but it would likely help me.
BeyondTheHubbleFlow@reddit
I've done both.
Honestly unless you are working with Cisco gear I think the Network+ is more useful as Cisco's one is VERY Ciscocentric.
They use a lot of their own terminology for things that have standard names a few examples
A lot of it is just learning their marketing speak similar to how the 104 microsoft examples are learning Microsoft terminololgy.
There is still a lot more there like learning to use IOS and stuff but if you aren't working with Cisco gear professionally the Network+ is a better foundation as if you do the CCNA later you alreadly know a lot of the concepts and find yourself going "oh! X is just Y renamed"
chory06@reddit
Ive taken net+ and ccna, ccna is much more useful. Comptia is mostly definitions and such - net+ probably a little more then definitions when compared to a+ and sec+.
Net+ teaches you general open standard protocols while ccna teaches you both open and cisco standards.
Net+ passers wont be able to tell why/how a traffic flows in a network but a good ccna can(which is great for cybersecurity as well).
Net+ teaches you that spanning tree prevents loops and thats really it.
Ccna teaches you it prevents loops and how it does that. Then theres also why.
Just my 2cents
neploxo@reddit
And the Cisco-specific stuff you really NEED to know that's NOT covered in CCNA. Like how their own documentation and sales engineers couldn't agree on how many T1 modules we could put in a router. It had the slots for 4, the sales configurator allowed 4, but the CPU couldn't handle the interrupts from more than 2 so the thing basically became useless. Or how many times they'll sell you something that is going EOL a month after you install it. Or how they change up the names of product lines every few years so you don't know what you're talking about. Or how all the security features they advertise aren't included in the base OS license and you have to pay extra. It's been over a decade since I had to deal with a Cisco purchase, but oh the memories.
j1mmyava1on@reddit (OP)
Off-topic but thats a neat little study chart I'm saving for later hehe
autogyrophilia@reddit
The thing is, there are a lot of things that are covered that don't really matter, and a lot of things that aren't covered that do. So there are always alternative ways.
Not that I don't get your point. Really my suggestion to anyone learning is to get yourself a bunch of virtual machine and start making the enviroment as complex as you may want, throw VPNs and services like AD in there, see what happens, do things that should work work? do things that shouldn't work not work? . Now that Proxmox has SDN and helps you do nested virtualization it is much easier to get it going .
neploxo@reddit
Do they still ask you questions about frame relay? I took it in 2003 and those were the only ones I missed.
rw_mega@reddit
I would say it's what makes the difference between a shittysysadmin and a great sysadmin
Fuskeduske@reddit
Honestly i just hate working with people not understanding the fundamentals of what they are working with
Igot1forya@reddit
CCNA is just one angle in the multifaceted subject of networking. I've met CCNA certified folks who were absolutely clueless when dealing with client-side and even wireless networking or even breaking out of the Cisco ecosystem. I don't know, but I feel like some folks going down that road get blinders on and try to silo themselves and simultaneously become less helpful outside of that narrow focus.
ibleedtexnicolor@reddit
This is why I firmly believe anyone who wants to be in networking should go through helpdesk first. It's the best way to start learning how to troubleshoot from the bottom, and as you gain more experience with networks you learn how to start from the top or from both directions at once.
flucayan@reddit
There’s definitely a type of networking guy like that (thinking about quite a few of them who do tutorial online and literally boast about this).
This is why I always stress that in this industry you need to go through the trenches. You should not hold the title of network/security admin or anything above that if you’ve never been a sysadmin, similarly you shouldn’t be a sysadmin if you’ve never worked as a technician or helpdesk.
Similarly to math or traditional engineering there’s building blocks you should have at least an intermediate understanding and experience of and you before you touch most advanced problems i.e. how did you get to the answer and how are the pieces applicable to the solution, don’t just give me the answer.
ibleedtexnicolor@reddit
Everyone does, because when the sysadmins don't have a basic understanding of networking they blame everything on the network. They're the ones who waste our time having to prove it's their systems. I've been blessed to work with a lot of outstanding sysadmins who knew enough to listen when I gave them the high-level explanation for how "it's NOT the network" and would them go troubleshoot their systems more. Many of them would come back to me after locating the problem and let me know what it was.
I've also worked with sysadmins who wouldn't believe me until I ran packet mirrors on every interface of every server they had in our AWS DR setup, proved the traffic didn't go through a firewall, and then additionally diagnosed their Kerberos problem without ever seeing their servers. That took two weeks to sort out.
heroik-red@reddit
Out of curiosity, what were your experiences with working with admins that don’t understand networking?
Mammoth_War_9320@reddit
Escalating things that they should be able to resolve themselves giving me more work to do. Simple things like not verifying up/subnets on a host to figure out why it has internet but can’t connect to other internal resources. Stuff like that.
autogyrophilia@reddit
Did you run "route print"?
Daphoid@reddit
It's amazing how many don't know DNS either (and just knowing that domain <-> Ip address is not enough).
I don't have my CCNA, I'm poor at subnetting but understand the basics enough of network to trace issues, look at wireshark, follow things along a path, etc.
I don't think a sysadmin (especially in these times of specializing and full cloud org's) needs CCNA, but a basic understanding is good.
In general, a basic understanding of everything IT will go a long way to working with other teams who may need your help (in whatever you do) connecting the two together. "Oh I'm a database guy I only know that" or "I only do cloud stuff" just doesn't cut it unless your org is so huge they have teams for everything.
jreykdal@reddit
CCNA is not required for sysadmin work as it is networking, and Cisco focused.
But having a decent understanding of networking is healthy for admins so it won't hurt. But it's definitely not a requirement.
robvas@reddit
It should be required
Calleb_III@reddit
Why? If your environment is big enough to actually need all the knowledge of CCNA, but has no dedicated network admin(s) you should run away, not study for CCNA.
Basic understanding of layer2/3, TCP/IP, DNS, DHCP and routing is plenty for sysadmin
Due_Peak_6428@reddit
what if you dont have a basic network and you have an issue you are screwed
Calleb_III@reddit
Then get a basic network knowledge, don’t overdo it with CCNA. There are better certifications for sysadmins to spend your time on.
If you still want to get CCNA as a sysadmin - by all means go for it, but that’s not what OP is asking.
Due_Peak_6428@reddit
Ccna is a entry level cert lol. If you can't do ccna level networking then you are screwed
Beginning_Ad1239@reddit
And I'm over here wondering why the industry has this hyper focus on Cisco. Too many network admins can't do anything outside of Cisco's proprietary way of doing things. I would say go get network+ and never look back unless you're needing to deal exclusively with Cisco.
Calleb_III@reddit
Well i must be an exception then, because I don’t have CCNA yet somehow got a triving career as systems engineer for over 2 decades. Note that i’m not saying I don’t have networking knowledge, just never bothered with CCNA
Due_Peak_6428@reddit
i said if you CANT do ccna level networking then you are screwed. i never said you need the cert
Stonewalled9999@reddit
Blame the network like my T1 and T2 and T3 does. Even my network engineer doesn’t understand networking sometimes
NorthernVenomFang@reddit
With that attitude you really limit your job opportunities.
I work for an org that has a fairly large/geographic are for it's network (50 sites, approx 33K end-users), a mix of Cisco/Meraki/Aruba-HP. Even though I am the equivalent of a Sr SysAdmin, I would not be able to do my job without the knowledge that came without learning what is in CCNA.
Calleb_III@reddit
What attitude? Specialising deeper into sysadmin skillset instead of trying to be a jack of all trades, master of none?
Network issue goes to dedicated network admins to solve. Your understanding of networking should be mostly to guide them in the general direction of the issue. For example - looks like routing issue or FW issue etc.
NorthernVenomFang@reddit
Your assuming that you will always have a network admin to do this for you.
Their is absolutely nothing wrong with being a jack of all trades... In fact a lot of people end of as sysadmin by doing help desk/desktop support -> jr sysadmin/network admin. I would rather have sysadmins brought into the fold this way, they tend to have better troubleshooting skills.
neploxo@reddit
Even if you DO have a network admin, basic knowledge is essential in communicating with them accurately and efficiently.
Calleb_III@reddit
Did you even read my first post? Go read what i said about size of environment and relation to CCNA level network knowledge.
While at it read OP too.
NorthernVenomFang@reddit
I read both.
OP mentioned that they found CCNA concepts difficult...
Well hate to state the obvious, IT is a field that keeps constantly changing, their are going to be things you are required to learn in order to do your job and advance in your career, and a lot of them are going to be difficult to consume. Not trying to come off as mean, just stating the truth.
As to a specific size of org that requires CCNA... I have seen tiny orgs (3 people), medium size orgs, and large ISPs need and not need CCNA equivalent network admins.... It all depends, and the same goes for having dedicated network admins (it depends).
Now is having a CCNA going to help the OP get a chance to get out of Help Desk and into a SysAdmin position, maybe, it is definitely not going to be a liability. What it will do though is show his current manager/employer/HR that the OP is willing to learn something that may be uncomfortable outside of their duties; this will put the OP in a better chance for advancement within the department. The road to sysadmin is not always a straight line; Help Desk -> Jr sysadmin, Help Desk -> Field tech -> Jr sysadmin, Help Desk -> Field tech -> jr Network Admin -> Sysadmin, ect...
neploxo@reddit
There are a lot of networking principles I'd say apply very well to sysadmin work.
1) Always back up/save your configuration before you change anything
2) Test BEFORE you commit a change/write mem
3) OSI model applies not just to troubleshooting networks but very much to troubleshooting standalone PCs/servers
To name a few.
robvas@reddit
Most people don't have that though
Calleb_III@reddit
Be as it may, that’s not a reason to “require” CCNA for sysadmins
chipredacted@reddit
Networking CAN be system administration work, but there is a point where requirements become complex enough that it constitutes its own role
derango@reddit
But it’s still REALLY helpful to understand basic networking, subnetting, vlans, spanning tree, etc
chipredacted@reddit
Agreed 100%, but a CCNA goes much further than that I feel like. Maybe I'm wrong tho
KangarooSavings2745@reddit
Nah you aren't wrong. Lots of routing protocols that most admins won't use.
Diseased-Imaginings@reddit
I'd add the caveat that actually having the cert is optional, BUT at least studying the material and understanding packets, subnets, VLANs, STP, and related is absolutely required to be a sysadmin. You literally can't do the job without it.
Inocain@reddit
So the Network+, basically?
robvas@reddit
And you can probably skip the actual Cisco router commands if you don't have any equipment on-site
Warm_Protection_6541@reddit
It should not, and likewise is not required.
crazycanucks77@reddit
I don't understand these people who want to take the easy way. CCNA should always be required. It's a great course/exam to learn the fundamentals of networking.
Crazy to see that people that want to be a Sysadmin but don't think they need CCNA or learn it.
Brandhor@reddit
I don't think ccna itself shoul be required since it's cisco specific, I personally don't have it and I've never used cisco hardware but I agree that all sysadmins should know networking
NorthernVenomFang@reddit
I don't think he cert itself should be required; the knowledge/ skills learned studying for it should be.
chesser45@reddit
Because systems administrators are a catchall term and spending the time capital investment to do CCNA and be certified isn’t of much value if you can do some bad stuff and then you don’t touch a NIC or anything for the rest of your career.
johnsmithdoe15@reddit
unlike most manu certs ccna r&s networking is one of the least manu centric certs out there, its pure network fundamentals, heck even ccnp r&s isnt really cisco centric, and anyone in any it role should have at minimum basic network understanding as its such a core part of the stack, be that onprem, or on someone elses prem (cloud is just someone elses tin)
christurnbull@reddit
Meanwhile, me getting stuck on converting decimal - binary and petty much flunking out there
I did find the osi model helpful though
GhostandVodka@reddit
The title "Sysadmin" does not automatically silo you into only doing windows patches for your entire your career. Sysadmins need to know networking. Network engineers need to know how OSes work
qwertydiy@reddit
Network Engineering pops up everywhere in sysops and even in programming, very underrated.
tuvar_hiede@reddit
Yes, having the CCNA will be helpful. You can't be a sys admin without knowing how a network functions. On the otherhand the Network+ will also work for your goals. The CCNA is a higher tier cert though.
AaronKClark@reddit
In this climate you having your CCNA might be the difference between getting a SysAdmin job vs being unemployed. I say go for it.
Sudden_Office8710@reddit
If you can’t figure out basic networking you might want to find another line of work. AI is coming for the uninitiated if you can’t teach yourself networking how do you expect to pick up DNS, mail, DHCP, Active Directory. You should know networking first because everything builds off of it. If I had that give up mentality 30 years ago I’d still have a sad job of being a sys admin. The problem with AI is companies will be hiring guys like me over guys who just know bits and pieces and not the full stack. I run into guys that have been doing the same garbage for 30 years and still barely making chicken scratch. Like the Concert contractors that do the dirty for Lumen. Getting new circuits is depressing seeing these guys and I basically have to take over the entire install process because they are so clueless.
QPC414@reddit
CCNA has changed a lot in the past 5 years. Less of the nuts and bolts config and more theory and abstract information.
For Sys (Server) Admin work you are probably better served following the MS track for Azure, 365 and server/desktop as well as virtualization.
What you need for networking at this point can probably be covered by reviewing a recent Net+ study guide or books, as they are generic as opposed to vendor specific.
SevaraB@reddit
Sysadmin without networking? Doable but only at really big places with really narrow silos, and has constant risk that you’ll be part of the next round of RIFs or layoffs. Not to mention you’re not going to get a big payday without putting on more hats.
Take the AZ-104, for example- It’ll teach you how to use Azure public cloud resources, but it won’t teach you how to plan vnets to integrate those resources into your other infrastructure as private cloud. While CCNA doesn’t teach network design, either, it will at least give you a peek into what config items you’re trying to keep from leaking into and out of your cloud tenant, and understanding ARP and routing protocols and L7 protocols on top of them will help you understand what you can filter out via a hub-spoke routed gateway versus what just needs to be in a flat mesh as a single subnet.
CharlieTheK@reddit
It's a good breakdown on networking that you'll use in most technical jobs. It's Cisco-specific but makes it easier to pick up other vendors as well. Bonus points for having a ton of quality study resources.
Honestly it's probably the most recognizable cert in tech in the lower and mid-range career spaces and will help you a lot with getting interviews, even if it isn't a requirement for sysadmin work.
fdeyso@reddit
I did a ccna a really long time ago and i’m a sysadmin (not network admin) but it’s a good foundation to understand networking that a lot of sysadmin lacks.
BonezOz@reddit
Not every business runs Cisco networking equipment. Where I work, everything is Fortinet, and we also push Fortinet and Ubiquity out to our customer (we're a SME MSP). While Fortinet does have a CLI like Cisco, most all configurations are done through the WEB UI.
I've also worked in places that were strictly HP Procurve networks, or even Netgear networks.
But the funny thing is, you don't have to be a network guru to become a Sys Admin. Shit, I suck at networking, though today I can do a lot more than I could 10 years ago, I still struggle with the basics. But my official job title? Senior Systems Administrator/Engineer. Certifications? None. Everything I know is based on things I've learnt while on the job. DNS migration, DHCP clustering, configuring VPNs, etc. all learnt and a lot of it taught to those up and coming junior admins.
You want to break free of the Hell Desk, volunteer to assist on projects, tell your team leader/IT manager that you want to learn more (they love that kinda shit) so that you can do your job better. Next thing you know, you'll be a junior sys admin writing PowerShell scripts to automate tasks.
merkat106@reddit
Sys Admin here. I got my A+ in 2008 and CCNA in 2010. My current employer respects it even though mine is now expired. I am on my company’s soc/noc team. But every employer is different in regard to certs versus experience.
I have known many who do sys admin work who have certs and those who don’t. Certs show you can take an exam. Focus on learning the platforms and topics that system administrators utilize (whether you set up a homelab or take a course) and show that you have exposure in it.
For me, I had lots of on the job exposure and read everything I could get my hands on.
Kikz__Derp@reddit
CCNA is a cert for people wanting to be a Network admin (not that the info isn’t somewhat useful for a sys admin) but almost all of the Cisco centric CLI work won’t be relevant to most sys admin jobs.
Ihaveasmallwang@reddit
I don’t know a single sysadmin with a CCNA certification. Only network admins/engineers.
johnsmithdoe15@reddit
and this is why theres the plethora of 'blame the network' memes
Ihaveasmallwang@reddit
To be fair, a lot of times it is the network. The network engineers having a CCNA doesn’t mean they are good network engineers.
jazzy095@reddit
CCNA is simple these days and has solid core concepts you should be aware of. Highly suggested. There is not even routing in the cert anymore. Just super basic. Will pay dividends with your Azure studies.
BWMerlin@reddit
IMO CCNA has more recognition than Net+ but at the end of the day if you aren't enjoying the study and the financial commitment don't do it.
certifiedsysadmin@reddit
CCNA will teach you two things that 90% of people in our industry don't understand: - The OSI model, probably the single most useful piece of knowledge any network or system admin will use throughout their entire career - Methodical troubleshooting using the OSI model, which applies to at least half of every ticket or project implementation you'll work on in your career.
I've seen time and time again in our industry that people who understand networking are the ones who excel in every other area.
Virtualization, cloud, and artificial intelligence have changed our industry drastically. Yet all of it and everything else we do depends on Layer 1-4 of the OSI model, especially IP/TCP/UDP, three technologies that have barely changed in 40+ years.
neploxo@reddit
The same layers of abstraction OSI applies to networking also apply to system virtualization with products like VMWare, storage virtualization, and more or less with Kubernetes.
MSP_Guy999@reddit
I won’t get it. 20+ years of skin in the game. Get your AZ104, devops, and AZ security so you can build enterprise cloud networks. Study SAN and cloud storage technologies so you can work on hybrid enterprise with confidence. Learn Terraform and ansible conceptually so you can utilize IaaS. I’m not saying people shouldn’t have CCNA but I find I can google or use AI to get the subnet math and other trivial things. Learn how to get AI (Claude code and gpt 5.5) to do the heavy lifting without breaking prod, that’s a real skill set!
Camp-Complete@reddit
Been a SysAdmin for 10 years and I'm doing CCNA certs now for the first time. I've never really needed to know it but have felt its been a missing part in my overall scope of knowledge.
Learning it has connected a lot of dots that I already knew into a single point. I've found it useful as I can look at networking with some networking guys and talk them through what the issue could be
CMMCTrack@reddit
It's not required but it's a great cert/skill to have. So many SysAdmins/Devs have no idea about the network stack it's amazing things actually work together.
anonpf@reddit
You may not enjoy it, but I guarantee, the knowledge you pick up from it will make you an infinitely better sys admin. You don’t need the cert, but it’s nice to have the knowledge.
Comfortable_Ad1816@reddit
Sysadmins manage systems but basic networking knowledge is needed
STDS13@reddit
I was a sysadmin for years and hate networking. I’d wager 80%+ of what is involved in the CCNA will never come up in sysadmin roles.
TxJprs@reddit
i got my ccna over 15 years ago when i career switched into it and it’s been the invaluable. specially when dealing with actual networking people and arguing if it’s networking vs systems. the basics of ccna go far. is it still centered around subnetting, route and switch.
Skunkfest@reddit
I read and worked through the textboot for this, I took the test at got a 600 or something. I think that translates to a D.
I did not get the cert but that is still one of the most valuable books I've read since.
It makes troubleshooting things easier, it's well regarded on any technical team.
linhartr22@reddit
Maybe you should consider another path to system administration. Learn a scripting language like PowerShell for a Windows environment or Python for Linux environments. While on the help desk you can look for opportunities to automate common tasks. Get a few of these under your belt then show them to your manager or make a portfolio and show them during an interview.
Suitable-Hand-1059@reddit
I’m a systems administrator with around 10 years in the field. I still don’t have a CCNA, and really don’t need one.
You WILL need to understand network fundamentals, but imo the CCNA focuses far too much on the minutia of frame headers, packet structure, etc.
Darkside_310@reddit
I'm in the same boat here, current hell desk worker with an opportunity to join the sys admin team or become a full network admin. I ate shit tickets for about 4 years now, not escalating tickets over to the tier 2/3 team ( not unless I have don't have the m365 gloabal admin rights to do so, or access to the network portal meraki cloud, etc)
I studied CCNA a little about 6 months and took the exam and bombed, the material doesn't stick for me, I find the multiple choice questions and subneting practice just not for me. I rather work on live equipment.
Luckily with the new direction our IT manager is heading towards a major refresh with Arista networking gear, (switches, routers, access point, etc) and as I was doing some research their ACE level 1 is just a x2 hour open book lab exam, for the same cost as CCNA 300$. So I popped open some switches and routers and started, working on live equipment, (only with permission from my boss) And my boss said it's an equivalent as CCNA so it's a green light for me.
My current role and environment is different, I don't shade on CCNA but I find this path not well suited for me. I would recommend keep on with Microsoft cets maybe Az-104 or (if you have access to firewalls) Palo Alto or Fortinet, and maybe jump into some Juniper certs. Lucky we have Arista equipment, but every organization I worked for had a mixed stack of cisco, juniper, extreme network, equipment. And made getting some hands on learning a leg up, instead of mentally recalling bullshit for an exam. Some of these heavy cisco dudes I worked with in the past are some of the most entitled, self serving pricks I ever worked with. I littlerelay had to teach a network admin ( in a past company I worked with) how to run a patch Ethernet cable, crimp and show them the T568B methodm
My situation is different, I learned in this organization I am currently employed to just, throw myself into the fire and throw some 💦 💦 💦 before executive management smells any 🔥 🔥 🔥
Hope this helps.
AmiDeplorabilis@reddit
You may not ever need the cert, but you need the knowledge, and the CCNA is a prime way of getting that knowledge.
ez12a@reddit
I'm a sys engineer for FAANG and dont have certs beyond comptia a+ and network+. CCNA is if you want to get into network engineering/architecture. I wouldn't say it's a requirement for sysadmin.
How I personally broke out of help desk was gaining hands on experience with sysadmin duties starting out with learning and using Windows MDT and SCCM. See if there are opportunities in your role to get to know your sysadmins in the company.
8923ns671@reddit
Currently studying to try to get into cloud engineering coming from a service desk/light sys admin background. Working through the Az-104 and the devops course on boot.dev. I'm confident in my fundamentals like networking and basic programming. Is there any thing else you would recommend? I enjoy automation, IaC, and think something SRE like would be interesting.
ez12a@reddit
You are on the right track. I would add some kind of platform agnostic config management, like chef, puppet, ansible, etc.
For more Linux oriented roles definitely Linux internals like sys calls, signals, interrupts, memory management, etc.
whynot817@reddit
It gives you a solid understanding of networking that from a sysadmin side is helpful, since it’s your not enjoying it might mean something else. I’ve been in IT for 25 years, Helpdesk, sysadmin, network engineer, telecom, virtualization
Engineer, IT manager, IT director roles. I’ve had to learn lots of stuff I didn’t enjoy but were deeply related to the role. So my take is yes you should still work on getting it. What you learn now may help you down the road, you just don’t know it yet.
statix85@reddit
Ccna is entry level. I was also not too keen to learn for ccna, but it gave me a solid networking foundation.
tgwill@reddit
If I’ve got a candidate for a Sysadmin role with an understanding of networking, I’ll probably choose that guy.
More and more, a basic understanding of networks is missing and it’s becoming more required as each year passes.
shimoheihei2@reddit
There's a lot more future growth in cloud than in networking. Knowing the basics for networking is crucial, but a lot more employers want people who know the cloud.
valar12@reddit
It’s not required. Basic understanding of tiered networking and DNS still is but the CCNA is just one representation. You’re fine to learn it elsewhere.
Test-NetConnection@reddit
It's required. Cisco is ubiquitous in the industry and you need a working knowledge of networking whether you become a network engineer or systems engineer.
Ihaveasmallwang@reddit
Not required to be a sysadmin. Maybe for some companies for network admins.
JustAnEngineer2025@reddit
It'd be in your long term best interest to at least learn the concepts of network and how do to the basics.
Imagine having to call your network engineering team because you 1) do not know what a subnet mask and default gateway are and 2) you do not know how determine them.
RedhandKitten@reddit
Sysadmin here, who failed the CCNA twice. lol. Which was a bummer because I did well with CompTIA. I feel like I learned the most from Network+ that now applies to my role.
In a small shop, it helps because you’re one of a few (if not the only one) keeping everything running. Somewhere big, you’re likely not the one handling those types of problems. But it’s going to be a lot easier, and appreciated, when you have to talk to the team that does.
ThoriumOverlord@reddit
Not a network admin proper, but I do enough with networking on the daily that the CCENT (a "stepping stone" to CCNA) worked perfect for me so I could ask the actual network guys the right questions and convey what I'm looking for better with requests. Even helped me do basics like port configuration, adding stuff to my vlan, etc. before we got official network admins. Looks like that's been replaced now by the CCST but if it's similar, it'd help work your way to it if you don't already have a background in that line.
traviss8@reddit
I'm helpdesk who larps as a system administrator, but CCNA is only really relevant if you want to be a network admin for Cisco devices. Lots of places use aruba or ubiquiti or fortinet or whatever. Lots of options
IdidntrunIdidntrun@reddit
The CCNA helped me better understand all network equipment for any manufacturer/vendor, not just Cisco stuff.
Like yeah the exam has a decent amount of focus on Cisco proprietary things, but forcing myself to better understanding subnetting, routing, STP, packet traffic and flags, etc. applies to concepts industry-wide
It's like learning learning a programming language. If you can code with Python you can probably use a lot of concepts you know to learn a different language without having to start over
BadCatBehavior@reddit
Yeah I got my CCNA back in 2016 and I've never actually managed any Cisco equipment, but the fundamentals I learned from the CCNA made it easy to deal with other brands.
It's like learning to drive a car. You might learn and pass your driving test in one car, but you can drive other cars. The buttons and knobs might be different but it functions basically the same.
crazycanucks77@reddit
That is so wrong. The CCNA is not just a vendor exam, it teaches you network fundamentals. That's why it is always a recommended cert!
Due_Peak_6428@reddit
just do the networking parts of the course
NorthernVenomFang@reddit
Not required, but the knowledge and skills you gain from it will tremendously help you if wish to pursue becoming a SysAdmin. Being able to keep up with the networking admins/techs when you are in meetings with them is crucial, not only that earning their respect is a plus.
Unnamed-3891@reddit
CCNA is not a requirement but it sure helps.
frankztn@reddit
No CCNA needed, but you need to understand networking.But you need to understand how to troubleshoot using the OSI model and at what layer is the issue being an issue. I defer to experts(vendor support😂) when I have done the basic troubleshooting and I know the general cause.
Bladerunner243@reddit
CCNA is Cisco, just one brand of many for networking. I would focus on CompTia generalist certs like Network+ and Security+ since theres no guarantee a job you want will be using Cisco. After that just focus on experience and try to proactively teach yourself brand specific skills if you are in an environment that gives you the opportunity to do so.
Ok-Measurement-1575@reddit
Cisco certs are probably the only worthwhile certs in all of tech.
RadiantWhole2119@reddit
That’s a dumb ass comment.
TechMonkey13@reddit
As a sysadmin who spends a good amount of time managing networks, yes.
gnipz@reddit
I’ve heard that learning the theory half is good, but the gritty, Cisco-specific pieces aren’t necessary.
bayridgeguy09@reddit
Don’t give up. CCNA was 25 years ago for me. I still use that knowledge daily.
For me what finally made it click was doing it and not just reading it, it didn’t make sense until I saw it in action. I didn’t have money for gear back then but used Boson Router Sim and Netsim to see it actually happening.
LegRepresentative418@reddit
Yes. You don't necessarily need to pass the test in my opinion. But the concepts are absolutely essential if you want to be good at your job.
StyxCoverBnd@reddit
What type of sysadmin role would you like to ultimately be in? Working at a small company where you do a combo of sysadmin/network stuff or working at a big corporation where you focus on just one thing? IMO, unless you want to be a jack of trades type of person in small 3-5 man IT teams, forget about CCNA and focus on the Azure certs.
Antoine-UY@reddit
No. If you hate network administration, you certainly don't have to study it. Simply build some other form of expertise and go from there. Just now that, at some level, intersections with actual network deeper understanding will necessarily emerge. And if you wind up actually doing stuff outside of the homelab/helpdesk L1/L2... you will have to get some understanding of networks. But:
a) doesn't mean it has to be now
b) with accrued interest for the discipline (once you start to feel what it could bring to the table FOR YOu because you can already useful stuff), it might be easier for you to focus on it in the future
Time_Coffee_5907@reddit
Well that's a job mate you're not supposed to "enjoy" that stuff, it was annoying as well for most of us I guess but once you know your shit it's more interesting, goal is to make money, if you can do something else to make money easier then go for it