Integrity Servers
1753783 Members
6898 Online
108799 Solutions
New Discussion

Re: how to identify de-configured CPU from HPUX

 
SOLVED
Go to solution
cpdla
Advisor

how to identify de-configured CPU from HPUX

Hi

 

we have 2 x npars each has 2 x vpars running 11.23.

 

parstatus is showing that cell 0 has 2 cpus deconfigured (2 x dual cores).

 

[CPU Details]

Type : FFFF
Speed : 1000 MHz
CPU Status
=== ======
0 Deconfigured
1 Deconfigured
2 Deconfigured
3 Deconfigured
4 OK
5 OK
6 OK
7 OK

 

does this mean cpu 0 and cpu 1 are deconfigured ?

if not, how can we identify the socket of the cpu (0,1,2 or 3)?

 

thanks

2 REPLIES 2
S_Logan
HPE Pro
Solution

Re: how to identify de-configured CPU from HPUX

Hi ,

 

from the parstatus output, we can say that CPU0 and 1 are deconfigured State:

 

[CPU Details]

Type : FFFF
Speed : 1000 MHz
CPU Status
=== ======
0 Deconfigured
1 Deconfigured
2 Deconfigured
3 Deconfigured
4 OK
5 OK
6 OK
7 OK

 

if it is single core CPU, the numbering will be 0,1,2and 3= all are single physical processor

 

If it is a dual core system ) the CPU numbering would be 0,1 ( Logical processors) for 0 Physical processor and so on..

 

Please run EFI command CPUCONFIG then you will see the deconfigured CPU by slot wise:

 

CPUCONFIG.jpg

 

Also ,Please  run ioscan -fnC processor and update

 

 

HTH,

Surendar

Was the post useful?

Say Thank you by Clicking the WHITE KUDOS! Star.

For HP Guided Troubleshooting; http://www.hp.com/support/hpgt

 

 

I work for HPE

Accept or Kudo


[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
S_Logan
HPE Pro

Re: how to identify de-configured CPU from HPUX

Hi,

 

If it is a dual core system and HT is on ) the CPU numbering would be 0,1,2,3  for 0 Physical processor and so on..

 

HTH,

Surendar

Was the post useful?

Say Thank you by Clicking the WHITE KUDOS! Star.

For HP Guided Troubleshooting; http://www.hp.com/support/hpgt

I work for HPE

Accept or Kudo


[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]