- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- HP Sum Remote Update through ESXi
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2019 12:30 AM
07-31-2019 12:30 AM
HP Sum Remote Update through ESXi
I am trying to use the Smart Update Manager to remotly update firmware on a dl360 Gen9 on reading the documentation this should be possible using the cli interface so after getting many errors I saught assistance from HPE Support who simply advised to insert the iso to the ilo of the machine and run it from there.
My end goal is to intergrate this as part of a powershell script (of which i have the code to call the smartupdate) but the remote update fails even using the verbose logging it does not give much information.
This is the string that is passed from powershell.
smartupdate /v /s /target **esxi host ip here** /user root /password ***Password Removed*** /vcenter_host *Vcentre IP Here* /vcenter_username **vcentre user** /vcenter_password ***Password Removed*** /use_location E:\
I am using Smart Update Manager 8.4.0."43".33406M.x64
Running this from CMD comes back with Inventory failed for Node - 192.168.21.170 Reason: Inventory Error
Raw Execution Log
START|'SUM 8.4.0."43".33406M.x64'|07-30-2019 05:26:19 pm'
07302019-172619|07302019-172619|0|'IP:0.0.0.0'|0|0|Server: nclconclrds01<br>Current Directory: S:/sum/packages.
07302019-172623|07302019-172623|0|'RP:l2'|2|2|Repository E:/packages: Add failed. *** This comes back as a failure but I can see in the manifest it has done the inventory on the spp packages directory ***
07302019-172655|07302019-172655|0|'IP:0.0.0.0'|0|2|Remote Host *IP Removed*: Host type is VMWARE.
07302019-172707|07302019-172707|0|'IP:0.0.0.0'|0|1|Host*IP Removed*:: Core discovery started.
07302019-172759|07302019-172759|0|'IP:0.0.0.0'|2|1|Host*IP Removed*:: Core discovery failed.
07302019-172759|07302019-172759|0|'IP:0.0.0.0'|2|0|Host*IP Removed*:: Discovery failed. Cannot continue with this host.
07302019-172802|07302019-172802|0|'IP:0.0.0.0'|0|0|Exit code : 3, Exit Message : The node is up-to-date. No update is required.
END|'07-30-2019 05:28:03 pm'
The fustrating thing is the end of this log says all good nothing to do where I know there are firmware packages that need to be ran from this spp on the destination host.
Has anyone had this working?
I am currently targeting an ESXi 6.0 Update 3 host.
KInd Regards
Martin Brown
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2019 10:35 PM
08-01-2019 10:35 PM
Re: HP Sum Remote Update through ESXi
Greetings Martin,
Issue reported: HP SUM displays an inventory error on a VMware node.
Possible Cause: Other processes, such as a backup or process that accesses the registry might be running on the remote
Windows node.
Solution:
1. Shut down the remote process that is accessing the registry, or run SUM locally on the node to perform
inventory and deploy updates.
2. Else try to use a windows machine & run the HP SUM remotely on the esxi host.