GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- 3i Hosts disappearing after 'identify systems' tas...
Server Management - Systems Insight Manager
1848503
Members
7158
Online
104030
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
11-09-2009 01:14 AM
11-09-2009 01:14 AM
3i Hosts disappearing after 'identify systems' task runs
Hi - i have 3 ESX3i Hosts running on DL385 G5's. I can discover the hardware ok using the Discovery option and entering credentials for WBEM. Each night however after the 'Identify systems' task runs, the Preferred syatsem name and the Network name of the Host changes to the serial number, and states that 'Monitoring of the system is suspended indefinitely'. Has anyone seen this before or knows how to resolve. Thanks.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2009 01:34 PM
12-16-2009 01:34 PM
Re: 3i Hosts disappearing after 'identify systems' task runs
Maybe same issue as...
http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1391514
The fix is to disable the global option to automatically discover a server when it's ilo is discovered. The reason...apparently a BUG in HPSIM 5.3 SP1 wherein it ALWAYS creates a bare-metal node when identifying an ILO...even if the managed server already exists in HPSIM.
http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1391514
The fix is to disable the global option to automatically discover a server when it's ilo is discovered. The reason...apparently a BUG in HPSIM 5.3 SP1 wherein it ALWAYS creates a bare-metal node when identifying an ILO...even if the managed server already exists in HPSIM.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP