Slow upload ESXi 5.0
-
@KOM:
You could try using vmx NICs instead of the E1000's and see if that makes any difference. I don't know if ESXi that old properly supports FreeBSD 10.1. Any reason you're not at least on 5.5U3?
This has been running with no downtime since I set it up.
-
@KOM:
You could try using vmx NICs instead of the E1000's and see if that makes any difference. I don't know if ESXi that old properly supports FreeBSD 10.1. Any reason you're not at least on 5.5U3?
FWIW I am running several pfSense 2.2.4 on ESXi 4.1.0 in CARP setup with other boxes on ESXi 5.5U3, all with E1000 interfaces. Works like a charm.
-
freebsd 10.1 is not supported on that esxi version - your on your own.. I can tell you I have no speed issues running esxi 6u1a and 2.2.4 using e1000
There have been other threads where odd stuff is happening, they updated esxi to current and weirdness went away.. Why anyone would be running outdated esxi is beyond me.. Not like its not freaking free to update.. Especially when vm os they are wanting to run is not even supported by vmware on that version..
Why do you have your mtu setup in esxi to 1400?
-
freebsd 10.1 is not supported on that esxi version - your on your own.. I can tell you I have no speed issues running esxi 6u1a and 2.2.4 using e1000
There have been other threads where odd stuff is happening, they updated esxi to current and weirdness went away.. Why anyone would be running outdated esxi is beyond me.. Not like its not freaking free to update.. Especially when vm os they are wanting to run is not even supported by vmware on that version..
Why do you have your mtu setup in esxi to 1400?
Maybe I did not make it clear but there has been no issue or opportunity to upgrade. This has been deployed since 2011. What's more is this is NOT a new install or issue. Because of the way we used the circuit it never came about.
-
Why do you have your mtu setup in esxi to 1400?
-
@KOM:
Why do you have your mtu setup in esxi to 1400?
Sorry, answered it in my head only. This is the max i was told by my ISP. So there was no mismatch, everything is set to this.
-
sorry but 2.2.4 could not not have been installed since 2011 ;) Back when you installed freebsd was not 10.1 and supported by your version of esxi… If your going to want too update your VMs OS running on you esxi host, then your going to have to keep esxi updated to support the newer OS versions.
As to everything set to mtu 1400.. For what possible reason?? What isp are you on an connection type where you would have a 1400 mtu???
If you want to run an unsupported configuration - good luck..
-
sorry but 2.2.4 could not not have been installed since 2011 ;) Back when you installed freebsd was not 10.1 and supported by your version of esxi… If your going to want too update your VMs OS running on you esxi host, then your going to have to keep esxi updated to support the newer OS versions.
As to everything set to mtu 1400.. For what possible reason?? What isp are you on an connection type where you would have a 1400 mtu???
If you want to run an unsupported configuration - good luck..
You are not really reading what I wrote. Thanks for your help. Enjoy.
-
sorry but 2.2.4 could not not have been installed since 2011
I suspect he means that he's been running various versions of pfSense since 2011 on his ESXi host, and he can't|didn't upgrade the host only. Perhaps his problem didn't surface until 2.2.4, but I'm only guessing.
-
@KOM:
sorry but 2.2.4 could not not have been installed since 2011
I suspect he means that he's been running various versions of pfSense since 2011 on his ESXi host, and he can't|didn't upgrade the host only. Perhaps his problem didn't surface until 2.2.4, but I'm only guessing.
Thank you for clarifying. That is correct. I am not sure when the problem actually arose.
-
Exactly and now your running non supported configuration so either go back to version of pfsense that is supported on your esxi version, or update esxi to support pfsense version your running.