I'd say that, to be a true network engineer, you need to be doing the work of a network engineer, which means heavy design & implementation work on networks. None of that other stuff really matters.
Job titles don't mean anything. I've worked with people with "network engineer" and "network architect" titles who did zero networking. Companies come up with all sorts of weird title/position combinations, usually to make the job sound better than it actually is.
Certs don't count, either. Having a CDL license doesn't make you a truck driver, driving trucks makes you a truck driver. Not to mention that you have guys with just a CCNA doing architecture work and people in the CCIE hall of fame who don't actually know any networking.
I've personally seen this myself in the two places I've worked. The guys who do architecture and design where I work have zero certs and our CCIE consultants don't know a single thing about our infrastructure.
I am not sure what IR is .... ?
Cyber Security is more likely to land a networking gig than helpdesk. Even if that role is in compliance or assurance. Knowledge of security is a desired trait in networking.
Thanks for the insight. I think I’ll just stick it out until I find a networking job.
I was in the same boat back in the day. I was an IT Security Analyst.. sounded cool but it was bs and didn’t really even do anything technical. And this was my first real job in “IT”.. I studied and got a cert. That job, my degree and cert all on my resume helped me get a job in networking.
Makes sense. Thanks for the insight!
I have taken classes that use both curriculums and am currently re-reading ICND2 now to write my CCNA and I believe the ICND1 is more memorization-based since it’s more conceptual in nature while ICND2 builds off of what was memorized. That’s not to say there isn’t anything to memorize for ICND2.
I say go CCENT. Its meant to serve as an entry-level certification and I feel the Official Cert Guide does a good job at explaining the concepts. You can always supplement the reading with CBT nuggets videos as they are easy to watch.
Your problem is that you aren’t using a routing protocol to exchange routes. Floating static routes are meant to replace a dynamically learned route if that route is removed from the routing table. With only static routes configured on the routers, there’s no way for your routers to communicate route statuses to one another. Try configuring RIPv2 between your routers and then set the floating static route with a higher administrative distance than RIP-learned routes. That should make everything work.
Administrative distance is used by a router when it learns of routes to the same subnet via different methods. It basically tells the router which learned route it should trust more. In your case, the static route is the only method in which it has learned routes.
Not on my pc at the moment, will try this asap, I have a small doubt though.
There's a part that is not clear to me however. What I know is that the lower the number, the more "believable" the route is and thus, the router will pick that one over another one with higher AD
If I want to ping a PC that is on the router 1 by passing through router 2, I ought to add a static route that has a higher trustworthiness than the RIP discovered one otherwise, the route will always pick the "backup" route to route packets towards router 1. I should do the same on router 1 and add a static route that has higher trustworthiness so that the router will send the packets back through router 2.
But if I do that, won't the router pick up always the static route and ignore the one it learnt through RIP? and, if I do set the reliability fo the floating static route to be higher than the RIP learned one, won't the router just always prefer the RIP one then?
I am a bit confused as this wasn't part of the lesson at all, we've just got explained the ip route command and how to add static routes, there was a talk about routing protocols but he said that we'd look at them in-depth in one of the next lessons
RIP is going to choose the route that goes from Router0 -> Router1 to reach subnet 172.16.44.0/24 by design as it has the shortest hop count (distance)
I do not think your professor has thought this assignment through because while you can configure static routes with varying AD values on your routers, Router1 will not learn about the link between Router0 and Router2 failing which thus causes Router1 to send packets back toward 10.10.10.0/24 using the primary route through Router2 (which has failed). This creates a routing loop because Router2 is going to use it's backup static route that tells it to route packets to Router1 who will then send back to Router2 and so on until the TTL expires on the packet, as you explained in your initial post.
boson's tests are frighting me to death
Don’t let them scare you though. In my experience (and I’m sure others will agree), the Boson exams are harder than the actual Cisco exam.
i was usually failing the first attempt on 700-800 score and the second time is get better and score +900 but dunno
this is the only exam i have been so uncertain about it
If it makes you feel better, I scored less than 800 on both my Boson exams and scored a 903/1000 on my actual Cisco exam 😊
You would be better off purchasing the current version of any reading material you plan on using. At best the only things you would take away from the older versions are very foundational concepts, like OSI reference models or the structure of an IP header, etc.
I would take two or three days off and then plow through the last chapters given how close you are to finishing your studies. Keep in mind that you can always reschedule your exam if need be.
That is what I would do. I am reading Odom's book for CCNA R&S and it includes a huge wealth of information. Don't stress over failing the exam though, you'll get it next time for sure!