[Users] host goes to non-operational because interface down message

Thu Apr 11 03:14:08 UTC 2013

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 at 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 at 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 at 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 at 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 at 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 at 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 at 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 at 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 at 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 at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>