Well there is still one more "error" by updating Aruba Software with IMC Task.
I always mark "Set the Current Running Software as Backup Startup Software" and it has worked fine for the Aruba OS.
But the Aruba CX --> ... -vtysh[2660906] <ERR> Event|4404|LOG_ERR|AMM|1/1|User manager: secondary image update failed via local copy
Before: primary and secondary image --> LL.10.09.1020
And much more important that the secondary image is shown as the same as before, is that the software image had been corrupted. Verify Command tells about failed:
sasw-rz-r08# sh images
---------------------------------------------------------------------------
ArubaOS-CX Primary Image
---------------------------------------------------------------------------
Version : LL.10.09.1040
Size : 572 MB
Date : 2022-07-18 23:56:41 UTC
SHA-256 : 9c7bb4983bdc7de41b3c25b454a74213b8721636965a1ec573b83202c997ed29
---------------------------------------------------------------------------
ArubaOS-CX Secondary Image
---------------------------------------------------------------------------
Version : LL.10.09.1010
Size : 572 MB
Date : 2022-03-10 23:07:42 UTC
SHA-256 : 0d1f269211262c4ef3e2c4596e8ef8d59f59e69c2070d92f1ee721b47f327f01
Default Image : primary
Boot Profile Timeout : 5 seconds
------------------------------------------------------
Management Module 1/1 (Active)
------------------------------------------------------
Active Image : primary
Service OS Version : LL.01.10.0001
BIOS Version : LL.01.0001
sasw-rz-r08# sho images verify secondary
Image verification failed, internal software error
That of course is VERY DANGEROUS and really should not be!
Edit: the verify statement is only available on the 8360 plattform, not on the 8325. So on this platform there is no way to check if the image has been corrupted by the update/copy task...
Edit Update:
After uploading the new image files from IMC to 8325 now the option verify can be used for show images.
The messages for theuploaded image is valid, the untouched backup/secondary software gets the result invalid.
In this run I do not have used the option to copy the running software to the second boot bank.
Seems that updating by IMC enables some more options on the switch...
Original Message:
Sent: Jul 22, 2022 07:09 AM
From: Robert Großmann
Subject: HPE IMC Software Import and Update for Aruba CX
Yes TFTP is the default.
I now have installed a 3rd party scp/sftp Server on the HPE IMC and changed the transfer mode for one of the Aruba CX Switches.
Now the Software update is working.
Of course I have to be aware of the VSX Pairs. I guess I will create to tasks, or manually do tghe update by CLI "vsx update-software boot-bank primary"
HPE IMC and VSF/VSX seems to not interact with each other very well.
And the other question is, why it is not possible to get Aruba CX Software to IMC via Import from Web?
Original Message:
Sent: Jul 22, 2022 06:48 AM
From: Davide Poletto
Subject: HPE IMC Software Import and Update for Aruba CX
Hi Robert, TFTP and "SFTP Server" file transfer modes are supported (Configuration Backup and Restore, Software Upgrade, Compliance Check Task all support TFTP and "SFTP Server" file transfer modes). Are you using TFTP transfer mode?
Original Message:
Sent: Jul 22, 2022 03:14 AM
From: Robert Großmann
Subject: HPE IMC Software Import and Update for Aruba CX
Hello Guys,
We're using HPW IMC (iMC PLAT 7.3 (E0706P11)).
Software Import to Software Library is working fine for Aruba OS (Download from Web) and Software Update is also working fine.
But when I try to Import Software from Web for Aruba CX Switches (6100, 6200, 8325, 8360) then there always the message "no update items found".
So I have downloaded the software files manually and imported them by file to software library.
When I do a Deployment to a Aruba CX Switch this does not work. After rond about 30 Minutes the task for a single Device is "particially succeeded", but the new Device Software has not been uploaded to the Device.
All I can find in the routers log is the following: "Event|4404|LOG_ERR|AMM|1/1|User manager: secondary image update failed via local copy"
All Switches are configured with "ip source-interface all interface vlan8 [vrf MGMT-Switches]".
For all VRF Aware Devices the VPN Instance MGMT-Switches has been set in IMC Options.
Manually upgrading from the switch CLI is working fine, but the automated task from within HPE IMC NOT.
Does anyone have an idea?
Thanks and Kind Regards
Robert