- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Servers - General
- >
- Who Me Too'd this topic
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
Who Me Too'd this topic
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2020 06:13 AM
06-17-2020 06:13 AM
iLO Amplifier Looses Connection to Servers
I have a subnet that contains an assortment of 30 DL360 G8/G9/G10 servers and I am running iLO Amplifier 1.60 to manage the servers. When I initially discovered the servers I had no problem connecting to the iLOs and performing the inventory. But, every day between 2-5 of the servers are tagged "Unknown" and the Status shows the error "Server not Reachable". Attempted "Refresh" actions will not resolve this problem. If I delete the server and do an immediate Discovery, it comes right back into iLO Amplifier with out any problems.
I did not have this problem when I was running Version 1.55 of the product. This behavior only started when I upgraded to Version 1.60.