HP ProLiant DL380 G3 with MSA500 ProLiant DL380 Generation 3 Packaged Cluster - Page 85

server node A, In Service., and server node B becomes active.

Get HP ProLiant DL380 G3 with MSA500 PDF manuals and user guides View all HP ProLiant DL380 G3 with MSA500 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 85 highlights

System Setup and Configuration for Red Hat Linux 7.3 Professional 3. After server node B is active, right-click server node A and select In Service. Again, a window displays as the scripts run to make server node A active. 4. After server node A is active, power off server node A. This initiates a failure and server node B becomes active. There will be a slight pause before server node B takes over. This is normal because it takes a few seconds for server node B to see that the heartbeat signal for server node A is gone. Configuration is now complete. IMPORTANT: If the packaged cluster is being transferred, return to "Setup in the Configuration Fixture" in Chapter 2 or refer to the packaged cluster hardware installation and configuration poster to complete the process. 7-8 HP ProLiant DL380 Generation 3 Packaged Cluster Setup and Installation Guide

  • 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
System Setup and Configuration for Red Hat Linux 7.3 Professional
7-8
HP ProLiant DL380 Generation 3 Packaged Cluster Setup and Installation Guide
3.
After server node B is active, right-click
server node A
and select
In Service.
Again, a window displays as the scripts run to make server node A active.
4.
After server node A is active, power off server node A. This initiates a failure
and server node B becomes active.
There will be a slight pause before server node B takes over. This is normal
because it takes a few seconds for server node B to see that the heartbeat signal
for server node A is gone.
Configuration is now complete.
IMPORTANT:
If the packaged cluster is being transferred, return to “Setup in the
Configuration Fixture” in Chapter 2 or refer to the packaged cluster hardware installation and
configuration poster to complete the process.