Sponsored Content
Full Discussion: Qlogic 2300 and WWN display
Operating Systems Solaris Qlogic 2300 and WWN display Post 302089512 by shorty on Tuesday 19th of September 2006 12:23:43 PM
Old 09-19-2006
One way to check is to do a format (as root). The WWN, I believe, is the last 12 characters BEFORE the last comma.
 

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 (1 Reply)
Discussion started by: pressy
1 Replies

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... (0 Replies)
Discussion started by: BFLO
0 Replies

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... (1 Reply)
Discussion started by: tresani
1 Replies

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... (9 Replies)
Discussion started by: floydm
9 Replies

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... (0 Replies)
Discussion started by: sbk1972
0 Replies

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... (1 Reply)
Discussion started by: sbk1972
1 Replies

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: (0 Replies)
Discussion started by: ppchu99
0 Replies

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... (17 Replies)
Discussion started by: bentech4u
17 Replies

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:... (4 Replies)
Discussion started by: bentech4u
4 Replies

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 (2 Replies)
Discussion started by: nixhead
2 Replies
GEOM_FOX(4)						   BSD Kernel Interfaces Manual 					       GEOM_FOX(4)

NAME
geom_fox -- GEOM based basic disk multipathing SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: options GEOM_FOX Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): geom_fox_load="YES" DESCRIPTION
The intent of the geom_fox framework is to provide basic multipathing support to access direct access devices. Basic in the above sentence should be read as: geom_fox only provides path failover functionality, not load balancing over the available paths etc. Using suitable hard- ware like SCSI or FibreChannel disks it is possible to have multiple (typically 2) host bus adapters access the same physical disk drive. Without a multipathing driver the FreeBSD kernel would probe the disks multiple times, resulting in the creation of multiple /dev entries for the same underlying physical device. A unique label written in the GEOM label area allows geom_fox to detect multiple paths. Using this information it creates a unique da#.fox device. The geom_fox device is subsequently used by the FreeBSD kernel to access the disks. Multiple physical access paths ensure that even in case of a path failure the FreeBSD kernel can continue to access the data. The geom_fox driver will disallow write operations to the underlying devices once the fox device has been opened for writing. EXAMPLES
o geom_fox needs a label on the disk as follows in order to work properly: "0123456789abcdef0123456789abcdef" "GEOM::FOX <--unique--id-->" For the unique ID 16 bytes are available. The ``GEOM::FOX'' is the magic to mark a geom_fox device. The actual labelling is accomplished by echo "GEOM::FOX someid" | dd of=/dev/da2 conv=sync For FibreChannel devices it is suggested to use the Node World Wide Name (Node WWN) as this is guaranteed by the FibreChannel standard to be worldwide unique. The use of the Port WWN not recommended as each port of a given device has a different WWN, thereby confusing things. The Node WWN can be obtained from a verbose boot as in for example isp1: Target 1 (Loop 0x1) Port ID 0xe8 (role Target) Arrived Port WWN 0x21000004cfc8aca2 Node WWN 0x20000004cfc8aca2 This Node WWN would then be used like so: echo "GEOM::FOX 20000004cfc8aca2" | dd of=/dev/da2 conv=sync For non-FibreChannel devices you could for example use the serial number of the device. Regardless of what you use, make sure the label is unique. Once the labelling has been performed and assuming the geom_fox module is loaded the kernel will inform you that it has found a new geom_fox device with a message similar to Creating new fox (da2) fox da2.fox lock 0xfffffc0000fdba20 o To check which physical devices match a given geom_fox device: # geom fox list Geom name: da2.fox Providers: 1. Name: da2.fox Mediasize: 73407865344 (68G) Sectorsize: 512 Mode: r0w0e0 Consumers: 1. Name: da2 Mediasize: 73407865856 (68G) Sectorsize: 512 Mode: r0w0e0 2. Name: da6 Mediasize: 73407865856 (68G) Sectorsize: 512 Mode: r0w0e0 o To check the status of the geom_fox components: # geom fox status Name Status Components da2.fox N/A da2 da6 SEE ALSO
GEOM(4), geom(8), gmultipath(8) AUTHORS
The geom_fox driver was written by Poul-Henning Kamp <phk@FreeBSD.org>. This manual page was written by Wilko Bulte <wilko@FreeBSD.org>. CAVEATS
The geom_fox driver depends on the underlying hardware drivers to do the right thing in case of a path failure. If for example a hardware driver continues to retry forever, geom_fox is not able to re-initiate the I/O to an alternative physical path. You have to be very sure to provide a unique label for each of the geom_fox devices. Safety belts are not provided. For FibreChannel devices it is suggested to use the Port WWN of the device. The World Wide Name is guaranteed to be worldwide unique per the FibreChannel standard. BUGS
The geom_fox framework has only seen light testing. There definitely might be dragons here. The name geom_fox is completely obscure. Just remember that any sly fox has multiple exits from its hole. The examples provided are too FibreChannel-centric. BSD
January 2, 2005 BSD
All times are GMT -4. The time now is 03:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy