Since the use of GNS3, it is not how to use Packet Tracer, today took packet tracer to do a terminal access to the server experiment, feel packet tracer more powerful than we think, it seems to be a good study ah.
Let's start by introducing what is Cisco's Terminal server. When we do experiments with more than one switch or router, it is very inconvenient to unplug the console line often. The terminal access server is a router with 8 or 16 asynchronous interfaces, connected to multiple routers or the console port of the switch using a eight-claw fish cable. We only need to log in to the terminal access server, and then we can easily access each router or switch.
Here is an experimental topology diagram:
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/6C/AE/wKiom1VQB42ScsYlAACD0H0RdyE355.jpg "title=" 2.JPG " alt= "Wkiom1vqb42scsylaacd0h0rdye355.jpg"/>
The terminal in the figure is the terminal access server we need to configure, and the green cable is the last "octal" line of the "cable" type, which is the eight-claw fish line. This cable was added after the packet Tracer6.0, so students who use the previous version of 6.0 can't do this experiment. In the topology, we can easily access other devices simply by configuring the terminal. 2811 is no asynchronous module, we build a topology, the first thing to do is to install the asynchronous module for terminal, is the hwic-8a, as to how to install the module on the packet Tracer device is not necessary I said:
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/6C/AE/wKiom1VQCoGCLwK2AAJOLVTW2bk187.jpg "title=" 1.JPG " alt= "Wkiom1vqcogclwk2aajolvtw2bk187.jpg"/>
After the topology is set up, it is the configuration of the terminal. Here is the configuration process:
router# conf t
Router (config) # no IP domain-lookup
Router (config) # host Terminal
Router (config) # no IP routing//Turn off routing function, use router as server
Terminal (config) # line vty 0 15//Configure vty lines for remote login from PC1 to Terminal
Terminal (config-line) # no login//Configure password-free login
Terminal (config-line) # no EXEC//Set no timeout exit
Terminal (config-line) # Logg SYN//sync prompt to prevent interference with our configuration commands
Terminal (config-line) # exit
Terminal (config) # enable secret 123456//configure privileged mode password, must be configured Oh, otherwise telnet into the privileged mode
Terminal (config) # int F 0/0
Terminal (config-if) # IP Add 192.168.1.1 255.255.255.0
Terminal (config-if) # no shutdown
Terminal (config-if) # exit
Terminal (config) # int loopback 0
Terminal (config-if) # IP Add 1.1.1.1 255.255.255.255//Note This mask is 32 OH
Terminal (config-if) # exit
Terminal (config) # exit
The play is coming--
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/6C/AC/wKioL1VQNBvT5tZ0AAO3CapY77s657.jpg "title=" 4.JPG " alt= "Wkiol1vqnbvt5tz0aao3capy77s657.jpg"/>
This is my show line, remember Typ is TTY line, they are 50 to 57, we configure these line:
Terminal (config) # line TTY 50 57
Terminal (config-line) # no EXEC
Terminal (config-line) # Logg SYN
Terminal (config-line) # no Login
Terminal (config-line) # Transport input All//allow all protocols to be transferred, but only allow Telnet
Terminal (config-line) # exit
Configuration here is actually able to access the connection, we use the following command to log in:
terminal# Telnet 1.1.1.1 2050//2050 is the port number, here's 50 that's our line
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/6C/AC/wKioL1VQPemSU-1ZAABB8JzstWI621.jpg "title=" 5.JPG " alt= "Wkiol1vqpemsu-1zaabb8jzstwi621.jpg"/>
We saw that the login was successful. But use this command every time you log in, and remember that the device that corresponds to the port number is cumbersome. Don't worry, we can use the Host table feature to simplify the login command:
Terminal (config) # IP host R1 2050 1.1.1.1
Terminal (config) # IP host S1 2051 1.1.1.1
Terminal (config) # IP host S2 2052 1.1.1.1
Once configured, we will be able to log in directly using the host name:
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/6C/B2/wKiom1VQPnaSdKiyAAAsM9w3_94758.jpg "title=" 6.JPG " alt= "Wkiom1vqpnasdkiyaaasm9w3_94758.jpg"/>
In this step, the terminal access server is configured. After we log in R1, if want to return terminal, need to use the combination key ctrl+shift+6 (also write ctrl+^), and then type "x" key, can exit. But I found that after returning the terminal, if you hit "Enter" key, and then return to R1,
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/6C/B2/wKioL1VQcu6SYDSpAABNtz0J0cg757.jpg "title=" 7.JPG " alt= "Wkiol1vqcu6sydspaabntz0j0cg757.jpg"/>
In this case, after we return the terminal, we can use the following command to end the session:
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/6C/B2/wKioL1VQc9ahf-CRAAC64mDfwr8822.jpg "title=" 8.JPG " alt= "Wkiol1vqc9ahf-craac64mdfwr8822.jpg"/>
If you remember the port number where the line is located, you can also end the session with the following command:
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/6C/B7/wKiom1VQczCB9QfmAACB07i79A0661.jpg "title=" 9.JPG " alt= "Wkiom1vqczcb9qfmaacb07i79a0661.jpg"/>
We try to access it from PC1, and the effect is the same:
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/6C/B8/wKiom1VQdOTgbVfzAAH3KzdmeE8538.jpg "title=" 10.JPG "alt=" Wkiom1vqdotgbvfzaah3kzdmee8538.jpg "/>
However, using the Packet tracer command prompt, I found another problem, that is, after logging in R1, you cannot use ctrl+shift+6, and then type "X" key to return to terminal in this way. It seems Packer Tracer still have a lot to be perfected.
Write here, the configuration of the terminal access server is done. Because I am also a beginner, writing these things is also to give themselves a summary of learning, so inevitably there is a wrong place, welcome to correct me.
This article is from the "industrious Little ant" blog, please make sure to keep this source http://qlxmy.blog.51cto.com/8016580/1650343
Packet Tacer doing Cisco Terminal Access server experiments