Compare cert salaries and plan your next career move
jeanathan wrote: » Many have said before and I shall repeat them now. GNS3. Poor, no matter, GNS3 allows the poorest of the poor to build labs in excess of 20000 usd and gain invaluable experience configuring and troubleshooting networks with cisco equipment.
teksource1984 wrote: » Guys, I will probably pass and have my CCNA certification towards the end of spring this year. However, I have no experience with Cisco routers or the CLI. How can I get some experience working with Cisco Switches, Routers, CLI etc.
tim100 wrote: » some experience
never be equivalent to experience on actual equipment
Packet Tracer
jeanathan wrote: » Semantics. GNS3 is software, where by hardware specifications, task, and rommon configuration can be found online and in CCNA books.
tim100 wrote: » Simulators will only get you so far. Some things will work perfect in GNS3 whereas the same configuration will break on actual routers. Some errors that real routers will report in debugging information won't be produced in GNS3 which will make it look like the configuration is perfectly fine and if you happen to come across something like that in the real world then you won't know where to start troubleshooting. The list goes on and on...
jeanathan wrote: » Wouldn't you agree that for a large MPLS lab or a large 10 router mixed OSPF, BGP, and EIGRP lab that GNS3 is a life saver? Of course for the CCIE labs I would prefer a rack rental because GNS3 is not perfect, which again takes some of the physical element out of the loop.
MentholMoose wrote: » If someone can't cope and doesn't "know where to start troubleshooting" with a config not working in production that works in test, I doubt it matters if test is Packet Tracer or a $20K lab environment.
tim100 wrote: » Who said anything about a configuration not working in production that works in a test environment? I'm talking about differences between a simulator and actual equipment.
tim100 wrote: » Some errors that real routers will report in debugging information won't be produced in GNS3 which will make it look like the configuration is perfectly fine and if you happen to come across something like that in the real world then you won't know where to start troubleshooting.
MentholMoose wrote: » i.e. it fails in real routers (production), but works fine in GNS3 (test).
tim100 wrote: » You have misread. "Some errors that real routers will report in debugging information won't be produced in GNS3" meaning you will see the output in real routers whereas you won't see the output in GNS3 so you will then think your configuration on GNS3 is a perfectly working configuration but in reality it is not.
MentholMoose wrote: » I equated and error with a failure
tim100 wrote: » Errors don't necessarily have to be failures. If that were the case then network problems would be quite easy to pinpoint and troubleshoot and debugging would be futile.
Compare salaries for top cybersecurity certifications. Free download for TechExams community.