Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Disabling IPv6

avatar
Rising Star

In a recent Predictive Cluster Validation Summary for one of my clusters, Cloudera Proactive Support states:

 

"The following hosts have IPv6 enabled, which is against our best practices, because it can cause connectivity problems. This is discussed in the CDH documentation. (http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cdh_ig_req_supported_ve..."

 

Yet that page simply says that "IPv6 is not supported and must be disabled."

 

If this is a hard requirement, then why is there no documentation on *how* to disable IPv6 for the various supported OSs?  I understand that Cloudera may not want to get into the OS configuration business, but at least pointers to vender documentation should be provided.

 

1 ACCEPTED SOLUTION

avatar
Expert Contributor
hide-solution

This problem has been solved!

Want to get a detailed solution you have to login/registered on the community

Register/Login
10 REPLIES 10

avatar
Master Guru

Hello @mjarnold,

 

Thank you for pointing that out.  I have added this post to internal Cloudera Jira DOCS-1862 where we are discussing documentation.

 

Regards,

 

Ben

avatar
Expert Contributor

Thank you Ben.

avatar
Rising Star

Hey @bgooley,

 

Is there any update on DOCS-1862?

avatar
Expert Contributor
hide-solution

This problem has been solved!

Want to get a detailed solution you have to login/registered on the community

Register/Login

avatar
Rising Star

@Alex,

 

I am curious as to what the Proactive Support tests look for when testing whether IPv6 is enabled.  Is it the existence of IPv6 addresses on interfaces or the presence of the IPv6 kernel module?

 

Red Hat's solutions indicate that you can either disable the kernel module via kernel boot options (results in other things breaking) or disable IPv6 on network interfaces via sysctl.  Debian appears to be similar.

 

avatar
Expert Contributor

Hi Michael,

 

Based on what I see in the script/code, it's the presence of inet6 in the ifconfig output, which is included in the diagnostic bundle. If inet6 is present and in use, I believe that's the basis for the alert that was issued.

 

Best,

Alex

avatar
Rising Star

Thanks.  It sounds like the following should suffice:

 

sysctl -w net.ipv6.conf.all.disable_ipv6=1

sysctl -w net.ipv6.conf.default.disable_ipv6=1

 

avatar
Expert Contributor

Completely agreed sir. +1