Sponsored Content
Operating Systems AIX Live Partition Mobility using HP XP SAN storage Post 302669631 by zaxxon on Wednesday 11th of July 2012 06:55:37 AM
Old 07-11-2012
Lol yes, stop it - else you will get a cold when winter is coming Smilie
 

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Switching SAN storage

Hi, I have an existing SUN server that has a SAN storage installed on it. It also has softwares like Appwrox(scheduler), Taradata (database client), Samba Share and a few more installed on it. Now suppose that I have a new unix server server and i switch the same SAN store from the old unix... (1 Reply)
Discussion started by: myloginid
1 Replies

2. AIX

SAN storage and speed

I have 3 SAN disks of 1 TB each. Is it more efficient to make 1 large Volume group with multiple LV's or 3 Volume Groups with 1 LV each. The SAN disk is where all my backups will be dumped.:confused: (1 Reply)
Discussion started by: daveisme
1 Replies

3. Solaris

SAN Storage to solaris 10 server

Hi, I have configured our SAN Storage to be connected to our new SUN T5220. On the SAn it looks all fine on the server I do not see any connection: cfgadm -al Ap_Id Type Receptacle Occupant Condition c1 scsi-bus connected ... (4 Replies)
Discussion started by: manni2
4 Replies

4. Red Hat

how do we check SAN storage?

Hello, I am using LINUX OS. I want to check what is the SAN storage size. How do i check this in server? Any help is really appreciated.. (3 Replies)
Discussion started by: govindts
3 Replies

5. Solaris

Cannot see the IBM SAN storage

HI all, I had recently change the Server storage from EMC to the IBM SAN. but after the configuration, the IBM success to see the server HBA port and successfully assign a LUN for the server. When i go to the server, and restarted it. i use the "format" command to check, but din see any... (1 Reply)
Discussion started by: SmartAntz
1 Replies

6. UNIX for Dummies Questions & Answers

Storage from SAN

hi guys I installed Centos 5.5 (local disk). I am using 2 HBAs Now I mapped 5 LUNs from a Storage. I will be using LVM just to test I assigned a LUN I've read I have to use multipath to avoid my Centos see the LUN twice I enabled mdmpd and multipathd... something else I should do? ... (8 Replies)
Discussion started by: kopper
8 Replies

7. Solaris

SAN Storage for ASM

Hi, We are planning to setup a 10gR2 RAC and storage on ASM. We use Sun StorEdge SAN. The installation and configuration manual says to configure ASM diskgroups with raw devices (preferably raw disk not volumes). I dont really know if its possible to present raw disks to the Solaris... (4 Replies)
Discussion started by: esmgr
4 Replies

8. AIX

New to San Storage

Can anyone recommend a good book on san storage basics and how it communicates with an AIX server? (1 Reply)
Discussion started by: NycUnxer
1 Replies

9. AIX

Live Partition Mobility

Hello All, I recently did LPM at one of my client site, and thought of sharing it with the forum. I hope you find it helpful. (2 Replies)
Discussion started by: ibmtech
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 11:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy