HP ProLiant DL185 HP Insight Server Migration Software for ProLiant User Guide - Page 129

Destination server boots from the SMP boot CD on a manual boot, Migration process

Get HP ProLiant DL185 - G5 Server PDF manuals and user guides View all HP ProLiant DL185 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 129 highlights

• Network on both the source and the SMP station must be properly working. • The root login must be enabled on the destination ESX 3.x host, and root credentials are used for deploying agent to the host. To deploy the agent: 1. Edit the /etc/ssh/sshd_config file. 2. Set PermitRootLogin to yes and ensure it is not commented out. 3. Restart the sshd service. • If you are launching SMP Source Agent to a virtual machine, check the virtual machine console with virtual machine host management console for any errors. The agent success and failures are logged onto system drive\hpsmpagent.log file on the source server. Destination server boots from the SMP boot CD on a manual boot During the migration, when the auto-boot option is chosen to boot the destination server, the application station boots the destination server from the SMP boot CD by connecting the virtual media to the destination iLO. When the migration is canceled by closing the migration wizard, the virtual media remains connected to the destination iLO. You can view a list of IP addresses where virtual media is still connected to the server in the SMP installation directory/bin/iLOIP.lst file. To disconnect these virtual media, enter SMP installation directory/bin/ResetILOVM.cmd -i xxx.xxx.xxx.xxx -u username -p password where xxx.xxx.xxx.xxx is the iLO IP address. Migration process Drivers cannot be installed or injected onto boot disk This error is reported if SMP fails to install or inject device drivers. In most cases, additional information is reported on the destination server. Possible causes for this error include: • The boot partition was not migrated to the boot volume on the destination server. Verify that the boot partition is selected for migration and placed on the boot volume of the destination server. • The network connection failed during driver installation. • The destination server failed or was powered down during driver installation. • The storage controller where the boot partition was placed is not supported. For a complete list of supported controllers, see the HP Insight Server Migration software for ProLiant Support Matrix. • The iSCSI initiator failed to mount the disk. To resolve this issue, reinstall the iSCSI initiator on the application station. Large volumes fail with server thread error Migrating extremely large volumes (larger than 1 TB) can result in a failed migration with the following message: Server Migration failed. Error occurred in server thread; nested exception is: java.lang.OutOfMemoryError. To resolve this issue, increase the size of the Windows paging file. For Windows 2003 1. From the Control Panel, double-click System. 2. In the System Properties window, click the Advanced tab. 3. In the Performance section, click Settings. 4. In the Performance Options window, click the Advanced tab. 5. In the Virtual memory section, click Change. 6. In the Drive [Volume Label] column, select the drive that contains the paging file to be changed. 7. Select Custom size, and then enter a new paging file size in the Initial size (MB) box. 8. Click Set. 9. Click OK until all windows are closed. Troubleshooting 129

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
•
Network on both the source and the SMP station must be properly working.
•
The root login must be enabled on the destination ESX 3.
x
host, and root credentials are used for
deploying agent to the host. To deploy the agent:
1.
Edit the
/etc/ssh/sshd_config
file.
2.
Set
PermitRootLogin
to
yes
and ensure it is not commented out.
3.
Restart the sshd service.
•
If you are launching SMP Source Agent to a virtual machine, check the virtual machine console with
virtual machine host management console for any errors.
The agent success and failures are logged onto system
drive\hpsmpagent.log
file on the source server.
Destination server boots from the SMP boot CD on a manual boot
During the migration, when the
auto-boot
option is chosen to boot the destination server, the application
station boots the destination server from the SMP boot CD by connecting the virtual media to the destination
iLO. When the migration is canceled by closing the migration wizard, the virtual media remains connected
to the destination iLO.
You can view a list of IP addresses where virtual media is still connected to the server in the
SMP
installation directory
/bin/iLOIP.lst
file. To disconnect these virtual media, enter
SMP
installation directory
/bin/ResetILOVM.cmd -i
xxx.xxx.xxx.xxx
-u
username
-p
password
where
xxx.xxx.xxx.xxx
is the iLO IP address.
Migration process
Drivers cannot be installed or injected onto boot disk
This error is reported if SMP fails to install or inject device drivers. In most cases, additional information is
reported on the destination server. Possible causes for this error include:
•
The boot partition was not migrated to the boot volume on the destination server. Verify that the boot
partition is selected for migration and placed on the boot volume of the destination server.
•
The network connection failed during driver installation.
•
The destination server failed or was powered down during driver installation.
•
The storage controller where the boot partition was placed is not supported. For a complete list of
supported controllers, see the
HP Insight Server Migration software for ProLiant Support Matrix
.
•
The iSCSI initiator failed to mount the disk. To resolve this issue, reinstall the iSCSI initiator on the
application station.
Large volumes fail with server thread error
Migrating extremely large volumes (larger than 1 TB) can result in a failed migration with the following
message:
Server Migration failed. Error occurred in server thread; nested exception is:
java.lang.OutOfMemoryError.
To resolve this issue, increase the size of the Windows paging file.
For Windows 2003
1.
From the Control Panel, double-click
System
.
2.
In the
System Properties
window, click the
Advanced
tab.
3.
In the
Performance
section, click
Settings
.
4.
In the
Performance Options
window, click the
Advanced
tab.
5.
In the
Virtual memory
section, click
Change
.
6.
In the
Drive [Volume Label]
column, select the drive that contains the paging file to be changed.
7.
Select
Custom size
, and then enter a new paging file size in the
Initial size (MB)
box.
8.
Click
Set
.
9.
Click
OK
until all windows are closed.
Troubleshooting
129