[Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'"

[오재욱]

Thanks Yong,

1.  checked my ovs-vswitchd.log, and I think br-int has some problem.
I found something weird in the log,
"2019-03-25T06:11:01.884Z|00192|rconn|WARN|
br-int<->tcp:127.0.0.1:6633: connection failed (Connection refused)"

Is this the main reason of the problem?

2. And below is my ovs-vsctl show result:
controller-1:~$ sudo ovs-vsctl show
10fb65fb-9bac-4ef2-9221-8c27f53afcd3
    Manager "ptcp:6639:127.0.0.1"
        is_connected: true
    Bridge "br-phy0"
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port "br-phy0"
            Interface "br-phy0"
                type: internal
        Port "phy-br-phy0"
            Interface "phy-br-phy0"
                type: patch
                options: {peer="int-br-phy0"}
        Port "lldp6b8235ce-e2"
            Interface "lldp6b8235ce-e2"
                type: internal
        Port "eth0"
            Interface "eth0"
                type: dpdk
                options: {dpdk-devargs="0000:81:00.0", n_rxq="2"}
    Bridge br-int
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port br-int
            Interface br-int
                type: internal
        Port "int-br-phy0"
            Interface "int-br-phy0"
                type: patch
                options: {peer="phy-br-phy0"}
    ovs_version: "2.9.0"

BR,
Jaewook.


2019년 3월 26일 (화) 오후 12:48, Hu, Yong <yong.hu at intel.com>님이 작성:

> Jaewook,
>
> I just now looked through your puppet log, and there was no error message
> at all.
>
> Though the alarm was about “management network” communication failure, the
> essence of problem might be just about controller-1 was not under a right
> state.
>
>
>
> Anyway, we guess maybe something wrong with ovs on your controller-1 and
> it led controller-1 unlock failure.
>
> You can have a check with these stuffs:
>
>    1. Check if any errors are in “/var/log/openvswitch/ovs-vswitchd.log”
>    in controller-1
>    2. Run “sudo ovs-vsctl show” on controller-1
>
>
>
>
>
> Regards,
>
> Yong
>
> *From: *"Sun, Austin" <austin.sun at intel.com>
> *Date: *Tuesday, 26 March 2019 at 11:31 AM
> *To: *오재욱 <kyle.oh95 at gmail.com>, starlingx-discuss <
> starlingx-discuss at lists.starlingx.io>
> *Subject: *Re: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical
> error after deployment] About "persistent critical 'Management Network'"
>
>
>
> Hi Jaewook:
>
> Could you run ‘system host-list’ or ‘system host-show controller-1’ to see
> the status of controller-1?  Is it available  degrade or others ?
>
>
>
> Thanks.
>
> BR
> Austin Sun.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190326/e21aa7a2/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ovs-vswitchd.log
Type: application/octet-stream
Size: 197609 bytes
Desc: not available
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190326/e21aa7a2/attachment-0001.obj>