When starting GNS3 we have an empty working space. This is the topology that we will use, as shown in the CCNA4 curriculum lab manual. When you have a router set up and configured with an IDLE PC value that doesn’t consume all your processor cycles, continue building the topology in GNS3, as follows. Also remember to add a WIC-2T card to the router, or make sure it has two serial interfaces. Read the “Creating the Simplest Topology” section of the PDF linked above to learn how to accomplish that. The first thing you should do is following the documentation of GNS3, to set up a router with an IOS image, and set it’s IDLE PC value. PuTTY (or the telnet client of your choice on the OS you run).GNS3 (the all-in-one Windows installer including Dynamips, Pemu and WinPCAP if under Windows).I will try to give a decent how-to styled instruction how to accomplish this using GNS3 (under Windows since that’s what this box runs at the moment). But, in many cases to play with certain protocols or functions, emulating the hardware works as good, or better, if you don’t have a decent rack with hardware in your home.
The strong point of Packet Tracer is it’s design mode, basically one can build larger topologies, and atleast look at them, and simulate basic network functionality, but if one wants to learn to configure and handle real equipment, using real equipment is the only way. It does have one strong point, and it is CPU and memory usage, compared to emulating router hardware, which this article will be mainly about. Cisco’s Packet Tracer works for very basic labs, but it has so many irritating small things that are missing, that it causes more frustration than nice experiences if doing anything involving anything more than the absoulte basic configurations.
0 kommentar(er)
