Sponsored Content
Operating Systems Linux Red Hat Advice on allocating SAN storage to a virtual database server on VMware Post 303027922 by gull04 on Friday 28th of December 2018 09:00:18 AM
Old 12-28-2018
Hi dkmartin,

From the way you describe the layout, I'm going to assume that you're running something like SVC for the management of the LUN's. Are the AIX environment LPAR's or are they standalone machines, or something else of course.

Managing LUN's accross six individual SAN devices is very costly in resource, along with the planning headache when it comes to new system builds - well inless you have plenty of disk. I currently have two devices - a 1.5Pb VMax and a 250Gb VNX and that provides enough confusion.

Where ver possible our approach is to go for a single LUN, but we do have quite a number of systems with large numbers of luns (some are in excess of 200) on AIX, Solaris and RHEL. We do have some very old versions on VMware, but they are slowly being decommissioned.

So in reality I would if time permits look at load and I/O on a system by system basis, where the results indicate there would be a benefit - replicate the existing model. If the results show it would be OK, go for the single LUN, if you're using Metro or Global mirror you may have to delve a bit deeper and look at inter system bandwidth.

Regards

Gull04
 

5 More Discussions You Might Find Interesting

1. Solaris

Using San storage - advice needed

Thinking of using our San for network backups.. Have a Netra 240 being installed and planning to get some space on our San. Do you know what software is used to access the San from my server or what I would need to do? I know how to connect to local storage, disk arrays etc but not sure what... (1 Reply)
Discussion started by: frustrated1
1 Replies

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

3. SuSE

Hot-add memory to SuSE / VMware virtual server

Hi, Here is the issue. Some more memory has been added from vCenter to the virtual machine. From the virtual machine running SuSE 11 SP3. # modprobe acpiphp # modprobe acpi-memhotplug # grep -v online /sys/devices/system/memory/*/state # It looks like there is no offline memory, but free... (1 Reply)
Discussion started by: aixlover
1 Replies

4. UNIX for Dummies Questions & Answers

Allocating Unallocated Drive Space from a SAN to a filesystem

Good Morning everyone, I want to know how to allocate unallocated drive space from a SAN to a file system that desperately needs the drive space. Does anyone have any documentation or tips on how to accomplish this? I am running on AIX version 6.1. (2 Replies)
Discussion started by: ryanco
2 Replies

5. Homework & Coursework Questions

How to mount a 79TB SAN storage to another server?

Hi Team, How do i mount or connect the SAN storage to a specific folder. I have tried to mount it but each time i can only mount 900GB of the storage to the folder: ipmi1 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup-root_vol ... (0 Replies)
Discussion started by: ElVista
0 Replies
fp(7d)								      Devices								    fp(7d)

NAME
fp - Sun Fibre Channel port driver DESCRIPTION
The fp driver is a Sun fibre channel nexus driver that enables fibre channel topology discovery, device discovery, fibre channel adapter port management and other capabilities through well-defined fibre channel adapter driver interfaces. The fp driver requires the presence of a fabric name server in fabric and public loop topologies to discover fibre channel devices. In pri- vate loop topologies, the driver discovers devices by performing PLOGI to all valid AL_PAs, provided that devices do not participate in LIRP and LILP stages of loop initialization. The fp driver also discovers devices in N_Port point-to-point topologies. CONFIGURATION
The fp driver is configured by defining properties in the fp.conf file. Note that you must reboot the system to have any changes you make to fp.conf take effect. The fp driver supports the following properties: mpxio-disable Solaris I/O multipathing is enabled or disabled on fibre channel devices with the mpxio-disable property. Specifying mpxio-disable="no" activates I/O multipathing, while mpxio-disable="yes" disables the feature. Solaris I/O multipathing may be enabled or disabled on a per port basis. Per port settings override the global setting for the specified ports. The following example shows how to disable mul- tipathing on port 0 whose parent is /pci@8,600000/SUNW,qlc@4: name="fp" parent="/pci@8,600000/SUNW,qlc@4" port=0 mpxio-disable="yes"; manual_configuration_only Automatic configuration of SCSI devices in the fabric is enabled by default and thus allows all devices discovered in the SAN zone to be enumerated in the kernel's device tree automatically. The manual_configuration_only property may be configured to disable the default behavior and force the manual configuration of the devices in the SAN. Specifying manual_configuration_only=1 disables the automatic configuration of devices. pwwn-lun-blacklist Allows you to specify target port WWNs and LUN numbers you do not want configured. LUN numbers are interpreted as decimals. White spa- ces and commas (',') can be used in the list of LUN numbers. # # pwwn-lun-blacklist= # "target-port-wwn,lun-list" # # To prevent LUNs 1 and 2 from being configured for target # port 510000f010fd92a1 and target port 510000e012079df1, set: # # pwwn-lun-blacklist= # "510000f010fd92a1,1,2", # "510000e012079df1,1,2"; # FILES
/kernel/drv/fp 32-bit ELF kernel driver (x86) /kernel/drv/amd64/fp 64-bit ELF kernel driver (x86) /kernel/drv/sparcv9/fp 64-bit ELF kernel driver (SPARC) /kernel/drv/fp.conf fp driver configuration file. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |mpxio-disable |Uncommitted | +-----------------------------+-----------------------------+ |manual_configuration_only |Obsolete | +-----------------------------+-----------------------------+ |Availability |SUNWfctl | +-----------------------------+-----------------------------+ SEE ALSO
cfgadm_fp(1M), prtconf(1M), stmsboot(1M), driver.conf(4), attributes(5), fcp(7D), fctl(7D), scsi_vhci(7D) Writing Device Drivers Fibre Channel Physical and Signaling Interface (FC-PH) ANSI X3.230: 1994 Fibre Channel Generic Services (FC-GS-2) Project 1134-D Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.272-1996 Fibre Channel Protocol for SCSI (FCP) ANSI X3.269-1996 SCSI-3 Architecture Model (SAM) Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) ANSI X3.270-1996 SCSI Direct Attach (FC-PLDA) ANSI X3.270-1996 SCSI Direct Attach (FC-PLDA) NCITS TR-19:1998 Fabric Loop Attachment (FC-FLA), NCITS TR-20:1998 NOTES
In N_Port point-to-point topologies, FCP error recovery does not work across events such as link bounce/cable pull. I/O to devices with FCP-2/FCP-3 support (for example, FC tape drives) will be disrupted by such events. SunOS 5.11 10 Jan 2008 fp(7d)
All times are GMT -4. The time now is 01:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy