We are implementing NFS storage as a transfer datastore and for ISO, templates, etc. We have 2 datacenters with low latency link between them. Our NFS Storage exists in one datacenter.
DC-1 (ESXi Hosts and NFS Storage)
DC-2 (ESXi Hosts)
I'm having issues with DC-2 NFS configuration. I have a seperate network and VMKernel defined for NFS traffic. I assume I need to define a static route for this NFS traffic so it isn't pushed out the default gateway. Anyone have familiar with the approriate way to configure additional static routes for routable NFS traffic.
Sure, like this:
~ # esxcli network ip route ipv4 add -n 192.168.100.0/24 -g 192.168.1.1
In this example, we've created a static route for the 192.168.100.0/24 subnet with next hop 192.168.1.1.
Thanks for the reply. After the first one, I'm hoping this is a configuration that can be picked up and applied via Host profile.
Yes, a host profile is able to pick this up. Specifically under: Networking -> Netstack Instance -> defaultTcpipStack -> ApplyProfile -> IP route config.
I'll play with this a little more but the Host profile is not remediating this correctly. When I manually make the change and update the profile it picks up the new route just like your image. When I check compliance, it does show non-compliant with "Number of IPv4 routes do not match" however, applying that profile to another Host does not result in the inclusion of this missing route in the list of configuration changes to be applied to the Host. It is the same with both the Web and C# clients. I am using vSphere 5.5.
I'll see if I can reproduce this, will let you know.
I'm running the 5.5 U1 version in my lab (build-1623387) and did not have this issue. If I add a route on a host, update the reference profile and remediate the non-compliant host, it get's the route pushed down by the HP.
Before the remedation:
~ # esxcli network ip route ipv4 list
Network Netmask Gateway Interface Source
------------- ------------- ------------- --------- ------
default 0.0.0.0 192.168.1.254 vmk0 DHCP
192.168.1.0 255.255.255.0 0.0.0.0 vmk0 MANUAL
192.168.100.0 255.255.255.0 192.168.1.1 vmk0 MANUAL
And after:
~ # esxcli network ip route ipv4 list
Network Netmask Gateway Interface Source
------------- ------------- ------------- --------- ------
default 0.0.0.0 192.168.1.254 vmk0 DHCP
192.168.1.0 255.255.255.0 0.0.0.0 vmk0 MANUAL
192.168.100.0 255.255.255.0 192.168.1.1 vmk0 MANUAL
192.168.101.0 255.255.255.0 192.168.1.1 vmk0 MANUAL
This was a rather simple HP though. Are you running U1 also?
Appreciate the assist and good to know. I will need to update my lab to U1 and try again to verify it isn't a pre-U1 bug. It may take a bit but, I'll report results here for those interested.