Describes how to configure a Cisco switch port.

Cisco switches are currently the main force in the Exchange industry, and their products are doing very well in the market. Here we mainly analyze some usage skills of Cisco switches. As a network manager, it is inevitable to debug switches frequently. The core backbone switches in Xiangzi are mainly Cisco switches.

In the process of debugging and maintaining Cisco switches, Xiangzi may encounter some headaches. Fortunately, after a period of system learning, these problems have been solved one by one. In fact, understanding these methods is very helpful for improving the efficiency of debugging vswitches. Here, we will introduce some accumulated experiences for your reference.

I believe many network administrators and friends have encountered this problem: when debugging a Cisco switch through the CONSOLE port connected to the switch through a serial port (except for the first time configuring the switch, most of them are due to switch faults and cannot be logged on through the network port ).

At this time, it is often 100,000 in a rush, but the more urgent it is, the more difficult it is to make a command than to log on to the sky, because the configuration interface opened by the super terminal will be from time to time (or non-stop) some system prompts are displayed. At this time, the command input will be completely disrupted.

That is to say, you cannot enter a complete string of commands in one line. At that time, it was a test of the psychological quality of the network administrator and the keyboard-based fingering method. It can be described by typing commands with your eyes closed, after the command is completed, it is expected that the error will be eliminated and so many error messages will not be displayed (of course, it will not succeed in ). In fact, there is a way to deal with these constantly changing information. When we log on through the CONSOLE port, we only need to type 3550 # conf t.

In this way, you can effectively avoid the interference caused by commands repeatedly popped up by console messages when you enter commands. In fact, logon through the network port is also affected by system information, but this situation does not appear in the Cisco switch by default.

But it can be implemented with only one command, namely: 3550 # terminal monitor. In order to experience the actual effect, we can open two DOS windows on our microcomputer and log on to the same Cisco switch via TELNET, one for monitoring.

In addition, perform the following operations: for example, we can execute one port shutdown and then no shutdown, in this case, the system information is disturbed when you want to enter the command in the first window, as shown in the following figure: 3550 (config )#.

In fact, I want to type inter fa0/4, but this command is drowned in the system prompt information. If you want to solve the problem, just type the following command: 3550 # conf t; Enter configuration commands, one per line. End with CNTL/Z. TELNET logon and CONSOLE logon. If you want to prevent the input command from being disturbed by the prompt information of the switch, you can solve the problem in the same way.

What does this mean? When debugging a switch, we will inevitably enter an incorrect command, for example, if we type one more letter or one less letter, I thought the switch would prompt this command error, but a strange thing happened at this time. The system didn't prompt us for a command error, but made a connection to it (that is, the command was executed the same ), 3550 # beijing.

That is to say, the Cisco switch considers the incorrect command as the host name and tries to resolve it by querying the DNS server. If the DNS server is set on the switch, the progress will be faster. If there is no DNS server, the progress will be slow. How can we avoid this situation? Enter the following command: 3550 # conf t. After the preceding commands are executed, when an incorrect command is entered, the Cisco switch will not perform unnecessary connections for a long time.

As a network administrator, when we access a new service on a vswitch, we always need to find an idle port on the Cisco switch and configure necessary services, connect the network cable, but there are many cables on the switch.

With the naked eye, it is difficult to accurately identify idle ports at once (if an error is accidentally pulled, the Network may fail). Therefore, we used to log on to the switch, run the following command: 3550 # show inter. At this time, the switch will display the details of each port in sequence, including the port disconnection, but it is still too slow.

1. Let's talk about the "potential rules" of the security switch"
2. Summarize the market status of high-end Switches
3. Security risks of LAN switches
4. PythonAndroid analyzes the differences and relationships between layer-3 switches and other layer Switches
5. Measure the Power Consumption Characteristics of LAN switches.