HP Integrity Superdome 2 8-socket HP Integrity Superdome 2 Onboard Administrat - Page 69

Services unavailable, Management Processor access

Page 69 highlights

new partition firmware packages (system firmware) will require a partition reboot to activate, but the timing of such an operation can be done on an individual nPartition basis as determined by the operator to best fit their individual needs. When performing an online complex firmware update, Superdome 2 server management capabilities are inactive, and this is something which operators should keep in mind. It should not be surprising that server management entities throughout the Superdome 2 complex will bear responsibility to update their own firmware Flash ROMs, reboot updated firmware images, and reestablish internal communications with each other, but it is important to remind operators what kinds of management services will become temporarily unavailable at the server level during an online complex firmware update operation. This information is being provided to inform the user of such server management limitations, but will not be a complete listing of all possible consequences which may be encountered during an online complex firmware update. Please note that Superdome 2 systems not already running a firmware bundle released prior to (numbered lower than) 2.2.27 do not possess the capability to perform an online complex firmware update, so it should be understood that updating to a future firmware bundle from firmware release 1.3.1, for example, must be performed with all partitions taken offline, and the xfabric powered off. Services unavailable Superdome 2 server management features are unavailable during the process of an online complex firmware update. System firmware will continue to operate and support the OS running on partitions in the complex, however, certain activities may require system firmware to interact with server management firmware, and these operations will not work during the actual process of executing an online complex firmware update. These partition/complex firmware interactions may either be delayed until after the complex firmware update operation has completed, or may be dropped or only partially used. Legacy sx2000 Superdome systems also supported online update of server management entities (MP, ED, PDHC, CLU), and performing such updates held similar consequences for that platform. The following table shows the major classes of server management services which the OS and applications use during normal runtime and details their Availability or Unavailability during the online complex firmware update process: Service Status during online complex firmware update Management processor access (for example: poweron/off, Unavailable restart, TOC, console, logs) IPMI services Unavailable Console service to OS Unavailable, and some character loss is possible if the buffer fills up System firmware services during boot, shutdown, MCA, Available INIT and CMC logging operations Network management services (SD2 has additional Unavailable services). OS-debugger, HP-SIM XML query, HP-SUM SOAP query, WEBES ws-manage events and query. Management Processor access When an online complex firmware update is initiated, all current users are disconnected from the OA for the duration of the complex firmware update process. This includes all OA CLI and GUI sessions, with one possible exception: If the operator initiates the firmware update from the CLI, then this session will remain active to allow for tracking the progress of the update for all but the last few minutes. The time it takes for a complex firmware update to complete is highly variable based on system size and complexity (bigger systems take longer), and the number of firmware Complex Information: Firmware Management 69

  • 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
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197

new partition firmware packages (system firmware) will require a partition reboot to activate, but
the timing of such an operation can be done on an individual nPartition basis as determined by
the operator to best fit their individual needs.
When performing an online complex firmware update, Superdome 2 server management capabilities
are inactive, and this is something which operators should keep in mind. It should not be surprising
that server management entities throughout the Superdome 2 complex will bear responsibility to
update their own firmware Flash ROMs, reboot updated firmware images, and reestablish internal
communications with each other, but it is important to remind operators what kinds of management
services will become temporarily unavailable at the server level during an online complex firmware
update operation. This information is being provided to inform the user of such server management
limitations, but will not be a complete listing of all possible consequences which may be encountered
during an online complex firmware update.
Please note that Superdome 2 systems not already running a firmware bundle released prior to
(numbered lower than) 2.2.27 do not possess the capability to perform an online complex firmware
update, so it should be understood that updating to a future firmware bundle from firmware release
1.3.1, for example, must be performed with all partitions taken offline, and the xfabric powered
off.
Services unavailable
Superdome 2 server management features are unavailable during the process of an online complex
firmware update. System firmware will continue to operate and support the OS running on partitions
in the complex, however, certain activities may require system firmware to interact with server
management firmware, and these operations will not work during the actual process of executing
an online complex firmware update. These partition/complex firmware interactions may either be
delayed until after the complex firmware update operation has completed, or may be dropped or
only partially used. Legacy sx2000 Superdome systems also supported online update of server
management entities (MP, ED, PDHC, CLU), and performing such updates held similar consequences
for that platform.
The following table shows the major classes of server management services which the OS and
applications use during normal runtime and details their Availability or Unavailability during the
online complex firmware update process:
Status during online complex firmware update
Service
Unavailable
Management processor access (for example: poweron/off,
restart, TOC, console, logs)
Unavailable
IPMI services
Unavailable, and some character loss is possible if the
buffer fills up
Console service to OS
Available
System firmware services during boot, shutdown, MCA,
INIT and CMC logging operations
Unavailable
Network management services (SD2 has additional
services). OS-debugger, HP-SIM XML query, HP-SUM SOAP
query, WEBES ws-manage events and query.
Management Processor access
When an online complex firmware update is initiated, all current users are disconnected from the
OA for the duration of the complex firmware update process. This includes all OA CLI and GUI
sessions, with one possible exception: If the operator initiates the firmware update from the CLI,
then this session will remain active to allow for tracking the progress of the update for all but the
last few minutes. The time it takes for a complex firmware update to complete is highly variable
based on system size and complexity (bigger systems take longer), and the number of firmware
Complex Information: Firmware Management
69