I forgot to check that out. Will check and get back to you. My problem is that even if the devices do show up in inquire -l, the library will still not be auto configurable. The client site where I am rolling out this want it to be auto-configurable.

Some new background I was just informed about. This problem has cropped up since the customer upgraded nw from 7.0 to 7.4. Pre-upgrade both tape libraries and all drives were visible on inquire and were getting configured using jbconfig. At present jbconfig is only picking up the physical library.

Do you have check st.conf file?
path: /kernel/drv/st.conf and /usr/kernel/drv/st.conf,

I was got the similar problem, while I change my stuck tape drive (LTO3) with the new tape drive, library auto changer become disappear and not work, but I can done Unix command to all drives (12 drives).

Then vendor of tape drive request me to update those files and it works. Based explanation of vendor, it can happened because Networker need sequential tape drive, if not, Networker will failed to using auto changer

Sorry if this not helpful

Regards
Roud

I verified that the lus.conf as of preupgrade and the lus.conf after the upgrade are the same. I tried the lus_add_fp_devs script and got the message that nothing is configured in lus.

Have already verified the st.conf. Thanks anyway.

luss_add_fp_devs won't configure your lus.conf always

First check if your hba is listed in lus.conf and add it if not. Make sure range you specify is the right one.

True ... In any case, the way it turned out was a problem with the lpfc cofiguration. Didn't need to configure lus at all. Thanks a lot for the suggestions.

Hi hari,

We are facing a similar issues. Could you let me know what did u do for the lpfc to resolve the issue.

Danny.