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

Sun, Austin austin.sun at intel.com
Tue Mar 26 03:29:31 UTC 2019


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/f0e13c4c/attachment-0001.html>


More information about the Starlingx-discuss mailing list