snapcreator does not like nfs mountpoints over IPv6 [ Edited ]

[#1]

Hello,

Excerpt of the config file:

NTAP_USERS=nas2:root/foo;[2001:67c:168:100::176]:root/foo

MANAGEMENT_INTERFACES=[2001:67c:168:100::176]:nas2

* Debug of the run

[Tue Jun 12 23:14:07 2012] DEBUG: Parsing NTAP_USERS - controller: nas2 user: root

[Tue Jun 12 23:14:07 2012] DEBUG: Parsing NTAP_USERS - controller: [2001 user: 67c

Obviously not what I meant

Regards

jm

[#2]

Hi JM,

Does it work if you you simply have hostnames in NTAP_USERS, no IPs? Also forget about MANAGEMENT_INTERFACES for now.

The issue with [2001:67c:168:100::176] is we use ":" as a separator in our parsing so this will never work, but I want to understand if that is only issue? Please also give us examples of IPV6 you want to use?

If we understand all the issues SC has with IPV6 I can assure you they will be addressed in future versions, IPV6 is very key and important to us.

Regards,

Keith

[#3]

Hello Keith,

Thanks for the quick reply.

It works with a static entry in the /etc/hosts file (NFS mountpoints are in a private VLAN => no DNS entries).

On the linux box:

* /etc/fstab looks like this:

#[2001:67c:168:100::176]:/vol/nfs_wiki/mysql    /var/lib/mysql    nfs4 rw,bg,hard,noatime,nointr,timeo=600 0 0  (does not work with snapcreator)

nas2-nfs-ipv6:/vol/nfs_wiki/mysql    /var/lib/mysql    nfs4 rw,bg,hard,noatime,nointr,timeo=600 0 0

* /etc/hosts looks like:

# snapcreator

2001:67c:168:100::176   nas2-nfs-ipv6

> The issue with [2001:67c:168:100::176] is we use ":" as a separator in our parsing so this will never work

Mmh, if you look at your brower this kind of stuff, it will parse the following input correctly:

http://www-kame.net/

http://203.178.141.194/

http://[2001:200:dff:fff1:216:3eff:feb1:44d7]/

mount can also parse /etc/fstab with IPv4/IPv6 addresses. So it is a problem that has been solved already many times :-)

You have to modify your parser/regexp to accomodate IPv6 addresses inside []. (ok, easier said than done ;-)

So it works this the workaround (static entry in /etc/hosts)

Regards,

Jean-Marc

[#4]

Yep work around is use /etc/hosts until we get this bug fixed.

I totally agree this is an SC issue and we need to do more testing on IPV6 with IPV6 IP address schemes.

I am however encouraged to hear workaround works and thank you for helping make SC better. In case you are in SC developer community, www.snapcreator.com, here is the bug for this so you can track progress:

https://github.com/NetApp/SC-Framework/issues/608

Regards,

Keith

[#5]

To be honest, NFSv4 over IPv6 is rather exotic setup ATM..., but it's working.

Thanks

jm