- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Remote Server Management
- >
- Find-HPiLO bug, for non HPE hardware
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
Forums
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
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
08-28-2017 08:30 AM
08-28-2017 08:30 AM
Find-HPiLO bug, for non HPE hardware
Hello,
I'm seeing an odd behaviour for the Find-HPiLO cmdlet (v. 1.4.0.2). When trying to find all remote servers, in a big infrastructure that mixes both HPE and Dell/Lenovo servers, if I execute:
$ilo = Find-HPiLO 10.10.1-254.40 -Timeout 1000
I obtain duplicate rows (with same SPN/UUID and SerialNumber of a previously found HP server), when a non-HPE hardware seats at the .40 IP address of a remote subnet.
It seems the cmdlet still generates an (incorrect) output object, caching a previously found server data.
Has anybody seen the same beahviour ?
Thanks,
Claudio
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2017 10:24 AM
09-12-2017 10:24 AM
Re: Find-HPiLO bug, for non HPE hardware
Hi,
This is a known issue and fix will be available in the next release i.e., iLO 1.5..0.0 version which will be available probably next week or so on the HPE web.
Thanks,
Gokul
HPE PowerShell Expert Team
I am a HPE Employee