Did someone happen, by some unlucky chance...<div><br></div><div>modify the network connections with Filerview or System Manager?</div><div><br></div><div>I know there have been many bugs, most of which blow away the</div>

<div>network configs in the /etc/rc file....</div><div><br></div><div>Recommend to modify /etc/rc network info via text editor...</div><div><br></div><div>I have had more than a customer have his filer reboot and not come up</div>

<div>on the network only to find out....the network config was blown out by filerview.</div><div><br></div><div><br></div><div>Other than that...were release notes read? Not looking at that specific release,</div><div>I know at some point NetApp changed some details with the way they </div>

<div>reference VIFs and specified a certain order of things for the /etc/rc file.</div><div><br clear="all">--tmac<br>         Tim McCarthy<br>     Principal Consultant<br><br>  RedHat Certified Engineer<br>   804006984323821 (RHEL4)<br>

   805007643429572 (RHEL5)<br>
<br><br><div class="gmail_quote">On Mon, Oct 22, 2012 at 5:21 PM, Randy Rue <span dir="ltr">&lt;<a href="mailto:rrue@fhcrc.org" target="_blank">rrue@fhcrc.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Hello All,<br>
<br>
We just had a rough night trying to upgrade a 3020 from 7.2.4 to 7.3.7<br>
where the upgraded node came up with no working network connections. Turns<br>
out the same setup / RC file that works great in 7.2.4 crumps in 7.3.7.<br>
After some flailing, we used revert_to to roll back. In the mean time, our<br>
VMware farm had several hundred VMs suffer a ~1 hour loss of their disks<br>
and ~40 VMs needed help ranging from just a reboot to a full rollback of<br>
the disk image.<br>
<br>
This Sunday we&#39;re scheduled to upgrade a v3170 pair that supports about<br>
three times as many VMs and uses the same network design. We have some<br>
reasons to hope that the same issue won&#39;t bite us, and also have better<br>
options to test before we have to risk the virtual farm, and some other<br>
ideas on how to mitigate risk and impact. But it was also suggested that<br>
an even better way to avoid a problem would be if we could upgrade a node<br>
and then test the RC file before it was actually &quot;given back.&quot;<br>
<br>
If I do a takeover from Node B, then upgrade Node A, is there a way to<br>
bring up Node A far enough to test that its RC file loaded successfully<br>
but before it tries to go back into production?<br>
<br>
Hope to hear from you,<br>
<br>
Randy<br>
<br>
_______________________________________________<br>
Toasters mailing list<br>
<a href="mailto:Toasters@teaparty.net">Toasters@teaparty.net</a><br>
<a href="http://www.teaparty.net/mailman/listinfo/toasters" target="_blank">http://www.teaparty.net/mailman/listinfo/toasters</a><br>
</blockquote></div><br></div>