1:20 a.m.
Hello,
I have a newly created datacenter in 3.2.1 with f18 host where
ovirtmgmt is set as vlan.
host is installed but after some minutes I get this messages:
Host management02 moved to Non-Operational state because interfaces
'em1.311' are down but are needed by networks 'ovirtmgmt' in the
current cluster
from an operating system point of view it seems that all is ok on the host
[root@management02 ~]# ip addr list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:15:17:b4:99:3c brd ff:ff:ff:ff:ff:ff
3: em2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:15:17:b4:99:3d brd ff:ff:ff:ff:ff:ff
inet 213.205.41.202/26 brd 213.205.41.255 scope global em2
4: em1.311@em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue master ovirtmgmt state UP
link/ether 00:15:17:b4:99:3c brd ff:ff:ff:ff:ff:ff
5: ovirtmgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether 00:15:17:b4:99:3c brd ff:ff:ff:ff:ff:ff
inet 10.39.71.12/26 brd 10.39.71.63 scope global ovirtmgmt
7: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
link/ether 36:98:c3:39:5f:43 brd ff:ff:ff:ff:ff:ff
8: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
9: bond4: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
10: bond1: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
11: bond2: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
12: bond3: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
[root@management02 ~]# ethtool em1
Settings for em1:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
[root@management02 ~]# ethtool em1.311
Settings for em1.311:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Link detected: yes
On engine
[root@management01 ~]# ip addr list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:15:17:b1:1f:e8 brd ff:ff:ff:ff:ff:ff
3: em2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:15:17:b1:1f:e9 brd ff:ff:ff:ff:ff:ff
inet 213.205.41.201/26 brd 213.205.41.255 scope global em2
4: em1.192@em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue state UP
link/ether 00:15:17:b1:1f:e8 brd ff:ff:ff:ff:ff:ff
inet 192.168.230.1/24 brd 192.168.230.255 scope global em1.192
5: em1.311@em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue state UP
link/ether 00:15:17:b1:1f:e8 brd ff:ff:ff:ff:ff:ff
inet 10.39.71.11/26 brd 10.39.71.63 scope global em1.311
[root@management01 ~]# ethtool em1
Settings for em1:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
[root@management01 ~]# ethtool em1.311
Settings for em1.311:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Link detected: yes
what can be the cause?
what is the check that runs and move the host to non-operational?
Thanks
Gianluca
6:14 a.m.
On 04/11/2013 06:20 AM, Gianluca Cecchi wrote:
Hello,
I have a newly created datacenter in 3.2.1 with f18 host where
ovirtmgmt is set as vlan.
host is installed but after some minutes I get this messages:
Host management02 moved to Non-Operational state because interfaces
'em1.311' are down but are needed by networks 'ovirtmgmt' in the
current cluster
What does 'vdsClient -s 0 getVdsStats' say on vdsm host?
Could you
please paste the whole line of 'network = {xxx}' in the output here?
Thanks!
from an operating system point of view it seems that all is ok on the host
[root@management02 ~]# ip addr list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:15:17:b4:99:3c brd ff:ff:ff:ff:ff:ff
3: em2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:15:17:b4:99:3d brd ff:ff:ff:ff:ff:ff
inet 213.205.41.202/26 brd 213.205.41.255 scope global em2
4: em1.311@em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue master ovirtmgmt state UP
link/ether 00:15:17:b4:99:3c brd ff:ff:ff:ff:ff:ff
5: ovirtmgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether 00:15:17:b4:99:3c brd ff:ff:ff:ff:ff:ff
inet 10.39.71.12/26 brd 10.39.71.63 scope global ovirtmgmt
7: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
link/ether 36:98:c3:39:5f:43 brd ff:ff:ff:ff:ff:ff
8: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
9: bond4: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
10: bond1: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
11: bond2: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
12: bond3: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
[root@management02 ~]# ethtool em1
Settings for em1:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
[root@management02 ~]# ethtool em1.311
Settings for em1.311:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Link detected: yes
On engine
[root@management01 ~]# ip addr list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:15:17:b1:1f:e8 brd ff:ff:ff:ff:ff:ff
3: em2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:15:17:b1:1f:e9 brd ff:ff:ff:ff:ff:ff
inet 213.205.41.201/26 brd 213.205.41.255 scope global em2
4: em1.192@em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue state UP
link/ether 00:15:17:b1:1f:e8 brd ff:ff:ff:ff:ff:ff
inet 192.168.230.1/24 brd 192.168.230.255 scope global em1.192
5: em1.311@em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue state UP
link/ether 00:15:17:b1:1f:e8 brd ff:ff:ff:ff:ff:ff
inet 10.39.71.11/26 brd 10.39.71.63 scope global em1.311
[root@management01 ~]# ethtool em1
Settings for em1:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
[root@management01 ~]# ethtool em1.311
Settings for em1.311:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Link detected: yes
what can be the cause?
what is the check that runs and move the host to non-operational?
Thanks
Gianluca
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
1:15 p.m.
On Thu, Apr 11, 2013 at 5:14 AM, Mark Wu wrote:
On 04/11/2013 06:20 AM, Gianluca Cecchi wrote:
>
> Hello,
> I have a newly created datacenter in 3.2.1 with f18 host where
> ovirtmgmt is set as vlan.
> host is installed but after some minutes I get this messages:
>
> Host management02 moved to Non-Operational state because interfaces
> 'em1.311' are down but are needed by networks 'ovirtmgmt' in the
> current cluster
What does 'vdsClient -s 0 getVdsStats' say on vdsm host? Could you please
paste the whole line of 'network = {xxx}' in the output here?
Thanks!
Thanks for your input Mark.
At the moment all is well again with the host; anyway I'm going to
give a long explanation of what I did below and so possible reasons
for that situation.
There is also feed for developers answers in that ...
I cannot connect at the moment to the host to cut and paste in text
but I have access to java console and here is a screenshot containing
the line you requested (captured now that all is ok and host up and
runnign with two VMs):
https://docs.google.com/file/d/0BwoPbcrMv8mvdmdIMUxTRVRVUzg/edit?usp=sharing
Which fields are expected to be indicators of problems, as I had yesterday?
The story:
oVirt is 3.2.1
- create a datacenter of type local_on_host
- create a cluster
- the ovirtmgmt is intended to be vlan tagged but I forget it... damn...
- I add a host (f18) where I prepared network configured with vlan
ifcfg-em1
ifcfg-em1.311
- the host deploy completes successfully --> here in my opinion a
possible bug because ovirtmgmt is not tagged?
- host reboots and apparently all is ok
- I can create local_on_host SD and ISO
- all is up and running without any VM yet
The host is a blade inside an IMS enclosure and I discover that
actually I can configure the storage assigned (second disk of the
blade) as FC and that there is also multipath for this kind of servers
(see the other thread of mine).
The optimal would be to deactivate all and redefine the DC as
Fibrechannel type but it seems not so easy....
I probably make an error at this point because instead of directly
putting host into maintenance I follow these steps in the gui:
- expand my DC at the left
- expand STORAGE of that DC on the left
- select my storage domain (LSTORAGE) on the left
On the right pane I select the line of LSTORAGE and in the bottom
pane I select the "datacenter" label where I then select the line of
my DC.
I choose "maintenance"
--> what is it supposed I have done this way?
Put storage domain in maintenance or DC or what?
Is it supposed to be a correct operation what I've done if the DC is
Up and this is the only SD I have?
Or would it be correct to receive an error from the system?
Because I don't receive any error and I see the SD down and host that
keeps staying with the status "Preparing to maintenance"
I don't remember correctly my steps here, possibly restart of host
that is recognized then as unassigned.
After that I cannot "force remove" the DC and I cannot remove the
cluster or host because it is not in maintenance.
After I also reboot the engine service and restart the host, it comes
up normally with all the DC with the old config.
At this point I can put host in maintenance and force remove the DC
I create a new DC with same name but with type FC and ovirtmgmt as
vlan tagged and I see that the existing cluster is still present, so I
attach it to the new DC (that has the same name as before).
I also find that there is my host that seems to automatically be in
this cluster.
But at this point when I activate it, it comes up but after a few
minutes I get the message I posted at the beginning
In host details, its network interfaces keep down.
Tried different restarts of host.
So I decide to put host into maintenance and select into the gui to
"reinstall" it.
After this all goes well again..
Sorry for the long story
Gianluca
8:47 a.m.
On 04/11/2013 01:15 PM, Gianluca Cecchi wrote:
On Thu, Apr 11, 2013 at 5:14 AM, Mark Wu wrote:
> On 04/11/2013 06:20 AM, Gianluca Cecchi wrote:
>>
>> Hello,
>> I have a newly created datacenter in 3.2.1 with f18 host where
>> ovirtmgmt is set as vlan.
>> host is installed but after some minutes I get this messages:
>>
>> Host management02 moved to Non-Operational state because interfaces
>> 'em1.311' are down but are needed by networks 'ovirtmgmt' in the
>> current cluster
>
> What does 'vdsClient -s 0 getVdsStats' say on vdsm host? Could you please
> paste the whole line of 'network = {xxx}' in the output here?
> Thanks!
Thanks for your input Mark.
At the moment all is well again with the host; anyway I'm going to
give a long explanation of what I did below and so possible reasons
for that situation.
There is also feed for developers answers in that ...
I cannot connect at the moment to the host to cut and paste in text
but I have access to java console and here is a screenshot containing
the line you requested (captured now that all is ok and host up and
runnign with two VMs):
https://docs.google.com/file/d/0BwoPbcrMv8mvdmdIMUxTRVRVUzg/edit?usp=sharing
Which fields are expected to be indicators of problems, as I had yesterday?
The story:
oVirt is 3.2.1
- create a datacenter of type local_on_host
- create a cluster
- the ovirtmgmt is intended to be vlan tagged but I forget it... damn...
- I add a host (f18) where I prepared network configured with vlan
ifcfg-em1
ifcfg-em1.311
I wasn't able to see any of the vlan nics in the output of the
getVdsStats. Perhaps you took that output in a different point of time
when the network was working properly, without configuring the vlan on
the host?
Once you'll be capable to connect to the host when the error appears in
the event log, please provide also the output of the getVdsCaps.
- the host deploy completes successfully --> here in my opinion a
possible bug because ovirtmgmt is not tagged?
- host reboots and apparently all is ok
- I can create local_on_host SD and ISO
- all is up and running without any VM yet
The host is a blade inside an IMS enclosure and I discover that
actually I can configure the storage assigned (second disk of the
blade) as FC and that there is also multipath for this kind of servers
(see the other thread of mine).
The optimal would be to deactivate all and redefine the DC as
Fibrechannel type but it seems not so easy....
I probably make an error at this point because instead of directly
putting host into maintenance I follow these steps in the gui:
- expand my DC at the left
- expand STORAGE of that DC on the left
- select my storage domain (LSTORAGE) on the left
On the right pane I select the line of LSTORAGE and in the bottom
pane I select the "datacenter" label where I then select the line of
my DC.
I choose "maintenance"
--> what is it supposed I have done this way?
Put storage domain in maintenance or DC or what?
Is it supposed to be a correct operation what I've done if the DC is
Up and this is the only SD I have?
Or would it be correct to receive an error from the system?
Because I don't receive any error and I see the SD down and host that
keeps staying with the status "Preparing to maintenance"
I don't remember correctly my steps here, possibly restart of host
that is recognized then as unassigned.
After that I cannot "force remove" the DC and I cannot remove the
cluster or host because it is not in maintenance.
After I also reboot the engine service and restart the host, it comes
up normally with all the DC with the old config.
At this point I can put host in maintenance and force remove the DC
I create a new DC with same name but with type FC and ovirtmgmt as
vlan tagged and I see that the existing cluster is still present, so I
attach it to the new DC (that has the same name as before).
I also find that there is my host that seems to automatically be in
this cluster.
But at this point when I activate it, it comes up but after a few
minutes I get the message I posted at the beginning
In host details, its network interfaces keep down.
Tried different restarts of host.
So I decide to put host into maintenance and select into the gui to
"reinstall" it.
After this all goes well again..
Sorry for the long story
Gianluca
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
4241
days inactive
4245
days old
3 comments
3 participants
participants (3)
-
Gianluca Cecchi -
Mark Wu -
Moti Asayag