Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

Re-identify P2V'ed server

 
Lars Bornich
Frequent Advisor

Re-identify P2V'ed server

Hi guys,

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!
9 REPLIES
Rob Buxton
Honored Contributor

Re: Re-identify P2V'ed server

Under the Tools & Links tab for the server, use Edit System Properties and verify that the option to Prevent Discovery etc. from changing the data is not checked.
Then ensure you have run the identification, discovery and data collection tasks.
Calvin Staples
Frequent Advisor

Re: Re-identify P2V'ed server

My thought is that the virtual to Proliant process left the VMM agents in place and did not install the agents for a physical system. If this is the case I'd run a PSP on the system and make sure all the management agents get installed.
Lars Bornich
Frequent Advisor

Re: Re-identify P2V'ed server

Calvin:
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.
NJK-Work
Honored Contributor

Re: Re-identify P2V'ed server

I have the same problem. I have never been able to re-identify a server after a P2V. I always have to delete the device and re-add it.

Nelson
Lars Bornich
Frequent Advisor

Re: Re-identify P2V'ed server

I don't know if this matters:

The server was virtualized using VMWare Converter - NOT SIM's ProLiant2Virtual process. All agents have been manually uninstalled from the system after the virtualization.
NJK-Work
Honored Contributor

Re: Re-identify P2V'ed server

Same here. I use the VMware Converter exclusively.

Nelson
Rob Buxton
Honored Contributor

Re: Re-identify P2V'ed server

Most servers we're now rebuilding rather than P2V'ing. But when we were P2V'ing we used the HP Product as it removed all of the agents and left a nice clean build. I did find a script called something like p2vcleanup that did a good job of removing most of the agents for those we P2V'ed using vmware converter.
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.
Louis Henninger_1
Regular Advisor

Re: Re-identify P2V'ed server

For Rob B.

Where did you locate the cleanup script???

Thanks,

Louis
Darrin Rawls
Respected Contributor

Re: Re-identify P2V'ed server

After moving a server from PHysical to Virtual (without Insight Control server migration product), you need to manually uninstall the HP Agents (I would suggest removing SNMP at this point too).

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.