Important Uses of The prtconf Command

May 13th, 2009

Normally its required to gather important information of unix machines. The prtconf command is specifically used in Aix and Solaris operating systems. The information required normally is:

  1. System model.
  2. Machine serial number.
  3. Processor type, number of processors and clock speed of processors.
  4. Network information.
  5. File system information.
  6. Paging space information.
  7. Devices information.
  8. Total memory size.

The explanation will be on the basis of AIX.
Now, information on prtconf command will be represented in the form of question and answers.

How To Gather General Machine Information
Using the command prtconf alone provides the whole information of machine.
The sample is given below. Some actual values have been replaced with other values for the sake of security.

wiw_labs: $ prtconf

System Model: IBM,9133-55A<
/strong>
Machine Serial Number: 06F865G
Processor Type: PowerPC_POWER5
Number Of Processors: 4
Processor Clock Speed: 1499 MHz
CPU Type: 64-bit
Kernel Type: 64-bit
LPAR Info: 1 galaxy198
Memory Size: 4096 MB
Good Memory Size: 4096 MB
Platform Firmware level: Not Available
Firmware Version: IBM,SF240_338
Console Login: enable
Auto Restart: true
Full Core: false
Network Information
Host Name: galaxy198
IP Address: 192.168.10.29
Sub Netmask: 255.255.255.0
Gateway: 192.168.10.1
Name Server: 192.168.19.28
Domain Name: foo.com
Paging Space Information
Total Paging Space: 8192MB
Percent Used: 1%
Volume Groups Information
==============================================================================
rootvg:
PV_NAME           PV STATE          TOTAL PPs   FREE PPs    FREE DISTRIBUTION
hdisk0            active            525         383         109..24..42..99..109
==============================================================================
INSTALLED RESOURCE LIST
The following resources are installed on the machine.
+/- = Added or deleted from Resource List.
*   = Diagnostic support not available.
Model Architecture: chrp
Model Implementation: Multiple Processor, PCI bus
+ sys0                                                                           System Object
+ sysplanar0                                                                     System Planar
* vio0                                                                           Virtual I/O Bus
* vsa0             U9133.55A.06F865G-V1-C0                                       LPAR Virtual Serial Adapter
* vty0             U9133.55A.06F865G-V1-C0-L0                                    Asynchronous Terminal
* pci2             U787B.001.DNWCF4C-P1                                          PCI Bus
* pci7             U787B.001.DNWCF4C-P1                                          PCI Bus
+ ent2             U787B.001.DNWCF4C-P1-T9                                       2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902)
+ ent3             U787B.001.DNWCF4C-P1-T10                                      2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902)
* pci8             U787B.001.DNWCF4C-P1                                          PCI Bus
+ usbhc0           U787B.001.DNWCF4C-P1                                          USB Host Controller (33103500)
+ usbhc1           U787B.001.DNWCF4C-P1                                          USB Host Controller (33103500)
* pci9             U787B.001.DNWCF4C-P1                                          PCI Bus
+ fcs2             U787B.001.DNWCF4C-P1-C1-T1                                    FC Adapter
* fcnet2           U787B.001.DNWCF4C-P1-C1-T1                                    Fibre Channel Network Protocol Device
* fscsi2           U787B.001.DNWCF4C-P1-C1-T1                                    FC SCSI I/O Controller Protocol Device
+ mem0                                                                           Memory
+ proc0                                                                          Processor
+ proc2                                                                          Processor
+ proc4                                                                          Processor
+ proc6                                                                          Processor

How To Get The Processor Clock Speed
For this issue the command with -s parameter.
wiw_labs: $ prtconf -s

How To Get CPU Type
To know if the cpu type is 32 bit or 64 bit, issue the command with -c parameter.
wiw_labs: $ prtconf -c

How To Know The Type of Kenel
To know which type of kernel is in use 32 bit or 64 bit, issue the command with -k parameter.
wiw_labs: $ prtconf -k

How To Get The LPAR Information of Machine
To know what is the LPAR partition number and partition name, issue with -L.
wiw_labs: $ prtconf -L

If its not LPAR, then “-1 NULL” will be returned.

How To Get The Physical Memory Size of Machine
To know the physical memory size of the machine, issue the command with -m flag.
wiw_labs: $ prtconf -m

How To Get The Details of All Physical Devices of The Machine
To know the Vital Product Data of all physical devices internal or attached to the machine, use -v option.
wiw_labs: $prtconf -v

Almost all of the information gathered by above commands is shown above in the output of prtconf command.

Tags: , , , , ,
Posted in Aix | No Comments »

Comments

Leave a Reply

 Comment Form 

 



More articles from the category: Aix


Important Uses of The prtconf Command

Using the command prtconf alone provides the whole information of machine.
The sample is given below. Some actual values have been replaced with other values for the sake of security.

Why SUID Programs Are Dangerous

SUID programs in Unix based systems are one of the most dangerous things you can every have one your systems. Today I’m gonna discuss the dangers of SUID programs in Unix based system. For system security, often it’s suggested to keep minimum or no suid programs in the systems. Here is a brief introduction and practicle demo of the dangers of SUID programs. I start from the definition and then explain a bit about these programs and then give an example to make you understand.

Working With Network Interfaces

In AIX the network interface works quite similar to other *nix systems. You can enable, disable, detach, delete the network interfaces. Apart from this you can do so many other things with network interfaces in AIX. Here I’m presenting how to work with network interfaces in AIX.

The mkvg FAQs

Here in this post I’m presenting few things in the form of FAQs. The can be used as a ready reference while creating Volume Groups. To know how to create Volume Group read the article: How To Create Volume Group.

How To Create Volume Group

Lots of things need to be considered while creating Volume Groups. In this post I’m presenting various scenarios of Volume Group creation. In the previous post I introduced you to listing of Volume Groups. For the ones interested in fundamentals of Logical Volume Manager read the previous article: Aix Logical Volume Manager A Brief Introduction…

How To List Volume Groups and Their Characteristics

I introduced Volume Groups in one of my previous posts. In this post I’m going to discuss, how to carry out common operations on Volume Groups. For more information you can see the previous article: Aix Logical Volume Manager A Brief Introduction.
Here are few things which I’m gonna discuss in this post:

What is Service Processor And How To Access It

The Service Processor provides the ability to view and change the power-on settings of running system. Service Processor also monitors the operating system to confirm that its running or hanged.

Reorganize Volume Group What Is It And How To Do It?

What is reorganization of a Volume Group and why its needed, is a bit confusing for the system administrators. Here in this article I am explaining it to make it easier for the reader

How To Work With Physical Volumes

I’ve written in my previous posts about introduction to Physical Volumes. There I also discussed some operations to be carried out on Physical Volumes. Now, I’ll be discussing some other operations on Physical Volumes like listing Physical Volumes, Logical Volumes on Physical Volumes, Physical Partitions allocations etc. For more information you can see the previous article: Aix Logical Volume Manager A Brief Introduction.

File Systems In AIX-A Primer

Generally talking, the File Systems are collection of files, directories etc. within a single partition or Logical Volume in a Volume Group. Collecting files and directories from different Logical Volumes or Partitions does not qualify to be named as File System. Aix supports mainly three types of File Systems: JFS, NFS and CDRFS. All these are being discussed here in this article. For more information you can see the previous article: Aix Logical Volume Manager A Brief Introduction

Logical Volume In AIX A Primer

Users can not access directly, the disk space available on Physical Volumes with in Volume Group. In order to access the space available, the users and applications need to access File Systems which are created on Logical Volumes. Therefore to manage Physical Volume space you need to manage Logical Volumes. For more information you can see the previous article: Aix Logical Volume Manager A Brief Introduction….

Volume Group In AIX – A Primer

Volume Group is at the highest level in LVM hierarchy. Hard disks are used as Physical Volumes in LVM. Then Physical partitions are mapped to Logical Partitions. Logical Partitions are combined to Logical Volumes. These Logical Volumes comprise the Volume Group. For more information you can see the previous article: Aix Logical Volume Manager A Brief Introduction..

How Does AIX Deal With Bad Blocks

The biggest concern for any organization using a server is data integrity. The various solutions like Network Attached Storage, Storage Area Networks, high availability servers, online data backup and disaster recovery solutions are among the available solutions.

AIX Logical Volume Manager A Brief Introduction

The storage in Aix can be divided in two layers: Physical and Logical.

On physical level the two things come into picture:

1. Physical Volume(PV).
2. Physical Partition(PP).

On logical level the storage is divided in three parts:

1. Logical Partition(LP).
2. Logical Volume(LV).
3. Volume Group(VG).

Physical Volume In AIX – A Primer

Physical Volume in AIX is a hard drive with special characteristics which are useful for LVM(Logical Volume Control). So, if any hard drive is to be used for LVM purpose, it needs to be made as Physical Volume. Physical Volume has several properties which differentiate it from normal hard drive. These are listed as below…

Introduction To HMC

HMC is a Linux based desktop PC workstation which is dedicated to a number of pSeries servers. It’s is used to manage LPARs. There can be several LPARs or a single full partition on physical pSeries server system…

Dynamically changing LPARs (Video)

The biggest benefit for LPARs is that they can be managed online. The CPU, Memory and adapters can be allocated on the spot without downtime, offcourse due care has to be taken. The process is also referred to as DLPAR. DLPAR is nothing but a daemon which runs on server. The name of the process is IBM.drm. Without this DLPAR is not possible, so far as I know.

Create the first Logical Partition (LPAR) (Video)

So, I thought of bringing a video for you which can give you a live demonstratino video for you. Its about 10 minutes video which demonstrates how to create LPAR on IBM machines using HMC(Hardware Management Console)…

Non Concurrent, Concurrent and Enhanced Concurrent Volume Groups

Often the confusion arises among these types. I am trying to clarify the differences.The terms often apply in clustering scenario.

Non Concurrent VG
In Non Concurrent VG, application runs typically on a single node only and data of VG is accessible to that node only. If however present…

Quorum-What it is and Why is it Needed

The importance of Quorum concept lies in fact that if quorum is enabled and VGDAs fall below 51% then the data on VG may be corrupted if VG remains varied on. Thats why quorum enabled VG is varied off if quorum falls below 51%. This way data is safe on VG because disk

Create the first Logical Partition Video (LPAR)

Creating your first LPAR on the HMC with physical resources and boot it up and accessing the remote console.

Difference between LPAR and VIO Server

VIO server is a special case of LPAR. In this the IOs are all virtual and provided to the partitions on VIO Server. Means IO slots, CPUs and Memory are all virtual. So, how is this done?

CC, CAPP, LSPP and EAL4+

If a system is evaluated according to CC, then it will remain valid only till the specific hardware/software configuration of the system is unchanged. Making any changes to the configuration brings the system in non evaluated state. That simply means that system

Physical Real Virtual and Logical Memory

Sometimes the memory available for operating systems is not enough to carry out all the processes. So, operating system uses the disk space as memory. Thus operating system is tricked to think that it has more memory than it actually has. Som

Difference Between ent0, en0 and et0

The notation ent0 is used to specify the hardware adapter. It has nothing to do with the TCP/IP address. The parameters associated with ent0 can be seen as below: