HP BL680c HP Virtual Connect Enterprise Manager User Guide - Page 97

Failover fails to initiate with an ERROR (30) - Could not initiate failover; nested exception is: java.net.SocketTimeoutException: Read timed out, VC Profile Failover fails during Onboard Administrator replacement, VCEM cannot power down ProLiant server m

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

Page 97 highlights

4. Replace the VC modules from the enclosure reader interconnect bays. Verify that the network and SAN connections that are wired to the new VC modules are the same as the old connections. 5. If the primary VC Ethernet module was replaced, then you must configure the VC Domain again through virtual Connect. For more information about configuring the VC Domain, see the HP virtual connect for c-Class BladeSystem User Guide. 6. Access the Onboard Administrator web interface for the enclosure to verify that the VC Domain link in the bottom left portion of the screen correctly points to the VC Domain Manager IP address. 7. Perform an HP SIM discovery against the Onboard Administrator IP address. 8. From the VCEM home page, click the VC Domains tab. 9. Select the same VC Domain, and then click Add to VC Domain Group. Wait for the job to complete successfully. Verify that the VC Domain meets the requirements for adding a VC Domain to a VC Domain Group. For more information, see Requirements for adding a VC Domain to a VC Domain Group. Failover fails to initiate with an ERROR (30) - Could not initiate failover; nested exception is: java.net.SocketTimeoutException: Read timed out This error can occur when the CLI cannot communicate to the VCEM SOAP interface. This communication issue can occur when an IP address or hostname lookup takes more than a few minutes to return or when there is a networking issue on the VCEM server. To resolve this issue, verify that the HP SIM system is running properly by logging in and that the IP address or hostname for the source system exists. If the IP address or hostname does not exist, perform an HP SIM discovery. VC Profile Failover fails during Onboard Administrator replacement If an enclosure has two Onboard Administrators with redundancy and one fails, then the redundant Onboard Administrator might take several minutes to take over. The VC Profile Failover operation fails when source or spare bays are associated to an enclosure while the redundant Onboard Administrator is taking place. To resolve this issue: 1. Wait until Onboard Administrator has failed over. Perform an HP SIM discovery to rediscover the new Onboard Administrator IP address. If the address is not rediscovered, see the HP BladeSystem c-Class Onboard Administrator User Guide. 2. If you initiated VC Profile Failover through the VCEM GUI: a. From the VCEM home page, click the Profiles tab. b. Select the server profile to failover and click Failover. The Virtual Connect Enterprise Manager is executing the request message appears. c. Click OK to go to the Jobs page and monitor job progress. VCEM cannot power down ProLiant server model BL465 G1 All VCEM operations that explicitly power down the server (such as VC Profile Failover, Momentary Press or Press and Hold) might not work well for ProLiant server model BL465c G1 unless the Onboard Administrator firmware version is 2.25. If you are managing enclosures that contain ProLiant server model BL465c G1, verify that you use Onboard Administrator firmware version 2.25. After VC Domain is removed from VC Domain Group in VCEM, profile with external-managed status cannot be edited through Virtual Connect Manager This situation occurs when the profile address are not in the released range selected during the remove VC Domain from VC Domain Group or delete entire VC Domain Group operations. To make changes to such server profiles, you must bring the VC Domain again to VCEM control and then update the server profile through the VCEM profile editor. Server profile edit operation fails when target server is powered on If you edit a server profile in VCEM and add, remove, or change an Ethernet network connection, add, remove, or change Fibre Channel SAN connections or change the server profile name, the edit server profile job might fail with the following message in the job details: Troubleshooting 97

  • 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
4.
Replace the VC modules from the enclosure reader interconnect bays. Verify that the network and SAN
connections that are wired to the new VC modules are the same as the old connections.
5.
If the primary VC Ethernet module was replaced, then you must configure the VC Domain again through
virtual Connect. For more information about configuring the VC Domain, see the
HP virtual connect for
c-Class BladeSystem User Guide
.
6.
Access the Onboard Administrator web interface for the enclosure to verify that the VC Domain link in
the bottom left portion of the screen correctly points to the VC Domain Manager IP address.
7.
Perform an HP SIM discovery against the Onboard Administrator IP address.
8.
From the VCEM home page, click the
VC Domains
tab.
9.
Select the same VC Domain, and then click
Add to VC Domain Group
. Wait for the job to complete
successfully.
Verify that the VC Domain meets the requirements for adding a VC Domain to a VC Domain Group.
For more information, see
Requirements for adding a VC Domain to a VC Domain Group
.
Failover fails to initiate with an ERROR (30) - Could not initiate failover; nested
exception is: java.net.SocketTimeoutException: Read timed out
This error can occur when the CLI cannot communicate to the VCEM SOAP interface. This communication
issue can occur when an IP address or hostname lookup takes more than a few minutes to return or when
there is a networking issue on the VCEM server. To resolve this issue, verify that the HP SIM system is running
properly by logging in and that the IP address or hostname for the source system exists. If the IP address or
hostname does not exist, perform an HP SIM discovery.
VC Profile Failover fails during Onboard Administrator replacement
If an enclosure has two Onboard Administrators with redundancy and one fails, then the redundant Onboard
Administrator might take several minutes to take over. The VC Profile Failover operation fails when source
or spare bays are associated to an enclosure while the redundant Onboard Administrator is taking place.
To resolve this issue:
1.
Wait until Onboard Administrator has failed over. Perform an HP SIM discovery to rediscover the new
Onboard Administrator IP address. If the address is not rediscovered, see the
HP BladeSystem c-Class
Onboard Administrator User Guide
.
2.
If you initiated VC Profile Failover through the VCEM GUI:
a.
From the VCEM home page, click the
Profiles
tab.
b.
Select the server profile to failover and click
Failover
. The
Virtual Connect Enterprise
Manager is executing the request
message appears.
c.
Click
OK
to go to the Jobs page and monitor job progress.
VCEM cannot power down ProLiant server model BL465 G1
All VCEM operations that explicitly power down the server (such as VC Profile Failover, Momentary Press
or Press and Hold) might not work well for ProLiant server model BL465c G1 unless the Onboard Administrator
firmware version is 2.25. If you are managing enclosures that contain ProLiant server model BL465c G1,
verify that you use Onboard Administrator firmware version 2.25.
After VC Domain is removed from VC Domain Group in VCEM, profile with
external-managed status cannot be edited through Virtual Connect Manager
This situation occurs when the profile address are not in the released range selected during the remove VC
Domain from VC Domain Group or delete entire VC Domain Group operations. To make changes to such
server profiles, you must bring the VC Domain again to VCEM control and then update the server profile
through the VCEM profile editor.
Server profile edit operation fails when target server is powered on
If you edit a server profile in VCEM and add, remove, or change an Ethernet network connection, add,
remove, or change Fibre Channel SAN connections or change the server profile name, the edit server profile
job might fail with the following message in the job details:
Troubleshooting
97