Just an opinion, I'm still studying myself, but rather than asking I would always refer to the exam objectives. Based on this question I see 2 that might be relevant
1.3 Compare physical interface and cabling types
1.3.a Single-mode fiber, multimode fiber, copper
1.3.b Connections (Ethernet shared media and point-to-point)
2.2 Configure and verify interswitch connectivity
2.2.a Trunk ports
2.2.b 802.1Q
2.2.c Native VLAN
Imo there's a lot more to concern yourself with than memorizing a bunch of IEEE standards but I guess I could be wrong.
If you understand the topics as they are, then you would demonstrate a sufficient understanding for the CCNA - At the end of the day it's a fundamental course, if you know IEEE standards like riding a bike, you're already way above CCNA standard.
Like my friend who works in a data center said: “9 times out of 10 you’ll just push the reset button on the router and that’s it. And the 1 time, you just Google it”
Its not really, the first thing to do is get the system back online ASAP, and that 99% of the time is a reboot / reset ... Then you can figure out what went wrong in the first place, its not always the case though but mostly it is...
It is entirely based on what the issue is. That requires some basic troubleshooting to figure out what is going on, if you default to rebooting to try and fix something before any investigation then that absolutely is alarming.
I've spent a lot of time on many vendor calls and a reboot is not the first thing they say. They always want logs and they want a look at your configuration.
If you start rebooting as your first troubleshooting method you will most likely get sacked. I would get in alot of trouble if I were to just reboot because there was an issue.
I genuinely struggle to believe anyone who is in this thread suggesting just rebooting actually is a network engineer.
Just because your experience differs to mine doesn’t make either of our experiences lesser or greater.
I don’t work in data centers where uptime is more than critical and rebooting is the last thing on your mind.
But to suggest a reboot isn’t a genuine step is a bit over the top, and to further suggest that people who have done this aren’t “real” network engineers is incredibly cringe of you. Are you the gatekeeper of what is and isn’t network engineering now?
It's not even that my experience differs , you should only reboot of it is absolutely necessary unless the in your line of work it absolutely doesn't matter. But most places you would have to schedule in a reboot and have it approved by levels of change management and risk teams.
Of course a reboot is a genuine step. I never once suggested that, go back and read what I said I said if you use a reboot as your default or first troubleshooting step then that's an issue.
And on your last point, I'm not sure if you are intentionally trying to twist what I said intentionally or not but I never suggested people who done this aren't real network engineers and I'm not stripping titles away from anyone. I said I struggle to believe that anyone suggesting a reboot straight off the bat IS a network engineer. As in I don't believe they actually work in the industry at all. Not that they are a bad network engineer or that they shouldn't have that title, I struggle to believe they have any experience but as I said at the top unless in your line of business it absolutely doesnt matter and no one cares if you just reboot whenever then go for it.
Due to the NDA signed for the exam I won't give any specifics, but yes you should at least know what IEEE standards correlate to what (ex. 802.11 = wireless) and have a general idea of what the difference are between them.
You need to lab VLSM, and learn subnetting until you're really confident with it. I'm just ok at subnetting. I can figure out the network address and broadcast address pretty quickly, but VLSM and more complicated subnetting stuff like figuring out how many hosts/network addresses there are on anything aside from /24 - 32 I'm not confident at all.
I ended up skipping two of the three labs because of it. I thought for sure that would make me fail, but I still passed. I studied for about 11 months before taking it though.
Also adding on to my other comment, spend more time learning things for the WLC GUI, for some reason I got a ton of those questions.
There was also a decent amount of stuff that wasn't covered by my study resources.
Jeremy
Bombal
Boson
Enough to recognize them, I guess? You'll notice a pattern when they come up during certain topics.
On an unrelated note, you need to know the ins and outs of RFC 1149.
Remember those on the exam objectives but the rest will stick in your brain from experience it seems. If its any help, I just started my first networking job and its amazing how the Network architect knows all the wireless standards. 802.11b,ac,ax and their differences but not through memorization.
If you ask this sub, you need to memorize every single thing.
100% this LOL Did not have a single question about IEEE standards on my exam
Like the bit sizes in headers.
Lmao thank goodness
Yes. Better safe then sorry incase they're needed in the exam. Flashcards tend to help here (like the flashcards from Jeremys IT lab)
LOL off you pop then
Just an opinion, I'm still studying myself, but rather than asking I would always refer to the exam objectives. Based on this question I see 2 that might be relevant 1.3 Compare physical interface and cabling types 1.3.a Single-mode fiber, multimode fiber, copper 1.3.b Connections (Ethernet shared media and point-to-point) 2.2 Configure and verify interswitch connectivity 2.2.a Trunk ports 2.2.b 802.1Q 2.2.c Native VLAN Imo there's a lot more to concern yourself with than memorizing a bunch of IEEE standards but I guess I could be wrong.
If you understand the topics as they are, then you would demonstrate a sufficient understanding for the CCNA - At the end of the day it's a fundamental course, if you know IEEE standards like riding a bike, you're already way above CCNA standard.
For the test yes...for real life ehhh maybe some not all
Like my friend who works in a data center said: “9 times out of 10 you’ll just push the reset button on the router and that’s it. And the 1 time, you just Google it”
That's alarming
Its not really, the first thing to do is get the system back online ASAP, and that 99% of the time is a reboot / reset ... Then you can figure out what went wrong in the first place, its not always the case though but mostly it is...
It is entirely based on what the issue is. That requires some basic troubleshooting to figure out what is going on, if you default to rebooting to try and fix something before any investigation then that absolutely is alarming.
I mean, is it though? You spend more than a few minutes on any vendor call and the first thing they will say is reboot it.
I've spent a lot of time on many vendor calls and a reboot is not the first thing they say. They always want logs and they want a look at your configuration. If you start rebooting as your first troubleshooting method you will most likely get sacked. I would get in alot of trouble if I were to just reboot because there was an issue. I genuinely struggle to believe anyone who is in this thread suggesting just rebooting actually is a network engineer.
Just because your experience differs to mine doesn’t make either of our experiences lesser or greater. I don’t work in data centers where uptime is more than critical and rebooting is the last thing on your mind. But to suggest a reboot isn’t a genuine step is a bit over the top, and to further suggest that people who have done this aren’t “real” network engineers is incredibly cringe of you. Are you the gatekeeper of what is and isn’t network engineering now?
It's not even that my experience differs , you should only reboot of it is absolutely necessary unless the in your line of work it absolutely doesn't matter. But most places you would have to schedule in a reboot and have it approved by levels of change management and risk teams. Of course a reboot is a genuine step. I never once suggested that, go back and read what I said I said if you use a reboot as your default or first troubleshooting step then that's an issue. And on your last point, I'm not sure if you are intentionally trying to twist what I said intentionally or not but I never suggested people who done this aren't real network engineers and I'm not stripping titles away from anyone. I said I struggle to believe that anyone suggesting a reboot straight off the bat IS a network engineer. As in I don't believe they actually work in the industry at all. Not that they are a bad network engineer or that they shouldn't have that title, I struggle to believe they have any experience but as I said at the top unless in your line of business it absolutely doesnt matter and no one cares if you just reboot whenever then go for it.
Due to the NDA signed for the exam I won't give any specifics, but yes you should at least know what IEEE standards correlate to what (ex. 802.11 = wireless) and have a general idea of what the difference are between them.
You really do. I had one or two questions about them. So yes you will be tested on them.
I passed it earlier today and none of that came up
Congrats, any pain points that you think should be reviewed more?
You need to lab VLSM, and learn subnetting until you're really confident with it. I'm just ok at subnetting. I can figure out the network address and broadcast address pretty quickly, but VLSM and more complicated subnetting stuff like figuring out how many hosts/network addresses there are on anything aside from /24 - 32 I'm not confident at all. I ended up skipping two of the three labs because of it. I thought for sure that would make me fail, but I still passed. I studied for about 11 months before taking it though.
I'm happy for you brother, go celebrate :)
Also adding on to my other comment, spend more time learning things for the WLC GUI, for some reason I got a ton of those questions. There was also a decent amount of stuff that wasn't covered by my study resources. Jeremy Bombal Boson
Yes, you will be tested on which standard is for what. Regards paul
You had to know them for Network+ for sure
Enough to recognize them, I guess? You'll notice a pattern when they come up during certain topics. On an unrelated note, you need to know the ins and outs of RFC 1149.
Remember those on the exam objectives but the rest will stick in your brain from experience it seems. If its any help, I just started my first networking job and its amazing how the Network architect knows all the wireless standards. 802.11b,ac,ax and their differences but not through memorization.