HP ProLiant DL380 HP Insight Server Migration Software for ProLiant User Guide - Page 128

Static IP address cannot be assigned on the destination server while booting using the Boot CD

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

Page 128 highlights

Static IP address cannot be assigned on the destination server while booting using the Boot CD Assigning a static IP address on the destination server might result in an error similar to the following: The IP address xxx.xxx.xxx.xxx you have entered for this network adapter is already assigned to another adapter. This might occur if the IP address is assigned to another network adapter on the destination server. To resolve this issue, assign a different IP address to the network adaptor or reboot the server. Supported storage controllers display Unknown on the Boot CD If the supported storage controllers for P2P or V2P migrations are blocked by the SMP Boot CD, the controller might appear as Unknown. To correct this issue, reset NVRAM on the destination server by completing the following: 1. Reboot destination server. 2. To enter ROM-Based Setup Utility (RBSU) during reboot, press F9. 3. Open Advanced Options, and then select Restore Settings/Erase Boot Disk or Clear NVRAM. 4. Reboot the system using the SMP Boot CD. The proper storage controller name is detected. Auto booting destination server using iLO fails If the destination server does not boot and no error message appears on the application station, then reset the iLO on the destination server, and reboot again. SMP might not detect virtual machines on mapped network drives SMP cannot locate virtual machines stored on mapped network drives if the service does not have access to the network shares. You must manually migrate these disks after a successful migration. Deploy Agent task to Windows fails Performing a Deploy Agent task to Windows for a virtual machine host or an SMP Source Agent might fails, causing the following message to appear: Unable to connect to the remote host. Before performing a deploy agent task, verify the following items: 1. No volumes on that host are mounted from the application station account. If there are volumes mounted from the application station, then delete them from the command window by entering: net use /delete *. 2. The destination IP address does not have the ADMIN$ share available. 3. A firewall was enabled on either the local or remote destination that prevented access to the share ports for network shares. 4. The destination server is unavailable or has ping (echo ICMP) disabled. 5. The user credentials provided have administrative access. If the issue persists, manually deploy the agent. Windows SMP Agent deployment fails SMP Agent might fail deployment because of the following: • Incorrect user name or password-Verify that you have provided valid credentials with administrative rights for the source physical machine for the SMP Agent deployment. NOTE: SMP application station server is not a valid source physical machine for migrations. • The ports reserved for SMP Agent (51124 through 51126) might be used by other processes-These ports are reserved during installation and this issue can usually be resolved with a reboot. If the issue persists, then other processes using the ports must be identified and disabled. • Agent might not be installed. For Windows 2008 Source servers, ensure the agent is installed. 64-bit Windows operating systems are not supported by SMP. • Ensure that there is sufficient disk space for agent to be copied and installed properly. 128 Troubleshooting

  • 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
Static IP address cannot be assigned on the destination server while booting using the Boot CD
Assigning a static IP address on the destination server might result in an error similar to the following:
The IP address xxx.xxx.xxx.xxx you have entered for this network adapter is
already assigned to another adapter.
This might occur if the IP address is assigned to another network adapter on the destination server. To resolve
this issue, assign a different IP address to the network adaptor or reboot the server.
Supported storage controllers display
Unknown
on the Boot CD
If the supported storage controllers for P2P or V2P migrations are blocked by the SMP Boot CD, the controller
might appear as
Unknown
.
To correct this issue, reset NVRAM on the destination server by completing the following:
1.
Reboot destination server.
2.
To enter ROM-Based Setup Utility (RBSU) during reboot, press
F9
.
3.
Open Advanced Options, and then select
Restore Settings/Erase Boot Disk
or
Clear NVRAM
.
4.
Reboot the system using the SMP Boot CD. The proper storage controller name is detected.
Auto booting destination server using iLO fails
If the destination server does not boot and no error message appears on the application station, then reset
the iLO on the destination server, and reboot again.
SMP might not detect virtual machines on mapped network drives
SMP cannot locate virtual machines stored on mapped network drives if the service does not have access
to the network shares. You must manually migrate these disks after a successful migration.
Deploy Agent task to Windows fails
Performing a Deploy Agent task to Windows for a virtual machine host or an SMP Source Agent might fails,
causing the following message to appear:
Unable to connect to the remote host.
Before performing a deploy agent task, verify the following items:
1.
No volumes on that host are mounted from the application station account. If there are volumes mounted
from the application station, then delete them from the command window by entering:
net use /delete *.
2.
The destination IP address does not have the ADMIN$ share available.
3.
A firewall was enabled on either the local or remote destination that prevented access to the share ports
for network shares.
4.
The destination server is unavailable or has ping (echo ICMP) disabled.
5.
The user credentials provided have administrative access.
If the issue persists, manually deploy the agent.
Windows SMP Agent deployment fails
SMP Agent might fail deployment because of the following:
•
Incorrect user name or password—Verify that you have provided valid credentials with administrative
rights for the source physical machine for the SMP Agent deployment.
NOTE:
SMP application station server is not a valid source physical machine for migrations.
•
The ports reserved for SMP Agent (51124 through 51126) might be used by other processes—These
ports are reserved during installation and this issue can usually be resolved with a reboot. If the issue
persists, then other processes using the ports must be identified and disabled.
•
Agent might not be installed. For Windows 2008 Source servers, ensure the agent is installed. 64-bit
Windows operating systems are not supported by SMP.
•
Ensure that there is sufficient disk space for agent to be copied and installed properly.
128
Troubleshooting