Re: [ovirt-users] Non-Operational state because management interfaces down

2014-11-23 Thread Lior Vernia
Hi Luf,

Let me have a think about it and I'll get back to you on whether there's
a workaround or something needs to be enhanced in the engine logic.
Thanks for bringing this up!

Yours, Lior.

On 20/11/14 15:11, Finstrle, Ludek wrote:
 
 Lior Vernia píše v St 19. 11. 2014 v 17:22 +0200:
 On 19/11/14 14:42, Finstrle, Ludek wrote:
  Engine has both networks (ovirtmgmt as eth0 and data as eth1).
  Internally the cluster should communicate via ovirtmgmt (installed using
  internal name for ovirtmgmt IP and this network is strictly local to the
  ovirt cluster). I'm reaching web of engine via data IP (public network
  as web is listening on all interfaces).

 So when you take node1 down and node2's management interface goes down,
 how come the engine is still able to communicate with node2? Is the
 hostname also resolved to the data IP?
 
 It's not exact description of the situation.
 
 1) both nodes up = everything is working properly
 2) second node power off
 3) first node still have interfaces up (ovirtmgmt - ens1f0 just without
 link detected) = first node is switched into Non-Operational mode
 (there should be at least some switch if I require link detected)
 4) ping is working correctly over ovirtmgmt (checked via tcpdump)
 between remaining node and hosted engine running on that node
 
 I switch back to the problematic situation and ensure I'm not saying
 misleading information (ens1f0 is network interface for ovirtmgmt):
 ovirtmgmt: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 9000
 ens1f0: flags=4099UP,BROADCAST,MULTICAST mtu 9000
 # ethtool ens1f0
 Settings for ens1f0:
 Supported ports: [ TP ]
 Supported link modes: 10baseT/Half 10baseT/Full
 100baseT/Half 100baseT/Full
 1000baseT/Full
 Supported pause frame use: No
 Supports auto-negotiation: Yes
 Advertised link modes: 10baseT/Half 10baseT/Full
 100baseT/Half 100baseT/Full
 1000baseT/Full
 Advertised pause frame use: No
 Advertised auto-negotiation: Yes
 Speed: Unknown!
 Duplex: Unknown! (255)
 Port: Twisted Pair
 PHYAD: 1
 Transceiver: internal
 Auto-negotiation: on
 MDI-X: Unknown (auto)
 Supports Wake-on: pumbg
 Wake-on: g
 Current message level: 0x0007 (7)
 drv probe link
 Link detected: no
 
 Cheers,
 
 Luf
 
  I'm sorry for worse responses as I'm on a business trip for next few
 weeks.
 
  Cheers,
 
  Luf
 
  sent from phone
 
  Dne 19. 11. 2014 9:34 Lior Vernia lver...@redhat.com napsal(a):
  Hey,
 
  Thanks, so how come node2 moves to non-operational state rather than
  non-responsive (i.e. how come it's reachable from the engine)? The IP
  address via which it was installed, belongs to which network interface?
  bond1 which is used for data?
 
  Lior.
 
  On 18/11/14 12:17, Finstrle, Ludek wrote:
 
  Hi,
 
  yes that's exactly what I tried to describe. Thanks Ekin.
  There is no switch between 2 hosts/nodes (for ovirtmgmt network). It's
  similar to situation when I tried just one host/node and put the
  ovirtmgmt network to not connected network interface (will connect it
  once we buy second host).
 
  Cheers,
 
  Luf
 
  Ekin Meroğlu píše v Út 18. 11. 2014 v 00:00 +0200:
  Hi Lior,
 
 
  If I'm not mistaken, on Luf's topology, there is no switch on the
  management bond (bond0) - just a cross or regular eth cable connecting
  physical interfaces on both nodes. So when one node is powered down,
  there is no link detected on the other node.
 
 
  Regards,
 
  On Mon, Nov 17, 2014 at 12:02 PM, Lior Vernia lver...@redhat.com
  wrote:
  Hi Luf,
 
  Apologies, I probably don't understand the details of your L2
  toplogy;
  how come when you turn off one host it affects the link state
  of of the
  other one's interfaces?...
 
  Yours, Lior.
 
  On 14/11/14 11:43, Finstrle, Ludek wrote:
  
   Hi,
  
   I have 2-node ovirt cluster. Both machines has 4
  interfaces.
   2 interfaces in bond1 for data
   2 interfaces in bond0 for management (short connected
  directly between
   servers)
  
   switch0 -\ /-\ /- switch0
   node1 node2
   switch1 -/ \-/ \- switch1
  
   I setup everything as I want/expect but I hit one problem
  and I don't
   know how to fix it. The problem is when I switch off one of
  the machines
   for maintenance (node01.ovirt in this case). I get in ovirt
  engine this
   message:
  
   Host node02.ovirt moved to Non-Operational state because
  interfaces
   which are down are needed by required networks in the
  current cluster:
   'bond0 (ovirtmgmt)'.
  
   Do you have any idea how to avoid it? I can't change
  physical
   architecture as I don't have 10Gb switch.
  
   BTW it's the same as if I want to start with only 1 node and
  separated
   data and mgmt networks:
  
   switch - host --(not connected iface for mgmt as I don't
  need it)
  
   Thanks,
  
   Luf
  
  
   NOTICE: This email and any attachments may contain
  confidential and
   proprietary information of NetSuite Inc. and is for the sole
  use of the
   intended recipient for the stated purpose. Any improper use
  or
   

Re: [ovirt-users] Non-Operational state because management interfaces down

2014-11-20 Thread Finstrle, Ludek
htmlbodyLior Vernia píše v St 19. 11. 2014 v 17:22 +0200:
 On 19/11/14 14:42, Finstrle, Ludek wrote:
  Engine has both networks (ovirtmgmt as eth0 and data as eth1).
  Internally the cluster should communicate via ovirtmgmt (installed using
  internal name for ovirtmgmt IP and this network is strictly local to the
  ovirt cluster). I'm reaching web of engine via data IP (public network
  as web is listening on all interfaces).
 
 So when you take node1 down and node2's management interface goes down,
 how come the engine is still able to communicate with node2? Is the
 hostname also resolved to the data IP?

It's not exact description of the situation.

1) both nodes up = everything is working properly
2) second node power off
3) first node still have interfaces up (ovirtmgmt - ens1f0 just without
link detected) = first node is switched into Non-Operational mode
(there should be at least some switch if I require link detected)
4) ping is working correctly over ovirtmgmt (checked via tcpdump)
between remaining node and hosted engine running on that node

I switch back to the problematic situation and ensure I'm not saying
misleading information (ens1f0 is network interface for ovirtmgmt):
ovirtmgmt: flags=4163UP,BROADCAST,RUNNING,MULTICAST  mtu 9000
ens1f0: flags=4099UP,BROADCAST,MULTICAST  mtu 9000
# ethtool ens1f0
Settings for ens1f0:
Supported ports: [ TP ]
Supported link modes:   10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
1000baseT/Full 
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
1000baseT/Full 
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: Unknown!
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x0007 (7)
   drv probe link
Link detected: no

Cheers,

Luf

  I'm sorry for worse responses as I'm on a business trip for next few weeks.
  
  Cheers,
  
  Luf
  
  sent from phone
  
  Dne 19. 11. 2014 9:34 Lior Vernia lver...@redhat.com napsal(a):
  Hey,
  
  Thanks, so how come node2 moves to non-operational state rather than
  non-responsive (i.e. how come it's reachable from the engine)? The IP
  address via which it was installed, belongs to which network interface?
  bond1 which is used for data?
  
  Lior.
  
  On 18/11/14 12:17, Finstrle, Ludek wrote:
 
  Hi,
 
  yes that's exactly what I tried to describe. Thanks Ekin.
  There is no switch between 2 hosts/nodes (for ovirtmgmt network). It's
  similar to situation when I tried just one host/node and put the
  ovirtmgmt network to not connected network interface (will connect it
  once we buy second host).
 
  Cheers,
 
  Luf
 
  Ekin Meroğlu píše v Út 18. 11. 2014 v 00:00 +0200:
  Hi Lior,
 
 
  If I'm not mistaken, on Luf's topology, there is no switch on the
  management bond (bond0) - just a cross or regular eth cable connecting
  physical interfaces on both nodes. So when one node is powered down,
  there is no link detected on the other node.
 
 
  Regards,
 
  On Mon, Nov 17, 2014 at 12:02 PM, Lior Vernia lver...@redhat.com
  wrote:
  Hi Luf,
 
  Apologies, I probably don't understand the details of your L2
  toplogy;
  how come when you turn off one host it affects the link state
  of of the
  other one's interfaces?...
 
  Yours, Lior.
 
  On 14/11/14 11:43, Finstrle, Ludek wrote:
  
   Hi,
  
   I have 2-node ovirt cluster. Both machines has 4
  interfaces.
   2 interfaces in bond1 for data
   2 interfaces in bond0 for management (short connected
  directly between
   servers)
  
   switch0 -\ /-\ /- switch0
   node1 node2
   switch1 -/ \-/ \- switch1
  
   I setup everything as I want/expect but I hit one problem
  and I don't
   know how to fix it. The problem is when I switch off one of
  the machines
   for maintenance (node01.ovirt in this case). I get in ovirt
  engine this
   message:
  
   Host node02.ovirt moved to Non-Operational state because
  interfaces
   which are down are needed by required networks in the
  current cluster:
   'bond0 (ovirtmgmt)'.
  
   Do you have any idea how to avoid it? I can't change
  physical
   architecture as I don't have 10Gb switch.
  
   BTW it's the same as if I want to start with only 1 node and
  separated
   data and mgmt networks:
  
   switch - host --(not connected iface for mgmt as I don't
  need it)
  
   Thanks,
  
   Luf
  
  
   NOTICE: This email and any attachments may contain
  confidential and
   proprietary information of NetSuite Inc. and is for the sole
  use of the
   intended recipient for 

Re: [ovirt-users] Non-Operational state because management interfaces down

2014-11-19 Thread Lior Vernia
Hey,

Thanks, so how come node2 moves to non-operational state rather than
non-responsive (i.e. how come it's reachable from the engine)? The IP
address via which it was installed, belongs to which network interface?
bond1 which is used for data?

Lior.

On 18/11/14 12:17, Finstrle, Ludek wrote:
 
 Hi,
 
 yes that's exactly what I tried to describe. Thanks Ekin.
 There is no switch between 2 hosts/nodes (for ovirtmgmt network). It's
 similar to situation when I tried just one host/node and put the
 ovirtmgmt network to not connected network interface (will connect it
 once we buy second host).
 
 Cheers,
 
 Luf
 
 Ekin Meroğlu píše v Út 18. 11. 2014 v 00:00 +0200:
 Hi Lior,


 If I'm not mistaken, on Luf's topology, there is no switch on the
 management bond (bond0) - just a cross or regular eth cable connecting
 physical interfaces on both nodes. So when one node is powered down,
 there is no link detected on the other node.


 Regards,

 On Mon, Nov 17, 2014 at 12:02 PM, Lior Vernia lver...@redhat.com
 wrote:
 Hi Luf,

 Apologies, I probably don't understand the details of your L2
 toplogy;
 how come when you turn off one host it affects the link state
 of of the
 other one's interfaces?...

 Yours, Lior.

 On 14/11/14 11:43, Finstrle, Ludek wrote:
 
  Hi,
 
  I have 2-node ovirt cluster. Both machines has 4
 interfaces.
  2 interfaces in bond1 for data
  2 interfaces in bond0 for management (short connected
 directly between
  servers)
 
  switch0 -\ /-\ /- switch0
  node1 node2
  switch1 -/ \-/ \- switch1
 
  I setup everything as I want/expect but I hit one problem
 and I don't
  know how to fix it. The problem is when I switch off one of
 the machines
  for maintenance (node01.ovirt in this case). I get in ovirt
 engine this
  message:
 
  Host node02.ovirt moved to Non-Operational state because
 interfaces
  which are down are needed by required networks in the
 current cluster:
  'bond0 (ovirtmgmt)'.
 
  Do you have any idea how to avoid it? I can't change
 physical
  architecture as I don't have 10Gb switch.
 
  BTW it's the same as if I want to start with only 1 node and
 separated
  data and mgmt networks:
 
  switch - host --(not connected iface for mgmt as I don't
 need it)
 
  Thanks,
 
  Luf
 
 
  NOTICE: This email and any attachments may contain
 confidential and
  proprietary information of NetSuite Inc. and is for the sole
 use of the
  intended recipient for the stated purpose. Any improper use
 or
  distribution is prohibited. If you are not the intended
 recipient,
  please notify the sender; do not review, copy or distribute;
 and
  promptly delete or destroy all transmitted information.
 Please note that
  all communications and information transmitted through this
 email system
  may be monitored and retained by NetSuite or its agents and
 that all
  incoming email is automatically scanned by a third party
 spam and
  filtering service which may result in deletion of a
 legitimate e-mail
  before it is read by the intended recipient.
 
 

  ___
  Users mailing list
  Users@ovirt.org mailto:Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users
 
 ___
 Users mailing list
 Users@ovirt.org mailto:Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users





 --
 Ekin Meroğlu Red Hat Certified Datacenter Specialist
 linuxera Özgür Yazılım Çözüm ve Hizmetleri
 T +90 (850) 22 LINUX GSM +90 (532) 137 77 04
 
 
 NOTICE: This email and any attachments may contain confidential and
 proprietary information of NetSuite Inc. and is for the sole use of the
 intended recipient for the stated purpose. Any improper use or
 distribution is prohibited. If you are not the intended recipient,
 please notify the sender; do not review, copy or distribute; and
 promptly delete or destroy all transmitted information. Please note that
 all communications and information transmitted through this email system
 may be monitored and retained by NetSuite or its agents and that all
 incoming email is automatically scanned by a third party spam and
 filtering service which may result in deletion of a legitimate e-mail
 before it is read by the intended recipient.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Non-Operational state because management interfaces down

2014-11-19 Thread Finstrle, Ludek
htmlbodyHi Lior,

  Engine has both networks (ovirtmgmt as eth0 and data as eth1). Internally the 
cluster should communicate via ovirtmgmt (installed using internal name for 
ovirtmgmt IP and this network is strictly local to the ovirt cluster). I'm 
reaching web of engine via data IP (public network as web is listening on all 
interfaces).

I'm sorry for worse responses as I'm on a business trip for next few weeks.

Cheers,

Luf

sent from phone

Dne 19. 11. 2014 9:34 Lior Vernia lver...@redhat.com napsal(a):
Hey,

Thanks, so how come node2 moves to non-operational state rather than
non-responsive (i.e. how come it's reachable from the engine)? The IP
address via which it was installed, belongs to which network interface?
bond1 which is used for data?

Lior.

On 18/11/14 12:17, Finstrle, Ludek wrote:

 Hi,

 yes that's exactly what I tried to describe. Thanks Ekin.
 There is no switch between 2 hosts/nodes (for ovirtmgmt network). It's
 similar to situation when I tried just one host/node and put the
 ovirtmgmt network to not connected network interface (will connect it
 once we buy second host).

 Cheers,

 Luf

 Ekin Meroğlu píše v Út 18. 11. 2014 v 00:00 +0200:
 Hi Lior,


 If I'm not mistaken, on Luf's topology, there is no switch on the
 management bond (bond0) - just a cross or regular eth cable connecting
 physical interfaces on both nodes. So when one node is powered down,
 there is no link detected on the other node.


 Regards,

 On Mon, Nov 17, 2014 at 12:02 PM, Lior Vernia lver...@redhat.com
 wrote:
 Hi Luf,

 Apologies, I probably don't understand the details of your L2
 toplogy;
 how come when you turn off one host it affects the link state
 of of the
 other one's interfaces?...

 Yours, Lior.

 On 14/11/14 11:43, Finstrle, Ludek wrote:
 
  Hi,
 
  I have 2-node ovirt cluster. Both machines has 4
 interfaces.
  2 interfaces in bond1 for data
  2 interfaces in bond0 for management (short connected
 directly between
  servers)
 
  switch0 -\ /-\ /- switch0
  node1 node2
  switch1 -/ \-/ \- switch1
 
  I setup everything as I want/expect but I hit one problem
 and I don't
  know how to fix it. The problem is when I switch off one of
 the machines
  for maintenance (node01.ovirt in this case). I get in ovirt
 engine this
  message:
 
  Host node02.ovirt moved to Non-Operational state because
 interfaces
  which are down are needed by required networks in the
 current cluster:
  'bond0 (ovirtmgmt)'.
 
  Do you have any idea how to avoid it? I can't change
 physical
  architecture as I don't have 10Gb switch.
 
  BTW it's the same as if I want to start with only 1 node and
 separated
  data and mgmt networks:
 
  switch - host --(not connected iface for mgmt as I don't
 need it)
 
  Thanks,
 
  Luf
 
 
  NOTICE: This email and any attachments may contain
 confidential and
  proprietary information of NetSuite Inc. and is for the sole
 use of the
  intended recipient for the stated purpose. Any improper use
 or
  distribution is prohibited. If you are not the intended
 recipient,
  please notify the sender; do not review, copy or distribute;
 and
  promptly delete or destroy all transmitted information.
 Please note that
  all communications and information transmitted through this
 email system
  may be monitored and retained by NetSuite or its agents and
 that all
  incoming email is automatically scanned by a third party
 spam and
  filtering service which may result in deletion of a
 legitimate e-mail
  before it is read by the intended recipient.
 
 

  ___
  Users mailing list
  Users@ovirt.org mailto:Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users
 
 ___
 Users mailing list
 Users@ovirt.org mailto:Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users





 --
 Ekin Meroğlu Red Hat Certified Datacenter Specialist
 linuxera Özgür Yazılım Çözüm ve Hizmetleri
 T +90 (850) 22 LINUX GSM +90 (532) 137 77 04


 NOTICE: This email and any attachments may contain confidential and
 proprietary information of NetSuite Inc. and is for the sole use of the
 intended recipient for the stated purpose. Any improper use or
 distribution is prohibited. If you are not the intended recipient,
 please notify the sender; do not review, copy or distribute; and
 promptly delete or destroy all transmitted information. Please note that
 all communications and information transmitted through this email system
 may be monitored and retained by NetSuite or its agents and that all
 incoming email is automatically scanned by a third party spam and
 filtering service which may result in deletion of a legitimate e-mail
 before it is read by the intended recipient.


NOTICE: This email and any attachments may contain confidential and proprietary 
information of NetSuite Inc. and is for the sole use of the intended recipient 
for the stated purpose. Any improper use or distribution is 

Re: [ovirt-users] Non-Operational state because management interfaces down

2014-11-19 Thread Lior Vernia


On 19/11/14 14:42, Finstrle, Ludek wrote:
 
 Hi Lior,
 
 Engine has both networks (ovirtmgmt as eth0 and data as eth1).
 Internally the cluster should communicate via ovirtmgmt (installed using
 internal name for ovirtmgmt IP and this network is strictly local to the
 ovirt cluster). I'm reaching web of engine via data IP (public network
 as web is listening on all interfaces).

So when you take node1 down and node2's management interface goes down,
how come the engine is still able to communicate with node2? Is the
hostname also resolved to the data IP?

 
 I'm sorry for worse responses as I'm on a business trip for next few weeks.
 
 Cheers,
 
 Luf
 
 sent from phone
 
 Dne 19. 11. 2014 9:34 Lior Vernia lver...@redhat.com napsal(a):
 Hey,
 
 Thanks, so how come node2 moves to non-operational state rather than
 non-responsive (i.e. how come it's reachable from the engine)? The IP
 address via which it was installed, belongs to which network interface?
 bond1 which is used for data?
 
 Lior.
 
 On 18/11/14 12:17, Finstrle, Ludek wrote:

 Hi,

 yes that's exactly what I tried to describe. Thanks Ekin.
 There is no switch between 2 hosts/nodes (for ovirtmgmt network). It's
 similar to situation when I tried just one host/node and put the
 ovirtmgmt network to not connected network interface (will connect it
 once we buy second host).

 Cheers,

 Luf

 Ekin Meroğlu píše v Út 18. 11. 2014 v 00:00 +0200:
 Hi Lior,


 If I'm not mistaken, on Luf's topology, there is no switch on the
 management bond (bond0) - just a cross or regular eth cable connecting
 physical interfaces on both nodes. So when one node is powered down,
 there is no link detected on the other node.


 Regards,

 On Mon, Nov 17, 2014 at 12:02 PM, Lior Vernia lver...@redhat.com
 wrote:
 Hi Luf,

 Apologies, I probably don't understand the details of your L2
 toplogy;
 how come when you turn off one host it affects the link state
 of of the
 other one's interfaces?...

 Yours, Lior.

 On 14/11/14 11:43, Finstrle, Ludek wrote:
 
  Hi,
 
  I have 2-node ovirt cluster. Both machines has 4
 interfaces.
  2 interfaces in bond1 for data
  2 interfaces in bond0 for management (short connected
 directly between
  servers)
 
  switch0 -\ /-\ /- switch0
  node1 node2
  switch1 -/ \-/ \- switch1
 
  I setup everything as I want/expect but I hit one problem
 and I don't
  know how to fix it. The problem is when I switch off one of
 the machines
  for maintenance (node01.ovirt in this case). I get in ovirt
 engine this
  message:
 
  Host node02.ovirt moved to Non-Operational state because
 interfaces
  which are down are needed by required networks in the
 current cluster:
  'bond0 (ovirtmgmt)'.
 
  Do you have any idea how to avoid it? I can't change
 physical
  architecture as I don't have 10Gb switch.
 
  BTW it's the same as if I want to start with only 1 node and
 separated
  data and mgmt networks:
 
  switch - host --(not connected iface for mgmt as I don't
 need it)
 
  Thanks,
 
  Luf
 
 
  NOTICE: This email and any attachments may contain
 confidential and
  proprietary information of NetSuite Inc. and is for the sole
 use of the
  intended recipient for the stated purpose. Any improper use
 or
  distribution is prohibited. If you are not the intended
 recipient,
  please notify the sender; do not review, copy or distribute;
 and
  promptly delete or destroy all transmitted information.
 Please note that
  all communications and information transmitted through this
 email system
  may be monitored and retained by NetSuite or its agents and
 that all
  incoming email is automatically scanned by a third party
 spam and
  filtering service which may result in deletion of a
 legitimate e-mail
  before it is read by the intended recipient.
 
 

  ___
  Users mailing list
  Users@ovirt.org mailto:Users@ovirt.org mailto:Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users
 
 ___
 Users mailing list
 Users@ovirt.org mailto:Users@ovirt.org mailto:Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users





 --
 Ekin Meroğlu Red Hat Certified Datacenter Specialist
 linuxera Özgür Yazılım Çözüm ve Hizmetleri
 T +90 (850) 22 LINUX GSM +90 (532) 137 77 04


 NOTICE: This email and any attachments may contain confidential and
 proprietary information of NetSuite Inc. and is for the sole use of the
 intended recipient for the stated purpose. Any improper use or
 distribution is prohibited. If you are not the intended recipient,
 please notify the sender; do not review, copy or distribute; and
 promptly delete or destroy all transmitted information. Please note that
 all communications and information transmitted through this email system
 may be monitored and retained by NetSuite or its agents and that all
 incoming email is automatically scanned by a third party spam and
 filtering service which may result in deletion of a 

Re: [ovirt-users] Non-Operational state because management interfaces down

2014-11-18 Thread Finstrle, Ludek
htmlbodyHi,

  yes that's exactly what I tried to describe. Thanks Ekin.
There is no switch between 2 hosts/nodes (for ovirtmgmt network). It's
similar to situation when I tried just one host/node and put the
ovirtmgmt network to not connected network interface (will connect it
once we buy second host).

Cheers,

Luf

Ekin Meroğlu píše v Út 18. 11. 2014 v 00:00 +0200:
 Hi Lior,
 
 
 If I'm not mistaken, on Luf's topology, there is no switch on the
 management bond (bond0) - just a cross or regular eth cable connecting
 physical interfaces on both nodes. So when one node is powered down,
 there is no link detected on the other node. 
 
 
 Regards,
 
 On Mon, Nov 17, 2014 at 12:02 PM, Lior Vernia lver...@redhat.com
 wrote:
 Hi Luf,
 
 Apologies, I probably don't understand the details of your L2
 toplogy;
 how come when you turn off one host it affects the link state
 of of the
 other one's interfaces?...
 
 Yours, Lior.
 
 On 14/11/14 11:43, Finstrle, Ludek wrote:
 
  Hi,
 
  I have 2-node ovirt cluster. Both machines has 4
 interfaces.
  2 interfaces in bond1 for data
  2 interfaces in bond0 for management (short connected
 directly between
  servers)
 
  switch0 -\ /-\ /- switch0
  node1 node2
  switch1 -/ \-/ \- switch1
 
  I setup everything as I want/expect but I hit one problem
 and I don't
  know how to fix it. The problem is when I switch off one of
 the machines
  for maintenance (node01.ovirt in this case). I get in ovirt
 engine this
  message:
 
  Host node02.ovirt moved to Non-Operational state because
 interfaces
  which are down are needed by required networks in the
 current cluster:
  'bond0 (ovirtmgmt)'.
 
  Do you have any idea how to avoid it? I can't change
 physical
  architecture as I don't have 10Gb switch.
 
  BTW it's the same as if I want to start with only 1 node and
 separated
  data and mgmt networks:
 
  switch - host --(not connected iface for mgmt as I don't
 need it)
 
  Thanks,
 
  Luf
 
 
  NOTICE: This email and any attachments may contain
 confidential and
  proprietary information of NetSuite Inc. and is for the sole
 use of the
  intended recipient for the stated purpose. Any improper use
 or
  distribution is prohibited. If you are not the intended
 recipient,
  please notify the sender; do not review, copy or distribute;
 and
  promptly delete or destroy all transmitted information.
 Please note that
  all communications and information transmitted through this
 email system
  may be monitored and retained by NetSuite or its agents and
 that all
  incoming email is automatically scanned by a third party
 spam and
  filtering service which may result in deletion of a
 legitimate e-mail
  before it is read by the intended recipient.
 
 
 
  ___
  Users mailing list
  Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users
 
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
 
 
 
 
 
 -- 
 Ekin Meroğlu Red Hat Certified Datacenter Specialist
 linuxera Özgür Yazılım Çözüm ve Hizmetleri
 T +90 (850) 22 LINUX GSM +90 (532) 137 77 04


NOTICE: This email and any attachments may contain confidential and proprietary 
information of NetSuite Inc. and is for the sole use of the intended recipient 
for the stated purpose. Any improper use or distribution is prohibited. If you 
are not the intended recipient, please notify the sender; do not review, copy 
or distribute; and promptly delete or destroy all transmitted information. 
Please note that all communications and information transmitted through this 
email system may be monitored by NetSuite or its agents and that all incoming 
email is automatically scanned by a third party spam and filtering service

/body/html
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Non-Operational state because management interfaces down

2014-11-17 Thread Lior Vernia
Hi Luf,

Apologies, I probably don't understand the details of your L2 toplogy;
how come when you turn off one host it affects the link state of of the
other one's interfaces?...

Yours, Lior.

On 14/11/14 11:43, Finstrle, Ludek wrote:
 
 Hi,
 
 I have 2-node ovirt cluster. Both machines has 4 interfaces.
 2 interfaces in bond1 for data
 2 interfaces in bond0 for management (short connected directly between
 servers)
 
 switch0 -\ /-\ /- switch0
 node1 node2
 switch1 -/ \-/ \- switch1
 
 I setup everything as I want/expect but I hit one problem and I don't
 know how to fix it. The problem is when I switch off one of the machines
 for maintenance (node01.ovirt in this case). I get in ovirt engine this
 message:
 
 Host node02.ovirt moved to Non-Operational state because interfaces
 which are down are needed by required networks in the current cluster:
 'bond0 (ovirtmgmt)'.
 
 Do you have any idea how to avoid it? I can't change physical
 architecture as I don't have 10Gb switch.
 
 BTW it's the same as if I want to start with only 1 node and separated
 data and mgmt networks:
 
 switch - host --(not connected iface for mgmt as I don't need it)
 
 Thanks,
 
 Luf
 
 
 NOTICE: This email and any attachments may contain confidential and
 proprietary information of NetSuite Inc. and is for the sole use of the
 intended recipient for the stated purpose. Any improper use or
 distribution is prohibited. If you are not the intended recipient,
 please notify the sender; do not review, copy or distribute; and
 promptly delete or destroy all transmitted information. Please note that
 all communications and information transmitted through this email system
 may be monitored and retained by NetSuite or its agents and that all
 incoming email is automatically scanned by a third party spam and
 filtering service which may result in deletion of a legitimate e-mail
 before it is read by the intended recipient.
 
 
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Non-Operational state because management interfaces down

2014-11-17 Thread Ekin Meroğlu
Hi Lior,

If I'm not mistaken, on Luf's topology, there is no switch on the
management bond (bond0) - just a cross or regular eth cable connecting
physical interfaces on both nodes. So when one node is powered down, there
is no link detected on the other node.

Regards,

On Mon, Nov 17, 2014 at 12:02 PM, Lior Vernia lver...@redhat.com wrote:

 Hi Luf,

 Apologies, I probably don't understand the details of your L2 toplogy;
 how come when you turn off one host it affects the link state of of the
 other one's interfaces?...

 Yours, Lior.

 On 14/11/14 11:43, Finstrle, Ludek wrote:
 
  Hi,
 
  I have 2-node ovirt cluster. Both machines has 4 interfaces.
  2 interfaces in bond1 for data
  2 interfaces in bond0 for management (short connected directly between
  servers)
 
  switch0 -\ /-\ /- switch0
  node1 node2
  switch1 -/ \-/ \- switch1
 
  I setup everything as I want/expect but I hit one problem and I don't
  know how to fix it. The problem is when I switch off one of the machines
  for maintenance (node01.ovirt in this case). I get in ovirt engine this
  message:
 
  Host node02.ovirt moved to Non-Operational state because interfaces
  which are down are needed by required networks in the current cluster:
  'bond0 (ovirtmgmt)'.
 
  Do you have any idea how to avoid it? I can't change physical
  architecture as I don't have 10Gb switch.
 
  BTW it's the same as if I want to start with only 1 node and separated
  data and mgmt networks:
 
  switch - host --(not connected iface for mgmt as I don't need it)
 
  Thanks,
 
  Luf
 
 
  NOTICE: This email and any attachments may contain confidential and
  proprietary information of NetSuite Inc. and is for the sole use of the
  intended recipient for the stated purpose. Any improper use or
  distribution is prohibited. If you are not the intended recipient,
  please notify the sender; do not review, copy or distribute; and
  promptly delete or destroy all transmitted information. Please note that
  all communications and information transmitted through this email system
  may be monitored and retained by NetSuite or its agents and that all
  incoming email is automatically scanned by a third party spam and
  filtering service which may result in deletion of a legitimate e-mail
  before it is read by the intended recipient.
 
 
  ___
  Users mailing list
  Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users
 
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users




-- 
Ekin Meroğlu *Red Hat Certified Datacenter Specialist*
*linuxera* Özgür Yazılım Çözüm ve Hizmetleri
*T* +90 (850) 22 LINUX *GSM* +90 (532) 137 77 04
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Non-Operational state because management interfaces down

2014-11-14 Thread Finstrle, Ludek
htmlbodyHi,

  I have 2-node ovirt cluster. Both machines has 4 interfaces.
2 interfaces in bond1 for data
2 interfaces in bond0 for management (short connected directly between
servers)

switch0 -\   /-\   /- switch0
 node1 node2
switch1 -/   \-/   \- switch1

I setup everything as I want/expect but I hit one problem and I don't
know how to fix it. The problem is when I switch off one of the machines
for maintenance (node01.ovirt in this case). I get in ovirt engine this
message:

Host node02.ovirt moved to Non-Operational state because interfaces
which are down are needed by required networks in the current cluster:
'bond0 (ovirtmgmt)'.

Do you have any idea how to avoid it? I can't change physical
architecture as I don't have 10Gb switch.

BTW it's the same as if I want to start with only 1 node and separated
data and mgmt networks:

switch - host --(not connected iface for mgmt as I don't need it)

Thanks,

Luf


NOTICE: This email and any attachments may contain confidential and proprietary 
information of NetSuite Inc. and is for the sole use of the intended recipient 
for the stated purpose. Any improper use or distribution is prohibited. If you 
are not the intended recipient, please notify the sender; do not review, copy 
or distribute; and promptly delete or destroy all transmitted information. 
Please note that all communications and information transmitted through this 
email system may be monitored by NetSuite or its agents and that all incoming 
email is automatically scanned by a third party spam and filtering service

/body/html
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Non-Operational state because management interfaces down

2014-11-14 Thread Demeter Tibor
Hi, 

Did you set your bond devices and IP addresses via ovirt's network management, 
or by hand on the nodes? 

In my experiences you need to set up ip addresses on the node's network 
interface via ovirt' management, because it won't working. 

Tibor 

- Eredeti üzenet -

 Hi,

 I have 2-node ovirt cluster. Both machines has 4 interfaces.
 2 interfaces in bond1 for data
 2 interfaces in bond0 for management (short connected directly between
 servers)

 switch0 -\ /-\ /- switch0
 node1 node2
 switch1 -/ \-/ \- switch1

 I setup everything as I want/expect but I hit one problem and I don't
 know how to fix it. The problem is when I switch off one of the machines
 for maintenance (node01.ovirt in this case). I get in ovirt engine this
 message:

 Host node02.ovirt moved to Non-Operational state because interfaces
 which are down are needed by required networks in the current cluster:
 'bond0 (ovirtmgmt)'.

 Do you have any idea how to avoid it? I can't change physical
 architecture as I don't have 10Gb switch.

 BTW it's the same as if I want to start with only 1 node and separated
 data and mgmt networks:

 switch - host --(not connected iface for mgmt as I don't need it)

 Thanks,

 Luf

 NOTICE: This email and any attachments may contain confidential and
 proprietary information of NetSuite Inc. and is for the sole use of the
 intended recipient for the stated purpose. Any improper use or distribution
 is prohibited. If you are not the intended recipient, please notify the
 sender; do not review, copy or distribute; and promptly delete or destroy
 all transmitted information. Please note that all communications and
 information transmitted through this email system may be monitored and
 retained by NetSuite or its agents and that all incoming email is
 automatically scanned by a third party spam and filtering service which may
 result in deletion of a legitimate e-mail before it is read by the intended
 recipient.
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Non-Operational state because management interfaces down

2014-11-14 Thread Finstrle, Ludek
htmlbodyHi,

  I setup it via oVirt. The problem is that there is no link detected on
the real interfaces for management (ovirtmgmt is UP but NO-CARRIER). If
I add another interface (with link detected) to the bond (temporarily as
I need it for backup) it's working properly.

Cheers,

Luf

Demeter Tibor píše v Pá 14. 11. 2014 v 12:42 +0100:
 Hi,
 
 
 Did you set your bond devices and IP addresses via ovirt's network
 management, or by hand on the nodes?
 
 
 In my experiences you need to set up ip addresses on the node's
 network interface via ovirt' management, because it won't working.
 
 
 
 
 
 
 Tibor
 
 
 
 
 
 __
 
 Hi,
 
 I have 2-node ovirt cluster. Both machines has 4 interfaces.
 2 interfaces in bond1 for data
 2 interfaces in bond0 for management (short connected directly
 between
 servers)
 
 switch0 -\ /-\ /- switch0
 node1 node2
 switch1 -/ \-/ \- switch1
 
 I setup everything as I want/expect but I hit one problem and
 I don't
 know how to fix it. The problem is when I switch off one of
 the machines
 for maintenance (node01.ovirt in this case). I get in ovirt
 engine this
 message:
 
 Host node02.ovirt moved to Non-Operational state because
 interfaces
 which are down are needed by required networks in the current
 cluster:
 'bond0 (ovirtmgmt)'.
 
 Do you have any idea how to avoid it? I can't change physical
 architecture as I don't have 10Gb switch.
 
 BTW it's the same as if I want to start with only 1 node and
 separated
 data and mgmt networks:
 
 switch - host --(not connected iface for mgmt as I don't
 need it)
 
 Thanks,
 
 Luf
 
 
 NOTICE: This email and any attachments may contain
 confidential and proprietary information of NetSuite Inc. and
 is for the sole use of the intended recipient for the stated
 purpose. Any improper use or distribution is prohibited. If
 you are not the intended recipient, please notify the sender;
 do not review, copy or distribute; and promptly delete or
 destroy all transmitted information. Please note that all
 communications and information transmitted through this email
 system may be monitored and retained by NetSuite or its agents
 and that all incoming email is automatically scanned by a
 third party spam and filtering service which may result in
 deletion of a legitimate e-mail before it is read by the
 intended recipient.
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
 
 


NOTICE: This email and any attachments may contain confidential and proprietary 
information of NetSuite Inc. and is for the sole use of the intended recipient 
for the stated purpose. Any improper use or distribution is prohibited. If you 
are not the intended recipient, please notify the sender; do not review, copy 
or distribute; and promptly delete or destroy all transmitted information. 
Please note that all communications and information transmitted through this 
email system may be monitored by NetSuite or its agents and that all incoming 
email is automatically scanned by a third party spam and filtering service

/body/html
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users