'ioscan -fnC processor' - Shows status "SCAN" ??

[Alex Bradley]

rp3440

We have several identical rp3440 boxes, but this one in particular (sometimes) returns a processor state "SCAN" instead of the usual "CLAIMED" for 2 of its 4 processors. Other times, ioscan returns "CLAIMED" for all 4 processors.

Any idea if the "SCAN" status for a processor indicates an imminent failure or another problem? ioscan man pages weren't entirely helpful.

Thank you,
Alex Bradley

[Devender Khatana]

Hi,

The SCAN result means the node is locked, try later.

The lock here means some interruption. I would suggest to raise a tag and clarify with HP.

HTH,
Devender1111

[Christine Hartman]

I've seen this when the scsi bus is busy or if more than one ioscan is happening at the same time (one than more admin troubleshooting). If this happens often I'd open a call with HP...I don't believe I've seen this cause problems before with anything though? You might try to see if there are any patches out there for ioscan first...I know there are a couple of cum. patches for it.

[Sivakumar TS]

Dear Alex,

Could you check the CPU utilization using ths follwoing command

#sar -u 1 5

are you able to find any relation to tha problem, ie. whether the SCAN status appears only during high CPU utilization period ?

With Regards,

Siva

[Scot Bean · Accepted solution]

It means ioscan is already running on that device.

OnlineDiags, or other live monitoring utilities can do this routinely, I would not worry about it too much, in my experience, this is normal.

[Alex Bradley]

Thanks All..

Scot, I think you're right.. I proved it by running 3 ioscan processes at once:


root:boa# ioscan -fnC processor &
[1] 25961

/var/spool/cron
root:boa# ioscan -fnC processor &
ioscan -fnC processor &
[2] 25974

/var/spool/cron
root:boa# ioscan -fnC processor &
[3] 25975

/var/spool/cron
root:boa# Class I H/W Path Driver S/W State H/W Type Description
===================================================================
processor 0 128 processor CLAIMED PROCESSOR Processor
processor 1 129 processor CLAIMED PROCESSOR Processor
processor 2 152 processor SCAN PROCESSOR Processor
processor 3 153 processor SCAN PROCESSOR Processor
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
processor 0 128 processor CLAIMED PROCESSOR Processor
processor 1 129 processor CLAIMED PROCESSOR Processor
processor 2 152 processor SCAN PROCESSOR Processor
processor 3 153 processor SCAN PROCESSOR Processor
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
processor 0 128 processor CLAIMED PROCESSOR Processor
processor 1 129 processor CLAIMED PROCESSOR Processor
processor 2 152 processor CLAIMED PROCESSOR Processor
processor 3 153 processor CLAIMED PROCESSOR Processor

[3] + Done ioscan -fnC processor &
[2] + Done ioscan -fnC processor &
[1] + Done ioscan -fnC processor &


Now I just have to hunt down the process that's scanning when my script runs..
Thanks again,
Alex

[BhupeshK]

Hi Alex,

I agree with what "Scot Bean" has just mentioned.

when you have multiple "ioscan" scanning the system for CPU's, status of some of the CPU's would be SCAN.

-Bhupesh

[Raj D.]

Hi Alex,

You can try this : to check the cpu's

# echo "selclass qualifier cpu;info;wait;infolog" | /usr/sbin/cstm

Cheers,
Raj.

[Scot Bean]

I will start an enhancement request that the "man ioscan" page will be updated to really describe what SCAN status is.