BladeSystem - General
cancel
Showing results for 
Search instead for 
Did you mean: 

Communication with Active Onboard Administrator Lost

CaroBell
Advisor

Communication with Active Onboard Administrator Lost

I am trying to update the interconnect module currently on my C7000 blade system but the OA always loses connection while in the middle of it. I have two OA (4.60) and two interconnect modules Flex-10 (4.31 and 4.45). I took one of the modules out to be able to update them since they are not at the same version. 

I get to the "Starting firmware update process" line in vcsu but the OA loses connection and will not come back up until I go physically "re-set" the ip address of the active OA. I can also do it by "force takeover" from the standby OA in SSH. 

I tried getting the Active OA to get back online by doing a takeover twice (so the Standby OA stays on Standby) but it does not change anything for the VCSU, it will get stuck on the update process line without ever going further. I have tried this with both VCSU 1.12 and 1.13 as well. 

This as been happening since I started playing around with this blade system. Everything seems to be working except this problem that occurs most of the time when I use virtual connect in some way. 

Sometimes there is error that appears if it was only part of the site that stopped working. Refreshing the page would then have the whole website be unreachable.

Uncaught TypeError: Failed to execute 'appendChild' on 'Node': parameter 1 is not of type 'Node'.

I have tried both on chrome and firefox. I have reset and took in/out both OA. 
System logs only show that it could not ping the dns and ntp servers, but I was able to ping them at the same time it gave those errors.

Any help would be appreciated as I have no idea how I can update anything if the connection is always lost. 

If it helps, I am using VCSU from a virtual machine on a computer that is connected to the same network as the blade system. I am trying to update the interconnect modules to 4.50 individually and then go to 4.60 on both modules. 
I tested with OA firmware 4.50, then 4.60 and am now updating to 4.70.

This is my first time using blades and it is, for now, only to learn how it works, a demo of sorts. If this problem can be taken care of without changing hardware or paying for support that would be preferable. 

EDIT:

I can update the OA from USB through the web GUI no problem tested and working from 4.50 to 4.60,
I cannot do it from a file on another computer through the GUI tested 4.60 to 4.70 update was not made and the active OA lost connection when it was supposed to restart.
I can do it from SSH, both OA were updated and even lived through the restart. Tested and working from 4.60 to 4.70. 

I am
17 REPLIES
peyrache
Respected Contributor

Re: Communication with Active Onboard Administrator Lost

Hello
Please post vcsu log, also I assume you are not connected
On VC to do update ?
Thanks
JY
CaroBell
Advisor

Re: Communication with Active Onboard Administrator Lost

I cannot do the update by VC only from VCSU (from what I understand) so I do not understand your question. 
What log ? There is no log for this as far as I am aware, It only stops when I shutdown VCSU. 

EDIT : Here is me trying to do a Healthcheck after the update froze :

[Thu Jul 13 11:00:19 2017]
[Thu Jul 13 11:00:19 2017] -------------------------------------------------------------------------------
[Thu Jul 13 11:00:19 2017] HPE BladeSystem c-Class Virtual Connect Support Utility
[Thu Jul 13 11:00:19 2017] Version 1.13.0 (Build 10)
[Thu Jul 13 11:00:19 2017] Build Date: Apr 11 2017 12:20:40
[Thu Jul 13 11:00:19 2017] Copyright (C) 2006-2017 Hewlett Packard Enterprise Development LP
[Thu Jul 13 11:00:19 2017] All Rights Reserved
[Thu Jul 13 11:00:19 2017] -------------------------------------------------------------------------------
[Thu Jul 13 11:00:19 2017]
[Thu Jul 13 11:00:19 2017] Initializing, please wait... [Step 1 of 2]
[Thu Jul 13 11:00:36 2017] ERROR: Invalid IP address
[Thu Jul 13 11:00:36 2017]
[Thu Jul 13 11:00:36 2017] Total execution time: 00:00:17
[Thu Jul 13 11:00:36 2017]
[Thu Jul 13 11:00:36 2017] VCSU log file is available at the following location:
[Thu Jul 13 11:00:36 2017] C:\Users\demotest\AppData\Local\Temp\vcsu-2536.log

[Thu Jul 13 11:00:19 2017] (2108)[VcsuInit.cpp:458] : VCSU Library Version: 1.13.0.10
[Thu Jul 13 11:00:19 2017] (2108)[VcsuInit.cpp:358] : User does not have Administrator privilege
[Thu Jul 13 11:00:36 2017] (2108)[LocalIp.cpp:92] : Failed to connect, errno = 13
[Thu Jul 13 11:00:36 2017] (2108)[AuthenticateTarget.cpp:60] : Unable to communicate with given IP 192.168.1.129
[Thu Jul 13 11:00:36 2017] (2108)[AuthenticateUser.cpp:56] : Authentication failed
[Thu Jul 13 11:00:36 2017] (2108)[Initialize.cpp:175] : Cleanup failed for one or more reasons

Here is the standby : 

[Thu Jul 13 11:01:54 2017]
[Thu Jul 13 11:01:54 2017] -------------------------------------------------------------------------------
[Thu Jul 13 11:01:54 2017] HPE BladeSystem c-Class Virtual Connect Support Utility
[Thu Jul 13 11:01:54 2017] Version 1.13.0 (Build 10)
[Thu Jul 13 11:01:54 2017] Build Date: Apr 11 2017 12:20:40
[Thu Jul 13 11:01:54 2017] Copyright (C) 2006-2017 Hewlett Packard Enterprise Development LP
[Thu Jul 13 11:01:54 2017] All Rights Reserved
[Thu Jul 13 11:01:54 2017] -------------------------------------------------------------------------------
[Thu Jul 13 11:01:54 2017]
[Thu Jul 13 11:01:54 2017] Initializing, please wait... [Step 1 of 2]
[Thu Jul 13 11:01:57 2017] ERROR: Specified OA is not primary
[Thu Jul 13 11:01:57 2017]
[Thu Jul 13 11:01:57 2017] Total execution time: 00:00:03
[Thu Jul 13 11:01:57 2017]
[Thu Jul 13 11:01:57 2017] VCSU log file is available at the following location:
[Thu Jul 13 11:01:57 2017] C:\Users\demotest\AppData\Local\Temp\vcsu-368.log

[Thu Jul 13 11:01:54 2017] (2900)[VcsuInit.cpp:458] : VCSU Library Version: 1.13.0.10
[Thu Jul 13 11:01:54 2017] (2900)[VcsuInit.cpp:358] : User does not have Administrator privilege
[Thu Jul 13 11:01:55 2017] (2900)[GetRemoteEndpointInfo.cpp:91] : OA found at 192.168.1.123 with version 4.60
[Thu Jul 13 11:01:56 2017] (2900)[VcsuCore.cpp:392] : Target name:
[Thu Jul 13 11:01:56 2017] (2900)[OaWrap.cpp:823] : OA IP Address:192.168.1.123
[Thu Jul 13 11:01:56 2017] (2900)[OaWrap.cpp:829] : OA1 IP Address:192.168.1.123
[Thu Jul 13 11:01:56 2017] (2900)[VcsuInit.cpp:579] : [] OA Version: 4.60
[Thu Jul 13 11:01:57 2017] (2900)[OaWrap.cpp:443] : Onboard Administrator Role: Standby
[Thu Jul 13 11:01:57 2017] (2900)[VcsuCore.cpp:189] : Specified Onboard Administrator is not primary
[Thu Jul 13 11:01:57 2017] (2900)[VcsuInit.cpp:589] : [] Failed to validate OA state
[Thu Jul 13 11:01:57 2017] (2900)[VcsuInit.cpp:675] : vcsuInitOA failed
[Thu Jul 13 11:01:57 2017] (2900)[AuthenticateTarget.cpp:91] : authenticateOA failed
[Thu Jul 13 11:01:57 2017] (2900)[AuthenticateUser.cpp:56] : Authentication failed

I am
peyrache
Respected Contributor

Re: Communication with Active Onboard Administrator Lost

How can you update vc ?
Using VCSU utilily right ?
So VCSU utility created logs for all step of update
These logs are located in vcsu directory
JY
CaroBell
Advisor

Re: Communication with Active Onboard Administrator Lost

Screenshot from 2017-07-13 11-33-20.pngVCSU Directory

These are the only files in the directory, I have no idea what logs you are speaking of.

All other logs are in the C:\Users\user\AppData\Local\Temp folder and named vcsu-### No log was made for the updates except what I said about it stopping at "Starting firmware update process" line. 

[Thu Jul 13 09:01:32 2017]
[Thu Jul 13 09:01:32 2017] -------------------------------------------------------------------------------
[Thu Jul 13 09:01:32 2017] HPE BladeSystem c-Class Virtual Connect Support Utility
[Thu Jul 13 09:01:32 2017] Version 1.13.0 (Build 10)
[Thu Jul 13 09:01:32 2017] Build Date: Apr 11 2017 12:20:40
[Thu Jul 13 09:01:32 2017] Copyright (C) 2006-2017 Hewlett Packard Enterprise Development LP
[Thu Jul 13 09:01:32 2017] All Rights Reserved
[Thu Jul 13 09:01:32 2017] -------------------------------------------------------------------------------
[Thu Jul 13 09:01:32 2017]
[Thu Jul 13 09:01:32 2017] Initializing, please wait... [Step 1 of 2]
[Thu Jul 13 09:02:03 2017] The target configuration is integrated into a Virtual Connect Domain. Please
[Thu Jul 13 09:02:03 2017] enter the Virtual Connect Domain administrative user credentials to continue.
[Thu Jul 13 09:02:03 2017] User Name:
[Thu Jul 13 09:02:18 2017] Password:
[Thu Jul 13 09:02:40 2017] Gathering module and package information [Step 2 of 2]
[Thu Jul 13 09:05:38 2017] The following modules will be updated:
[Thu Jul 13 09:05:38 2017]
[Thu Jul 13 09:05:38 2017] ===============================================================================
[Thu Jul 13 09:05:38 2017] Enclosure Bay Module Current Version New Version
[Thu Jul 13 09:05:38 2017] ===============================================================================
[Thu Jul 13 09:05:38 2017] SGH143PE4T 1 HP VC Flex-10 4.31 4.50
[Thu Jul 13 09:05:38 2017] Enet Module 2014-10-24T03:51:19Z 2016-04-21T16:52:32Z
[Thu Jul 13 09:05:38 2017] -------------------------------------------------------------------------------
[Thu Jul 13 09:05:38 2017]
[Thu Jul 13 09:05:38 2017] During the update process, modules being updated will be temporarily
[Thu Jul 13 09:05:38 2017] unavailable. In addition, the update process should NOT be interrupted by
[Thu Jul 13 09:05:38 2017] removing or resetting modules, or by closing the application. Interrupting
[Thu Jul 13 09:05:38 2017] the update or the modules being updated may cause the modules to not be updated
[Thu Jul 13 09:05:38 2017] properly.
[Thu Jul 13 09:05:38 2017]
[Thu Jul 13 09:05:39 2017] Please verify the above report before continuing.
[Thu Jul 13 09:05:39 2017]
[Thu Jul 13 09:05:39 2017] Would you like to continue with this update? [YES/NO]:
[Thu Jul 13 09:12:03 2017]
[Thu Jul 13 09:12:03 2017] Starting firmware update process

I am
peyrache
Respected Contributor

Re: Communication with Active Onboard Administrator Lost

That is I'm looking for also confirm you are not connected to VC
To do update ?
JY
CaroBell
Advisor

Re: Communication with Active Onboard Administrator Lost

I do not understand what you mean by "connected to VC" I am using VCSU because it is not possible to update interconnect module firmwares from the Virtual Connect Manager. I can connect to the Manager no problem. Is it the system log from the VC Manager you want to see ? 

Here it is : 

2017-07-13T09:05:38-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1010:Info] VCM user login : Administrator@192.168.0.200
2017-07-13T09:05:38-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1034:Info] User Operation : User LogOut (Administrator@192.168.0.200)
2017-07-13T09:05:38-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1011:Info] VCM user logout : Administrator@192.168.0.200
2017-07-13T09:05:40-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1010:Info] VCM user login : Administrator@192.168.0.200
2017-07-13T09:05:41-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1034:Info] User Operation : User LogOut (Administrator@192.168.0.200)
2017-07-13T09:05:41-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1011:Info] VCM user logout : Administrator@192.168.0.200
2017-07-13T09:05:43-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1010:Info] VCM user login : Administrator@192.168.0.200
2017-07-13T09:05:43-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1034:Info] User Operation : User LogOut (Administrator@192.168.0.200)
2017-07-13T09:05:43-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1011:Info] VCM user logout : Administrator@192.168.0.200
2017-07-13T09:12:02-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1010:Info] VCM user login : Administrator@192.168.0.200
2017-07-13T09:12:03-04:00 VCEX3C413300AG save_config: [CGI::10002:Info] Saving VC domain configuration file... : (Administrator@192.168.0.200)
2017-07-13T09:12:07-04:00 VCEX3C413300AG sr_vc_config: [CGI::10003:Info] VC domain configuration file saved : by Administrator
2017-07-13T09:12:07-04:00 VCEX3C413300AG save_config: [CGI::10003:Info] VC domain configuration file saved : vcConfig-test.local-20170713
2017-07-13T09:12:07-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1034:Info] User Operation : User LogOut (Administrator@192.168.0.200)
2017-07-13T09:12:07-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1011:Info] VCM user logout : Administrator@192.168.0.200
2017-07-13T09:12:08-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1010:Info] VCM user login : Administrator@192.168.0.200
2017-07-13T10:07:41-04:00 VCEX3C413300AG vcmd: [VCD:enc0:1003:Critical] VCM-OA communication down
2017-07-13T10:07:41-04:00 VCEX3C413300AG vcmd: [ENC:enc0:2011:Critical] Enclosure state NO_COMM : Enclosure is no-comm, Previous: Enclosure state OK, Cause: Enclosure enc0 unable to communicate with OA
2017-07-13T10:07:41-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1022:Critical] Domain state FAILED : 1+ enclosures not OK or DEGRADED, Previous: Domain state OK, Cause: Enclosure enc0 unable to communicate with OA
2017-07-13T10:07:41-04:00 VCEX3C413300AG vcmd: [PRO:test_16:6013:Minor] Profile state DEGRADED : At least 1 connection OK but not all connections OK, Previous: Enet Network state OK, Cause: State of port enc0:iobay1:X4 is unknown due to module condition: Module enc0:iobay1 unable to communicate with enclosure enc0; State of port enc0:iobay1:X7 is unknown due to module condition: Module enc0:iobay1 unable to communicate with enclosure enc0
2017-07-13T10:08:10-04:00 VCEX3C413300AG vcmd: [VCD:enc0:1002:Info] VCM-OA communication up
2017-07-13T10:08:12-04:00 VCEX3C413300AG vcmd: [ENC:SGH143PE4T:2001:Info] Enclosure import started : Name [BLADE-TEST]
2017-07-13T10:08:47-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev4:5004:Info] Server power on
2017-07-13T10:08:51-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev5:5004:Info] Server power on
2017-07-13T10:09:31-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev12:5004:Info] Server power on
2017-07-13T10:09:36-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev13:5004:Info] Server power on
2017-07-13T10:09:56-04:00 VCEX3C413300AG vcmd: [ENC:SGH143PE4T:2002:Info] Enclosure import completed : Name [BLADE-TEST]
2017-07-13T10:09:56-04:00 VCEX3C413300AG vcmd: [VCD:VCM:1035:Info] Build Information : 4.31-5
2017-07-13T10:09:57-04:00 VCEX3C413300AG vcmd: [PRO:test_1:6004:Info] Profile assigned : Bay 1
2017-07-13T10:09:57-04:00 VCEX3C413300AG vcmd: [ENC:enc0:2010:Info] Enclosure state OK : All modules & servers OK, Previous: Enclosure state DEGRADED
2017-07-13T10:09:57-04:00 VCEX3C413300AG vcmd: [ENET:enc0:iobay1:3010:Info] Enet Module state OK : All downlink ports OK, Previous: Enet Module state UNKNOWN
2017-07-13T10:09:57-04:00 VCEX3C413300AG vcmd: [NET:opeq:7010:Info] Enet Network state OK : Port set OK, Previous: Enet Network state DEGRADED
2017-07-13T10:09:57-04:00 VCEX3C413300AG vcmd: [NET:test_16:7010:Info] Enet Network state OK : All connections, PhysicalServer OK, Previous: Profile state DEGRADED
2017-07-13T10:09:57-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1020:Info] Domain state OK : All enclosures & profiles OK, Previous: Domain state DEGRADED
2017-07-13T10:09:57-04:00 VCEX3C413300AG vcmd: [NET:test_1:7010:Info] Enet Network state OK : All connections, PhysicalServer OK, Previous: Profile state UNKNOWN
2017-07-13T10:09:57-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev1:5010:Info] Server state OK : Component fully operational, Previous: Server state UNKNOWN
2017-07-13T10:09:57-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev2:5010:Info] Server state OK : Component fully operational, Previous: Server state UNKNOWN
2017-07-13T10:09:57-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev3:5010:Info] Server state OK : Component fully operational, Previous: Server state UNKNOWN
2017-07-13T10:11:46-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1004:Info] VCM Domain checkpointed
2017-07-13T10:14:32-04:00 VCEX3C413300AG vcmd: [VCD:enc0:1003:Critical] VCM-OA communication down
2017-07-13T10:14:32-04:00 VCEX3C413300AG vcmd: [ENC:enc0:2011:Critical] Enclosure state NO_COMM : Enclosure is no-comm, Previous: Enclosure state OK, Cause: Enclosure enc0 unable to communicate with OA
2017-07-13T10:14:32-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1022:Critical] Domain state FAILED : 1+ enclosures not OK or DEGRADED, Previous: Domain state OK, Cause: Enclosure enc0 unable to communicate with OA
2017-07-13T10:14:32-04:00 VCEX3C413300AG vcmd: [PRO:test_16:6013:Minor] Profile state DEGRADED : At least 1 connection OK but not all connections OK, Previous: Enet Network state OK, Cause: State of port enc0:iobay1:X4 is unknown due to module condition: Module enc0:iobay1 unable to communicate with enclosure enc0; State of port enc0:iobay1:X7 is unknown due to module condition: Module enc0:iobay1 unable to communicate with enclosure enc0
2017-07-13T10:15:03-04:00 VCEX3C413300AG vcmd: [VCD:enc0:1002:Info] VCM-OA communication up
2017-07-13T10:15:04-04:00 VCEX3C413300AG vcmd: [ENC:SGH143PE4T:2001:Info] Enclosure import started : Name [BLADE-TEST]
2017-07-13T10:15:41-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev4:5004:Info] Server power on
2017-07-13T10:15:46-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev5:5004:Info] Server power on
2017-07-13T10:16:24-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev12:5004:Info] Server power on
2017-07-13T10:16:29-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev13:5004:Info] Server power on
2017-07-13T10:16:50-04:00 VCEX3C413300AG vcmd: [ENC:SGH143PE4T:2002:Info] Enclosure import completed : Name [BLADE-TEST]
2017-07-13T10:16:50-04:00 VCEX3C413300AG vcmd: [VCD:VCM:1035:Info] Build Information : 4.31-5
2017-07-13T10:16:51-04:00 VCEX3C413300AG vcmd: [PRO:test_1:6004:Info] Profile assigned : Bay 1
2017-07-13T10:16:51-04:00 VCEX3C413300AG vcmd: [ENC:enc0:2010:Info] Enclosure state OK : All modules & servers OK, Previous: Enclosure state DEGRADED
2017-07-13T10:16:51-04:00 VCEX3C413300AG vcmd: [ENET:enc0:iobay1:3010:Info] Enet Module state OK : All downlink ports OK, Previous: Enet Module state UNKNOWN
2017-07-13T10:16:51-04:00 VCEX3C413300AG vcmd: [NET:opeq:7010:Info] Enet Network state OK : Port set OK, Previous: Enet Network state DEGRADED
2017-07-13T10:16:51-04:00 VCEX3C413300AG vcmd: [NET:test_16:7010:Info] Enet Network state OK : All connections, PhysicalServer OK, Previous: Profile state DEGRADED
2017-07-13T10:16:51-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1020:Info] Domain state OK : All enclosures & profiles OK, Previous: Domain state DEGRADED
2017-07-13T10:16:51-04:00 VCEX3C413300AG vcmd: [NET:test_1:7010:Info] Enet Network state OK : All connections, PhysicalServer OK, Previous: Profile state UNKNOWN
2017-07-13T10:16:51-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev1:5010:Info] Server state OK : Component fully operational, Previous: Server state UNKNOWN
2017-07-13T10:16:51-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev2:5010:Info] Server state OK : Component fully operational, Previous: Server state UNKNOWN
2017-07-13T10:16:51-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev3:5010:Info] Server state OK : Component fully operational, Previous: Server state UNKNOWN
2017-07-13T10:18:39-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1004:Info] VCM Domain checkpointed
2017-07-13T11:17:32-04:00 VCEX3C413300AG vcmd: [VCD:enc0:1003:Critical] VCM-OA communication down
2017-07-13T11:17:33-04:00 VCEX3C413300AG vcmd: [ENC:enc0:2011:Critical] Enclosure state NO_COMM : Enclosure is no-comm, Previous: Enclosure state OK, Cause: Enclosure enc0 unable to communicate with OA
2017-07-13T11:17:33-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1022:Critical] Domain state FAILED : 1+ enclosures not OK or DEGRADED, Previous: Domain state OK, Cause: Enclosure enc0 unable to communicate with OA
2017-07-13T11:17:33-04:00 VCEX3C413300AG vcmd: [PRO:test_16:6013:Minor] Profile state DEGRADED : At least 1 connection OK but not all connections OK, Previous: Enet Network state OK, Cause: State of port enc0:iobay1:X4 is unknown due to module condition: Module enc0:iobay1 unable to communicate with enclosure enc0; State of port enc0:iobay1:X7 is unknown due to module condition: Module enc0:iobay1 unable to communicate with enclosure enc0
2017-07-13T11:17:33-04:00 VCEX3C413300AG vcmd: [VCD:enc0:1002:Info] VCM-OA communication up
2017-07-13T11:17:35-04:00 VCEX3C413300AG vcmd: [ENC:SGH143PE4T:2001:Info] Enclosure import started : Name [BLADE-TEST]
2017-07-13T11:18:11-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev4:5004:Info] Server power on
2017-07-13T11:18:17-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev5:5004:Info] Server power on
2017-07-13T11:18:57-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev12:5004:Info] Server power on
2017-07-13T11:19:04-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev13:5004:Info] Server power on
2017-07-13T11:19:25-04:00 VCEX3C413300AG vcmd: [ENC:SGH143PE4T:2002:Info] Enclosure import completed : Name [BLADE-TEST]
2017-07-13T11:19:25-04:00 VCEX3C413300AG vcmd: [VCD:VCM:1035:Info] Build Information : 4.31-5
2017-07-13T11:19:26-04:00 VCEX3C413300AG vcmd: [PRO:test_1:6004:Info] Profile assigned : Bay 1
2017-07-13T11:19:26-04:00 VCEX3C413300AG vcmd: [ENC:enc0:2010:Info] Enclosure state OK : All modules & servers OK, Previous: Enclosure state DEGRADED
2017-07-13T11:19:26-04:00 VCEX3C413300AG vcmd: [ENET:enc0:iobay1:3010:Info] Enet Module state OK : All downlink ports OK, Previous: Enet Module state UNKNOWN
2017-07-13T11:19:26-04:00 VCEX3C413300AG vcmd: [NET:opeq:7010:Info] Enet Network state OK : Port set OK, Previous: Enet Network state DEGRADED
2017-07-13T11:19:26-04:00 VCEX3C413300AG vcmd: [NET:test_16:7010:Info] Enet Network state OK : All connections, PhysicalServer OK, Previous: Profile state DEGRADED
2017-07-13T11:19:26-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1020:Info] Domain state OK : All enclosures & profiles OK, Previous: Domain state DEGRADED
2017-07-13T11:19:26-04:00 VCEX3C413300AG vcmd: [NET:test_1:7010:Info] Enet Network state OK : All connections, PhysicalServer OK, Previous: Profile state UNKNOWN
2017-07-13T11:19:26-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev1:5010:Info] Server state OK : Component fully operational, Previous: Server state UNKNOWN
2017-07-13T11:19:26-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev2:5010:Info] Server state OK : Component fully operational, Previous: Server state UNKNOWN
2017-07-13T11:19:26-04:00 VCEX3C413300AG vcmd: [SVR:enc0:dev3:5010:Info] Server state OK : Component fully operational, Previous: Server state UNKNOWN
2017-07-13T11:21:01-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1004:Info] VCM Domain checkpointed
2017-07-13T11:41:26-04:00 VCEX3C413300AG vcmd: [VCD:test.local:1010:Info] VCM user login : Administrator@192.168.0.200

I am
peyrache
Respected Contributor

Re: Communication with Active Onboard Administrator Lost

Are you connected directly to oa ethernet port
To do update or somewhere on the network and passing thru VC
To reach them
That is my question
JY
CaroBell
Advisor

Re: Communication with Active Onboard Administrator Lost

Always testing I am. Here is what happens when I am connected to the web gui (OA and VC) at the same time as the VCSU : 

Screenshot from 2017-07-13 11-58-39.pngScreenshot from 2017-07-13 11-58-13.pngScreenshot from 2017-07-13 11-57-50.png

I then go to the standby OA's web gui (becasue I do not have access to the real thing right now), I transition it to active and wait for it to reload. During all this time I cannot ping the current Active OA's ip until it is in transitionned to Standy. 

I am
CaroBell
Advisor

Re: Communication with Active Onboard Administrator Lost

I am on the same network... ? 

I connect through the ip address and everything works until the ip stops working. That ip is the ip of the active OA that is connected to a switch with a RJ-45 cable.... I do not undertsand what you want to know more ?

EDIT: I think I just understood your question. As stated on the original post, I am on the same network, not connected directly to the blade which would be impossible as I am not in the same phisycal space as said blade system. Even if I was connected directly to it, how would that help as I would still need an ip address to make the update and the OA (as of now) always loses that connection ?

I am
Torsten.
Acclaimed Contributor

Re: Communication with Active Onboard Administrator Lost

I would first check for duplicated IP addresses.

Depending on the netmask used the components are/are not on the same network.

 

From your logs:

Unable to communicate with given IP 192.168.1.129

OA found at 192.168.1.123 with version 4.60

OA IP Address:192.168.1.123

OA1 IP Address:192.168.1.123

VCM user login : Administrator@192.168.0.200

 


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
CaroBell
Advisor

Re: Communication with Active Onboard Administrator Lost

The netmask is 255.255.254.0 for all of them. The network is 192.168.0.0/23. There is no duplicate that I am aware of.

192.168.1.129 and 192.168.1.123 are the OA (standby or active depending on who lost connection last) 

192.168.0.200 is the virtual machine connecting through VCSU or the Web GUI.

I am
Torsten.
Acclaimed Contributor

Re: Communication with Active Onboard Administrator Lost

How about the IP of the VC module(s)?

 

Sometimes it help sto reset the VCM, from CLI within the VC module you do

 

reset vcm

 

 


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
CaroBell
Advisor

Re: Communication with Active Onboard Administrator Lost

The ip of the module is also in the same network/netmask but follows the Active OA. If one does not work the other does not work either and it will only come back if I change the Standby OA to Active. I have previously reset the VCM. I am trying to connect to the CLI to reset and see if it changes anything. I have tried it before but does not hurt to try again since I just updated the OA.

EDIT: I seem to be stuck for the moment. Both OA are now offline (I cannot ping them) and I cannot go check physically why that is the case. I will come back with more when I can go check it out. 

I am
Torsten.
Acclaimed Contributor

Re: Communication with Active Onboard Administrator Lost

I would try this now:
- pull both OA modules
- re-seat the OA tray
- insert the OAs, first the primary, wait until it is up, then the second.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
CaroBell
Advisor

Re: Communication with Active Onboard Administrator Lost

Took both OA out, took out the OA bay and put it back in, than re-added the OAs inside it primary first, waited for it to set and then added the second. 

In addition to that I changed their adresses to be sure they were not duplicates (OA1 192.168.0.54 OA2 192.168.0.55 VC 192.168.0.56) but still no go, OA1 loses connection, which then make VC lose connection and can only get it back by changing the standby OA to active or physically play with the enclosure settings on the insight display of the blade system. 

I am
CaroBell
Advisor

Re: Communication with Active Onboard Administrator Lost

Something changed! I was finally able to get a % on the update. Here is the log file : 

[Fri Jul 14 10:36:14 2017]
[Fri Jul 14 10:36:14 2017] -------------------------------------------------------------------------------
[Fri Jul 14 10:36:14 2017] HPE BladeSystem c-Class Virtual Connect Support Utility
[Fri Jul 14 10:36:14 2017] Version 1.13.0 (Build 10)
[Fri Jul 14 10:36:14 2017] Build Date: Apr 11 2017 12:20:40
[Fri Jul 14 10:36:14 2017] Copyright (C) 2006-2017 Hewlett Packard Enterprise Development LP
[Fri Jul 14 10:36:14 2017] All Rights Reserved
[Fri Jul 14 10:36:14 2017] -------------------------------------------------------------------------------
[Fri Jul 14 10:36:14 2017]
[Fri Jul 14 10:36:14 2017] Initializing, please wait... [Step 1 of 2]
[Fri Jul 14 10:36:54 2017] The target configuration is integrated into a Virtual Connect Domain. Please
[Fri Jul 14 10:36:54 2017] enter the Virtual Connect Domain administrative user credentials to continue.
[Fri Jul 14 10:36:54 2017] User Name:
[Fri Jul 14 10:37:41 2017] Password:
[Fri Jul 14 10:37:59 2017] Gathering module and package information [Step 2 of 2]
[Fri Jul 14 10:42:10 2017] The following modules will be updated:
[Fri Jul 14 10:42:10 2017]
[Fri Jul 14 10:42:10 2017] ===============================================================================
[Fri Jul 14 10:42:10 2017] Enclosure Bay Module Current Version New Version
[Fri Jul 14 10:42:10 2017] ===============================================================================
[Fri Jul 14 10:42:10 2017] SGH143PE4T 1 HP VC Flex-10 4.31 4.50
[Fri Jul 14 10:42:10 2017] Enet Module 2014-10-24T03:51:19Z 2016-04-21T16:52:32Z
[Fri Jul 14 10:42:10 2017] -------------------------------------------------------------------------------
[Fri Jul 14 10:42:10 2017]
[Fri Jul 14 10:42:10 2017] During the update process, modules being updated will be temporarily
[Fri Jul 14 10:42:10 2017] unavailable. In addition, the update process should NOT be interrupted by
[Fri Jul 14 10:42:10 2017] removing or resetting modules, or by closing the application. Interrupting
[Fri Jul 14 10:42:10 2017] the update or the modules being updated may cause the modules to not be updated
[Fri Jul 14 10:42:10 2017] properly.
[Fri Jul 14 10:42:11 2017]
[Fri Jul 14 10:42:11 2017] Please verify the above report before continuing.
[Fri Jul 14 10:42:11 2017]
[Fri Jul 14 10:42:11 2017] Would you like to continue with this update? [YES/NO]:
[Fri Jul 14 10:43:38 2017]
[Fri Jul 14 10:43:38 2017] Starting firmware update process
[Fri Jul 14 10:45:57 2017] Updating firmware [Step 2 of 3 : 0% complete]
[Fri Jul 14 10:47:40 2017] Activating firmware [Step 3 of 3 : 0% complete]
[Fri Jul 14 10:48:13 2017] Firmware update completed
[Fri Jul 14 10:48:13 2017] The following modules were not successful:
[Fri Jul 14 10:48:13 2017]
[Fri Jul 14 10:48:13 2017] ===========================================================
[Fri Jul 14 10:48:13 2017] Enclosure Bay Module Status
[Fri Jul 14 10:48:13 2017] ===========================================================
[Fri Jul 14 10:48:13 2017] SGH143PE4T 1 HP VC Flex-10 Enet Module Update Failed
[Fri Jul 14 10:48:13 2017]
[Fri Jul 14 10:48:13 2017] Total execution time: 00:11:59
[Fri Jul 14 10:48:13 2017]
[Fri Jul 14 10:48:13 2017] VCSU log file is available at the following location:
[Fri Jul 14 10:48:13 2017] C:\Users\demotest\AppData\Local\Temp\vcsu-920.log

[Fri Jul 14 10:36:14 2017] (2912)[VcsuInit.cpp:458] : VCSU Library Version: 1.13.0.10
[Fri Jul 14 10:36:14 2017] (2912)[VcsuInit.cpp:358] : User does not have Administrator privilege
[Fri Jul 14 10:36:16 2017] (2912)[GetRemoteEndpointInfo.cpp:91] : OA found at 192.168.0.55 with version 4.70
[Fri Jul 14 10:36:17 2017] (2912)[VcsuCore.cpp:392] : Target name: BladeSystem c7000 Enclosure G2
[Fri Jul 14 10:36:17 2017] (2912)[OaWrap.cpp:823] : OA IP Address: 192.168.0.55
[Fri Jul 14 10:36:17 2017] (2912)[OaWrap.cpp:829] : OA1 IP Address: 192.168.0.54
[Fri Jul 14 10:36:17 2017] (2912)[OaWrap.cpp:823] : OA IP Address: 192.168.0.55
[Fri Jul 14 10:36:18 2017] (2912)[OaWrap.cpp:829] : OA1 IP Address: 192.168.0.55
[Fri Jul 14 10:36:18 2017] (2912)[VcsuInit.cpp:579] : [SGH143PE4T] OA Version: 4.70
[Fri Jul 14 10:36:19 2017] (2912)[OaWrap.cpp:443] : Onboard Administrator Role: Active
[Fri Jul 14 10:36:19 2017] (2912)[OaWrap.cpp:554] : User already exists
[Fri Jul 14 10:36:22 2017] (2912)[OaWrap.cpp:793] : User successfully deleted
[Fri Jul 14 10:36:41 2017] (2912)[OaWrap.cpp:443] : Onboard Administrator Role: Active
[Fri Jul 14 10:36:43 2017] (2912)[VcsuCore.cpp:5851] : Bay 1 IP Address is 192.168.1.6 and type is IPv4
[Fri Jul 14 10:36:45 2017] (2912)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:36:46 2017] (2912)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:36:46 2017] (2912)[VcsuCore.cpp:653] : Bay 1 Firmware Version: 4.31 2014-10-24T03:51:19Z
[Fri Jul 14 10:36:48 2017] (2912)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:36:49 2017] (2912)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:36:49 2017] (2912)[VcsuCore.cpp:1960] : Module not present in bay 2
[Fri Jul 14 10:36:50 2017] (2912)[VcsuCore.cpp:1960] : Module not present in bay 3
[Fri Jul 14 10:36:50 2017] (2912)[VcsuCore.cpp:1960] : Module not present in bay 4
[Fri Jul 14 10:36:51 2017] (2912)[VcsuCore.cpp:1960] : Module not present in bay 5
[Fri Jul 14 10:36:52 2017] (2912)[VcsuCore.cpp:1960] : Module not present in bay 6
[Fri Jul 14 10:36:52 2017] (2912)[VcsuCore.cpp:1960] : Module not present in bay 7
[Fri Jul 14 10:36:53 2017] (2912)[VcsuCore.cpp:1960] : Module not present in bay 8
[Fri Jul 14 10:36:53 2017] (2912)[VcsuCore.cpp:1029] : Domain configuration is present
[Fri Jul 14 10:36:53 2017] (2912)[VcsuCore.cpp:1043] : This is primary enclosure
[Fri Jul 14 10:36:53 2017] (2912)[VcsuInit.cpp:750] : OA VC Mode is set
[Fri Jul 14 10:36:54 2017] (2912)[VcsuCore.cpp:1866] : Primary VCM Found at : 192.168.1.6
[Fri Jul 14 10:37:43 2017] (2912)[OaWrap.cpp:1438] : OA Soap Call failed with error 404
[Fri Jul 14 10:37:43 2017] (2912)[VcmWrap.cpp:1732] : VCM Firmware Version: 4.31
[Fri Jul 14 10:37:43 2017] (2912)[VcsuCore.cpp:1259] : VCM IP Address: 192.168.1.6
[Fri Jul 14 10:37:43 2017] (2912)[VcsuCore.cpp:1260] : VCM Firmware Version: 4.31
[Fri Jul 14 10:37:43 2017] (2912)[VcsuCore.cpp:1029] : Domain configuration is present
[Fri Jul 14 10:37:43 2017] (2912)[VcsuCore.cpp:1043] : This is primary enclosure
[Fri Jul 14 10:37:44 2017] (2912)[VcsuInit.cpp:811] : VCM user authenticated successfully
[Fri Jul 14 10:37:44 2017] (2912)[VcmWrap.cpp:1732] : VCM Firmware Version: 4.31
[Fri Jul 14 10:37:45 2017] (2912)[VcmWrap.cpp:901] : Number of enclosures in the domain: 1
[Fri Jul 14 10:37:46 2017] (2912)[VcsuCore.cpp:1866] : Primary VCM Found at : 192.168.1.6
[Fri Jul 14 10:37:47 2017] (2912)[VcsuCore.cpp:5619] : VCM is in Unlocked mode
[Fri Jul 14 10:37:48 2017] (2912)[VcsuCore.cpp:5449] : User has domain privileges
[Fri Jul 14 10:37:48 2017] (2912)[VcmWrap.cpp:1732] : VCM Firmware Version: 4.31
[Fri Jul 14 10:37:49 2017] (2912)[VcmWrap.cpp:683] : User has the privilege to update the firmware
[Fri Jul 14 10:37:49 2017] (2912)[VcmWrap.cpp:688] : User has the privilege to save config
[Fri Jul 14 10:37:49 2017] (2912)[VcmWrap.cpp:693] : User has the privilege to save support information
[Fri Jul 14 10:37:49 2017] (2912)[VcmWrap.cpp:1732] : VCM Firmware Version: 4.31
[Fri Jul 14 10:37:49 2017] (2912)[VcmWrap.cpp:1684] : VCM FIPS Mode is disabled
[Fri Jul 14 10:37:50 2017] (2912)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:37:51 2017] (2912)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:37:55 2017] (2912)[VcsuCore.cpp:1866] : Primary VCM Found at : 192.168.1.6
[Fri Jul 14 10:37:56 2017] (2912)[VcsuCore.cpp:1866] : Primary VCM Found at : 192.168.1.6
[Fri Jul 14 10:37:57 2017] (2912)[VcsuCore.cpp:1866] : Primary VCM Found at : 192.168.1.6
[Fri Jul 14 10:37:58 2017] (2912)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:37:59 2017] (2912)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:37:59 2017] (2912)[VcmWrap.cpp:763] : Domain has Proper Stacking Connection
[Fri Jul 14 10:37:59 2017] (2912)[VcmWrap.cpp:774] : Domain has Proper Stacking Redundancy
[Fri Jul 14 10:37:59 2017] (2912)[VcsuFirmware.cpp:679] : Verifying package signature...
[Fri Jul 14 10:38:24 2017] (2912)[VcsuFirmware.cpp:697] : Extracting package
[Fri Jul 14 10:40:28 2017] (2912)[Extract.cpp:125] : Done extracting PackageDesc.xml from VCpackage.tar
[Fri Jul 14 10:40:38 2017] (2912)[Extract.cpp:125] : Done extracting vcenet.img from VCpackage.tar
[Fri Jul 14 10:40:52 2017] (2912)[Extract.cpp:125] : Done extracting vcenetfcoe.img from VCpackage.tar
[Fri Jul 14 10:41:04 2017] (2912)[Extract.cpp:125] : Done extracting vcg2enet.img from VCpackage.tar
[Fri Jul 14 10:41:17 2017] (2912)[Extract.cpp:125] : Done extracting vcg2enetfcoe.img from VCpackage.tar
[Fri Jul 14 10:41:22 2017] (2912)[Extract.cpp:125] : Done extracting vcfc.img from VCpackage.tar
[Fri Jul 14 10:41:30 2017] (2912)[Extract.cpp:125] : Done extracting vcfc2.img from VCpackage.tar
[Fri Jul 14 10:41:42 2017] (2912)[Extract.cpp:125] : Done extracting vcfc2.img from VCpackage.tar
[Fri Jul 14 10:42:00 2017] (2912)[VcsuFirmware.cpp:709] : Parsing package information
[Fri Jul 14 10:42:00 2017] (2912)[Extract.cpp:125] : Done extracting PackageDesc.xml from VCpackage.tar
[Fri Jul 14 10:42:00 2017] (2912)[Extract.cpp:125] : Done extracting ReleaseNotes.txt from VCpackage.tar
[Fri Jul 14 10:42:00 2017] (2912)[VcsuFirmware.cpp:769] : ReleaseNotes.htm saved in current directory
[Fri Jul 14 10:42:00 2017] (2912)[VcsuCore.cpp:7522] : Domain is not in FIPS mode
[Fri Jul 14 10:42:00 2017] (2912)[VcsuCore.cpp:2378] : Checking state of any incompleted firmware updates.
[Fri Jul 14 10:42:01 2017] (2912)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:42:02 2017] (2912)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:42:02 2017] (2912)[VcsuCore.cpp:2471] : No incomplete firmware updates detected.
[Fri Jul 14 10:42:02 2017] (2912)[VcsuCore.cpp:1866] : Primary VCM Found at : 192.168.1.6
[Fri Jul 14 10:42:03 2017] (2912)[VcmWrap.cpp:1732] : VCM Firmware Version: 4.31
[Fri Jul 14 10:42:04 2017] (2912)[VcsuCore.cpp:6942] : checkpoint_valid = 1
[Fri Jul 14 10:42:05 2017] (2912)[VcsuCore.cpp:1866] : Primary VCM Found at : 192.168.1.6
[Fri Jul 14 10:42:06 2017] (2912)[VcsuCore.cpp:1866] : Primary VCM Found at : 192.168.1.6
[Fri Jul 14 10:42:08 2017] (2912)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:42:09 2017] (2912)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:42:10 2017] (2912)[VcmWrap.cpp:763] : Domain has Proper Stacking Connection
[Fri Jul 14 10:42:10 2017] (2912)[VcmWrap.cpp:774] : Domain has Proper Stacking Redundancy
[Fri Jul 14 10:43:38 2017] (2912)[VcsuUpdate.cpp:978] : Checking for previous firmware update failures...
[Fri Jul 14 10:43:38 2017] (2912)[VcsuCore.cpp:2378] : Checking state of any incompleted firmware updates.
[Fri Jul 14 10:43:39 2017] (2912)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:43:40 2017] (2912)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:43:40 2017] (2912)[VcsuCore.cpp:2471] : No incomplete firmware updates detected.
[Fri Jul 14 10:43:40 2017] (2912)[VcsuUpdate.cpp:1126] : All fw upgrade verifications completed
[Fri Jul 14 10:43:43 2017] (2912)[VcsuCore.cpp:1365] : Saving Virtual Connect configuration file
[Fri Jul 14 10:43:43 2017] (2912)[VcsuCore.cpp:1866] : Primary VCM Found at : 192.168.1.6
[Fri Jul 14 10:43:48 2017] (2912)[VcDownload.cpp:1324] : Connection closed by peer
[Fri Jul 14 10:43:51 2017] (2912)[VcDownload.cpp:1532] : Download succeeded
[Fri Jul 14 10:43:51 2017] (2912)[VcDownload.cpp:1454] : Saving the downloaded file as ..\vcConfig-test.opeq.local-201707141043
[Fri Jul 14 10:43:51 2017] (2912)[VcsuCore.cpp:1305] : Saving Virtual Connect Support file
[Fri Jul 14 10:43:51 2017] (2912)[VcsuCore.cpp:1866] : Primary VCM Found at : 192.168.1.6
[Fri Jul 14 10:43:51 2017] (2912)[VcsuCore.cpp:1318] : Domain is not in FIPS Mode so ignoring the encryption password for supportdump
[Fri Jul 14 10:45:56 2017] (2912)[VcDownload.cpp:1324] : Connection closed by peer
[Fri Jul 14 10:45:56 2017] (2912)[VcDownload.cpp:1532] : Download succeeded
[Fri Jul 14 10:45:56 2017] (2912)[VcDownload.cpp:1454] : Saving the downloaded file as ..\vcSupportInfo-test.opeq.local-201707141045
[Fri Jul 14 10:45:57 2017] (2912)[VcsuUpdate.cpp:685] : [SGH143PE4T:1] Firmware update started
[Fri Jul 14 10:45:57 2017] (2912)[VcsuUpdate.cpp:1214] : All module firmware update operations have been started
[Fri Jul 14 10:45:57 2017] (2132)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:45:58 2017] (2132)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:45:59 2017] (1760)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:46:01 2017] (1760)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:46:01 2017] (1760)[VcsuProgress.cpp:149] : [SGH143PE4T:1] Bay Progress: 0% completed
[Fri Jul 14 10:46:04 2017] (1760)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:46:05 2017] (1760)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:46:06 2017] (1760)[VcsuProgress.cpp:149] : [SGH143PE4T:1] Bay Progress: 0% completed
[Fri Jul 14 10:46:06 2017] (2132)[VcsuCore.cpp:1960] : Module not present in bay 2
[Fri Jul 14 10:46:07 2017] (2132)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:46:08 2017] (1760)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:46:08 2017] (2132)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:46:09 2017] (2132)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:46:09 2017] (1760)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:46:09 2017] (1760)[VcsuProgress.cpp:149] : [SGH143PE4T:1] Bay Progress: 0% completed
[Fri Jul 14 10:46:10 2017] (2132)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:46:10 2017] (2132)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:46:11 2017] (2132)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:46:11 2017] (1760)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:46:11 2017] (2132)[VcsuUpdate.cpp:421] : [SGH143PE4T:1] Started firmware update
[Fri Jul 14 10:46:12 2017] (2132)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:46:12 2017] (1760)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:46:12 2017] (1760)[VcsuProgress.cpp:149] : [SGH143PE4T:1] Bay Progress: 0% completed
[Fri Jul 14 10:46:13 2017] (2132)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:46:13 2017] (2132)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:46:14 2017] (2132)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:46:14 2017] (1760)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:46:15 2017] (1760)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:46:15 2017] (1760)[VcsuProgress.cpp:149] : [SGH143PE4T:1] Bay Progress: 0% completed
[Fri Jul 14 10:46:17 2017] (1760)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:46:18 2017] (1760)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:46:18 2017] (1760)[VcsuProgress.cpp:149] : [SGH143PE4T:1] Bay Progress: 0% completed
[Fri Jul 14 10:46:20 2017] (1760)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:46:20 2017] (1760)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:46:21 2017] (1760)[VcsuProgress.cpp:149] : [SGH143PE4T:1] Bay Progress: 0% completed
[Fri Jul 14 10:46:23 2017] (1760)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:46:24 2017] (1760)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:46:24 2017] (1760)[VcsuProgress.cpp:149] : [SGH143PE4T:1] Bay Progress: 0% completed
[Fri Jul 14 10:46:26 2017] (1760)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:46:27 2017] (1760)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:46:27 2017] (1760)[VcsuProgress.cpp:149] : [SGH143PE4T:1] Bay Progress: 0% completed
[Fri Jul 14 10:46:29 2017] (1760)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:46:30 2017] (1760)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:46:30 2017] (1760)[VcsuProgress.cpp:149] : [SGH143PE4T:1] Bay Progress: 0% completed
[Fri Jul 14 10:46:32 2017] (1760)[VcsuSsh.cpp:143] : Connection established to 192.168.1.6
[Fri Jul 14 10:46:33 2017] (1760)[VcsuSsh.cpp:163] : Successfully established session to 192.168.1.6
[Fri Jul 14 10:46:33 2017] (1760)[VcsuProgress.cpp:149] : [SGH143PE4T:1] Bay Progress: 0% completed
[Fri Jul 14 10:46:51 2017] (2132)[VcsuSftp.cpp:835] : ERROR: Sftp write failed. errno = 0, No error
[Fri Jul 14 10:46:51 2017] (2132)[VcsuSftp.cpp:751] : sftp_close_handle failed, return code = -7
[Fri Jul 14 10:46:51 2017] (2132)[Command.cpp:629] : VCEnet image transfer failed
[Fri Jul 14 10:46:51 2017] (2132)[VcsuUpdate.cpp:182] : transfer_imagefiles failed
[Fri Jul 14 10:46:51 2017] (2132)[VcsuUpdate.cpp:424] : [SGH143PE4T:1] Firmware update completed
[Fri Jul 14 10:46:51 2017] (2132)[VcsuUpdate.cpp:424] : ErrorCode :49 Error :The SFTP write failed
[Fri Jul 14 10:46:51 2017] (2132)[VcsuUpdate.cpp:464] : [SGH143PE4T:1] Firmware update failed, FW Version: 2016-04-21T16:52:32Z
[Fri Jul 14 10:46:56 2017] (1760)[VcsuSsh.cpp:477] : Failed to connect, errno = 10060
[Fri Jul 14 10:46:56 2017] (1760)[VcsuSsh.cpp:137] : Failed to create session in iteration 1
[Fri Jul 14 10:46:57 2017] (1760)[VcsuSsh.cpp:137] : Failed to create session in iteration 2
[Fri Jul 14 10:46:58 2017] (1760)[VcsuSsh.cpp:137] : Failed to create session in iteration 3
[Fri Jul 14 10:46:59 2017] (1760)[VcsuSsh.cpp:137] : Failed to create session in iteration 4
[Fri Jul 14 10:47:00 2017] (1760)[VcsuSsh.cpp:137] : Failed to create session in iteration 5
[Fri Jul 14 10:47:01 2017] (1760)[VcsuSsh.cpp:150] : Failed to create session
[Fri Jul 14 10:47:01 2017] (1760)[VcsuCore.cpp:2849] : command session could not be established for bay 1
[Fri Jul 14 10:47:01 2017] (1760)[VcsuCore.cpp:2851] : number of failed attempts for bay 1: 1
[Fri Jul 14 10:47:01 2017] (1760)[VcsuProgress.cpp:149] : [SGH143PE4T:1] Bay Progress: 0% completed
[Fri Jul 14 10:47:03 2017] (1760)[VcsuUpdate.cpp:1715] : Deleting FC firmware images from the Enet modules
[Fri Jul 14 10:47:30 2017] (1760)[VcsuSsh.cpp:477] : Failed to connect, errno = 10060
[Fri Jul 14 10:47:30 2017] (1760)[VcsuSsh.cpp:137] : Failed to create session in iteration 1
[Fri Jul 14 10:47:31 2017] (1760)[VcsuSsh.cpp:137] : Failed to create session in iteration 2
[Fri Jul 14 10:47:33 2017] (1760)[VcsuSsh.cpp:137] : Failed to create session in iteration 3
[Fri Jul 14 10:47:34 2017] (1760)[VcsuSsh.cpp:137] : Failed to create session in iteration 4
[Fri Jul 14 10:47:35 2017] (1760)[VcsuSsh.cpp:137] : Failed to create session in iteration 5
[Fri Jul 14 10:47:37 2017] (1760)[VcsuSsh.cpp:150] : Failed to create session
[Fri Jul 14 10:47:37 2017] (1760)[VcsuSftp.cpp:88] : SSH connection could not be established
[Fri Jul 14 10:47:37 2017] (1760)[VcsuUpdate.cpp:1732] : SFTP create failed
[Fri Jul 14 10:47:37 2017] (1760)[VcsuProgress.cpp:210] : Starting Activation
[Fri Jul 14 10:47:37 2017] (1760)[VcsuProgress.cpp:362] : Storing Current vcmConfig for Rollback
[Fri Jul 14 10:48:06 2017] (1760)[VcsuSsh.cpp:477] : Failed to connect, errno = 10060
[Fri Jul 14 10:48:06 2017] (1760)[VcsuSsh.cpp:137] : Failed to create session in iteration 1
[Fri Jul 14 10:48:07 2017] (1760)[VcsuSsh.cpp:137] : Failed to create session in iteration 2
[Fri Jul 14 10:48:08 2017] (1760)[VcsuSsh.cpp:137] : Failed to create session in iteration 3
[Fri Jul 14 10:48:09 2017] (1760)[VcsuSsh.cpp:137] : Failed to create session in iteration 4
[Fri Jul 14 10:48:11 2017] (1760)[VcsuSsh.cpp:137] : Failed to create session in iteration 5
[Fri Jul 14 10:48:12 2017] (1760)[VcsuSsh.cpp:150] : Failed to create session
[Fri Jul 14 10:48:12 2017] (1760)[VcsuSftp.cpp:88] : SSH connection could not be established
[Fri Jul 14 10:48:12 2017] (1760)[Sftp.cpp:317] : Failed to create session
[Fri Jul 14 10:48:12 2017] (1760)[VcsuActivate.cpp:2880] : Error in deleting old backedup vcmConfig file
[Fri Jul 14 10:48:12 2017] (1760)[VcsuProgress.cpp:367] : Error in Storing vcmConfig for Rollback
[Fri Jul 14 10:48:12 2017] (1760)[VcsuProgress.cpp:231] : Activate Progress: 50% completed
[Fri Jul 14 10:48:12 2017] (1760)[VcsuProgress.cpp:577] : Activating VC-FC modules...
[Fri Jul 14 10:48:12 2017] (1760)[VcsuProgress.cpp:592] : FC Activation order is Serial
[Fri Jul 14 10:48:12 2017] (1760)[VcsuProgress.cpp:629] : Activating VC-FC modules completed
[Fri Jul 14 10:48:12 2017] (1760)[VcsuProgress.cpp:631] : Activate Progress: 100% completed
[Fri Jul 14 10:48:12 2017] (1760)[VcsuProgress.cpp:246] : Activate Progress: 100% completed
[Fri Jul 14 10:48:12 2017] (1760)[VcsuUpdate.cpp:636] : SUCCESS: All firmware update operations completed successfully
[Fri Jul 14 10:48:13 2017] (2912)[GetUpdateStatus.cpp:234] : [SGH143PE4T:1] Update Status: update_result= 1, updateThreadStatus= 49, updateState= 5
[Fri Jul 14 10:49:47 2017] (2912)[VcsuInit.cpp:1013] : vcsuCleanUp::Could not logout(User) of OA
[Fri Jul 14 10:49:47 2017] (2912)[Initialize.cpp:175] : Cleanup failed for one or more reasons

In bold (ERROR: Sftp write failed) seems to be where the error starts. Both Active OA and VC reset at this point and are unreachable (no ping).

I am
mziaei
Occasional Visitor

Re: Communication with Active Onboard Administrator Lost

Is there any new development on this?

I'm having the same issue,

trying to update from 4.45 to 4.50 and it failes with similar error.

It goes to $100 and then with following error:
[VcsuSsh.cpp:137] : Failed to create session in iteration 1