[vSphere failure case] case 7: data Center Virtualization Network failure

[vSphere failure case]

Case 7: data Center Virtualization Network failure

PS: actually, this is supposed to be a network failure, but the network of ESXi hosts is also affected. Let's share the study with the title (* ^ _ ^ *). There is no need to be serious about O (∩ _ ∩) O ~.

Time of occurrence: 2012-10-23

Hardware: switch

Impact: company-wide

Failure phenomenon: the core exchange of the company is down, the virtual network is out of connection with the outside, and each business network segment can not communicate.

The cause of the failure: the core switch automatically restarts when it is down, and the virtualized network configuration is lost.

Solution recommendations: network line backup redundancy, multi-link binding.

Handling the failure process (method): after the company core exchange goes down, the ESXi host in the virtualized environment cannot communicate with the outside world. Report the situation to the network engineer to solve the network failure. (this is a network failure, the whole company can not connect to the network, and the network engineer is also in a hurry ~ o (╯□╰) o.) after solving the network failure, it is found that some virtual machines in the ESXi host are connected to the outside, but some virtual machines are still unable to communicate. At this time, let the network engineer check on the switch, and finally find that the virtual network configuration on the core switch is lost, and then reconfigure one side.