HP Integrity rx5670 Windows Integrity nPartition Guide - Page 17

Managing nPartitions using IPMI over LAN, You can run Partition Manager

Get HP Integrity rx5670 PDF manuals and user guides View all HP Integrity rx5670 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 17 highlights

NOTE Introduction Management interface options To secure communication between the client and the server, the IPMI specification uses the MD5 algorithm (RFC1321) to encrypt the IPMI password and to authenticate both the server and the client. Other security mechanisms protect against replay attacks. When the management tool sends a request, the nPartition Provider first downloads a large data structure containing static configuration information about the server from the MP. This allows the Provider to request dynamic information about the server. When an nPartition command accesses a particular complex for the first time using IPMI over LAN, it can take a long time (two minutes or more) to complete, depending on network latency between the PC and the server MP. The nPartition Provider caches the static data and reuses it for subsequent requests so that future command usage will not incur that initial overhead. If the PC is rebooted or the nPartition Provider is restarted, the cached data is lost. The first request to the MP after the restart requires the same initial overhead. Also, IPMI specifies that data be sent as UDP datagrams over the LAN. Note that UDP does not guarantee delivery of individual datagrams. If datagrams fail to arrive in a reasonable amount of time, the nPartition Provider retries a number of times. But if the network connection between the PC and MP is too unreliable or too slow, the provider eventually times out and returns an error. The error is often seen as the message: [X] data is not available, where [X] is a cell, I/O chassis, cabinet, or other element in the complex. The speed and reliability of the network between the management station and the MP has a large effect on the reliability of command execution. When managing remotely via IPMI over a LAN, the management station should be on the same subnet as and physically close to the target complex. If you cannot access the management station directly, you can use a Remote Desktop application or equivalent tool to connect to it from a remote terminal. Managing nPartitions using IPMI over LAN Using IPMI over LAN, you can manage remote nPartitions via the MP. The management tool on the management station communicates directly with the local nPartition Provider. The nPartition Provider then communicates with the MP on the remote complex using IPMI over LAN. You must use IPMI over LAN to manage nPartitions remotely if none of the nPartitions on the target server have been booted or configured yet. To use IPMI over LAN, you must enable IPMI LAN Access at the MP, set the MP IPMI password, and install the nPar tools on your management station. You can then use any of the nPartition management tools to manage your remote nPartitions. Running Partition Manager using IPMI over LAN You can run Partition Manager using IPMI over LAN in one of two ways: • If running Partition Manager on an nPartition: From the Tools menu, select the Switch Complexes task. In the Switch Complexes dialog, enter the hostname or IP address of the MP in the target complex, and type that MP's IPMI password. Chapter 1 17

  • 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
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
Introduction
Management interface options
Chapter 1
17
To secure communication between the client and the server, the IPMI specification uses
the MD5 algorithm (RFC1321) to encrypt the IPMI password and to authenticate both
the server and the client. Other security mechanisms protect against replay attacks.
When the management tool sends a request, the nPartition Provider first downloads a
large data structure containing static configuration information about the server from
the MP. This allows the Provider to request dynamic information about the server.
When an nPartition command accesses a particular complex for the first time using
IPMI over LAN, it can take a long time (two minutes or more) to complete, depending on
network latency between the PC and the server MP.
The nPartition Provider caches the static data and reuses it for subsequent requests so
that future command usage will not incur that initial overhead. If the PC is rebooted or
the nPartition Provider is restarted, the cached data is lost. The first request to the MP
after the restart requires the same initial overhead.
Also, IPMI specifies that data be sent as UDP datagrams over the LAN. Note that UDP
does
not
guarantee delivery of individual datagrams. If datagrams fail to arrive in a
reasonable amount of time, the nPartition Provider retries a number of times. But if the
network connection between the PC and MP is too unreliable or too slow, the provider
eventually times out and returns an error. The error is often seen as the message:
[X]
data is not available
, where
[X]
is a cell, I/O chassis, cabinet, or other element in
the complex.
The speed and reliability of the network between the management station and the MP
has a large effect on the reliability of command execution. When managing remotely via
IPMI over a LAN, the management station should be on the same subnet as and
physically close to the target complex. If you cannot access the management station
directly, you can use a Remote Desktop application or equivalent tool to connect to it
from a remote terminal.
Managing nPartitions using IPMI over LAN
Using IPMI over LAN, you can manage remote nPartitions via the MP. The
management tool on the management station communicates directly with the local
nPartition Provider. The nPartition Provider then communicates with the MP on the
remote complex using IPMI over LAN.
NOTE
You
must
use IPMI over LAN to manage nPartitions remotely if none of the nPartitions
on the target server have been booted or configured yet.
To use IPMI over LAN, you must enable IPMI LAN Access at the MP, set the MP IPMI
password, and install the nPar tools on your management station. You can then use any
of the nPartition management tools to manage your remote nPartitions.
Running Partition Manager using IPMI over LAN
You can run Partition Manager
using IPMI over LAN in one of two ways:
•
If running Partition Manager on an nPartition:
From the
Tools
menu, select the
Switch Complexes
task. In the
Switch Complexes
dialog, enter the hostname or IP address of the MP in the target complex, and type
that MP’s IPMI password.