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

[MacDonald, Eric]

That alarm is indication that Maintenance is failing Heartbeat over the Management network.

Please check your network and maybe specifically its support for multicast messaging.

If you lock controller-1 can you ping it from the active controller.

If you need further assistance please provide the active controller’s mtcAgent.log and hbsAgent.log files

You can always run ‘collect’ or ‘collect all’ on the active controller to get a  summary of the system state and use those logs for off system debug of your issue.

Eric MacDonald.

From: Hu, Yong [mailto:yong.hu at intel.com]
Sent: Monday, March 25, 2019 11:48 PM
To: Sun, Austin; 오재욱; starlingx-discuss
Subject: Re: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'"

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.

From: 오재욱 [mailto:kyle.oh95 at gmail.com]
Sent: Tuesday, March 26, 2019 10:59 AM
To: starlingx-discuss <starlingx-discuss at lists.starlingx.io>
Subject: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'"


---------- Forwarded message ---------
보낸사람: 오재욱 <kyle.oh95 at gmail.com<mailto:kyle.oh95 at gmail.com>>
Date: 2019년 3월 26일 (화) 오전 11:58
Subject: Re: [Starlingx-discuss] [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'"
To: Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>>

Hi Yong,
Umm I think the controller0 was completely installed, but the controller1 was not.
When I unlocked the controller1, fm alarm shows the error.

So it does mean the controller1 was not completely installed.
If so, do you think there is a reason for the installation not being completed elsewhere?
Thank you for help,

BR,
Jaewook.

2019년 3월 26일 (화) 오전 11:53, Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>>님이 작성:
Have you installed 2 controllers already?
If by far you only setup 1 controller,  this alarm seems reasonable because it expects to communicate with another controller through mgt network.

Regards,
Yong

From: 오재욱 <kyle.oh95 at gmail.com<mailto:kyle.oh95 at gmail.com>>
Date: Tuesday, 26 March 2019 at 10:45 AM
To: starlingx-discuss <starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>>
Subject: [Starlingx-discuss] [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'"

Hello StarlingX Teams,

I finally deployed duplex starlingx model on two physical servers.
However, it was not truly deployed. The "all-in-one controller-1" has deploy failed,
The fault management alarm shows,
200.005
Failure: <hostname> is experiencing a persistent critical 'Management Network' communication failure."
And I think above fault is the main reason of deploy failed

I followed BIOS Setup for all nodes,
and used Feb 22 iso images.

I have no idea what can I do :(

Any help would be very appreciated.

Best Regards,
Jaewook.
================================================
Jaewook Oh (오재욱)
IISTRC - Internet Infra System Technology Research Center
369 Sangdo-ro, Dongjak-gu,
06978, Seoul, Republic of Korea


--
================================================
Jaewook Oh (오재욱)
IISTRC - Internet Infra System Technology Research Center
369 Sangdo-ro, Dongjak-gu,
06978, Seoul, Republic of Korea
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190326/7900ed4d/attachment-0001.html>