BladeSystem - General

Re: Communication with Active Onboard Administrator Lost

 
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

ChrisLC
New Member

Re: Communication with Active Onboard Administrator Lost

Running into the same issue with both SUM and VCSU failing and having the SFTP error stated in the post above me.