Long story short, I've been working on my new lab at home off and on. Tonight I was working on my lab to get to the point where I would have OVMM as a virtual machine as the dedicated host I have for temporary measures only has two gigs of ram vs the recommended 8 gigs of ram.
More to the point: I was working on the storage portion of my setup and I got my iSCSI target discovered (FreeNAS 9.3) and I was able to build my cluster of OVSs. I noticed earlier that my FreeNAS server had some pending updates and I figured it would be a good idea to perform these updates before I started using the iSCSI storage for active virtual machines. Naturally, when the updates are done on my FreeNAS server, it reboots.
What I don't understand is why both of my OVSs restarted at the same time after the FreeNAS server went down for a reboot. Was there a hidden gotcha? Did I overlook something in the documentation?
A side effect of the unexpected reboot is the fact that my OVS(2) did not come back online with OVMM and I could not ping my management interface for that OVS. I did several Google searches and tried some manual up/downs of the interfaces and tried one effort to manually configure bond0 to an IP address to try and get some sort of response. Needless to say, none of those were good ideas and didn't help. Therefore, I'm re-installing OVS on server 2 now.
If anyone has any ideas as to how I could have fixed OVS(2) I'm more than willing to take notes in case this happens again.
Thank you for any and all help,
Brendan
P.S. If this has any influence with my situation, I am running LACP bonds and all IP addresses are configured on the VLAN interfaces. I have not had any issues configuring my switch and with the exception of OVS(2) not wanting to reply after the unexpected restart I had everything working. An added gotcha is that the storage VLAN interface on OVS(2) continued to reply after the restart.