OK, thanks, Simon. That makes sense, after brushing up on STP again, I
configured a root switch where it should be, and hopefully that would
have solved the problem.
So, in Cloudstack, VMs will just shut down if storage is cut off?
On 2017-03-18 4:00 PM, Simon Weller wrote:
What I'm saying is that if your root bridge changed, it would cause all ports
(potentially on both switches) to go into blocking and then learning mode. If
that happened, it would have killed all of your storage.
________________________________
From: Asai <[email protected]>
Sent: Saturday, March 18, 2017 10:53 AM
To: [email protected]
Subject: RE: 1 Pod Host Offline, All VMs Shut Down
Thanks, Simon. But I still don't understand why the VMs that are on host 1 and
connected to PS 1 would be affected by a disconnect of another host and storage
that they're not dependent on. Will setting up the root switch for STP handle
that issue?
On March 17, 2017 6:10:05 PM MST, Simon Weller <[email protected]> wrote:
If no network storage path was available, more than likely fencing
would occur.
Simon Weller/615-312-6068
-----Original Message-----
From: Asai [[email protected]]
Received: Friday, 17 Mar 2017, 7:40PM
To: [email protected] [[email protected]]
Subject: RE: 1 Pod Host Offline, All VMs Shut Down
Ok, but why would all the VMs shut down? Is that an expected behavior?
On March 17, 2017 5:15:46 PM MST, Simon Weller <[email protected]> wrote:
So check your switch logs. It's possible all your switch ports went
into blocking mode when you lost the interswitch fiber patch.
Simon Weller/615-312-6068
-----Original Message-----
From: Asai [[email protected]]
Received: Friday, 17 Mar 2017, 6:56PM
To: [email protected] [[email protected]]
Subject: RE: 1 Pod Host Offline, All VMs Shut Down
Haven't configured that... [facepalm]
On March 17, 2017 4:46:24 PM MST, Simon Weller <[email protected]>
wrote:
Which switch is root bridge for spanning tree?
Simon Weller/615-312-6068
-----Original Message-----
From: Asai [[email protected]]
Received: Friday, 17 Mar 2017, 6:29PM
To: [email protected] [[email protected]]
Subject: Re: 1 Pod Host Offline, All VMs Shut Down
Yes, the cable was a fiber cable connecting two switches, one which
connects host 1 and PS 1 (NFS share running on host 1), and the other
switch connects host 2 and PS 2 (NFS share running on host 2).
On 2017-03-17 4:04 PM, Simon Weller wrote:
So was this cable connecting a couple of switches together? I'm
confused when you say a single cable was connecting 4 devices, unless
there is a switch or multiple switches involved. Is the primary
storage
NFS?
Simon Weller/615-312-6068
-----Original Message-----
From: Asai [[email protected]]
Received: Friday, 17 Mar 2017, 6:00PM
To: [email protected] [[email protected]]
Subject: Re: 1 Pod Host Offline, All VMs Shut Down
KVM, and the damaged cable connected host 2 and PS 2 back to the
host
1
and PS 1. Does that give you enough info to work with?
On 2017-03-17 3:55 PM, Simon Weller wrote:
What hypervisor are you using and what did the damaged cable
connect?
Simon Weller/615-312-6068
-----Original Message-----
From: Asai [[email protected]]
Received: Friday, 17 Mar 2017, 5:45PM
To: [email protected] [[email protected]]
Subject: 1 Pod Host Offline, All VMs Shut Down
Greetings,
I have 2 hosts in a pod, and 3 primary storage shares. I just ran
into
an issue where a cable accidentally got damaged which took host 2
offline and primary storage 2 offline, but ALL of my VMs shut down
spontaneously. Weird, because only half of my VMs are running on
host 2
and primary storage 2. Even the VMs on host 1 and primary storage
1
shut down. Can anyone shed light on why this would have happened
and
how I can avoid this in the future?
Much thanks,
Asai
--
Asai
--
Asai
--
Asai
