Common nPartition Boot Commands and Tasks
From Service processor console (MP or GSP) , we can use the below commands to boot the npartition
1.RS - Reset an nPartition
2.RR - Reset and perform a shutdown for reconfig of an nPartition.
3.BO — Boot the cells assigned to an nPartition past the "waiting at BIB" state and thus begin the nPartition boot phase.
4.TC — Perform a transfer of control reset of an nPartition.
5.PE — Power on or power off a cabinet, cell, or I/O chassis.
From EFI shell - we can use the below commands,
1.bcfg — List and configure the boot options list for the local nPartition.
2.autoboot — List, enable, or disable the nPartition autoboot configuration value.
3.acpiconfig — List and configure the nPartition ACPI configuration setting, which determines whether HP-UX, OpenVMS, Windows, or Linux can boot on the nPartition.
nPartition Modification Tasks
The below tasks commonly performed by the support team on npartion servers, Most of the interview questions are based on this tasks only.
1.Assigning and Unassigning Cells
2.Setting Cell Attributes
3.Setting Core Cell Choices
4.Setting nPartition Boot Paths
5.Renaming an nPartition
6.Removing an nPartition
Assigning and Unassigning Cells
parmodify -p# -a# : To assign (add) or unassign (remove) cells
parmodify -p# -d# :command to remove a cell from the specified nPartition
(-p#, where # is the partition number)
Setting Cell Attributes
parmodify -p# -m# : command to modify cell attributes for a specified nPartition
Setting Core Cell Choices
parmodify -p# -r# -r# :command to specify up to four core cell choices in priority order for a specified nPartition (
Setting nPartition Boot Paths
parmodify -p# -b... -s... -t : command to set boot paths for a specified nPartition
bcfg : On an HP Integrity server you can use the EFI Shell bcfg command to configure boot paths.
Renaming an nPartition
parmodify -p# -P name : command to set the name for a specified nPartition
Removing an nPartition
parremove -p# : command to remove a specified nPartition
From Service processor console (MP or GSP) , we can use the below commands to boot the npartition
1.RS - Reset an nPartition
2.RR - Reset and perform a shutdown for reconfig of an nPartition.
3.BO — Boot the cells assigned to an nPartition past the "waiting at BIB" state and thus begin the nPartition boot phase.
4.TC — Perform a transfer of control reset of an nPartition.
5.PE — Power on or power off a cabinet, cell, or I/O chassis.
From EFI shell - we can use the below commands,
1.bcfg — List and configure the boot options list for the local nPartition.
2.autoboot — List, enable, or disable the nPartition autoboot configuration value.
3.acpiconfig — List and configure the nPartition ACPI configuration setting, which determines whether HP-UX, OpenVMS, Windows, or Linux can boot on the nPartition.
nPartition Modification Tasks
The below tasks commonly performed by the support team on npartion servers, Most of the interview questions are based on this tasks only.
1.Assigning and Unassigning Cells
2.Setting Cell Attributes
3.Setting Core Cell Choices
4.Setting nPartition Boot Paths
5.Renaming an nPartition
6.Removing an nPartition
Assigning and Unassigning Cells
parmodify -p# -a# : To assign (add) or unassign (remove) cells
parmodify -p# -d# :command to remove a cell from the specified nPartition
(-p#, where # is the partition number)
Setting Cell Attributes
parmodify -p# -m# : command to modify cell attributes for a specified nPartition
Setting Core Cell Choices
parmodify -p# -r# -r# :command to specify up to four core cell choices in priority order for a specified nPartition (
Setting nPartition Boot Paths
parmodify -p# -b... -s... -t : command to set boot paths for a specified nPartition
bcfg : On an HP Integrity server you can use the EFI Shell bcfg command to configure boot paths.
Renaming an nPartition
parmodify -p# -P name : command to set the name for a specified nPartition
Removing an nPartition
parremove -p# : command to remove a specified nPartition
Understanding VMSTAT Output - Explained
vmstat is a nice tool, to analyze the Linux / UNIX server performance.
procs memory swap io system cpu
r b swpd free buff cache si so bi bo in cs us sy id wa
2 5 375912 19548 17556 477472 0 1 0 0 1 1 1 0 0 1
0 4 375912 18700 17556 478264 0 0 1044 0 774 1329 8 1 0 91
0 5 375912 17664 17556 479168 0 0 1160 0 764 1110 8 1 0 91
1 8 375912 15836 17568 479796 0 0 1144 840 751 1622 16 7 0 78
0 7 375912 19340 17576 480224 0 0 1224 148 587 1958 17 18 0 65
2 0 375912 18288 17588 481036 0 0 812 0 845 1732 18 3 21 59
0 2 375912 15868 17588 481528 0 0 1012 0 588 941 4 1 5 90
Proc:
-------
r: How many processes are waiting for CPU time.
b: Wait Queue - Process which are waiting for I/O (disk, network, user
input,etc..)
Memory:
-----------
swpd: shows how many blocks are swapped out to disk (paged). Total Virtual
memory usage.
Note: you can see the swap area configured in server using "cat proc/swaps"
free: Idle Memory
buff: Memory used as buffers, like before/after I/O operations
cache: Memory used as cache by the Operating System
Swap:
---------
si: How many blocks per second the operating system is swapping in. i.e
Memory swapped in from the disk (Read from swap area to Memory)
so: How many blocks per second the operating system is swaped Out. i.e
Memory swapped to the disk (Written to swap area and cleared from
Memory)
In Ideal condition, We like to see si and so at 0 most of the time, and we definitely don’t like to see more than 10 blocks per second.
IO:
------
bi: Blocks received from block device - Read (like a hard disk)
bo: Blocks sent to a block device - Write
System:
-------------
in: The number of interrupts per second, including the clock.
cs: The number of context switches per second.
CPU:
--------
us: percentage of cpu used for running non-kernel code. (user time, including
nice time)
sy: percentage of cpu used for running kernel code. (system time - network, IO
interrupts, etc)
id: cpu idle time in percentage.
wa: percentage of time spent by cpu for waiting to IO.
If you used to monitor this data, you can understand how is your server doing during peak usage times.
Note: the memory, swap, and I/O statistics are in blocks, not in bytes. In Linux, blocks are usually 1,024 bytes (1 KB).
procs memory swap io system cpu
r b swpd free buff cache si so bi bo in cs us sy id wa
2 5 375912 19548 17556 477472 0 1 0 0 1 1 1 0 0 1
0 4 375912 18700 17556 478264 0 0 1044 0 774 1329 8 1 0 91
0 5 375912 17664 17556 479168 0 0 1160 0 764 1110 8 1 0 91
1 8 375912 15836 17568 479796 0 0 1144 840 751 1622 16 7 0 78
0 7 375912 19340 17576 480224 0 0 1224 148 587 1958 17 18 0 65
2 0 375912 18288 17588 481036 0 0 812 0 845 1732 18 3 21 59
0 2 375912 15868 17588 481528 0 0 1012 0 588 941 4 1 5 90
Proc:
-------
r: How many processes are waiting for CPU time.
b: Wait Queue - Process which are waiting for I/O (disk, network, user
input,etc..)
Memory:
-----------
swpd: shows how many blocks are swapped out to disk (paged). Total Virtual
memory usage.
Note: you can see the swap area configured in server using "cat proc/swaps"
free: Idle Memory
buff: Memory used as buffers, like before/after I/O operations
cache: Memory used as cache by the Operating System
Swap:
---------
si: How many blocks per second the operating system is swapping in. i.e
Memory swapped in from the disk (Read from swap area to Memory)
so: How many blocks per second the operating system is swaped Out. i.e
Memory swapped to the disk (Written to swap area and cleared from
Memory)
In Ideal condition, We like to see si and so at 0 most of the time, and we definitely don’t like to see more than 10 blocks per second.
IO:
------
bi: Blocks received from block device - Read (like a hard disk)
bo: Blocks sent to a block device - Write
System:
-------------
in: The number of interrupts per second, including the clock.
cs: The number of context switches per second.
CPU:
--------
us: percentage of cpu used for running non-kernel code. (user time, including
nice time)
sy: percentage of cpu used for running kernel code. (system time - network, IO
interrupts, etc)
id: cpu idle time in percentage.
wa: percentage of time spent by cpu for waiting to IO.
If you used to monitor this data, you can understand how is your server doing during peak usage times.
Note: the memory, swap, and I/O statistics are in blocks, not in bytes. In Linux, blocks are usually 1,024 bytes (1 KB).
No comments:
Post a Comment