Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25
Page 103
... all cables are installed correctly, and that the board type and revision are installed correctly. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqSiHotPlugSlotChassis Server agents 103 A hot plug PCI adapter has been removed from the system. User Action: None. User Action: None. SNMP Trap: cpqSiHotPlugSlotBoardRemoved...
... all cables are installed correctly, and that the board type and revision are installed correctly. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqSiHotPlugSlotChassis Server agents 103 A hot plug PCI adapter has been removed from the system. User Action: None. User Action: None. SNMP Trap: cpqSiHotPlugSlotBoardRemoved...
ProLiant Essentials Foundation Pack Installation Guide
Page 1
.... registered trademarks of optimized ProLiant server drivers, utilities, and management agents. • HP Systems Insight Manager (SIM) - Seventeenth edition (September 2008) Part number 392580-408 Welcome to install required HP Systems Insight Manager and the ProLiant Essentials management tools. This pack supports HP ProLiant ML and DL 300, 500, and 700 servers, HP ProLiant server blades, and the HP BladeSystem c-Class. • SmartStart...
.... registered trademarks of optimized ProLiant server drivers, utilities, and management agents. • HP Systems Insight Manager (SIM) - Seventeenth edition (September 2008) Part number 392580-408 Welcome to install required HP Systems Insight Manager and the ProLiant Essentials management tools. This pack supports HP ProLiant ML and DL 300, 500, and 700 servers, HP ProLiant server blades, and the HP BladeSystem c-Class. • SmartStart...
HP Insight Server Migration Software for ProLiant User Guide
Page 4
Deploying SMP Agent through the HP SIM CMS menu if SMP and HP SIM 5.3 are installed 29 Deploying SMP Agent through the HP SIM CMS Quick Launch ...source server 32 Installing SMP Source Agent on a Windows 2008 Server 34 Restarting the SMP Agent...35 Booting the destination server for P2P, V2P, and X2V (agent-less) migrations 35 Manually booting a physical destination server ... licenses using License Migration Tool 45 5 Using SMP for server migration 47 Concurrent and queued migrations...47 Migration Wizard page...48 Physical-to-ProLiant (P2P) migrations for Windows 49 Preparing for a P2P ...
Deploying SMP Agent through the HP SIM CMS menu if SMP and HP SIM 5.3 are installed 29 Deploying SMP Agent through the HP SIM CMS Quick Launch ...source server 32 Installing SMP Source Agent on a Windows 2008 Server 34 Restarting the SMP Agent...35 Booting the destination server for P2P, V2P, and X2V (agent-less) migrations 35 Manually booting a physical destination server ... licenses using License Migration Tool 45 5 Using SMP for server migration 47 Concurrent and queued migrations...47 Migration Wizard page...48 Physical-to-ProLiant (P2P) migrations for Windows 49 Preparing for a P2P ...
HP Insight Server Migration Software for ProLiant User Guide
Page 5
... prerequisites 82 Performing a V2V migration...82 V2V post-migration tasks...92 Virtual-to-ProLiant (V2P) migrations...93 Preparing for a V2P migration...93 Source physical machine prerequisites...HP SIM 104 HP SIM integration...104 Launching SMP migration through HP SIM 106 Quick Launch details...109 Performing post-migration steps for Windows 2000, Windows 2003, and Windows 2008...some preinstalled HP Microsoft Windows Server 2003 operating systems...123 Corrective action is required for some source servers with HP iLO Management Channel Interface Drivers...123 Source server identification ...
... prerequisites 82 Performing a V2V migration...82 V2V post-migration tasks...92 Virtual-to-ProLiant (V2P) migrations...93 Preparing for a V2P migration...93 Source physical machine prerequisites...HP SIM 104 HP SIM integration...104 Launching SMP migration through HP SIM 106 Quick Launch details...109 Performing post-migration steps for Windows 2000, Windows 2003, and Windows 2008...some preinstalled HP Microsoft Windows Server 2003 operating systems...123 Corrective action is required for some source servers with HP iLO Management Channel Interface Drivers...123 Source server identification ...
HP Insight Server Migration Software for ProLiant User Guide
Page 6
... Virtual Boot CD 126 Manual boot of HP integrated Citrix XenServer fails 126 Mouse does not work after migrating a Hyper-V virtual machine to a ProLiant server........134 Static IP address cannot be assigned on the destination server after migration 134 Virtual machine hosts Integrated... screen 132 SAN-connected destination server displays blue screen 132 Post-migration...132 A PSP installation after confirmation. The event log continuously displays Operation Migration waiting for selection 127 Static IP address cannot be resized from a Windows 2008 application station 130 NTFS resize...
... Virtual Boot CD 126 Manual boot of HP integrated Citrix XenServer fails 126 Mouse does not work after migrating a Hyper-V virtual machine to a ProLiant server........134 Static IP address cannot be assigned on the destination server after migration 134 Virtual machine hosts Integrated... screen 132 SAN-connected destination server displays blue screen 132 Post-migration...132 A PSP installation after confirmation. The event log continuously displays Operation Migration waiting for selection 127 Static IP address cannot be resized from a Windows 2008 application station 130 NTFS resize...
HP Insight Server Migration Software for ProLiant User Guide
Page 17
...check (for example CHKDSK.exe) to the destination server after a migration. • Resizing disks for the boot disk. • The Migration Wizard enables the migration of the source server are migrated using a Windows 2008 application station. The partitions can leave the unsupported ...operating system on the destination server unbootable. Resizing NTFS volumes for Windows migration Under some cases, the volume...
...check (for example CHKDSK.exe) to the destination server after a migration. • Resizing disks for the boot disk. • The Migration Wizard enables the migration of the source server are migrated using a Windows 2008 application station. The partitions can leave the unsupported ...operating system on the destination server unbootable. Resizing NTFS volumes for Windows migration Under some cases, the volume...
HP Insight Server Migration Software for ProLiant User Guide
Page 19
... at least 900 MB • Availability of ports 51124 and 51125 (or ports specified during SMP installation for ProLiant Support Matrix. SMP is compatible with Virtual Machine Management Pack version 3.6. The SMP environment consists of the following ...Server Migration software for agent communications and iLO booting) • Availability of port 51127 • User account credentials with HP SIM 5.3. SMP does not require the application station to be installed on a 32-bit Windows operating system • Microsoft iSCSI Initiator 2.06, 2.07, or 2.08, which you are using Windows 2008...
... at least 900 MB • Availability of ports 51124 and 51125 (or ports specified during SMP installation for ProLiant Support Matrix. SMP is compatible with Virtual Machine Management Pack version 3.6. The SMP environment consists of the following ...Server Migration software for agent communications and iLO booting) • Availability of port 51127 • User account credentials with HP SIM 5.3. SMP does not require the application station to be installed on a 32-bit Windows operating system • Microsoft iSCSI Initiator 2.06, 2.07, or 2.08, which you are using Windows 2008...
HP Insight Server Migration Software for ProLiant User Guide
Page 27
... host, then other simultaneous migrations to any other virtual machine on a Linux operating system that is agent-based, see the HP Insight Server Migration software for ProLiant Support Matrix or see the "Agent-based hypervisors" section. • Linux VM Host Agent-This agent must be launched on...Windows VM Host Agent-This agent must be applied when a destination virtual machine is applied to Windows 2008 servers using the Deploy Agent tab on the source and destination servers. Therefore, verify the proper agent is created on an agent-based virtual machine host running on the ...
... host, then other simultaneous migrations to any other virtual machine on a Linux operating system that is agent-based, see the HP Insight Server Migration software for ProLiant Support Matrix or see the "Agent-based hypervisors" section. • Linux VM Host Agent-This agent must be launched on...Windows VM Host Agent-This agent must be applied when a destination virtual machine is applied to Windows 2008 servers using the Deploy Agent tab on the source and destination servers. Therefore, verify the proper agent is created on an agent-based virtual machine host running on the ...
HP Insight Server Migration Software for ProLiant User Guide
Page 28
... supported Windows migrations Agent-less hypervisors • HP integrated VMware ESXi 3.5 • HP integrated VMware ESXi Update 1 • HP integrated VMware ESXi Update 2 • HP integrated VMware ESXi Update 3 • HP integrated VMware ESXi Update 4 • Citrix XenServer 5.0 • HP integrated Citrix XenServer • Microsoft Hyper-V™ • Microsoft Hyper-V Server 2008 • VMware ESX 3.5 • VMware ESX...
... supported Windows migrations Agent-less hypervisors • HP integrated VMware ESXi 3.5 • HP integrated VMware ESXi Update 1 • HP integrated VMware ESXi Update 2 • HP integrated VMware ESXi Update 3 • HP integrated VMware ESXi Update 4 • Citrix XenServer 5.0 • HP integrated Citrix XenServer • Microsoft Hyper-V™ • Microsoft Hyper-V Server 2008 • VMware ESX 3.5 • VMware ESX...
HP Insight Server Migration Software for ProLiant User Guide
Page 34
...application station. To stop the source agent, on these servers, the agent is connected to Windows 2008 servers using SMP. To unlock the connection between the application station and the source server, access the agent console on the source server. NOTE: After completing a migration, SMP Source Agent no...Windows was used. 4. Installing SMP Source Agent on a Windows 2008 Server Source agents cannot be deployed to SMP Agent on the source page, click Abort and Exit. Record the IP addresses listed for the source server entry when using the Deploy Agent tab on the application station...
...application station. To stop the source agent, on these servers, the agent is connected to Windows 2008 servers using SMP. To unlock the connection between the application station and the source server, access the agent console on the source server. NOTE: After completing a migration, SMP Source Agent no...Windows was used. 4. Installing SMP Source Agent on a Windows 2008 Server Source agents cannot be deployed to SMP Agent on the source page, click Abort and Exit. Record the IP addresses listed for the source server entry when using the Deploy Agent tab on the application station...
HP Insight Server Migration Software for ProLiant User Guide
Page 51
...already running on a common destination disk. NOTE: Source agents cannot be migrated. The boot partition is migrated to be deployed to Windows 2008 servers using NT Boot Loader (NTLDR). Volumes on basic disks. Volumes that the volume containing the active boot partition (which contains the boot.ini...disk. To install SMP Source Agent on the application station wizard. You can only resize NTFS partitions. 3. Select the volumes to -ProLiant (P2P) migrations for Windows 51 Volumes marked as active are selected by default it contains the boot partition and cannot be stored ...
...already running on a common destination disk. NOTE: Source agents cannot be migrated. The boot partition is migrated to be deployed to Windows 2008 servers using NT Boot Loader (NTLDR). Volumes on basic disks. Volumes that the volume containing the active boot partition (which contains the boot.ini...disk. To install SMP Source Agent on the application station wizard. You can only resize NTFS partitions. 3. Select the volumes to -ProLiant (P2P) migrations for Windows 51 Volumes marked as active are selected by default it contains the boot partition and cannot be stored ...
HP Insight Server Migration Software for ProLiant User Guide
Page 57
...ProLiant (P2P) migrations for Linux Preparing for a P2P migration The following example. [boot loader] default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS timeout=30 [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /sos /bootlog /noexecute=optout /fastdetect multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="HP SMP Preserved: Windows Server...migration steps section in this guide, and for Windows 2003, see the Windows 2003 and Windows 2008 post-migration steps section in the following sections list prerequisites for Linux 57 If the Windows ...
...ProLiant (P2P) migrations for Linux Preparing for a P2P migration The following example. [boot loader] default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS timeout=30 [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /sos /bootlog /noexecute=optout /fastdetect multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="HP SMP Preserved: Windows Server...migration steps section in this guide, and for Windows 2003, see the Windows 2003 and Windows 2008 post-migration steps section in the following sections list prerequisites for Linux 57 If the Windows ...
HP Insight Server Migration Software for ProLiant User Guide
Page 69
... Next. 4. If SMP Source Agent is already running on the specified source server. For more information about licensing, see http://www.hp.com/go/migrate. If you select this option, you are migrating a server with an older version of the following options: • To launch SMP ...Source Agent is already running on the application station wizard. NOTE: Source agents cannot be deployed to Windows 2008 servers using Quick Launch, select the proper source server or virtual machine in HP SIM, scroll over Quick Launch, and then select Physical to Virtual Migration (P2V), and then click Next...
... Next. 4. If SMP Source Agent is already running on the specified source server. For more information about licensing, see http://www.hp.com/go/migrate. If you select this option, you are migrating a server with an older version of the following options: • To launch SMP ...Source Agent is already running on the application station wizard. NOTE: Source agents cannot be deployed to Windows 2008 servers using Quick Launch, select the proper source server or virtual machine in HP SIM, scroll over Quick Launch, and then select Physical to Virtual Migration (P2V), and then click Next...
HP Insight Server Migration Software for ProLiant User Guide
Page 83
... To launch SMP using Quick Launch, select the proper source server or virtual machine in HP SIM, scroll over Quick Launch, and then select Virtual to Windows 2008 servers using the Deploy Agent tab on the specified source server. If SMP Source Agent is already running on the application station...installing the SMP Source Agent. 1. For more information about licensing, see http://www.hp.com/go/migrate. Enter the source Server Name or four-part IP address. 2. To install SMP Source Agent on the source server. • Choose the Windows migration type. • Click Virtual to -virtual...
... To launch SMP using Quick Launch, select the proper source server or virtual machine in HP SIM, scroll over Quick Launch, and then select Virtual to Windows 2008 servers using the Deploy Agent tab on the specified source server. If SMP Source Agent is already running on the application station...installing the SMP Source Agent. 1. For more information about licensing, see http://www.hp.com/go/migrate. Enter the source Server Name or four-part IP address. 2. To install SMP Source Agent on the source server. • Choose the Windows migration type. • Click Virtual to -virtual...
HP Insight Server Migration Software for ProLiant User Guide
Page 95
...; Virtual to ProLiant (V2P), select Windows, and then follow the instructions to launch SMP Migration Tools. • To launch SMP using Quick Launch, select the proper source server or virtual machine in HP SIM, scroll over Quick Launch, and then select Virtual to Windows 2008 servers using the Deploy... Agent tab on the specified source server, make sure the Deploy SMP Source Agent checkbox is available, ...
...; Virtual to ProLiant (V2P), select Windows, and then follow the instructions to launch SMP Migration Tools. • To launch SMP using Quick Launch, select the proper source server or virtual machine in HP SIM, scroll over Quick Launch, and then select Virtual to Windows 2008 servers using the Deploy... Agent tab on the specified source server, make sure the Deploy SMP Source Agent checkbox is available, ...
HP Insight Server Migration Software for ProLiant User Guide
Page 110
...to satisfy the criteria to launch SMP migration, then the Quick Launch list does not display the unsupported migration options. • If the selected server or virtual machine meets the criteria, then the SMP application opens in the following conditions exist: • The PSP option was not selected ...Windows 2000 post-migration steps To install PSP with the IP address of the following sections. The HP SmartStart CD home page appears. 110 Using SMP for Windows 2000, Windows 2003, and Windows 2008 This section only applies if either of the selected host added in the local CD drive, or ...
...to satisfy the criteria to launch SMP migration, then the Quick Launch list does not display the unsupported migration options. • If the selected server or virtual machine meets the criteria, then the SMP application opens in the following conditions exist: • The PSP option was not selected ...Windows 2000 post-migration steps To install PSP with the IP address of the following sections. The HP SmartStart CD home page appears. 110 Using SMP for Windows 2000, Windows 2003, and Windows 2008 This section only applies if either of the selected host added in the local CD drive, or ...
HP Insight Server Migration Software for ProLiant User Guide
Page 125
... properties on the application station • A "Client for Microsoft Networks" client must be added to the host. For Windows 2008 Source servers, ensure the agent is installed. 64-bit Windows operating systems are reserved during installation and this issue can usually be resolved with... SELinux is unavailable or has ping (echo ICMP) disabled. 5. 4. If the issue persists, manually deploy the agent. NOTE: SMP application station server is not commented out. 3. Restart the sshd service. • If you have administrative access. To deploy the agent: 1. The agent success ...
... properties on the application station • A "Client for Microsoft Networks" client must be added to the host. For Windows 2008 Source servers, ensure the agent is installed. 64-bit Windows operating systems are reserved during installation and this issue can usually be resolved with... SELinux is unavailable or has ping (echo ICMP) disabled. 5. 4. If the issue persists, manually deploy the agent. NOTE: SMP application station server is not commented out. 3. Restart the sshd service. • If you have administrative access. To deploy the agent: 1. The agent success ...
HP Insight Server Migration Software for ProLiant User Guide
Page 128
...to Windows fails Performing a Deploy Agent task to Windows for P2P or V2P migrations are blocked by completing the following: 1. The destination server is detected. The user credentials provided have the ADMIN$ share available. 3. Reboot the system using the ports must manually migrate these disks ...systems are mounted from the command window by SMP. • Ensure that you have entered for the SMP Agent deployment. For Windows 2008 Source servers, ensure the agent is not a valid source physical machine for migrations. • The ports reserved for SMP Agent (51124 through ...
...to Windows fails Performing a Deploy Agent task to Windows for P2P or V2P migrations are blocked by completing the following: 1. The destination server is detected. The user credentials provided have the ADMIN$ share available. 3. Reboot the system using the ports must manually migrate these disks ...systems are mounted from the command window by SMP. • Ensure that you have entered for the SMP Agent deployment. For Windows 2008 Source servers, ensure the agent is not a valid source physical machine for migrations. • The ports reserved for SMP Agent (51124 through ...
HP Insight Server Migration Software for ProLiant User Guide
Page 130
... 2003 application station. Migration fails to terminate if source server is no longer available during a migration and remain in migration mode. Open the Windows Services Manager, and then restart the SMP application service and the HP SMP Web Service. To resolve this issue, initiate the...following error message appears on the source machine. To roll back the current version: 1. NTFS partitions cannot be resized from a Windows 2008 application station SMP does not resize NTFS partitions when migrating to Scsiport.sys.old. In the Paging file size for Windows 2000 Service ...
... 2003 application station. Migration fails to terminate if source server is no longer available during a migration and remain in migration mode. Open the Windows Services Manager, and then restart the SMP application service and the HP SMP Web Service. To resolve this issue, initiate the...following error message appears on the source machine. To roll back the current version: 1. NTFS partitions cannot be resized from a Windows 2008 application station SMP does not resize NTFS partitions when migrating to Scsiport.sys.old. In the Paging file size for Windows 2000 Service ...
HP Insight Server Migration Software for ProLiant User Guide
Page 144
... with SMP, 104 integration overview, 104 prerequisites for physical-to-ProLiant migration, 49, 58, 67, 81, 94 requirements, 19 I installation overview for SMP, 19 requirements, 19 SMP on the application station, 21 SMP on the HP SIM server, 21 Source Agents on a Windows 2008 Server, 34 troubleshooting, 121 Integrated Components do not install on destination...
... with SMP, 104 integration overview, 104 prerequisites for physical-to-ProLiant migration, 49, 58, 67, 81, 94 requirements, 19 I installation overview for SMP, 19 requirements, 19 SMP on the application station, 21 SMP on the HP SIM server, 21 Source Agents on a Windows 2008 Server, 34 troubleshooting, 121 Integrated Components do not install on destination...