11-04-2008
openSuse 10.3 , Emulex HBA
hello, i have a dell Poweredge 2950 ( Server ) and an IBM storage device DS 3000 family ( Storage ) . I am supposed to link the IBM storage device to the Dell Poweredge via "Emulex 4Gb Fibre Channel Host Bus Adapter".
I have put the addapter card in my server and connected it to the storage. When i lspci on my server i get this output :
0c:00.0 Fibre Channel: Emulex Corporation Zephyr-X LightPulse Fibre Channel Host Adapter (rev 02)
So that makes me belive that Suse knows about the adapter card. Problem is i have not been able to make the dell server "see" the storage device via the adapter card ( which is connected using optic fibers ). Another problem is that documantation is kind of scarce and i haven't used anything like this before. Can anyone help me figure this out ? What do i need to do in order to make this work ?
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi there,
does anybody knows/info on compatiblity on Emulex Lightpulse 9000 with IBM 8840 PKU X346 server.
Regards. (0 Replies)
Discussion started by: gagasan_makmur
0 Replies
2. Solaris
Hello,
I am new on solaris. We will connect our sun solaris system to the SAN and add 2 Emulex card on the system (solaris 9).
Who have already done this and can give me the procedure to follow ?
driver to install
multipath
etc...
Thanks in advance
Emmanuel (1 Reply)
Discussion started by: emma32
1 Replies
3. UNIX for Advanced & Expert Users
Hello!
I'm having problems to install Emulex fibrechannel card drivers to a HP DL580 G5 running Solaris 10 x86_64. Any of you guys had this problem or knows the answer? =)
cfgadm gives me the following info, which seems to say that it is ok?
But the card has'nt logged into the switch... (0 Replies)
Discussion started by: Esaia
0 Replies
4. Solaris
Hello...I got a problem here. I have HBAs installed in one of the domains in E20 and I gotta find out the brand and firmware. But when I do a prtconf, I cannot see the HBA. For other servers installed with HBAs, when I do prtconf on them I can see either qlc or em. Can you guys enlighten me how to... (5 Replies)
Discussion started by: xiaochensg
5 Replies
5. Solaris
Helo experts
What is an HBA? How can i know about that on any server?
Thanx in advance... (7 Replies)
Discussion started by: younus_syed
7 Replies
6. Solaris
Hi,
I'm connecting a Solaris 10 server to a Netapp filer with two single port Emulex (Sun StorageTek PCI-X Enterprise 4GB FC HBA) HBAs. After physically installing both these HBAs what do I ned to do within Solaris 10 to enable them and configure them with persistent bindings.
Do I need... (6 Replies)
Discussion started by: gwhelan
6 Replies
7. AIX
Hi All,
SUN emulex HBA card has been installed on P520 box.
When i run the cfgmgr i am getting the following message.
lpar2#cfgmgr
cfgmgr: 0514-621 WARNING: The following device packages are required for
device support but are not currently installed.... (0 Replies)
Discussion started by: b_manu78
0 Replies
8. Filesystems, Disks and Memory
Hope I'm in the right place. I'm in the process of zoning HBA's to my new library environment. Is there a "rule of thumb" for the number of physical tape drives that you zone to an HBA? I don't want to run the risk of overloading an HBA. Any information would be greatly appreciated. Thanks. (2 Replies)
Discussion started by: jwholey
2 Replies
9. Solaris
Hi,
I have a HBA that is currently offline for some unknown reason. The device shows up in the prtdiag -v stating it is okay. How can I bring this back online? It was working okay until recently. It is currently connected to the SAN. Details below.
# fcinfo hba-port
HBA Port WWN:... (7 Replies)
Discussion started by: sparcman
7 Replies
10. Solaris
Hi,
i have a two port hba card in solaris 10 system one of which is disabled. How to enable and configure the other port.
---------- Post updated at 08:17 AM ---------- Previous update was at 03:40 AM ----------
please help :( (7 Replies)
Discussion started by: rishiraaz
7 Replies
usoc(7D) Devices usoc(7D)
NAME
usoc - universal serial optical controller for Fibre Channel arbitrated loop (SOC+) device driver
DESCRIPTION
The Fibre Channel adapter is an SBus card that implements two full duplex Fibre Channel interfaces. Each interface can connect to a Fibre
Channel arbitrated loop (FC-AL). The usoc device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL.
FILES
/kernel/drv/usoc
32-bit ELF kernel module
/kernel/drv/sparcv9/usoc
64-bit ELF kernel module
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |SPARC |
+-----------------------------+-----------------------------+
|Interface stability |Unknown |
+-----------------------------+-----------------------------+
|Availability |SUNWusoc |
+-----------------------------+-----------------------------+
SEE ALSO
fctl(7D), sbus(4), fcp(7D), fp(7D), ssd(7D)
Writing Device Drivers
Fibre Channel Physical and Signaling Interface (FC-PH) ANSI X3.230: 1994
Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.272-1996
Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) NCITS TR-19:1998
Fabric Channel Loop Attachment (FC-FLA), NCITS TR-20:1998
DIAGNOSTICS
The following messages are logged and may also appear on the system console. On the console these messages are preceded by:
usoc%d:
where
usoc%d:
is the per-port instance number of the usoc controller.
Fibre Channel is ONLINE
The Fibre Channel loop is now online.
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: alloc soft state.
Driver did not attach, devices will be inaccessible.
attach failed: bad soft state.
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 20 Jul 1999 usoc(7D)