Qlogic 2300 and WWN display Post: 302089512

10 More Discussions You Might Find Interesting

1. Solaris

Wwn

hiho peeps, is there a possibility to see the WWNs of your SAN-HBAs, like in ifconfig the MAC-addresse.....??? greetings Pressy

2. Red Hat

RHEL AS 4 Kernel SRC + DKMS + QLogic

Hi, I need some help. I installed RHEL AS 4 u5 x86_64 (vendor requirement) on a Dell Blade 1855. I have a daughter board that will give it a HBA port. I can't install the daughter card until the Qlogic driver is loaded. I can't install the Qlogic driver sine the kernel src is not there. So I...

3. UNIX for Dummies Questions & Answers

Need to sort/change modify 2300 users ...

Ok, so here's my project I've been given and I know very little about this. I have an AIX unix box that has over 2300 local users. Any user with 4 or less characters in the username does not get changed. Any user with 5 or more needs to have the attribute shell=/bin/ksh changed to...

4. Solaris

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...

5. Solaris

Qlogic HBA's - lputil / lpfc.conf

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...

6. Solaris

Qlogic HBA + Veritas - Part 2

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...

7. Red Hat

lun masking at qlogic HBA level

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:

8. Solaris

Solaris OS having issue accessing LUN from Qlogic swich

Hi Community, I am facing one issue related storage accessing from solaris 10 machine(M5000). it was working fine then we shifted to another site. the only change on that site is FC switch. The issue i am facing is from solaris machine i can able to see the LUN, it;s only a test lun of 30...

9. Solaris

Qlogic 10G Ethernet adapter not working

Hi Community, i have one issue with 10 fiber ethernet adapter. here is my details: root@new-bpel.example.com #dladm show-dev bge0 link: unknown speed: 0 Mbps duplex: unknown bge1 link: up speed: 1000 Mbps duplex: full qlge2 link:...

10. Red Hat

Need WWN

How do I identify the WWN of associated SAN through a logical volume that is mounted on a RHEL 6 system

LEARN ABOUT NETBSD

isp

ISP(4)							   BSD Kernel Interfaces Manual 						    ISP(4)

NAME

     isp -- Qlogic based SCSI and FibreChannel SCSI Host Adapters

SYNOPSIS

     isp* at pci? dev? function? (PCI)
     isp* at sbus? slot ? offset ? (SBus)
     scsibus* at isp?

DESCRIPTION

     This driver provides access to SCSI or FibreChannel devices.

     SCSI features include support for Ultra SCSI and wide mode transactions for SCSI, and LVD (for the ISP1080 and ISP1280),

     Fibre Channel support uses FCP SCSI profile for FibreChannel.  and uses Class 3 connections only.	Support is available for Public and Pri-
     vate loops.  Command tagging is supported for all (in fact, FibreChannel requires tagging).

CONFIGURATION

     An optional flags 0x80 appended to the above isp* declarations will disable the download of driver firmware, which means you use whatever
     firmware is running on the card.  If no firmware is running on the card, the driver cannot operate the card.

     An optional flags 0x40 appended to the above isp* declarations (can be OR'd in with the other config flags option) will keep the driver from
     looking at device or bus NVRAM settings (this is in case NVRAM is just wrong and you have the card in a platform where it is inconvenient to
     change NVRAM settings on the card).

HARDWARE

     Supported cards include:

	   ISP1000
		   SBus Fast Wide, Ultra Fast Wide cards, Single Ended or Differential cards.

	   PTI SBS440
		   Performance Technology ISP1000 variants.

	   ISP1020
		   Qlogic 1020 Fast Wide and Differential Fast Wide PCI cards.

	   ISP1040
		   Qlogic 1040 Ultra Wide and Differential Ultra Wide PCI cards.

	   PTI SBS450
		   Performance Technology ISP1040 variants.

	   Qlogic 1240
		   Qlogic 1240 Dual Bus Ultra Wide and Differential Ultra Wide PCI cards.

	   Qlogic 1080
		   Qlogic 1280 LVD Ultra2 Wide PCI cards.

	   Qlogic 1280
		   Qlogic 1280 Dual Bus LVD Ultra2 Wide PCI cards.

	   Qlogic 2100
		   Qlogic 2100 and 2100A Copper and Optical Fibre Channel Arbitrated Loop

	   Qlogic 2102
		   Qlogic Dual Loop 2100A Optical Fibre Channel Arbitrated Loop PCI cards.

	   Qlogic 2200
		   Qlogic 2200 Copper and Optical Fibre Channel Arbitrated Loop PCI cards.

	   Qlogic 2202
		   Qlogic 2200 Dual Bus Optical Fibre Channel Arbitrated Loop PCI cards.

	   Qlogic 2204
		   Qlogic 2200 Quad Bus Optical Fibre Channel Arbitrated Loop PCI cards.

	   Qlogic 2300
		   Qlogic 2300 2-Gigabit Optical Fibre Channel PCI cards.

	   Qlogic 2312
		   Qlogic 2300 2-Gigabit Dual Channel Optical Fibre Channel PCI cards.

	   PTI SBS470
		   Performance Technology ISP2100 variants.

	   Antares P-0033
		   Antares Microsystems ISP2100 variants.

	   Qlogic 2400
		   Qlogic 2400 4-Gigabit Optical Fibre Channel PCI cards.

	   Qlogic 2500
		   Qlogic 2500 8-Gigabit Optical Fibre Channel PCI cards.

SEE ALSO

     cd(4), intro(4), scsi(4), sd(4), st(4)

AUTHORS

     The isp driver was written by Matthew Jacob for NASA/Ames Research Center.

BUGS

     The driver currently ignores some NVRAM settings.

     The driver currently doesn't do error recovery for timed out commands very gracefully.

     Sometimes, when booting, the driver gets stuck waiting for the Fibre Channel firmware to tell it that the loop port database is ready.  In
     this case you'll see an announcement that the loop state has a value of 0x1.  To unwedge the system, unplug and replug the fibre channel con-
     nection, or otherwise cause a LIP (Loop Initialization Primitive sequence) - this will kick the firmware into getting unstuck.

BSD
								   June 24, 2009							       BSD