Hardware HBA problem


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users Hardware HBA problem
# 1  
Old 06-04-2007
Hardware HBA problem

I have worked with Qlogic (Sun) fiber cards a lot and with Emulex fiber cards only a little. Here is the scenario: I have a Sun 490 with 3 Emulex cards in it. A pair are for the 6120 array that is attached, the other is a direct attach so our SAN for Veritas Netbackup to back up the system.I installed the Sun Foundation suite to get all the appropriate drivers installed and these 3 have been working perfectly for quite some time.
However, I recently added a fourth card to access some disk that is being published via the SAN fabric (that I am already attached to for backups!). When I boot the box I see the new wwn number and prtdiag reports the card so I know it is not failed in any way. The SAN disk is supposedly published correctly and I should be able to just do a devfsadm and see the new device in format. It does not show up. I know cfgadm will not report it because it is a non-Sun card. What other tools would be available to see out on the network to check the availability of the SAN disk other than just running devfsadm and hoping it will work? The system did reboot over the weekend but a reconfig was not issued, just a normal reboot - I'm wondering if a reboot -- -r would fix this problem. The SAN people tell me that their disk should be published correctly and I verified no switches/fwalls are blocking it (of course it is a direct attach to the SAN fabric, nothing should be).
Any ideas how to troubleshoot this?
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Extracting HBA Card Hardware info

Hello, I am very new to solaris so please bear with me. I have 2 machines in question. For both I am trying to get the HBA Card Hardware information such as: HBA Model Name HBA Firmware version HBA Port details HBA Driver details First machine is a Solaris 10. When I execute fcinfo... (6 Replies)
Discussion started by: flagman5
6 Replies

2. Solaris

HBA problem...? at SF V890

Dear All, I need your help. I have server like this SunOS 5.10 Generic_141444-09 sun4u sparc SUNW,Sun-Fire-V890 with messages like this... Oct 10 17:07:52 iscsi: NOTICE: unrecognized ioctl 0x403 Oct 10 17:07:52 scsi: WARNING: /pseudo/fcp@0 (fcp0): Oct 10 17:07:52 Invalid... (4 Replies)
Discussion started by: mbah_jiman
4 Replies

3. Solaris

Hardware Problem

Dear: the Cureent PC Dell GX620 the Current Hardware 4 GB ram 80 HDD what i do remove old 4GB ram and install 8 GB remove old HDD and install new on 160GB try to install the Unix Sun Solaris after booting and when arrive to step which i should select interactive error meg... (7 Replies)
Discussion started by: hosney00ux
7 Replies

4. HP-UX

Hardware problem diagnosing

Hey guys how to do diagnose HP-UX for hardware problems/issues. This is a general question for all common hardware components under HP-UX server. (4 Replies)
Discussion started by: sbn
4 Replies

5. Solaris

Hardware problem diagnosing

Hey guys how to do diagnose solaris for hardware problems/issues. This is a general question for all common hardware components under solaris server. (4 Replies)
Discussion started by: sbn
4 Replies

6. Linux

Hardware problem diagnosing

Hey guys how to do diagnose Linux for hardware problems/issues. This is a general question for all common hardware components under Linux server. (1 Reply)
Discussion started by: sbn
1 Replies

7. Solaris

problem in finding a hardware problem

Hi I am right now facing a strange hardware problem. System get booted with the following error: Fatal Error Reset CPU 0000.0000.0000.0003 AFSR 0100.0000.0000.0000 SCE AFAR 0000.07c6.0000.1000 SC Alert: Host System has Reset It happen 4 or 5 times and get the same error every time.I... (8 Replies)
Discussion started by: girish.batra
8 Replies

8. Solaris

How do I know which HBA cards' hardware I have (on Solaris 10) ?

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

9. UNIX for Advanced & Expert Users

How do I know which HBA cards' hardware I have (on Solaris 10) ?

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

10. Solaris

hardware problem?

Can someone tell me what the following means? We have a v440 running Solaris 9. What do the patterns actually mean? May 17 12:12:03 ibasdb02 cediag: Revision: 1.78 @ 2005/02/11 15:5 :29 UTC May 17 12:12:03 ibasdb02 cediag: Analysed System: SunOS 5.9 with UP 117171-17 (MPR active) May 17... (5 Replies)
Discussion started by: hshapiro
5 Replies
Login or Register to Ask a Question
ISP(4)                                                     BSD Kernel Interfaces Manual                                                     ISP(4)

NAME
isp -- Qlogic based SCSI and FibreChannel SCSI Host Adapters SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device scbus device isp Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): isp_load="YES" DESCRIPTION
This driver provides access to SCSI or FibreChannel devices. SCSI features include support for Ultra SCSI and wide mode transactions for SCSI, Ultra2 LVD (for the ISP1080 and ISP1280), and Ultra3 LVD (for the ISP12160). Fibre Channel support uses FCP SCSI profile for FibreChannel. and utilizes Class 3 and Class 2 connections (Qlogic 2100 is Class 3 only, minor patches to the Qlogic 2200 to force Class 2 mode). Support is available for Public and Private loops, and for point-to-point connec- tions (Qlogic 2200 only). The newer 2-Gigabit cards (2300, 2312, 2322) and 4-Gigabit (2422, 2432) are also supported. Command tagging is supported for all (in fact, FibreChannel requires tagging). Fabric support is enabled by default for other than 2100 cards. Fabric support for 2100 cards has been so problematic and these cards are so old now that it is just not worth your time to try it. FIRMWARE
Firmware is available if the ispfw(4) module is loaded during bootstrap (q.v.). It is strongly recommended that you use the firmware available from ispfw(4) as it is the most likely to have been tested with this driver. HARDWARE
Cards supported by the isp driver include: ISP1000 SBus Fast Wide, Ultra Fast Wide cards, Single Ended or Differential cards. ISP1020 Qlogic 1020 Fast Wide and Differential Fast Wide PCI cards. ISP1040 Qlogic 1040 Ultra Wide and Differential Ultra Wide PCI cards. Also known as the DEC KZPBA-CA (single ended) and KZPBA-CB (HVD differential). Qlogic 1240 Qlogic 1240 Dual Bus Ultra Wide and Differential Ultra Wide PCI cards. Qlogic 1020 Qlogic 1020 SCSI cards. Qlogic 1040 Qlogic 1040 Ultra SCSI cards. Qlogic 1080 Qlogic 1280 LVD Ultra2 Wide PCI cards. Qlogic 1280 Qlogic 1280 Dual Bus LVD Ultra2 Wide PCI cards. Qlogic 12160 Qlogic 12160 Dual Bus LVD Ultra3 Wide PCI cards. Qlogic 210X Qlogic 2100 and 2100A Copper and Optical Fibre Channel Arbitrated Loop (single, dual). Qlogic 220X Qlogic 2200 Copper and Optical Fibre Channel Arbitrated Loop PCI cards (single, dual, quad). Qlogic 2300 Qlogic 2300 Optical Fibre Channel PCI cards. Qlogic 2312 Qlogic 2312 Optical Fibre Channel PCI cards. Qlogic 234X Qlogic 234X Optical Fibre Channel PCI cards (2312 chipset, single and dual attach). Qlogic 2322 Qlogic 2322 Optical Fibre Channel PCIe cards. Qlogic 200 Dell Branded version of the QLogic 2312 Fibre Channel PCI cards. Qlogic 2422 Qlogic 2422 Optical Fibre Channel PCI cards (4 Gigabit) Qlogic 2432 Qlogic 2432 Optical Fibre Channel PCIe cards (4 Gigabit) CONFIGURATION OPTIONS
Target mode support may be enabled with the options ISP_TARGET_MODE option. BOOT OPTIONS
The following options are switchable by setting values in /boot/device.hints. They are: hint.isp.0.disable A hint value to disable driver in kernel. hint.isp.0.fwload_disable A hint value to disable loading of firmware ispfw(4). hint.isp.0.prefer_memmap A hint value to use PCI memory space instead of I/O space access for. hint.isp.0.prefer_iomap A hint value to use PCI I/O space instead of Memory space access for. hint.isp.0.ignore_nvram A hint value to ignore board NVRAM settings for. Otherwise use NVRAM settings. hint.isp.0.fullduplex A hint value to set full duplex mode. hint.isp.0.topology A hint value to select topology of connection. Supported values are: lport Prefer loopback and fallback to point to point. nport Prefer point to point and fallback to loopback. lport-only Loopback only. nport-only Point to point only. hint.isp.0.portwwn This should be the full 64 bit World Wide Port Name you would like to use, overriding the value in NVRAM for the card. hint.isp.0.nodewwn This should be the full 64 bit World Wide Node Name you would like to use, overriding the value in NVRAM for the card. hint.isp.0.iid A hint to override or set the Initiator ID or Loop ID. For Fibre Channel cards in Local Loop topologies it is strongly recommended that you set this value to non-zero. hint.isp.0.role A hint to define default role for isp instance (target, initiator, both). hint.isp.0.debug A hint value for a driver debug level (see the file /usr/src/sys/dev/isp/ispvar.h for the values. SYSCTL OPTIONS
dev.isp.N.loop_down_limit This value says how long to wait in seconds after loop has gone down before giving up and expiring all of the devices that were visi- ble. The default is 300 seconds (5 minutes). A separate (nonadjustable) timeout is used when booting to not stop booting on lack of FC connectivity. dev.isp.N.gone_device_time This value says how long to wait for devices to reappear if they (temporarily) disappear due to loop or fabric events. While this timeout is running, I/O to those devices will simply be held. dev.isp.N.wwnn This is the readonly World Wide Node Name value for this port. dev.isp.N.wwpn This is the readonly World Wide Port Name value for this port. SEE ALSO
da(4), intro(4), ispfw(4), sa(4), scsi(4), gmultipath(8) AUTHORS
The isp driver was written by Matthew Jacob originally for NetBSD at NASA/Ames Research Center. BUGS
The driver currently ignores some NVRAM settings. Target mode support is not completely reliable yet. It works reasonably well for Fibre Channel, somewhat well for Qlogic 1040 cards, but does not yet work for the other cards (due to last minute unannounced changes in firmware interfaces). BSD February 28, 2007 BSD