05-16-2005
You didn't say what the server/workstation model is. If it's a Sun server like a E220R or E420R, then yes, the id's will change if you move the hba. Look for your server manual and refer to the pci slots on the motherboard. The Sun System Handbook site,
http://sunsolve.sun.com/handbook_pub/Systems/ , has diagrams of the motherboards.
Some of the pci slots are 5v, 3.3v or a 3.3v/5v (meaning either voltage pci module will work).
I know that some fiber channel hba's will keep their lun id's when an extra hba card is installed, but you'll have to refer to the hba manual to be sure.
good luck.
10 More Discussions You Might Find Interesting
1. BSD
Hi!
I just wanted to know what network cards are supported in FreeBSD. I have looked at the list of supported cards but I can't find any of them in the stores. Is the list not updated, I would really preciate info about where (in EU, Sweden) I can buy them.
/Peter (2 Replies)
Discussion started by: Barfly.se
2 Replies
2. Solaris
Hi all,
I have a compatibly issues with a new hardware
My config is the following one :
Solaris 10
V490 Hardware
2 X HBA Qlogic 2310f cards
An HP EVA 5000 for storage ...
Veritas VxVM 4.1 MP1
When I reboot my server, VxVM is trying to mount/use the volume before it's... (0 Replies)
Discussion started by: unclefab
0 Replies
3. Solaris
Due to speed mismatch, the server kept crashing. Sun suggests that I need to move the two HBA cards from the 66Mhz to the 33Mhz slots. There are tons of disks that are connected to these HBAs and I have Veritas volume manager.
Does anyone have a list of what I need to do prior/after moving to... (3 Replies)
Discussion started by: kiem
3 Replies
4. Solaris
I've got lots of scsi transport errors on the E2900 - the HBA was replaced once out of curiosity but the problem still exists.
Feb 15 07:03:11 ivsdbch2 scsi: WARNING: /ssm@0,0/pci@18
,600000/SUNW,jfca@1,1/fp@0,0/ssd@w5005076300c889cb,4 (ssd21):
Feb 15 07:03:11 ivsdbch2 SCSI transport... (1 Reply)
Discussion started by: kiem
1 Replies
5. UNIX for Advanced & Expert Users
Hi,
I'm trying to determine which HBA cards are installed on my Solaris 10 (Sun-Fire-V240) machine.
The relevant data I have is below, but from it I cannot ascertain for sure if I have Emulex 10000 or 11000 HBA cards.
Can anyone suggest how to determine my HBA hardware ?
Thanks,
Ron.
... (3 Replies)
Discussion started by: ronbarak
3 Replies
6. Solaris
Hi,
I'm trying to determine which HBA cards are installed on my Solaris 10 (Sun-Fire-V240) machine.
The relevant data I have is below, but from it I cannot ascertain for sure if I have Emulex 10000 or 11000 HBA cards.
Can anyone suggest how to determine my HBA hardware ?
Thanks,
Ron.
... (4 Replies)
Discussion started by: ronbarak
4 Replies
7. SCO
I'm floundering here trying to locate a PCI-E 1x HBA that will support an external tape drive in SCO Openserver 6. I was unable to find anything that would work in the compatible hardware list and a call to Adaptec confirmed that PCI-X would've been a better option for the risers in the Dell 2950... (1 Reply)
Discussion started by: s_mal
1 Replies
8. Solaris
I'm looking for open PCI slots in our array of sun boxes. I need help on how to distinguish if there's an open slot or not using prtdiag and prtconf. Is there a better tool for this? TIA.
Here's my prtdiag -v | grep pci:
pci 66 PCI5 SUNW,qlc-pci1077,2312 (scsi-+
... (9 Replies)
Discussion started by: revzalot
9 Replies
9. BSD
Hi,
The title is a bit misleading, but it seems I can't re-edit the title after creating the post - apologies.
I have been handed a variety of servers, whereas quite a few of these are older FreeBSD (4.8, thank you legacy). I now have one of these servers which has a HBA card installed, and... (0 Replies)
Discussion started by: brightstorm
0 Replies
10. Solaris
How do I find any available PCI slots on a v440?
When I run prtconf, I get the following output? But I am not able to make out whether all the PCI slots are used.
================================= IO Devices =================================
Bus Freq
Brd Type MHz Slot ... (1 Reply)
Discussion started by: jtamminen
1 Replies
LEARN ABOUT HPUX
hba.conf
hba.conf(4) hba.conf(4)
NAME
hba.conf - configuration file for the HBAAPI library
The /etc/hba.conf file is used to specify the Vendor-Specific Libraries that are installed on the system. This file is used by the Common
Library to load the individual VSLs when HBA_LoadLibrary(3HBAAPI) is called. If changes are made to the file while the library is in use,
the library should be freed and reloaded. A version 1 VSL is compatible only with a version 1 Common Library. A version 2 VSL is compatible
with both a version 1 and a version 2 Common Library.
Each VSL entry is a single line of the form:
"name" "library path"
where:
name is the description of library. The library name should be prepended with the domain of the manufacturer of the library.
library path is the absolute path to the shared object library file.
Example 1: Contents of /etc/hba.conf
#
# This file contains names and references to HBA libraries
#
# Format:
#
# <library name> <library pathname>
#
# The library name should be prepended with the domain of
# the manufacturer or driver author.
com.sun.fchba32 /usr/lib/libsun_fc.so.1
com.sun.fchba64 /usr/lib/sparcv9/libsun_fc.so.1
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Standard: FC-MI 1.92 (API |
| |version 1) |
+-----------------------------+-----------------------------+
| |Standard: FC-HBA Version 4 |
| |(API version 2) |
+-----------------------------+-----------------------------+
HBA_LoadLibrary(3HBAAPI), libhbaapi(3LIB), attributes(5)
The HBAAPI is provided in both 32- and 64-bit versions, but only one configuration file is specified. As a result, both 32- and 64-bit VSL
libraries must be specified within the same file. When using the 32-bit Common Library, the 64-bit VSLs will fail to load. When using the
64-bit Common Library, the 32-bit VSLs will fail to load. These failures are silently ignored by the Common Library during normal usage,
but can result in warning messages when running client applications in a debugger.
4 Sep 2003 hba.conf(4)