HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Problem with ESXi Discovery/Identification
Server Management - Systems Insight Manager
1833758
Members
2627
Online
110063
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
Discussions
Forums
Discussions
back
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
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
04-17-2009 10:29 AM
04-17-2009 10:29 AM
Problem with ESXi Discovery/Identification
Hello Folks,
some days ago I implemented 2 ESX3i Servers (DL380 G5 with HP integrated USB Key) in our data center. All firmware's (including ESXi) were updated to the newest versions available. The servers work fine so far.
Only the integration into SIM is currently a problem. After the intital discovery of the two servers everything seems fine. I can check the hardware state, etc. via the SIM UI. The hostname is correctly shown as the system name.
But after the daily system identification job the system name in SIM changes to the serial number of the system and the monitoring state changes to suspended. There is no possibility to reenable the monitoring or run a further identification task.
This behaviour can also be reproduced through a second identification after inital discovery. The system credentials are entered correctly.
SIM version is 5.3 with Hotfix 1.
Has anyone an idea to solve this problem or can confirm it?
Regards
Dominic
some days ago I implemented 2 ESX3i Servers (DL380 G5 with HP integrated USB Key) in our data center. All firmware's (including ESXi) were updated to the newest versions available. The servers work fine so far.
Only the integration into SIM is currently a problem. After the intital discovery of the two servers everything seems fine. I can check the hardware state, etc. via the SIM UI. The hostname is correctly shown as the system name.
But after the daily system identification job the system name in SIM changes to the serial number of the system and the monitoring state changes to suspended. There is no possibility to reenable the monitoring or run a further identification task.
This behaviour can also be reproduced through a second identification after inital discovery. The system credentials are entered correctly.
SIM version is 5.3 with Hotfix 1.
Has anyone an idea to solve this problem or can confirm it?
Regards
Dominic
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 2025 Hewlett Packard Enterprise Development LP