error when detected new lun

[yulianto piyut]

hi,

i have many error messages in syslog.log

Aug 16 00:04:19 Athpux10 vmunix: fcparray_init unsuccessful. Bus Instance number 260 exceeded the maximum allowed (255).
Aug 16 00:04:19 Athpux10 vmunix: wsio_claim init failed isc=0x109a79c00 name=fcparray
Aug 16 00:04:19 Athpux10 vmunix: fcpdev_init unsuccessful. Bus Instance number 261 exceeded the maximum allowed (255).
Aug 16 00:04:19 Athpux10 vmunix: wsio_claim init failed isc=0x109a79c00 name=fcpdev
Aug 16 00:04:19 Athpux10 vmunix: fcpdev_init unsuccessful. Bus Instance number 268 exceeded the maximum allowed (255).
Aug 16 00:04:19 Athpux10 vmunix: wsio_claim init failed isc=0x1053d3c00 name=fcpdev
Aug 16 00:04:19 Athpux10 vmunix: fcparray_init unsuccessful. Bus Instance number 258 exceeded the maximum allowed (255).
Aug 16 00:04:19 Athpux10 vmunix: wsio_claim init failed isc=0x1058d3c00 name=fcparray
Aug 16 00:04:19 Athpux10 vmunix: fcpdev_init unsuccessful. Bus Instance number 259 exceeded the maximum allowed (255).
Aug 16 00:04:19 Athpux10 vmunix: wsio_claim init failed isc=0x1058d3c00 name=fcpdev
Aug 16 00:04:19 Athpux10 vmunix: fcparray_init unsuccessful. Bus Instance number 270 exceeded the maximum allowed (255).
Aug 16 00:04:19 Athpux10 vmunix: wsio_claim init failed isc=0x105994400 name=fcparray
Aug 16 00:04:19 Athpux10 vmunix: fcpdev_init unsuccessful. Bus Instance number 257 exceeded the maximum allowed (255).
Aug 16 00:04:19 Athpux10 vmunix: wsio_claim init failed isc=0x105994400 name=fcpdev
Aug 16 00:04:19 Athpux10 vmunix: fcparray_init unsuccessful. Bus Instance number 264 exceeded the maximum allowed (255).
Aug 16 00:04:19 Athpux10 vmunix: wsio_claim init failed isc=0x1053d3c00 name=fcparray
Aug 16 00:04:19 Athpux10 vmunix: fcpdev_init unsuccessful. Bus Instance number 265 exceeded the maximum allowed (255).
Aug 16 00:04:19 Athpux10 vmunix: wsio_claim init failed isc=0x1053d3c00 name=fcpdev

i don't know what its mean.
anyone know?


-yut-

[Ivan Krastev]

There is an ext_bus 255 instance number limit on HPUX 11.x. from the SCSI II driver. The driver can only address up to 255 HBAs (SCSI or FC virtual).


For more info see KB documents:
KBRC00016497 and
KBRC00013394 - Remapping
ext_bus instances above 255.


regards,
ivan

[yulianto piyut]

thx ivan,

where can i find the KB document and how to configure ext_bus above 255? I found the patches that mentioned about bus instance number. http://www.informatik.uni-frankfurt.de/RBI/hp-service/patches/s700_800/11.X/PHKL_34161.txt

" PHKL_27518:
( SR:8606248351 CR:JAGae14751 )
When the customer exhausts the maximum number of bus
instances (max number is 255) the system hangs.
Sometimes the system panics because of io probe timeout
and continues to panic repeatedly."

[Steven E. Protter]

Shalom,

It means you can't have more than 255 instances without a patch installation.

Here is how to find the doc:

http://itrc.hp.com

Click:
» search technical knowledge base

Pull down the choice
Search by Document ID

Put the two document id's in the prior postin and you should be able to find the docs.

The reason I can't post links is that I'm using a US user id and don't know if you are using a european one. If so, my links would not work anyway.

SEP

[yulianto piyut]

hmm,

i can find the document but i can open it.
" Please check your login status. The content identified requires a support agreement, HP CarePack or warranty. "

i have already login to itrc.

[A. Clay Stephenson]

An itrc login is not sufficient. You must also have a support agreement identifier linked to this login and that means that you are under warranty or a valid support contract which you must pay for. You may have a support agreement but have not linked the identifier(s) in the profile.

You do not have access to the Knowledge Base w/o this.

[Sandy Chen]

Hi,

Check for any unused disk on the sever first, remove it with:

# rmsf -H

last time I remember, there's a lot of unused disk there :D

Regards,
Sandy

[Joelmel Roche]

Hi,

There is an ext_bus 255 instance number limit on HPUX 11.x. The limit comes
from the SCSI II driver. The driver can only address up to 255 HBAs (SCSI or
FC virtual). HP has released a patch to address a known problem which caused
system hangs when the instance number limit was exceeded.

More info about the patch:

PHKL_27518 replaced by [PHKL_27751/PACHRDME/English]
PHKL_27518 Fibre Channel Mass Storage Patch

When the customer exhausts the maximum number of bus
instances (max number is 255) the system hangs.
Sometimes the system panics because of io probe timeout and continues to panic repeatedly.