Sponsored Content
Operating Systems Solaris Luxadm display not showing a LUN as expected Post 302976141 by Peasant on Friday 24th of June 2016 08:31:46 AM
Old 06-24-2016
Sorry, i have no idea about veritas multipathing solutions.
I only used native multipath on every linux/unix i worked on.

But, if you presented everything and MPXIO is not enabled..
You will see multiple devices (number depending on number of paths configured) for one presented LUN in the format output.

Also, check achenle suggestion.

*Edit achenle on cards which support NPIV the code you wrote will catch also Max NPIV Ports: resulting in output which is faulty (but will do no damage just print ILLEGAL WWN or alike)

Best regards
Peasant.
 

9 More Discussions You Might Find Interesting

1. Solaris

I have LUN ID, how to find disk relate to that LUN ID?

I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer. thanks (4 Replies)
Discussion started by: uuontario
4 Replies

2. Solaris

luxadm probe and vxdisk list don't matchup

I have a new SAN (Fujitsu Eternus 2000) and am trying to setup a veritas cluster on it, however veritas does not see all of the vluns I have exposed to the box. The OS does see them though. I have seen a lot of post about this, but it seems they are about people having just the opposite problem... (0 Replies)
Discussion started by: timothy.edwards
0 Replies

3. Solaris

Non-Root mode ... luxadm to show path(s) for Disks

Hi Gurus out there... I am pondering over a situation where I have non-root access (user account), where I am trying to determine paths (including multipaths) on a host. "luxadm display" seems very appropriate, but requires root access. Is there anyway I can get the FC path information? ... (1 Reply)
Discussion started by: verisund
1 Replies

4. Shell Programming and Scripting

Display Error [: : integer expression expected

i have lunix 5.4 i make script to tack the export from database 11g by oracle user the oracle sheel is /bin/bash when run this script display this error ./daily_xport_prod: line 36: the daily_xport_prod script #! /bin/sh # ORACLE_HOME=/u01/appl/oracle/product/11.2.0/db_1 export... (8 Replies)
Discussion started by: m_salah
8 Replies

5. Solaris

SAN/Solaris: luxadm shows NOT CONNECTED

Hi, I have a question regarding HBA configuration. Here are the commands' output: # cfgadm -al | grep fc c1 fc-fabric connected unconfigured unknown c2 fc connected unconfigured unknown c5 ... (11 Replies)
Discussion started by: aixlover
11 Replies

6. Solaris

Mpathadm showing no paths to 1 lun, others luns are fine

Hi, I've noticed that mpathadm states that one of our luns has no active paths: /dev/rdsk/c6t60000970000298700009533031324333d0s2 Total Path Count: 4 Operational Path Count: 4 /dev/rdsk/c6t60000970000298700009533031333037d0s2 ... (3 Replies)
Discussion started by: badoshi
3 Replies

7. Solaris

Luxadm displaying incorrect LUN parameter...

Hello, I have Solaris 10 running on one of rack server with dual port FC card. Each port of FC card is connected to two switches respectively. I have been trying to test multipathing functionality with one of FC Storage. While I have two storage controllers , each connected to the two switches... (0 Replies)
Discussion started by: linuxfreaker
0 Replies

8. Solaris

Issue with luxadm?

Hello, I have Solaris 10 running on one of rack server with dual port FC card. Each port of FC card is connected to two switches respectively. I have been trying to test multipathing functionality with one of FC Storage. While I have two storage controllers , each connected to the two switches... (2 Replies)
Discussion started by: linuxfreaker
2 Replies

9. Solaris

LUn' unmapped from storage still showing on Solaris 10

How can i remove LUN's from solaris 10 those are unmapped from SAN? from storage side i got confirmation that they removed lun. but in my solaris box still it's visible. i tried below. root@globalares2.example.com #luxadm -e offline /dev/rdsk/c2t600D02310007D16C42FF09E24B5B8255d0s2... (7 Replies)
Discussion started by: bentech4u
7 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 05:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy