10 More Discussions You Might Find Interesting
1. AIX
i connect an ibm ultrium lto 5 (sas) to an 8204-e8a (v6.1 TL5 SP 1)
then i do an cfgmgr and get message about missing filesets
devices.pciex.1410ca03
devices.pciex.pciexclass.00107
devices.pciex.00107200
devices.pciex.pciex100.72.3
and a few others
i try to find the filesets on the two OS... (1 Reply)
Discussion started by: AIXBlueCat
1 Replies
2. Solaris
Hi all,
this time I'd need a help from an advanced Solaris system admin :rolleyes:
I attached a HP StorageWorks Ultrium 215 Tape Drives - Overview - c00059530 - HP Business Support Center to my Sun E220R and it got recognized immediately (probe-scsi-all).
Now the operating system boot process... (8 Replies)
Discussion started by: pseudocoder
8 Replies
3. Solaris
Hi guys,
I've changed the LTO3 device, but the OS (Solaris10) doesn't feel it.
From the ok> prompt i've launched the probe-scsi-all command and it worked fine because i could see the new device; the from the ok> i booted the system (normal boot, probably a boot -r could be better..) and from... (11 Replies)
Discussion started by: cecco16
11 Replies
4. AIX
I have a p570 running AIX 5.2 ml 10. We just got in a IBM 3582 library. The library is connected directly to the lpar via fibre cable.
I've installed:
Atape.driver 11.7.7.0
atldd.driver 6.8.4.0
After a reboot, I can see the one tape drive:
... (2 Replies)
Discussion started by: BobSmith
2 Replies
5. HP-UX
Please help me >
How to diag the external DVD-ROM drive issue whether it is working or not? on HP 9000 server rp7400
I needed to install HP 11i v1 using external DVD-ROM drive on HP 9000 server rp7400. While boot in CO> “search” command is not showing DVD-ROM device only showing all disks >... (0 Replies)
Discussion started by: tpuser
0 Replies
6. Solaris
Can I do this live? Or, do I need to do a probe-scsi-all after doing a stop/A? (10 Replies)
Discussion started by: jgordon
10 Replies
7. HP-UX
Is any one told me that LTO3 tape Cartridge is compatible with LTO2 Tape Drive. (2 Replies)
Discussion started by: Shawn Paul
2 Replies
8. UNIX for Dummies Questions & Answers
Can anybody help me ? ?
Previously data was taken multi volume LTO Tape backup in Red hat Linux by following command : tar -cvf /dev/rmt/tps6d7v -b 1000 -M filenames , now i try to Restore it in SELS9 by following command : tar -xvf /dev/st1 -b 1000 -M filenames , it extracts only part of the... (0 Replies)
Discussion started by: pramanik
0 Replies
9. AIX
Hey anyone have the hot news on where to find out if This tape will work with my AIX 5.3?
a Dell PV110T ~ AIX
Base Unit:
PV110T,LTO-3,400/800GB,EXT PowerVault 110T, LTO-3 400/800GB, External Drive-R (222-2100)
Hard Drive Controller:
External 4M SCSI Cable VHDCI/68 pin for Tape... (0 Replies)
Discussion started by: Keith Johnson
0 Replies
10. UNIX for Dummies Questions & Answers
Hi Gurus,
I would like to clarify some doubts regarding a backup strategy.
I have been working on various *NIX as AIX,Solaris and Linux.
I would like to design a backup procedure.WOuld it be possible for me to use a single LTO tape device to backup all the different server with different... (2 Replies)
Discussion started by: mickykt
2 Replies
socal(7D) Devices socal(7D)
NAME
socal - Serial Optical Controller for Fibre Channel Arbitrated Loop (SOC+) device driver
SYNOPSIS
socal@sbus-slot,0
DESCRIPTION
The Fibre Channel Host Bus Adapter is an SBus card which implements two full duplex Fibre Channel interfaces. Each Fibre Channel interface
can connect to a Fibre Channel Arbitrated Loop (FC-AL).
The socal device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL.
FILES
/kernel/drv/socal ELF Kernel Module
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |SPARC |
+-----------------------------+-----------------------------+
SEE ALSO
sbus(4), sf(7D), ssd(7D)
Writing Device Drivers
ANSI X3.230-1994, Fibre Channel Physical and Signalling Interface (FC-PH)
ANSI X3.272-1996, Fibre Channel Arbitrated Loop (FC-AL)
Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA)
DIAGNOSTICS
The messages described below may appear on system console in addition to being logged.
On the console, these messages are preceded by:
socal%d: port %a
where %d is the instance number of the socal controller and %a is the port on the host adapter.
Fibre Channel Loop is ONLINE
The Fibre Channel loop is now online.
Fibre Channel Loop is OFFLINE
The Fibre Channel loop is now offline.
attach failed: device in slave-only slot.
Move soc+ card to another slot.
attach failed: bad soft state.
Driver did not attach, devices will be inaccessible.
attach failed: unable to alloc xport struct.
Driver did not attach, devices will be inaccessible.
attach failed: unable to map eeprom
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to map XRAM
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to map registers
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to access status register
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to install interrupt handler
Driver was not able to add the interrupt routine to the kernel. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to access host adapter XRAM
Driver was unable to access device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to write host adapter XRAM
Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: read/write mismatch in XRAM
Driver was unable to verify device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
SunOS 5.10 9 May 1997 socal(7D)