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
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
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
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? (1 Reply)
Discussion started by: rainbow_bean
1 Replies
5. Solaris
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
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
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
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
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
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
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)