Low bandwidth on Virtual IP address
-
Hello,
In our network we have VMware ESXI Servers, and the Virtual machines are backed up daily to Backup server. Until the last week ESXI Servers and Backup server were in the same network (192.168.2.0/24).
This week, I created Virtual IP address as IP Alias in Virtual IPs (172.16.100.1/24) in LAN interface where 192.168.2.0/24 is located and changed the ip addresses of ESXi Servers from 192.168.2.0/24 to 172.16.100.0/24. But now backups are transferred in low bandwidth to Backup Server (192.168.2.103).Just in case, I created a virtual machine and ip address and noticed that files are also transferred in low bandwidth between my computer and the server. I also tested internet speed which is high almost 95mbits. How can I solve this issue?
-
So you moved the ESXi sever into a different subnet from the backup server?
When they were in the same subnet the traffic between them would have gone directly, limited only by the speed of those two hosts.
With them now in different subnets that traffic has to be routed and firewalled, presumably through pfSense. So it's dependent on the pfSense throughput.
It's also probably in and out of the same interface which further limits it.Steve
-
This post is deleted! -
Thank you for your reply. ESXI servers and backup server at the same interface in pfSense which is 1GB Ethernet port, but on different subnets. For example: ESXI server ip address: 172.16.100.2, but Backup server ip address: 192.168.2.103.
172.16.100.0/24 is Virtual ip address as an IP Alias.
If I add a secondary ip address to Backup Server (172.16.100.10), then backups and files are transferred in high speed.
How can I solve this problem? Please help. -
Use the dual-home backup server if that's what you need. Make sure it cannot route between them though.
If routing between those subnets is restricting the throughput then look into where that is. pfSense maxing out the CPU?
You should be using different interfaces for the subnets, VLANs at least but preferably two NICs so you are not seeing throughput killed by the ACK traffic.
Steve
