2015-06-12 09:49 AM
I perform transition consulting for NetApp.
If you are running 8.2.3 or 8.3, UDP is used by default if the lookup results are less than 512 bytes. See this excerpt from the Name Services Best Practices TR-4379:
In the clustered Data ONTAP 8.2.3 operating system, UDP support for DNS was added for hostname
lookups. Both UDP and TCP can be used for DNS lookups in 8.2.3 and later. UDP will be used for
smaller lookups, while TCP will be used if the UDP response is truncated because of the size of the
skynet::> system image show -iscurrent true -fields version node image version --------- ------ ------- skynet-01 image2 8.3 skynet-02 image2 8.3 2 entries were displayed. skynet::> nfs server show -vserver hadrian_skyvs1 -fields name-service-lookup-protocol vserver name-service-lookup-protocol -------------- ---------------------------- hadrian_skyvs1 udp skynet::>
Enjoy! If this helped out, please hit the Kudos button and mark as Answered.
2015-06-12 11:03 AM
We happened to be runing 8.2.1. So, what do i need to do on the storage, in order to use UDP?
The provided command doesn't work on this cluster:
Error: invalid argument "name-service-lookup-protocol"
Looking forward to hear you again.
2015-06-12 11:36 AM - edited 2015-06-12 11:40 AM
Perform the upgrade to 8.2.3P3 and it will be turned on by default and is not tunable, so the command still won't return.
See the 8.2.3 download page and read the Upgrade Guide and run an upgrade advisor: http://mysupport.netapp.com/NOW/download/software/ontap/8.2.3/
In 8.3, that command becomes available in order to let you force TCP instead of UDP for lookup results under 512 bytes.
If this helped out, please hit the Kudos button and accept as Answered.
2015-06-12 11:38 AM - edited 2015-06-12 11:39 AM
OK. Then anything we could do now for this issue on 8.2.1P1? You know, upgrading is not something we could do immediately.
2015-06-12 11:43 AM
Until your Data ONTAP upgrade window is available, take a read through section 5.3 on TR-4379 for workarounds to ensure better performance when dealing with huge amounts of TCP DNS traffic.