Hello Team, The st drivers is the OS driver that create drive entries in /dev/rmt . There are 149 device entries under /dev/rmt but when i ran sgscan command then it shows 32 tape deivce entries only. if /dev/rmt shows 149 device entries then there must be 149 tape drives configured at nbu end but it shows only 32 tape devices. Secondly, if i want to rebuild the tape drives then what is the maximum number of target and luns i have to mention.

@wannawin Are you 100% sure that this large number of devices actually exist? It seems to be an aweful lot to be attached to a single host. When there is no Persistent Binding in place, the target numbers may change when the server is rebooted. The tape drives could then be added with new device addresses, while old entries are left in the /dev/rmt tree. Please do the following (procedure is safe because we are only working with symbolic links). # cd /dev/rmt # rm * # devfsadm -C -c tape # ls -l *cbn # ls -l *cbn |wc -l

The sg driver used by NBU on Solaris will by default only add 7 targets per controller and 2 luns per target. It is quite normal to need to rebuild sg drivers on Solaris. See this post for steps that I usually follow: recreate /dev/sg/* on solaris 10 without reboot

There are several entries for under /dev/rmt for each drive. i.e. for /dev/rmt0 there will be: rmt/0lbn rmt/0mbn rmt/0hbn rmt/0cbn So just because there are more entries for the rmt entries - doesn't mean that NetBackup isn't functioning correctly. We will only look or the cbn entities.

Hello Marianne/Deb. Thanks for update.. but my doubt is , if there are 149 device entries in /dev/rmt then it means 149 tape drives should be configured under NBU. But here , only 32 tape drives show in sgscan output . Please find attached out for the same. One more question, dev/rmt shows drives at os level, is it right or wrong..

Please read though my previous post again.............................. An the TN in the link.................. You need to specify large numer of targets, not luns when rebuilding sg driver.

I disagree that xx drive paths = xx drives in NBU ... You can have 100 cbn files in /dev/rmt and one physical tape drive if you really wanted to - it would be pointless, but possile ... Certainly, when I mess around with test servers I sometimes end up with device files that have nothing on the end of them. I'm failrly certain that NBU sends a scsi command during device wizard, if no response, it doesn't configure that path as a drive. Please note, generally with sg these days, it should be run without the mt and ml options, as the config for the drives is via WWN, not target/ lun. Adding the standard mt 15 ml 5 or whatever the TNs generally say is a catch all, trying to get a command that will work in most situations. The problem with this, is that it creates 75 sg files that 'might' have no device, this drastically slows down scan / sgscan / tpautoconf and device wizard, as it scans every path. The correct way (well I believe) , is to create device files and then delete those that are not needed. If the drives/ library are configured via WWN, then you just need sg.build -all option. If this doesn't get all the devices, then the 'missing WWNs need to be added into sg.conf / sg.links files manually. When you are used to sg, it is fairly straightforward, but because there are a few things that can catch you out, it is quite difficult to explain 100% clearly. To answer your question, it does appear you are configure via target/ lun: eg .../st@48,0:cbn So this would be target 48 (but you need to convert this to decimal), lun 0. So find the higherst target number (remember to convert), find the highest lun number and use these values. Then in the sg.links and .conf files, delete the lines that are not needed. I will add this little note ... The strings st@2,0 st@3,0 st@13,1 and st@20,0 at the end of the device paths. These are the scsi target and lun values. Also Note: The target and lun values for "st@?,?" are in hexadecimal format, NOT decimal. I managed to forget that the values are hex a while back, which was slightly embarrasing as I couldn't work out why we couldn't configre the sg driver ... M

Tape drives confusion

22 Replies

Marianne
Level 6
11 years ago
The sg driver used by NBU on Solaris will by default only add 7 targets per controller and 2 luns per target.

It is quite normal to need to rebuild sg drivers on Solaris.

See this post for steps that I usually follow: recreate /dev/sg/* on solaris 10 without reboot
Deb_Wilmot
Level 6
11 years ago
There are several entries for under /dev/rmt for each drive.

i.e. for /dev/rmt0 there will be:

rmt/0lbn
rmt/0mbn
rmt/0hbn
rmt/0cbn

So just because there are more entries for the rmt entries - doesn't mean that NetBackup isn't functioning correctly. We will only look or the cbn entities.
wannawin
Level 6
11 years ago

Hello Marianne/Deb.

Thanks for update.. but my doubt is , if there are 149 device entries in /dev/rmt then it means 149 tape drives should be configured under NBU.

But here , only 32 tape drives show in sgscan output . Please find attached out for the same.

One more question, dev/rmt shows drives at os level, is it right or wrong..
drives.txt5 KB
Marianne
Level 6
11 years ago
Please read though my previous post again..............................

An the TN in the link..................

You need to specify large numer of targets, not luns when rebuilding sg driver.
Marianne
Level 6
11 years ago
@wannawin

Are you 100% sure that this large number of devices actually exist?

It seems to be an aweful lot to be attached to a single host.

When there is no Persistent Binding in place, the target numbers may change when the server is rebooted. The tape drives could then be added with new device addresses, while old entries are left in the /dev/rmt tree.

Please do the following (procedure is safe because we are only working with symbolic links).

# cd /dev/rmt
# rm *
# devfsadm -C -c tape
# ls -l *cbn
# ls -l *cbn |wc -l
mph999
Level 6
11 years ago
I disagree that xx drive paths = xx drives in NBU ...

You can have 100 cbn files in /dev/rmt and one physical tape drive if you really wanted to - it would be pointless, but possile ... Certainly, when I mess around with test servers I sometimes end up with device files that have nothing on the end of them.

I'm failrly certain that NBU sends a scsi command during device wizard, if no response, it doesn't configure that path as a drive.

Please note, generally with sg these days, it should be run without the mt and ml options, as the config for the drives is via WWN, not target/ lun. Adding the standard mt 15 ml 5 or whatever the TNs generally say is a catch all, trying to get a command that will work in most situations. The problem with this, is that it creates 75 sg files that 'might' have no device, this drastically slows down scan / sgscan / tpautoconf and device wizard, as it scans every path.

The correct way (well I believe) , is to create device files and then delete those that are not needed.

If the drives/ library are configured via WWN, then you just need sg.build -all option.

If this doesn't get all the devices, then the 'missing WWNs need to be added into sg.conf / sg.links files manually.

When you are used to sg, it is fairly straightforward, but because there are a few things that can catch you out, it is quite difficult to explain 100% clearly.

To answer your question, it does appear you are configure via target/ lun: eg

.../st@48,0:cbn

So this would be target 48 (but you need to convert this to decimal), lun 0.

So find the higherst target number (remember to convert), find the highest lun number and use these values. Then in the sg.links and .conf files, delete the lines that are not needed.

I will add this little note ...

The strings st@2,0 st@3,0 st@13,1 and st@20,0 at the end of the device paths. These are the scsi target and lun values.

Also Note: The target and lun values for "st@?,?" are in hexadecimal format, NOT decimal.

I managed to forget that the values are hex a while back, which was slightly embarrasing as I couldn't work out why we couldn't configre the sg driver ...

M
wannawin
Level 6
11 years ago
Hello Marianne. what does this command do devfsadm -C -c tape can I run this in production
wannawin
Level 6
11 years ago
Hello Marianne. ls -l *cbn |wc -l 149 # ls -l *cbn lrwxrwxrwx 1 root root 53 Sep 20 13:29 0cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@41,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 100cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@46,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 101cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@47,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 102cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@48,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 103cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@49,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 104cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@4a,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 105cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@4b,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 106cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@4c,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 107cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@4d,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 108cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@4e,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 109cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@6,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 10cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@1d,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 110cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@7,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 111cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@8,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 112cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@a,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 113cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@b,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 114cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@d,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 115cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@e,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 116cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@f,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 117cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@12,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 118cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@15,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 119cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@19,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 11cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@1e,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 120cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@1b,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 121cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@1c,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 122cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@20,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 123cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@22,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 124cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@25,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 125cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@26,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 12:57 126cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@3e,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 12:57 127cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@3f,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 12:58 128cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@45,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 12:58 129cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@4f,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 12cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@1f,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 12:58 130cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@50,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 12:58 131cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@51,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 12:58 132cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@52,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 12:58 133cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@4,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 12:58 134cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@5,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 13:29 135cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@4c,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 13:29 136cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@4d,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 13:29 137cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@4e,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 13:29 138cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@4f,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 13:29 139cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@50,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 13cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@22,0:cbn lrwxrwxrwx 1 root bin 53 Sep 20 13:45 140cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@51,0:cbn lrwxrwxrwx 1 root bin 53 Sep 20 13:45 141cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@52,0:cbn lrwxrwxrwx 1 root root 53 Oct 10 12:05 142cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@53,0:cbn lrwxrwxrwx 1 root root 53 Oct 10 12:05 143cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@54,0:cbn lrwxrwxrwx 1 root root 53 Nov 24 04:23 144cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@17,0:cbn lrwxrwxrwx 1 root root 53 Nov 24 04:23 145cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@53,0:cbn lrwxrwxrwx 1 root root 53 Nov 24 04:23 146cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@54,0:cbn lrwxrwxrwx 1 root root 53 Nov 24 04:23 147cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@55,0:cbn lrwxrwxrwx 1 root root 53 Nov 24 04:23 148cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@56,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 14cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@24,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 15cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@25,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 16cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@26,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 17cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@28,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 18cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@2a,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 19cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@2b,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 13:29 1cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@42,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 20cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@2e,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 21cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@2f,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 22cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@30,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 23cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@31,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 24cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@32,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 25cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@33,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 26cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@34,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 27cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@35,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 28cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@36,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 29cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@37,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 13:29 2cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@44,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 30cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@38,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 31cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@39,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 32cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@3a,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 33cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@3b,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 34cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@3c,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 35cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@3d,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 36cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@40,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 37cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@41,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 38cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@42,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 39cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@44,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 13:29 3cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@45,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 01:47 40cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@0,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 01:47 41cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@1,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 01:47 42cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@2,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 01:47 43cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@3,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 01:47 44cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@9,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 01:47 45cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@c,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 46cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@10,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 47cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@11,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 48cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@13,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 49cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@14,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 13:29 4cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@46,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 50cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@16,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 51cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@17,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 52cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@18,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 53cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@1a,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 54cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@1d,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 55cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@1e,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 56cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@1f,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 57cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@21,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 58cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@23,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 59cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@24,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 13:29 5cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@47,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 60cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@27,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 61cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@28,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 62cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@29,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 63cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@2a,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 64cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@2b,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 65cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@2c,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 66cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@2d,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 67cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@2e,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 68cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@2f,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 69cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@33,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 13:29 6cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@48,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 70cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@38,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 71cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@39,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 72cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@3a,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 73cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@3b,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 74cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@3c,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 75cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@3d,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 76cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@3e,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 77cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@3f,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 78cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@40,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 01:47 79cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@43,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 13:29 7cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@49,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 80cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@0,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 81cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@1,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 82cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@2,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 83cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@3,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 84cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@4,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 85cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@5,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 86cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@6,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 87cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@7,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 88cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@9,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 89cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@a,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 13:29 8cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@4a,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 90cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@c,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 91cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@d,0:cbn lrwxrwxrwx 1 root root 52 Sep 20 11:14 92cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@e,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 93cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@10,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 94cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@11,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 95cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@14,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 96cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@15,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 97cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@16,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 98cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@18,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 11:14 99cbn -> ../../devices/pci@84,2000/fibre-channel@1/st@43,0:cbn lrwxrwxrwx 1 root root 53 Sep 20 13:29 9cbn -> ../../devices/pci@85,2000/fibre-channel@1/st@4b,0:cbn
Mark_Solutions
Level 6
11 years ago
You really need to answer the questions asked of you... the main one being ...

how many drives do you actually have in your tape library

Then we have a starting point - next question is how they are connected - if via fibre (i believe that they are) how are they zoned and do they have multiple paths - because 10 drives with 8 paths each to the server will appear as 80 devices - but only 10 drives in NetBackup

Please read through the above posts and what you have been asked for and we may be able to assist further
Marianne
Level 6
11 years ago

ls -l *cbn |wc -l 149

So, you exectuted the last of the commands that I have suggested.

What about these??

# cd /dev/rmt
# rm *
# devfsadm -C -c tape

Ask your Solaris sysadmin. These commands are safe.

It will delete all the symbolic links in /dev/rmt (rm) and then recreate links for only the devices that actually exist (devfsadm). We ensure that only tape devices are scanned for with -C -c tape.

How many tape drives are REALLY in this environment?
There is NO way that any server can actually manage or use 149 tape drives!