After the cloud desktop infrastructure VM is deployed and all node components are installed, the local PC cannot ping the service plane but can ping the management plane of the vLB/vAG node. Each node and the PC can communicate with each other.
In the network environment, the management plane network segment of the system is 10.144.11.0/25, belonging to VLAN 412, the service plane network segment is 10.144.11.128/25, belonging VLAN 413, and the gateways are 10.144.11.1 and 10.144.11.129. My local PC is configured with 10.144.11.90/25.
1. Check the connectivity of each node. It is found that the connectivity is normal and the PC can ping the management plane of the vLB/vAG node. The filtering policy of the firewall is correct.
2. Log in to the vLB/vAG VM and run the ip route command to check the routing table. The routing table shows that the source address of the data packet destined for the network segment 10.144.11.128/25 is 10.144.11.144, and that for the network segment 10.144.11.0/25 is 10.144.11.33. As a result, the destination address and source address of the ping packets sent and received by the PC are different.
To solve this problem, you can use either of the following methods:
1. Log in to the vLB/vAG VM and write the static route route add –host 10.144.11.90 dev eth0 gw 10.144.11.129. This command becomes invalid after the VM restarts.
2. Configure the PC to any other network segment address.
This problem is not caused by incorrect configuration of the VM. You need to pay attention to this problem. Otherwise, the login page of the cloud desktop cannot be displayed. You are advised to solve the problem using method 1, verify the cloud desktop function, and restart the VM to delete the static route. This avoids unnecessary troubles for customer networks.