An Analysis of vswitch port congestion fault

An Analysis of the Application of HIS in case of switch port congestion to greatly improve the efficiency of hospital work. With the development of hospital services, HIS is growing and more problematic. This article introduces the analysis and handling process of a switch fault. A workstation A at www.2cto.com reports an error after the client program has entered the data. After restarting, you cannot log on to the network. Because only one line is reserved, workstation A and B connect to the second-level switch through the HUB. Based on the actual situation, the following measures are taken: ping the wks A point and the wks B point are connected to eliminate faults between the HUB and A and B points; ping the server and other wks are disconnected, redo the crystal head at both ends of the network cable between the HUB and the switch, and the fault persists. Use the tester to measure the network cable of the HUB switch, and the line is smooth. So the problem is locked on the switch, other workstations connected to the vswitch can work normally. The problem is resolved to the port of the vswitch, and the switch port lights connected to the HUB are not on. Is this port closed or congested? We know that the port status on a vswitch is divided into five types: Off, blocking, listening, learning, and forwarding. The first four statuses do not receive user data. Because the port of the switch is full and there is no remaining port to replace, you can only suspend a workstation C from using the computer, and then connect the network cable connected to the HUB to the switch port used by C, A and B can work normally. Now you can determine that the port of the switch connected to the HUB is faulty. Because the switch cannot be restarted during working hours, you can only temporarily Add A HUB extension port to solve the problem. After the rest time, connect the-point network cable to the original port. After the switch is powered off, it restarts. Five minutes later, the problem port will shine normally, and the communication will be normal. The problem is solved. We know that a switch is equivalent to a computer. After receiving the data packet, the processing port will look for the MAC address table in the memory to determine the port on which the target MAC Nic is mounted; the data packet is directly transmitted to the target node through the internal switching matrix. If the target MAC does not exist, it is broadcast to all ports. There are many reasons for the blockage of the switch port, such as the Bridge Protocol Data Unit (BPDU) error, port configuration error, DHCP rate limit, GBIC fault of the Light interface, protocol channel error, circuit generation, broadcast storm, etc. Www.2cto.com analyzes the cause of this fault: to minimize the use of the HUB in the M network, but due to insufficient reserved lines during construction, the HUB has to be used to expand the port; some NICs often fail during 10/100 M Adaptive Communication and can work normally if they are reduced to 10 M in full duplex mode. Through Sniffer data analysis, a large amount of broadcast data is found in the network. Based on the previous situation, it can be inferred that a local broadcast storm between the switch, HUB and computer blocks a port of the switch. After the switch is restarted, the port can be restored to the initial state. Finally, the fault diagnosis sequence in daily work is: the user notifies the network center after the network performance is degraded. The Network Administrator starts to diagnose the fault from the faulty access point. This method is completely passive. The ideal method is to use proactive and proactive monitoring to regularly query each switch, monitor the traffic and traffic trends of each switch port, and detect other related network segments, early detection of abnormal data and prevention of faults. Independent blog from Wangwang