Second, try not to switch to use DNS server to resolve the host name which is what this means, when we switch in the debug time will inevitably lose the wrong order, such as typing a letter more or 642-812 less typed a letter, would have thought that the switch prompted the order wrong, but this time something strange has happened, the system is not prompt us to order errors, but their was a connection (is this the same command executed), as follows: 3550 # beijing. In other words, Cisco switches to that input the wrong command for the host name, and try to query the DNS server to resolve it. If you then set the DNS server on the switch, the progress will be faster, if there is no DNS server, it can be called a slow pace, how to avoid this situation? Can type the following command: 3550 # conf t. Complete the implementation of the above command, type the command when an error occurs again, when, Cisco switches do not do unnecessary long connected. Third, rapid understanding of the switch port off the situation as a network administrator, we switch on a new service access when the switch is always first to find Cisco above a free port, its operational configuration necessary , and finally the network cable connected, but will switch more cables above the case. With the naked eye it's hard to put accurate identification of free port out (If accidentally pulled out the wrong, may cause network failure), so we had all to log on to the switch, use the appropriate command to view, order as follows: 3550 # show inter. This time the switch will in turn show the details of each port, including the port off the situation, but this way is much slower.350-001

exambible