Sponsored Content
Operating Systems AIX Safe Number of Disks Assigned to a VIO Server Post 302598169 by gito on Monday 13th of February 2012 03:36:43 PM
Old 02-13-2012
There are few other limitation you should know
You should not use more then 85 Disks per vscsi pair (queue_deph 3)
Best practice said queue deph 10 on VIO client then calculation give us about 40 disks per vscsi pair.

Few days ago we made a test 230 disks assigned to vscsi pair of vscsi with default queue_deph setting
compering to 40 disks per vscsi pair with queue_deph 10
We got up to 20% improvement on oracle query speed.

It is really worth to do it
 

10 More Discussions You Might Find Interesting

1. Solaris

Command to list all the VIP addresses assigned to Solaris server

Hello All, I want to list all the VIP addresses assigned to Solaris server. whats the command we have use on solaris for this? Please help Thanks!! Weblogic Consultant (1 Reply)
Discussion started by: weblogicsupport
1 Replies

2. AIX

vio server and vio client

Hi, I want to know wheather partition size for installation of vio client can be specified on vio server example If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Discussion started by: manoj.solaris
1 Replies

3. AIX

how to erase VIO server's rootvg?

how to erase VIO server's rootvg? I don't have CD can reinstall a new OS, can I go to maintenance to erase rootvg? (1 Reply)
Discussion started by: rainbow_bean
1 Replies

4. AIX

Inherited VIO server an LPARs

Lucky me, someone has installed a server and got it running with the best intentions, but leaving me a headache. :wall: We have a simple p520 with 4 disks. 2x145Gb & 2x300Gb. The smaller disk pair have been built into a VIO mirrored rootvg, and quite right too. The other two disks form a... (3 Replies)
Discussion started by: rbatte1
3 Replies

5. AIX

VIO server on p520

trying to put VIO server software into this p520, firmware upgraded to the latest and greatest..SF240_415_318 , I think a few questions, on this practice AIX machine on AIX 7.1 VIO can only be installed if ASMI or HMC is running ??? if so, perhaps ASMI is much simpler, since I will need to... (2 Replies)
Discussion started by: ppchu99
2 Replies

6. AIX

vio server ethernet to vio client ethernet(concepts confusing)

Hi In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID. Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies

7. AIX

VIO server does not show new LPAR

Hi All, I've been trying to create a new LPAR for some days now but I can't get the VIO server to recognize the new LPAR. This is what I did: On HMC create new LPAR On HMC create new virtual scsi adapter for LPAR in VIO profile On HMC add new virtual scsi adapter for LPAR with DLPAR... (6 Replies)
Discussion started by: petervg
6 Replies

8. AIX

Mirroring vio server

Hi, I would like to know installing vio server on local disk and mirroring rootvg, if I am creating AIX VIO CLIENT(lpar), and any of single local hard disk failuare. will it affect lpars? will lpars able to boot. what needs to be done? (1 Reply)
Discussion started by: manoj.solaris
1 Replies

9. AIX

VIO Server

Hi, I am facing an issue in vio server. When I run bosboot -ad /dev/hdisk0 I am getting an error trustchk: Verification of attributes failed: /usr/sbin/bootinfo : accessauths regards, vjm Please use code tags next time for your code and data. (8 Replies)
Discussion started by: vjm
8 Replies

10. IP Networking

Safe port number to use for custom purpose?

Hello, this is a really quick question that should be easy to answer. I want to forward a certain port through a firewall. I know 0-1024 are out of the question and 1024-49151 are considered "registered" ports and 49152-65535 are dynamic or private. I want to be sure I pick a port that won't ever... (1 Reply)
Discussion started by: tay9000
1 Replies
SCSI(4) 						     Kernel Interfaces Manual							   SCSI(4)

Name
       SCSI - Small Computer System Interconnect

Description
       The  ULTRIX  system interfaces to disk and tape devices through the Small Computer System Interconnect (SCSI).  Initial ULTRIX SCSI support
       is limited to the Digital-supplied mass storage devices.  The following devices are fully supported on the ULTRIX system:

       o    Winchester disks: RZ22, RZ23, RZ23L, RZ24, RZ55, RZ56, RZ57, RX23, RX26, RX33

       o    Magnetic tapes: TZ30, TZK50, TLZ04, TSZ05, TKZ08, TZK10

       o    Optical disks: RRD40, RRD42

       Under the ULTRIX operating system, a SCSI device is referred to by its logical name.  Logical names take the following form:
       nn#
       The nn argument is the two-character name; the number sign (#) represents the unit number.  The two character names for SCSI devices are:

       rz  -  RZ22, RZ23, RZ23L, RZ24, RZ55, RZ56, RZ57, RX23, RX26, RX33, RRD40, RRD42 disks

       tz  -  TZ30, TZK50, TLZ04, TSZ05, TKZ08, and TZK10 tapes

       The unit number is a combination of the SCSI bus number, either 0, 1, ... and the device's target ID number.   The  unit  number  is  eight
       times  the  bus	number plus the target ID.  For example, an RZ23 disk at target ID 3 on bus 0 would be referred to as rz3; a TZK50 tape at
       target ID 5 on the second SCSI bus would be referred to as 13.

       The SCSI bus has eight possible target device IDs.  By default, one is allocated to the system.	This allows for a maximum of seven  target
       devices connected to a SCSI bus.

Restrictions
       The ULTRIX SCSI device driver does not operate with optical disks, other than the Digital-supplied devices.

       The SCSI driver attempts to support on a best effort basis, non-Digital-supplied winchester disks and magnetic tapes.

       The following notes apply to the driver's handling of non-Digital-supplied disks:

	  o   These disks are assigned a device type of RZxx, instead of RZ22, RZ23, RZ23L, RZ55, RZ56, RZ57, RX23, RX26, or RX33.  The RZxx disks
	      follow the same logical device naming scheme as the Digital-supplied disks.

	  o   During the autoconfigure phase of the system startup, the driver prints the contents of the SCSI vendor  ID,  product  ID,  and  the
	      revision level fields of the inquiry data return by the SCSI device.

	  o   RZxx  disks  are	assigned a default partition table. The default table can be modified by editing the sz_rzxx_sizes[8] entry in the
	      file The utility can also be used to modify the partition table on a RZxx disk.

	  o   The only logical unit number (LUN) supported for each target ID is 0.

See Also
       rz(4), tz(4), chpt(8)

																	   SCSI(4)
All times are GMT -4. The time now is 07:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy