10-02-2008
Qlogic HBA card in E450 with errors
I have installed a qlogic HBA card in an E450 Solaris 9 with all the SUNW packages and the latest EPROM version. Configuration reboot was done. An orange light flashes to the right of where the card plugs into the fiber cable after booting, and the following error apprears at the start of the boot sequence, before the Openboot banner appears:
Unimplemented FCode token before address fff0dce9
Warning: Fcode sequence resulted in a net stack depth change of 1
Also the following messages appear during boot up:
WARNING: /pci@1f,4000/scsi@3 (glm0):
SCSI bus DATA IN phase parity error
Target 0 reducing sync. transfer rate
Target 0 disabled wide SCSI mode
Target 0 reverting to async. mode
Can you tell me whether I have a problem with the cable or the card or both? How do I troubleshoot this?
Thanks so much
Margaret
10 More Discussions You Might Find Interesting
1. 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
2. UNIX for Advanced & Expert Users
I have a V490 that has couple internal disks attached to the same dual-port HBA card that I'm planning attach to the SAN for additional storage.
Would I sacrifice performance if I use the same HBA?
Is it better to throw in a new HBA instead? (1 Reply)
Discussion started by: kiem
1 Replies
3. 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
4. Solaris
Hi all
Hope your all well and happy in solaris land :-)
Recently purchased some Qlogic HBA's for a few solaris servers. Was told that you cant have mixed chipsets and as this client is all qlogic, have to have hba's using qlogic.
1) Is that correct ? Cant mix different chipsets of... (0 Replies)
Discussion started by: sbk1972
0 Replies
5. Solaris
Hi all,
New to the world of SAN, so forgive me for any ambigious terminology.
I have a sun 6800 chassis with two domains, both domains connected to a San ancor sanbox ( 2 x Storeedge T3 / Mcdata switch ). Current Qlogic HBA's are 1Gb glc adaptors, version of qlc drivers... (1 Reply)
Discussion started by: sbk1972
1 Replies
6. Solaris
Hi All,
I'm actually trying to configure a Qlogic HBA on a solaris9 connecting in a Brocade SAN. I installed Solaris9 and now trying to look at FC devices..
bash-2.05# luxadm -e port
Found path to 0 HBA ports
bash-2.05# luxadm probe
No Network Array enclosures found in /dev/es... (7 Replies)
Discussion started by: ilan
7 Replies
7. 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
8. Solaris
I have JNI FCE-6460-N fc card , it is detected in OK prompt.....I connected Sun StorEDGE A5000 FC storage.
in OK prompt, PROBE-SCSI-ALL
showing A5000 fc hdds details in ok prompt.....
but in OS level.....not showing the hdd, i tried in DEVFSADM command and FORMAT command not showing A5000... (3 Replies)
Discussion started by: anysystem
3 Replies
9. Red Hat
need to do LUN masking at qlogic HBA level..at RHEL 5.x
I am using qla* module at part of the Unix kernel, it is not OEM drivers that come with the HBA card, so I can't use Sansurfer to do this..
Is there a way to do this at all ??
:wall: (0 Replies)
Discussion started by: ppchu99
0 Replies
10. Red Hat
Hi,
How to determine if HBA card in getting faulty from linux host ? any pointers. (2 Replies)
Discussion started by: saurabh84g
2 Replies
AHA(4) BSD Kernel Interfaces Manual AHA(4)
NAME
aha -- Adaptec SCSI host adapter driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device scbus
device aha
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
aha_load="YES"
In /boot/device.hints:
hint.aha.0.at="isa"
DESCRIPTION
This driver provides access to the SCSI bus connected to the Adaptec AHA-154x and AHA-1640 SCSI host adapters. x is 0 for controllers with-
out a floppy drive and 2 for controllers that have them. For optimum performance, Adaptec AHA-174x controllers should be configured in
enhanced mode and attached via the ahb(4) driver.
One device hint entry for every card to be attached by the system is required. Specific values for the port address, IRQ, and DRQ may be
specified. If wildcard values are used, the driver will query the device for its current settings and use those. If the port address is a
wildcard, the driver consults an internal table of possible port address locations and attaches to the first unattached card it finds. The
possible port addresses for this card are 0x330, 0x334, 0x230, 0x234, 0x130, and 0x134.
The AHA-1640 is an MCA bus card. Since the MCA bus is a self-identifying bus, no setting of hints is required.
HARDWARE
The aha driver supports the following SCSI host adapters:
o Adaptec AHA-154xB
o Adaptec AHA-154xC
o Adaptec AHA-154xCF
o Adaptec AHA-154xCP
o Adaptec AHA-1640
o Adaptec AHA-174x in 154x emulation mode
o DTC 3290 SCSI controller in 1542 emulation mode
o Tekram SCSI controllers in 154x emulation mode
SEE ALSO
ahb(4), ahc(4), aic(4), cd(4), da(4), sa(4), scsi(4)
AUTHORS
The aha driver was ported by M. Warner Losh from the bt driver written by Justin T. Gibbs.
BUGS
The AHA-154xA card does not support residuals on data transfers. As a result, this card is no longer supported.
There have been some reports that the AHA-154xB does not work well under heavy load.
The AHA-154xCP is a plug and play controller. However, its resources are set using the on-board BIOS and cannot be moved. Failures to
attached for this card are often caused when the resources set in the BIOS conflict.
BSD
July 4, 2004 BSD