11-21-2007
"Device Type: ssa-scsi-2" will be an SSA adapter. Ignore that.
Which of the three scsi interfaces is it connected to?
I presume scsi1 has the disks so it would be scsi0 in the pci slot 6 or the other onboard adapter scsi2.
As well as checking for the Atape fileset / driver please post the output of the following:
lscfg -vp l grep -i -p rmt
lsdev -Cs scsi
lsdev -Cc disk
lsdev -Cc tape
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I picked up this library but I cannot get the device to actuate.
How do I make this work with Solaris 7? (2 Replies)
Discussion started by: n9ninchd
2 Replies
2. HP-UX
Hi All,
Hoping that you'll be able to help out on - I've a problem occuring in our backups that's driving me up the wall.
I've got an HP-UX Visualise 6500 as below:
================================
root # uname -a
HP-UX <NAME> B.11.00 A 9000/785 2005956095 two-user license... (2 Replies)
Discussion started by: geralex
2 Replies
3. AIX
I am having my 14 Aix 5.3 servers on bladecenters connected with my Tape Library.
I had a backup scheduled on tape library but after taking backup successfully,
Now,
Question 1:-
I wanted to restore backup but tape library could not recognize the tape and I get I/O error in TSM. I think it... (0 Replies)
Discussion started by: Shrek
0 Replies
4. Solaris
Hi all ,
Anybody has an installation manual for Sun StorageTek C4 tape library . i am trying to do the installation on a Sun Fire V245 .
Thanks a million
cheers
ppass (4 Replies)
Discussion started by: ppass
4 Replies
5. Solaris
Env:
Server : Sparc Ultra-80
OS: Solaris 10
Direct SCSI connection to Library. Terminator connected at the Tape End.
Problem: Unable to see any device file related to Robotic /dev/rsst0.
Unable to see any device file /dev/rmt.
------------
Messages while the machine boots
sst0: No... (3 Replies)
Discussion started by: amqstam
3 Replies
6. AIX
hello,
I am facing this problem when trying to prepare AIX 5.3 for Veritas Backup:
Veritas Software is not able to communicate properly with our tape library
When we tried to run these commands here's the output
# cfgmgr -l fscsi0
# cfgmgr -l fscsi2
# cfgmgr -l fscsi1
cfgmgr:... (3 Replies)
Discussion started by: filosophizer
3 Replies
7. Solaris
Hello,
i am trying to get following configuration up running, but get no access to the library roboter.
Server: SunOS 5.10 Generic_138889-03 i86pc i386 i86pc
DELL TL-2000: 1 Tape: IBM ULT3580-HH4 and Robot: 3573-TL,
connected via ISCSI Bridge (build into the TL)
... (1 Reply)
Discussion started by: austin73
1 Replies
8. Solaris
I am a solaris noob. I have a SPARC enterprise T5120 server which i am trying to connect 1 StorEdge 3300 and 1 StorageWorks MSL2024 tape library. Each device is connecting to 1 pci card on the server. I can see the array when i run the format command but i can't seem to detect the tape library.
... (2 Replies)
Discussion started by: M_Owen
2 Replies
9. Hardware
Team ,
currently I am doing some inventory on our hardware.
I know that the old school IBM 3583 tape drive has some license
feature enable but I dont know where can I check If the feature
currently enable or not on our drive...
Ive checked trough Web Base and Panel base but nowhere I... (0 Replies)
Discussion started by: thermometer
0 Replies
10. Solaris
hi all
please tell me how can i connect SunFire V240 to a SL24 tape library.
is there any slots which i can connect?
can i connect through SCSI port? (1 Reply)
Discussion started by: nikhil kasar
1 Replies
LSDEV(8) Linux System Manual LSDEV(8)
NAME
lsdev - display information about installed hardware
SYNOPSIS
lsdev
DESCRIPTION
lsdev gathers information about your computer's installed hardware from the interrupts, ioports and dma files in the /proc directory, thus
giving you a quick overview of which hardware uses what I/O addresses and what IRQ and DMA channels.
OPTIONS
None.
FILES
/proc/interrupts
IRQ channels.
/proc/ioports
I/O memory addresses.
/proc/dma
DMA channels.
BUGS
lsdev can't always figure out which lines in the three examined files refer to one and the same device, because these files sometimes use
different names for the same piece of hardware. For example, in some kernels the keyboard is referred to as `kbd' in /proc/ioports and as
`keyboard' in /proc/interrupts. This should be fixed in the kernel, not in lsdev (as has indeed happened for this particular example).
The program does however try to match lines by stripping anything after a space or open parenthesis from the name, so that e.g. the
`serial' lines from /proc/interrupts match the `serial(set)' lines from /proc/ioports. This attempt at DWIM might be considered a bug in
itself.
This program only shows the kernel's idea of what hardware is present, not what's actually physically available.
SEE ALSO
procinfo(8).
AUTHOR
Sander van Malssen <svm@kozmix.cistron.nl>
3rd Release 1998-05-31 LSDEV(8)