Dell PowerEdge R830 Integrated Remote Access Controller 8 Version 2.70.70.70 U - Page 101

Monitoring performance index of CPU, memory, and IO modules, and IO modules using web interface

Page 101 highlights

Monitoring performance index of CPU, memory, and IO modules In Dell's 13th generation Dell PowerEdge servers, Intel ME supports Compute Usage Per Second (CUPS) functionality. The CUPS functionality provides real-time monitoring of CPU, memory, and I/O utilization and system-level utilization index for the system. Intel ME allows out-of-band (OOB) performance monitoring and does not consume CPU resources. The Intel ME has a system CUPS sensor that provides computation, memory, and I/O resource utilization values as a CUPS Index. iDRAC monitors this CUPS index for the overall system utilization and also monitors the instantaneous utilization index of the CPU, Memory, and I/O. NOTE: This feature is not supported on PowerEdge R930 servers. The CPU and chipset have dedicated Resource monitoring Counters (RMC). The data from these RMCs is queried to obtain utilization information of system resources. The data from RMCs is aggregated by the node manager to measure the cumulative utilization of each of these system resources that is read from iDRAC using existing intercommunication mechanisms to provide data through out-of-band management interfaces. The Intel sensor representation of performance parameters and index values is for complete physical system. Therefore, the performance data representation on the interfaces is for the complete physical system, even if the system is virtualized and has multiple virtual hosts. To display the performance parameters, the supported sensors must be present in the server. The four system utilization parameters are: • CPU Utilization - Data from RMCs for each CPU core is aggregated to provide cumulative utilization of all the cores in the system. This utilization is based on time spent in active and inactive states. A sample of RMC is taken every six seconds. • Memory Utilization - RMCs measure memory traffic occurring at each memory channel or memory controller instance. Data from these RMCs is aggregated to measure the cumulative memory traffic across all the memory channels on the system. This is a measure of memory bandwidth consumption and not amount of memory utilization. iDRAC aggregates it for one minute, so it may or may not match the memory utilization that other OS tools, such as top in Linux, show. Memory bandwidth utilization that the iDRAC shows is an indication of whether workload is memory intensive or not. • I/O Utilization - There is one RMC per root port in the PCI Express Root Complex to measure PCI Express traffic emanating from or directed to that root port and the lower segment. Data from these RMCs is aggregated for measuring PCI express traffic for all PCI Express segments emanating from the package. This is measure of I/O bandwidth utilization for the system. • System Level CUPS Index - The CUPS index is calculated by aggregating CPU, Memory, and I/O index considering a predefined load factor of each system resource. The load factor depends on the nature of the workload on the system. CUPS Index represents the measurement of the compute headroom available on the server. If the system has a large CUPS Index, then there is limited headroom to place more workload on that system. As the resource consumption decreases, the system's CUPS index decreases. A low CUPS index indicates that there is a large compute headroom and the server can receive new workloads and the server is in a lower power state to reduce power consumption. Workload monitoring can then be applied throughout the data center to provide a high-level and holistic view of the data center's workload, providing a dynamic data center solution. NOTE: The CPU, memory, and I/O utilization indexes are aggregated over one minute. Therefore, if there are any instantaneous spikes in these indexes, they may be suppressed. They are indication of workload patterns not the amount of resource utilization. The IPMI, SEL, and SNMP traps are generated if the thresholds of the utilization indexes are reached and the sensor events are enabled. The sensor event flags are disabled by default. It can be enabled using the standard IPMI interface. The required privileges are: • Login privilege is required to monitor performance data. • Configure privilege is required for setting warning thresholds and reset historical peaks. • Login privilege and Enterprise license are required to read historical statics data. Monitoring performance index for of CPU, memory, and IO modules using web interface To monitor the performance index of CPU, memory, and I/O modules, in the iDRAC web interface, go to Overview > Hardware. The Hardware Overview page displays the following: • Hardware section - Click the required link to view the health of the component. • System Performance section - Displays the current reading and the warning reading for CPU, Memory and I/O utilization index, and system level CUPS index in a graphical view. Viewing iDRAC and managed system information 101

  • 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
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298

Monitoring performance index of CPU, memory,
and IO modules
In Dell’s 13
th
generation Dell PowerEdge servers, Intel ME supports Compute Usage Per Second (CUPS) functionality. The CUPS
functionality provides real-time monitoring of CPU, memory, and I/O utilization and system-level utilization index for the system. Intel ME
allows out-of-band (OOB) performance monitoring and does not consume CPU resources. The Intel ME has a system CUPS sensor that
provides computation, memory, and I/O resource utilization values as a CUPS Index. iDRAC monitors this CUPS index for the overall
system utilization and also monitors the instantaneous utilization index of the CPU, Memory, and I/O.
NOTE:
This feature is not supported on PowerEdge R930 servers.
The CPU and chipset have dedicated Resource monitoring Counters (RMC). The data from these RMCs is queried to obtain utilization
information of system resources. The data from RMCs is aggregated by the node manager to measure the cumulative utilization of each
of these system resources that is read from iDRAC using existing intercommunication mechanisms to provide data through out-of-band
management interfaces.
The Intel sensor representation of performance parameters and index values is for complete physical system. Therefore, the performance
data representation on the interfaces is for the complete physical system, even if the system is virtualized and has multiple virtual hosts.
To display the performance parameters, the supported sensors must be present in the server.
The four system utilization parameters are:
CPU Utilization
— Data from RMCs for each CPU core is aggregated to provide cumulative utilization of all the cores in the system.
This utilization is based on time spent in active and inactive states. A sample of RMC is taken every six seconds.
Memory Utilization
— RMCs measure memory traffic occurring at each memory channel or memory controller instance. Data from
these RMCs is aggregated to measure the cumulative memory traffic across all the memory channels on the system. This is a measure
of memory bandwidth consumption and not amount of memory utilization. iDRAC aggregates it for one minute, so it may or may not
match the memory utilization that other OS tools, such as
top
in Linux, show. Memory bandwidth utilization that the iDRAC shows is
an indication of whether workload is memory intensive or not.
I/O Utilization
— There is one RMC per root port in the PCI Express Root Complex to measure PCI Express traffic emanating from
or directed to that root port and the lower segment. Data from these RMCs is aggregated for measuring PCI express traffic for all PCI
Express segments emanating from the package. This is measure of I/O bandwidth utilization for the system.
System Level CUPS Index
— The CUPS index is calculated by aggregating CPU, Memory, and I/O index considering a predefined
load factor of each system resource. The load factor depends on the nature of the workload on the system. CUPS Index represents
the measurement of the compute headroom available on the server. If the system has a large CUPS Index, then there is limited
headroom to place more workload on that system. As the resource consumption decreases, the system’s CUPS index decreases. A
low CUPS index indicates that there is a large compute headroom and the server can receive new workloads and the server is in a
lower power state to reduce power consumption. Workload monitoring can then be applied throughout the data center to provide a
high-level and holistic view of the data center’s workload, providing a dynamic data center solution.
NOTE:
The CPU, memory, and I/O utilization indexes are aggregated over one minute. Therefore, if there are any
instantaneous spikes in these indexes, they may be suppressed. They are indication of workload patterns not the
amount of resource utilization.
The IPMI, SEL, and SNMP traps are generated if the thresholds of the utilization indexes are reached and the sensor events are enabled.
The sensor event flags are disabled by default. It can be enabled using the standard IPMI interface.
The required privileges are:
Login privilege is required to monitor performance data.
Configure privilege is required for setting warning thresholds and reset historical peaks.
Login privilege and Enterprise license are required to read historical statics data.
Monitoring performance index for of CPU, memory, and IO
modules using web interface
To monitor the performance index of CPU, memory, and I/O modules, in the iDRAC web interface, go to
Overview
>
Hardware
. The
Hardware Overview
page displays the following:
Hardware
section — Click the required link to view the health of the component.
System Performance
section — Displays the current reading and the warning reading for CPU, Memory and I/O utilization index,
and system level CUPS index in a graphical view.
Viewing iDRAC and managed system information
101