Fujitsu 2000 SERIES User Manual
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6
4.2 Hot add of SB
4.2 Hot add of SB
63
C122-E175-01EN
MemTotal: 65271964 kB
In case that the number of CPU or the size of memory keeps increasing:
It is expected that cause of the delay is the load of the partition. The process of SB hot add can be
completed sooner by reducing the load of the partition.
completed sooner by reducing the load of the partition.
In case that the number of CPU or the size of memory does not increase though they does not reach
expected quantity.
expected quantity.
3. Checking post-process of collaboration program
Process of below messages in /var/log/messages is post-process of the collaboration program.
Dec 17 00:15:47 xxx dp-util[4457]: INFO : 807 : Execute 1
user programs at ADD_POST timing
...
Dec 17 00:15:48 SB-hotplug dp-util[4457]: 10-FJSVdp-util-
kdump-restart : INFO : start
...
Dec 17 00:15:49 SB-hotplug dp-util[4457]: 10-FJSVdp-util-
kdump-restart : INFO : result: 0
...
Dec 17 00:15:49 xxx dp-util[4457]: INFO : 808 : Executed
user programs at ADD_POST timing
user programs at ADD_POST timing
...
Dec 17 00:15:48 SB-hotplug dp-util[4457]: 10-FJSVdp-util-
kdump-restart : INFO : start
...
Dec 17 00:15:49 SB-hotplug dp-util[4457]: 10-FJSVdp-util-
kdump-restart : INFO : result: 0
...
Dec 17 00:15:49 xxx dp-util[4457]: INFO : 808 : Executed
user programs at ADD_POST timing
If “INFO : 808 : Executed user programs at ADD_POST timing” is not output, post-process of the
collaboration program is delayed. Check which collaboration program takes a lot of time by seeing
/var/log/messages and ‘collaboration program name.log’ made in /opt/FJSVdp-util/var/log directory, if any.
The developer of the collaboration program can be confirmed by below rpm command. Ask the developer
about the cause of its delay.
collaboration program is delayed. Check which collaboration program takes a lot of time by seeing
/var/log/messages and ‘collaboration program name.log’ made in /opt/FJSVdp-util/var/log directory, if any.
The developer of the collaboration program can be confirmed by below rpm command. Ask the developer
about the cause of its delay.
(Example) Checking the developer of the collaboration program “10-FJSVdp-util-kdump-restart”
$ rpm -qif /opt/FJSVdp-util/user_command/10-FJSVdp-util-
kdump-restart
...
kdump-restart
...
Rebooting the partition is recommended because SB hot add process has been imperfect state.
4.2.5 Operation after SB hot add
This section describes the process and operations after SB hot add.
After completing DR command operation, check that the quantity of added resources is correct by opening
below files as doing before SB hot add.
After completing DR command operation, check that the quantity of added resources is correct by opening
below files as doing before SB hot add.
-
CPU: /proc/cpuinfo
(Added CPU information is added.)
(Added CPU information is added.)
# grep -c processor /proc/cpuinfo
180
180
-
Memory: /proc/meminfo
(Added memory size is reflected to MemTotal)
(Added memory size is reflected to MemTotal)
# cat /proc/meminfo
MemTotal: 98724424 kB
MemFree: 96825552 kB
Buffers: 30804 kB
：
：
MemTotal: 98724424 kB
MemFree: 96825552 kB
Buffers: 30804 kB
：
：
If below command keeps to be executed, added resources are not reflected. Re-execute the command in
order to reflect added resources.
order to reflect added resources.
- sar
- iostat
- mpstat