Title: The NV driver fails to attach or is not installed automatically - how to use sgen instead
Date: 28/06/06
NV Version: 7. This is the surefire way of getting changers to work on Solaris 8, 9 and 10:
Library devices directly attached to a Solaris 10 (x86) system require that you configure/use the “sgen” driver utility in order to completely add the library device to the NetVault Server (e.g., in order for the NetVault Server to access the library device’s robotic arm when a user adds a library). It is strongly recommended that you accommodate for this issue, prior to installing. Follow the steps below to accomplish this:
1. Log in to the machine to which the device is directly attached and launch a
terminal session. Ensure that the device is recognized by the operating
system, by inputting the following commands:
.. Cfgadm -al
.. Cfgadm -al -o show_FCP_dev XX:WWN
.. Cfgadm -o force_update -c unconfigure/configure XX or XX:WWN or XX:WWN:LUN
2. From the terminal session prompt, navigate to the following directory:
/kernel/drv/
3. In this directory, locate the file “sgen.conf” and open it for editing. Ensure that the sgen driver is configured to attach to the target device (e.g., the “sgen” line of this file should look similar to the folowing: name="sgen" parent="fp" target=0 lun=0;
4. Validate that the sgen driver has successfully created the necessary device files by:
.. Step 1: Checking to ensure that the “/devices” directory exists:
/devices/pci@7c,0/pci1022,7458@2/pci1077,1401/fp@0,0/sgen@w1000000cc4c8m0
.. Step 2: Checking to ensure that the “/dev/scsi/changer” directory
contains the appropriate files and these files have been properly
associated to the target device:
/dev/scsi/changer/c2t1000000cc4c8m0d0
5. Create a symbolic link in the “/dev” directory for the NetVault device file
associated with the hardware path used in the “/dev/scsi/chan
Please refer to the text above
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center