Sponsored Content
Operating Systems AIX New IBM Power8 (S822) and StorWiz V3700 SAN, best practices for production setup/config? Post 302932843 by bakunin on Sunday 25th of January 2015 03:28:05 PM
Old 01-25-2015
Quote:
Originally Posted by c3rb3rus
Did a fresh AIX 7.1 install on the internal scsi hdisk, mirror'ed the rootvg and made sure it can boot from both hdisks in case one fails using this guide.
This is all fine, but you should be aware that this way you will never have the possibility of LPM (live partition mobility). LPM means the ability to move an LPAR to another hardware box ("managed system" in IBM-speak) on the same HMC without even stopping it. For this to work you (obviously) must not have any non-virtualised components in the LPAR: disks, adapters, etc..

If you want LPM you need to create 1 (2) VIOS LPARs, give these all the physical adapters, then create virtual adapters and give out these to the other LPARs. Instead of physical SCSI disks you usually create LUNs on the SAN, connect them to the VIOS, give them out to the LPARs as virtual SCSI (vscsi) disks and use these. Usually this is used for boot disks, for data disks you either use the same or FC-connected ("NPIV")-disks. When you move a LPAR via LPM the vscsi-disks are moved to the VIOS on the target managed system in the process.


Quote:
Originally Posted by c3rb3rus
The AIX oslevel is 7100-03, going to check for any updates.
That is OK. In fact some applications will prescribe exact versions anyway, so, as long as your version is supported (which is the case with 7.1), you are on the safe side.

Quote:
Originally Posted by c3rb3rus
What about firmware/microcode? How does one go about updating that for the head unit?
The POWER8 is a new hardware so expect the microcode to change quite oftenly in the next future. In general you only update when you must, not, when you can. It is good practice to install the very latest revision before the system goes productive because this way you might avoid the one or other downtime. Save for that: wait until you have a support case and support advises you to update microcode or a software update makes it necessary. Only then install the - at that time - latest microcode. As long as you haven't got a problem related to it: leave it alone.

Do you have a NIM server? If so make sure this is at the absolutely latest AIX version there is, because it can only serve systems at the same or lower versions than it is itself.

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. AIX

ibm san cache battery with aix

Hi All, I would like to share this incident that happened the other day. I have a question with this, https://www.unix.com/aix/64921-create-new-vg-san-rename-fs.html And I thought it's related to the above link but the problem was the ibm san 4300 cache battery was dead and I need to click... (2 Replies)
Discussion started by: itik
2 Replies

2. Filesystems, Disks and Memory

First steps on Ibm SAN DS4500

Hello everyone ! Im new on Ibm San DS4500. Can you give me some tips to this, because I dont want to make a mistake. I have some questions. How can I know how much space get on the san, I cant find it. How can add more space to a partition. Do you have some tutorial about this. I... (0 Replies)
Discussion started by: lo-lp-kl
0 Replies

3. AIX

Question about IBM San Ds4500

I have a question about SAN commands I have almost 15Tb of disk on my san but assigned and something else I have almost 11Tb There is a command to know, what its my real total storage capacity and another command to know how much I used .? Thanks again in advance (0 Replies)
Discussion started by: lo-lp-kl
0 Replies

4. AIX

Which Forum for IBM Storage production are good?

Which Forum for IBM Storage production are good? (1 Reply)
Discussion started by: rainbow_bean
1 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. AIX

IBM SAN storage -- cache battery

Hello, I have IBM SAN STORAGE DS4100 and one of the cache battery for the controller is dead. Suddenly the performance has been degraded and access to SAN disks ( reading and writing ) became very slow ? My query: Replacing the battery will take 6 days, so in the mean time what are the ways... (1 Reply)
Discussion started by: filosophizer
1 Replies

7. AIX

IBM SAN TO SAN Mirroring

Has anyone tried SAN to SAN mirroring on IBM DS SAN Storage. DS5020 mentions Enhanced Remote Mirror to multi-LUN applications I wonder if Oracle High availibility can be setup using Remote Mirror option of SAN ? (1 Reply)
Discussion started by: filosophizer
1 Replies

8. AIX

IBM AIX - SAN Storage DS4300 issue

Hi, This is follow up to the post https://www.unix.com/aix/233361-san-disk-appearing-double-aix.html When I connected Pseries Machine HBA Card ( Dual Port ) directly to the SAN Storage DS4300 , I was able to see Host Port Adapter WWN numbers , although I was getting this message... (2 Replies)
Discussion started by: filosophizer
2 Replies

9. AIX

StorWize v3700 and Power8 (S822) AIX, configuration best practice for LUNs?

Hello, We have an Power8 System (S822) and a IBM StorWize v3700 SAN. The OS is AIX 7.1. With this hardware from what I read I need to download/install special SDDPCM drivers, so I did (SDDPCM VERSION 2.6.6.0 (devices.sddpcm.71.rte). I carved my volumes in the StorWize and presented to... (3 Replies)
Discussion started by: c3rb3rus
3 Replies

10. AIX

IBM Power Linux Cluster Fence device on Power8 Platform

wasn't quite sure which forum to post in. What typical fence device to configure for a Power Linux PaceMaker Cluster running on the Power8 Platform (S822 Model of hardware), or what should be ordered with the S822 for use as a Fence Device? (5 Replies)
Discussion started by: mrmurdock
5 Replies
SD(4)							   BSD Kernel Interfaces Manual 						     SD(4)

NAME
sd -- SCSI and ATAPI disk driver SYNOPSIS
sd* at scsibus? target ? lun ? sd3 at scsibus0 target 3 lun 0 sd* at atapibus? drive ? flags 0x0000 DESCRIPTION
The sd driver provides support for SCSI bus and Advanced Technology Attachment Packet Interface (ATAPI) disks. It allows the disk to be divided up into a set of pseudo devices called partitions. In general the interfaces are similar to those described by wd(4). Where the wd(4) device has a fairly low level interface to the system, SCSI devices have a much higher level interface and talk to the system via a SCSI host adapter (e.g., ahc(4)). A SCSI adapter must also be separately configured into the system before a SCSI disk can be config- ured. When the SCSI adapter is probed during boot, the SCSI bus is scanned for devices. Any devices found which answer as 'Direct' type devices will be attached to the sd driver. For the use of flags with ATAPI devices, see wd(4). PARTITIONING
On many systems disklabel(8) is used to partition the drive into filesystems. On some systems the NetBSD portion of the disk resides within a native partition, and another program is used to create the NetBSD portion. For example, the i386 port uses fdisk(8) to partition the disk into a BIOS level partition. This allows sharing the disk with other operat- ing systems. CONFIGURATION OPTIONS
The following config(1) options may be applied to SCSI disks as well as to other disks. SDRETRIES Set the number of retries that will be performed for operations it makes sense to retry (e.g., normal reads and writes). The default is four (4). SD_IO_TIMEOUT Set amount of time, in milliseconds, a normal read or write is expected to take. The defaults is sixty seconds (60000 mil- liseconds). This is used to set watchdog timers in the SCSI HBA driver to catch commands that might have died on the device. IOCTLS
The following ioctl(2) calls apply to SCSI disks as well as to other disks. They are defined in the header file <disklabel.h>. DIOCGDINFO Read, from the kernel, the in-core copy of the disklabel for the drive. This may be a fictitious disklabel if the drive has never been initialized, in which case it will contain information read from the SCSI inquiry commands. DIOCSDINFO Give the driver a new disklabel to use. The driver will not write the new disklabel to the disk. DIOCKLABEL Keep or drop the in-core disklabel on the last close. DIOCWLABEL Enable or disable the driver's software write protect of the disklabel on the disk. DIOCWDINFO Give the driver a new disklabel to use. The driver will write the new disklabel to the disk. DIOCLOCK Lock the media cartridge into the device, or unlock a cartridge previously locked. Used to prevent user and software eject while the media is in use. DIOCEJECT Eject the media cartridge from a removable device. In addition, the scsi(4) general ioctl() commands may be used with the sd driver, but only against the 'c' (whole disk) partition. NOTES
If a removable device is attached to the sd driver, then the act of changing the media will invalidate the disklabel and information held within the kernel. To avoid corruption, all accesses to the device will be discarded until there are no more open file descriptors referenc- ing the device. During this period, all new open attempts will be rejected. When no more open file descriptors reference the device, the first next open will load a new set of parameters (including disklabel) for the drive. FILES
/dev/sdup block mode SCSI disk unit u, partition p /dev/rsdup raw mode SCSI disk unit u, partition p DIAGNOSTICS
None. SEE ALSO
ioctl(2), intro(4), scsi(4), wd(4), disklabel(5), disklabel(8), fdisk(8), scsictl(8) HISTORY
The sd driver was originally written for Mach 2.5, and was ported to FreeBSD by Julian Elischer. It was later ported to NetBSD. BSD
January 18, 1996 BSD
All times are GMT -4. The time now is 09:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy