Hi.
I'm having an issue with utilizing vPower NFS on a VxRail env.
The VxRail hosts have by design a vmk0 with and ipv6 that can't be removed and with management service enabled on the interface.
When the vPowerNFS tries to mount the nfs datastore fails. There is no ports blocked on the env.
We reached the following KB to test it https://www.veeam.com/kb1055 and we realized that if we add the following it works:
"With new security enhancements in Veeam B&R 9.5 Update 4 it is no longer possible to mount vPower NFS datastore manually to an arbitrary server. To be able to perform this test, add vPowerNFSDisableIPAuth (DWORD) = 1 registry value to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Veeam\Veeam NFS\ and restart Veeam vPower NFS Service."
I have in mind that Veeam is doing a query to the esxi and enabling only the ipv6 IP to access the NFS Datastore.
Any clues on how to add specific ips instead of complete disabling the protection?
Regards.
-
- Service Provider
- Posts: 17
- Liked: 3 times
- Joined: May 05, 2016 3:01 am
- Full Name: Francisco Fernandez Cardarelli
- Contact:
-
- Product Manager
- Posts: 15343
- Liked: 3322 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: VxRail vPower NFS Problem
Hello,
I'm not sure whether IPv6 has anything to do with that. As of today, we ignore IPv6 completely (IPv6 support is something we plan for V12). I suggest checking with support why it really fails and which IP is used.
Best regards,
Hannes
PS: support can only help if logfiles are provided.
I'm not sure whether IPv6 has anything to do with that. As of today, we ignore IPv6 completely (IPv6 support is something we plan for V12). I suggest checking with support why it really fails and which IP is used.
Best regards,
Hannes
PS: support can only help if logfiles are provided.
-
- VP, Product Management
- Posts: 7259
- Liked: 1552 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: VxRail vPower NFS Problem
It works a bit different. We ask through vCenter that the ESXi host connects to our NFS server and try all IP addresses of the Veeam vPOWER NFS server.
What interface is used then, depends on the IP settings on the ESXi host. For example if you have an NIC in the same subnet, this interface is automatically used.
If the is no NIC in the ESXi host in the same subnet, then the default gateway is used for communication.
Overall I think, please check if the NFS service is running on the ESXi host.
Then try to PING all IP addresses of the vPOWER NFS service from the ESXi host console to check if connection is working at all.
As Hannes said, support can give you an idea based on uploaded logs.
What interface is used then, depends on the IP settings on the ESXi host. For example if you have an NIC in the same subnet, this interface is automatically used.
If the is no NIC in the ESXi host in the same subnet, then the default gateway is used for communication.
Overall I think, please check if the NFS service is running on the ESXi host.
Then try to PING all IP addresses of the vPOWER NFS service from the ESXi host console to check if connection is working at all.
As Hannes said, support can give you an idea based on uploaded logs.
-
- Service Provider
- Posts: 17
- Liked: 3 times
- Joined: May 05, 2016 3:01 am
- Full Name: Francisco Fernandez Cardarelli
- Contact:
Re: VxRail vPower NFS Problem
Hannesk, Andrea. If we enable that registry it works. Its not related to NFS Service running or not, because we only do a change on Veeam side and works. The ESXi has 2 management vmkernels ( 1 is IPV6, the other IPv4). The other vmkernels are for vSAN and vMotion (non routable networks) that do not have Management services enabled on them.
We will open a SR and upload the logs.
We will open a SR and upload the logs.
Who is online
Users browsing this forum: Google [Bot] and 12 guests