02-08-2011 06:11 AM
Hi,
I have one media server configured with 6 LTO3 drives coming from Quantum px720.
Now I have zoned 2 more LTO4 drives of I2K from different robot which are not showing up in the media server even after sg rebuild and reconfig reboot. From scli tool I can see the 2 LTO4 drives along with 6 LTO3 drives, yet OS is not able to create the tape device paths for those 2LTO4 drives.
OS version: Solaris 5.8
Netbackup version : NetBackup-Solaris8 6.5.3.1
Let me know if you guys have some ideas and/or am I missing something?
Thanks
Anand Sengar
Solved! Go to Solution.
02-08-2011 06:23 AM
Hi,
You said the O/S is not seeing the drives, do you mean there are no entries in /dev/rmt/ for the new drives? If so, you need to check out your st.conf. NetBackup wont see any devices unless the O/S sees them.
If there are entries in /dev/rmt note down the ids/target/lun numbers and rebuild your sg.conf and sg.links. Then use sg.install to apply the new settings.
02-08-2011 06:23 AM
Hi,
You said the O/S is not seeing the drives, do you mean there are no entries in /dev/rmt/ for the new drives? If so, you need to check out your st.conf. NetBackup wont see any devices unless the O/S sees them.
If there are entries in /dev/rmt note down the ids/target/lun numbers and rebuild your sg.conf and sg.links. Then use sg.install to apply the new settings.
02-08-2011 06:41 AM
There is no entries in /dev/rmt/ for new drives.. what should be checked on st.conf file?
I have 15 targets with 5 luns each in st.conf file. ( I have tried increasing the luns as well .. doesn't help)
Thanks
Anand Sengar
02-08-2011 06:49 AM
Hmmm,
Haven't seen Solaris 8 for a looooooong time. You should be able to check /var/adm/messages to see the new fc devices (tape drives) it discovers as its booting. You'll be able to figure out what the target / lun numbers are via that.
You could also configure persistent binding in your fibre channel card configurations. Then the targets / luns will be determined by you.
02-08-2011 09:12 AM
I agree - Solaris 8 is SO OLD that it's difficult to find any info... Have you checked compatibility? Do you have up-to-date st drivers that support your make/model LTO4?
If you boot with -rv you will see if the devices are seen by the OS at boot time.
Also check the .conf file for your hba in /kernel/drv. For example, qla2300.conf might have a firm requirement for persistent biding, i.e:
# Persistent binding only option.
# 0 = Reports to OS discovery of binded and non-binded devices
# 1 = Reports to OS discovery of persistent binded devices only
hba0-persistent-binding-configuration=1;
02-08-2011 10:25 AM
cfgadm -al
Maybe they are sitting there as "unconfigured"?
02-17-2011 03:03 AM
we have got some progree in this issue by changing the kernel parameter as it was set to 1 and was reporting to OS discovery of persistent binded devices only.
hba1-persistent-binding-configuration=0
We have got the device files created now but still sgscan is only showing one of the LTO4 drive even after sg rebuild.
/dev/rmt/0cbn -> ../../devices/pci@1d,700000/fibre-channel@1/st@1,0:cbn
/dev/rmt/1cbn -> ../../devices/pci@1d,700000/fibre-channel@1/st@2,0:cbn
/dev/rmt/2cbn -> ../../devices/pci@1d,700000/fibre-channel@1/st@3,0:cbn
/dev/rmt/3cbn -> ../../devices/pci@1d,700000/fibre-channel@1/st@4,0:cbn
/dev/rmt/4cbn -> ../../devices/pci@1d,700000/fibre-channel@1/st@5,0:cbn
/dev/rmt/5cbn -> ../../devices/pci@1d,700000/fibre-channel@1/st@6,0:cbn
/dev/rmt/6cbn -> ../../devices/pci@1d,700000/fibre-channel@1/st@7,0:cbn ---- lto4
/dev/rmt/7cbn -> ../../devices/pci@1d,700000/fibre-channel@1/st@8,0:cbn ---- lto4
Anymore suggestions
Andy,
We don't have any unconfigured entry showing up in "cfgadm -al" .
Thanks
Anand Sengar
02-19-2011 09:11 PM
Please upload your sg.conf and sg.links.
Did you perform all the steps in this doc?
http://www.symantec.com/docs/TECH71073
02-23-2011 04:40 AM
Issue resolved.
Below steps resolved the issue:-
1) Changed the persistance binding option back to 1.
2) Mentioned the binding in qla2300.conf file:-
hba1-SCSI-target-id-10-fibre-channel-port-name="5006048452a72d46";
hba1-SCSI-target-id-11-fibre-channel-port-name="5006048452a72d47";
hba1-SCSI-target-id-12-fibre-channel-port-name="5006048452a72d48";
hba1-SCSI-target-id-13-fibre-channel-port-name="5006048452a72d49";
hba1-SCSI-target-id-0-fibre-channel-port-name="500508404416080C";
hba1-SCSI-target-id-1-fibre-channel-port-name="5005084044160901";
hba1-SCSI-target-id-2-fibre-channel-port-name="5005084044160905";
hba1-SCSI-target-id-3-fibre-channel-port-name="5005084044160909";
hba1-SCSI-target-id-4-fibre-channel-port-name="500508404416090d";
hba1-SCSI-target-id-5-fibre-channel-port-name="5005084044160919";
hba1-SCSI-target-id-6-fibre-channel-port-name="500508404416091d";
hba1-SCSI-target-id-9-fibre-channel-port-name="500308c00221104a";
hba1-SCSI-target-id-8-fibre-channel-port-name="500308c002211050";
strangely while putting target-id equal to 7 .. drive was not getting recognized. I changed to 9 and it was visible on NB after the sg rebuild.
Thank you all for your contribution in resolving this issue.
Regards
Anand Sengar
02-23-2011 04:44 AM
Target ID 7 is reserved, you can't use it. Its a SCSI thing....
Glad you got it working, please mark the post that helped you most as the solution.
02-23-2011 12:34 PM
We actually got sg driver to use target 7 - after sg.build step, simply edit sg.links and sg.conf in driver folder to add entries for target 7, followed by sg.install.
Good thimg you added persistent binding - without that you would've battled with incorrect device mappings after each reboot.