`<div dir="ltr">It does, i got another email from another member directly that explained the issue as well, i however did have my router in there and another active DNS controller and yet it still happened... The other guy recommended to get around this eaiser to put the esxi host names in the /etc/hosts file to ensure that dns was ok....<div><br></div><div>Funny part is i didnt think it would be DNS as my hosts were using IPs to connect not DNS names.. My Resolv.conf had the following info and even tho .15 and .1 were both online as soon as i lost .14 it lost connectivity... so i think theres still something wonky with the NFS protocol as it shouldnt have lost connection consistently... it would go up and down like it was always trying to hit 14 first and lost connection then found 15 then reconnected... then rechecked at 14 then lost it....</div><div><br></div><div>192.168.30.14 - DC1</div><div>192.168.30.15 - DC2</div><div>192.168.30.1 - Router</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 26, 2016 at 4:08 PM, Aaron Curry <span dir="ltr"><<a href="mailto:asc1111@gmail.com" target="_blank">asc1111@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">I had a similar problem. Turned out to be a DNS issue. Our DNS was running on the DC. When the DC was down, NFS wouldn't work. All I had to do was add our router as a nameserver in resolv.conf and it started working again. It seemed to be that as long as OmniOS has someone responding to DNS requests NFS will work, even if the DNS has no local info.</p>
<p dir="ltr">Hope that helps.</p><span class="HOEnZb"><font color="#888888">
<p dir="ltr">Aaron</p>
</font></span><div class="gmail_quote"><div><div class="h5">On Oct 25, 2016 1:13 PM, "Matt Mabis" <<a href="mailto:dasaint.blair@gmail.com" target="_blank">dasaint.blair@gmail.com</a>> wrote:<br type="attribution"></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Hey All,<div><br></div><div>Was wondering if you could help me out, using b13298F but i have seen this in other versions too where i joined the Omni to the Domain so i could use ACLs and UserID Mappings for SMB. however when i reboot one of the 2 DCs i have it looks like it loses all access to the NFS Shares till that DC Comes back online.</div><div><br></div><div>From my troubleshooting i have figured out it has something to do with Kerberos and NFS together if the System cannot talk to Kerberos NFS Drops the connections (Even though i am doing Root @ IP Range) based ESXi Mappings for NFS v3 I believe Kerberos and NFS are intertwined in some sense cause even though i can ping the IP its like i just get inherently denied access when that DC Is down... </div><div><br></div><div>Trying to make sure if i have to take these DC's down for updates/patches/maintenance they arent going to take down my entire NFS structure... </div><div><br></div><div>Any Help would be appreciated.</div><div><br></div><div><br></div><div>KRB5.CONF File</div><div>See Data *Changed domain name to DOMAIN.LOCAL* but all other information is correct 192.168.30.14 is DC1 and 192.168.30.15 is DC2.. (When i power down DC1 is when i start loosing connection)</div><div><br></div><div><br></div><div><div>#</div><div># CDDL HEADER START</div><div>#</div><div># The contents of this file are subject to the terms of the</div><div># Common Development and Distribution License (the "License").</div><div># You may not use this file except in compliance with the License.</div><div>#</div><div># You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE</div><div># or <a href="http://www.opensolaris.org/os/licensing" target="_blank">http://www.opensolaris.org/os/<wbr>licensing</a>.</div><div># See the License for the specific language governing permissions</div><div># and limitations under the License.</div><div>#</div><div># When distributing Covered Code, include this CDDL HEADER in each</div><div># file and include the License file at usr/src/OPENSOLARIS.LICENSE.</div><div># If applicable, add the following below this CDDL HEADER, with the</div><div># fields enclosed by brackets "[]" replaced with your own identifying</div><div># information: Portions Copyright [yyyy] [name of copyright owner]</div><div>#</div><div># CDDL HEADER END</div><div>#</div><div># </div><div># Copyright 2007 Sun Microsystems, Inc. All rights reserved.</div><div># Use is subject to license terms.</div><div>#</div><div># ident → "%Z%%M% → %I% → %E% SMI"</div><div>#</div><div><br></div><div># krb5.conf template</div><div># In order to complete this configuration file</div><div># you will need to replace the __<name>__ placeholders</div><div># with appropriate values for your network and uncomment the</div><div># appropriate entries.</div><div>#</div><div>[libdefaults]</div><div> default_realm = DOMAIN.LOCAL</div><div><br></div><div><br></div><div>[realms]</div><div> DOMAIN.LOCAL = {</div><div> kdc = 192.168.30.14</div><div> kdc = 192.168.30.15</div><div> admin_server = 192.168.30.15</div><div> kpasswd_server = 192.168.30.15</div><div> kpasswd_protocol = SET_CHANGE</div><div> }</div><div><br></div><div>[domain_realm]</div><div> .domain.local = DOMAIN.LOCAL</div><div><br></div><div>[logging]</div><div> default = FILE:/var/krb5/kdc.log</div><div> kdc = FILE:/var/krb5/kdc.log</div><div> → kdc_rotate = {</div><div><br></div><div># How often to rotate kdc.log. Logs will get rotated no more</div><div># often than the period, and less often if the KDC is not used</div><div># frequently.</div><div><br></div><div> → → period = 1d</div><div><br></div><div># how many versions of kdc.log to keep around (kdc.log.0, kdc.log.1, ...)</div><div><br></div><div> → → versions = 10</div><div> → }</div><div><br></div><div>[appdefaults]</div><div> → kinit = {</div><div> → → renewable = true</div><div> → → forwardable= true</div><div> → }</div></div></div>
<br></div></div><span class="">______________________________<wbr>_________________<br>
OmniOS-discuss mailing list<br>
<a href="mailto:OmniOS-discuss@lists.omniti.com" target="_blank">OmniOS-discuss@lists.omniti.co<wbr>m</a><br>
<a href="http://lists.omniti.com/mailman/listinfo/omnios-discuss" rel="noreferrer" target="_blank">http://lists.omniti.com/mailma<wbr>n/listinfo/omnios-discuss</a><br>
<br></span></blockquote></div>
</blockquote></div><br></div>
`