- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re-identify P2V'ed server
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
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
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
тАО02-16-2010 12:38 PM
тАО02-16-2010 12:38 PM
Re-identify P2V'ed server
Is there a way short of deleting a system and rediscovering it to update the details of that system after it has been virtualized. Currently, the details of our virtualized systems still show them supporting SMH, showing their physical serial number, server type etc...
Re-identifying the system does nothing - even though the identify clearly states that the system does NOT support SMH:
Starting identification process...
Checking for known running web servers.
Checking for System Management Home Page and other HP web agents.
The System Management Homepage is not supported on this system.
Checking for WBEM support on system.
This system does not have any SMI-S CIMOM installed
This system doesn't have a server CIMOM installed locally, or cannot connect to it using all credentials specified
Running WBEM rules based identification.
Cannot get ComputerSystem WBEM/WMI data from the system
Running VM Identification.
The system is not a VM Host, or WBEM credentials may not be specified, skipping VM Identification
Running WS-Man identification.
The system did not respond to WS-Management, verify credentials.
Checking for SNMP support on system.
The system responded to a SNMP request, it supports SNMP.
Running SNMP base Cluster identification using common cluster MIB.
This was not a system with the common cluster MIBs supported.
Running HP ProLiant management agent identification
System does not have the SNMP ProLiant Server (foundation) agents installed.
Running HP NetServer identification.
System supports the NetServer SNMP agent, adding system type
Running HP-UX SNMP identification.
System does not have the HPUX SNMP agents installed.
Running SNMP System Type Manager identification.
No matching SNMP System Type Manager rule was found.
Checking for DMI protocol support.
DMI is globally disabled, skipping DMI identification.
Running DMI System Type Manager identification.
DMI is globally disabled, skipping DMI identification.
Running HP-UX DMI identification.
DMI is globally disabled, skipping DMI identification.
Running HP/Compaq Desktop identification.
DMI is globally disabled, skipping DMI identification.
Running HP DMI Desktop identification.
DMI is globally disabled, skipping DMI identification.
Running Generic DMI identification.
DMI is globally disabled, skipping DMI identification.
Running SSH Protocol identification.
The SSH protocol is not supported on this system
Running SSH Identification.
SSH Protocol is not detected; skipped SSH Identification
Running Storage identification.
Did not detect WBEM support on this system. Will not attempt storage identification. If this is a storage host, check WBEM credentials and make sure the providers and CIMOM are operational on the host.
Storage identification completed.
Running HP Service Guard Identification.
Running SNMP Subtypes identification
No additional subtypes found from SNMP
Create bare-metal device nodes if OA is discovered with "Automatic Device discovery" option enabled.
Create bare-metal server node if ILO is discovered with "Automatic Server discovery" option enabled.
Checking if this system is supported by Insight Power Manager.
Insight Power Manager is not supported.
Running VM identification.
VMM is installed, but the system is not a VM Host or may not be configured in VMM
Building system relationships.
Running limited data collection for common attribute.
SMH trust status is false.
Running node communication diagnosis
System identification done with this system.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-16-2010 02:47 PM
тАО02-16-2010 02:47 PM
Re: Re-identify P2V'ed server
Then ensure you have run the identification, discovery and data collection tasks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2010 06:26 AM
тАО02-17-2010 06:26 AM
Re: Re-identify P2V'ed server
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2010 08:10 AM
тАО02-17-2010 08:10 AM
Re: Re-identify P2V'ed server
P2V = Physical 2 Virtual
Rob:
The checkbox is not checked, and I have run both identification and data collection against the system - properties never change.
I don't want to have to delete a system from SIM when I virtualize it just to rediscover it as a VM.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2010 08:15 AM
тАО02-17-2010 08:15 AM
Re: Re-identify P2V'ed server
Nelson
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2010 08:17 AM
тАО02-17-2010 08:17 AM
Re: Re-identify P2V'ed server
The server was virtualized using VMWare Converter - NOT SIM's ProLiant2Virtual process. All agents have been manually uninstalled from the system after the virtualization.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2010 08:24 AM
тАО02-17-2010 08:24 AM
Re: Re-identify P2V'ed server
Nelson
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2010 11:27 AM
тАО02-17-2010 11:27 AM
Re: Re-identify P2V'ed server
I think like others I've deleted and re-added servers after a P2V though. Just seemed quicker than trying to get all of the detail changed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2010 06:18 AM
тАО07-09-2010 06:18 AM
Re: Re-identify P2V'ed server
Where did you locate the cleanup script???
Thanks,
Louis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-12-2010 12:49 PM
тАО07-12-2010 12:49 PM
Re: Re-identify P2V'ed server
In this new configuration, the only 'details' needed are ones coming from WMI for windows boxes. Make sure you have specified the WMI/WBEM credentials on the System's Page for that device. Rerunning the Daily Identification task (default is Daily) and the Data Collection task (every 2 weeks) should go and get all the latest info for the VM at that point.