Using the AIX Logical Volume Manager to perform SAN storage migrations. Introduction. If you work with AIX long enough, a time will come when you will need to migrate an. AIX system from an old SAN storage device to a shiny, new SAN storage.
- 1) # vi /etc/security/user 파일 실행하여 아래와 같이 설정 (단위: 주) minlen = 8 maxage = 10 minage = 1 histsize = 12. 2) 계정 잠금 임계 값 설정 # vi /etc/security/user 파일 실행하여 아래와.
- I'm SO confused about the question of whether I can or cannot update an lpp_source with a bunch of patches. Someone I know who I think knows a lot about AIX and NIM says I should never do this. But I'm looking at the Redbook.
The lease may be up on the old device, or it may simply need to be replaced by newer technology. This storage device could be an IBM product or that of another vendor. Either way, you will be faced with the decision of how best to migrate your AIX system to the newer device. Of course, you will also want to minimize the impact to your running systems as a result of the migration. In this article, I will share some examples of how I migrated AIX systems from old to.
SAN storage subsystems. I will cover both dedicated and virtual I/O (VIO) systems. To demonstrate the approach, the examples will include both IBM and non- IBM storage. Back to top. Preparation. Any migration of this type requires careful preparation and planning.
Back to top. What's new? OpenSSH has been updated to the 3.4p1 version of the open source code from openssh.org. You can get this version of binaries from the AIX 5L Expansion Pack and Web Download.
A Sysadmin's Unixersal Translator (ROSETTA STONE) OR What do they call that in this world? Contributions and corrections gratefully accepted. Please help us fill in the blanks. New 'tasks' are welcome, too! The table has. Note: This web page was automatically created from a PalmOS 'pedit32' memo. Useful AIX commands svmon svmon -P <pid> Further: use can user svmon command to monitor memory usage as follows; (A) #svmon -P -v -t 10 | more. DeveloperWorks; Technical topics; AIX and UNIX; Technical library; Using the AIX Logical Volume Manager to perform SAN storage migrations. Migrating AIX systems to new SAN storage subsystems with the Logical Volume Manager. One aspect of maintaining your AIX system to a current OS level entails making sure its filesets are up to date. Actually, does any system admin apply updates as soon as they’re available? I don't. I’m always a couple of.
I’m going to. assume that you or your SAN storage administrator have already cabled, configured and. SAN storage device to your existing SAN. Also, I'll assume that your AIX systems already have SAN connectivity to your existing SAN fabric. Before migrating, verify support with your storage vendor. Review the vendor's. These matrices are usually listed on the storage. They will. highlight which systems are supported with their storage device.
For example. for IBM Enterprise class storage devices (such as the DS8. The. DS8. 30. 0 Interoperability Matrix (see the Resources section) identifies important support and. They cover a wide spectrum of support checks such as supported. Fibre Channel (FC) adapter firmware, supported SAN switch types/firmware, and much more. One of the most important pieces of the puzzle is the required multi- path I/O. FC adapter firmware (Microcode).
I have seen all sorts of problems when these components are not. SAN and AIX. environment. Most vendors provide tools to help with the planning and. IBM provides the Fix Level Recommendation. Tools website, as well the IBM HBA support site (see the Resources section). If a vendor does not provide online tools to assist in the planning, then I recommend you ask them for help directly.
After all, it is in their interests to help you make their product work in your environment! Another important (and surprisingly sometimes overlooked) stage in the planning and. Take the time to design how your new SAN storage. SAN. Ask questions that will help the design. Can/should this device connect to the existing SAN or is this a good time to provision a new SAN Fabric? How will the AIX systems connect to the new storage device? How will the AIX operating system and data be migrated from the old to the new disk?
If it helps (and it usually does), draw pictures to help demonstrate answers to these. It will also help others to visualize and understand what you are trying to. Start with a diagram that encapsulates your current state, then another that.
Finally, at the end, state how the environment will look once the old device is no longer needed and all the data has been migrated from it. Will you be migrating from a dedicated I/O environment to a virtual one? If you are, then I recommend you review the latest IBM Redbook on migrating from physical to virtual storage (see Resources).
This publication guides you through the migration process and offers several methods for migrating. If you are migrating a dedicated I/O environment to another dedicated I/O. LPAR. For example, for. IBM DS8. 30. 0 storage you need to ensure that you have the appropriate SDDPCM MPIO device drivers (e.
DS8. 30. 0 Host Attachment kit (e. FC adapter Microcode (firmware).
If you already have a virtual I/O environment (running a virtual I/O server, or VIOS, for disk traffic), then consider the requirements for the VIOS. If you are migrating from IBM to IBM storage, then it is likely that you will simply need to update the MPIO code, FC adapter firmware and supporting device drivers. However, if you are migrating from Vendor A to Vendor B, you may need a different approach. The design process should shake out these considerations beforehand. For example, if you are migrating (VIOS presented disk) from IBM DS to Net.
App storage. then it is likely that you will need to consider provisioning new VIO servers for the. Net. App disk. Rather than mix two vendors' MPIO code on the same VIOS, it may be simpler to manage if each storage type has its own VIOS. I recommend this approach and my examples will cover how I chose to deploy this type of configuration. Unfortunately, I won't be discussing N- Port ID Virtualization (NPIV) in this article. NPIV adds another dimension to storage virtualization on the Power platform. NPIV with. a VIOS, utilizes virtual FC devices to present disk (and tape) natively to the client. LPARs. See the resources section for more information.
I'm also assuming that you do not have an IBM SAN Volume Controller (SVC) in your. If you do have an SVC and all your AIX systems are already behind it, then I suggest you take advantage of this product's amazing capabilities.
It can migrate storage transparently, from one storage device to another, without the host system ever being aware of the move. If you don’t have an SVC, and you are considering implementing one, I say proceed. With an SVC in your environment, storage migrations (for the AIX. And that’s just one of the many advantages to using this wonderful device. See the Resources section for more information on the IBM SVC.
Without an SVC, AIX storage migrations will most likely involve the use of the AIX Logical Volume Manager (LVM). This is what I will cover in the examples that follow.
Back to top. IBM SAN Storage Migration with AIX and dedicated I/OSeveral years ago I needed to migrate a large number of AIX hosts from an old IBM ESS. F2. 0) to a shiny, new IBM DS8. The AIX hosts were all using dedicated FC adapters (HBAs). Each host had at least two FC adapters connected to our SAN. The following diagram shows the high- level view of the SAN storage and AIX LPAR connectivity to the existing SAN Fabric: Figure 1. IBM ESS to DS8. 30. Dedicated I/O - Current state.
The MPIO code for every AIX system connected to this type of storage had to be updated. SDD device driver and FC adapter Microcode. For example, our design document stated the following: Ensure that the following software is installed on all AIX systems, at these levels: AIX5. IY6. 21. 65 Abstract: Target device rejects writes - AIX Host to Mc. Data switch. Fileset devices.
IY6. 21. 16 Abstract: after EEH error, attached hdisks failed Fileset devices. COMMITTED IBM 2. 10. Disk Devicedevices. COMMITTED IBM Subsystem Device Driver for AIX V5. COMMITTED IBM FCP Disk Device. Ensure that the latest.
Microcode for Fibre Channel. Use the lscfg command to determine the Microcode level of the FC adapter.$ lscfg - vpl fcs. Z9. Updating all of our 1. AIX systems, before migrating, was a sizeable task. However, once completed we were able to move to the new storage device without an issue.
The approach to migrating data from the old disk to the new disk was to employ the AIX. Logical Volume Manager.
There were two LVM utilities at the core of our data migration. Both commands can copy/move data between disks. Due to the very I/O intensive nature of these commands, they could impose a slight performance impact to I/O on the system. Therefore, it was determined that we would not perform a data migration when the system was running peak (disk I/O) load. We would schedule these tasks during relatively quiet periods.
The arrow (from hdisk. Figure 2 represents the LVM mirroring (and migratepv) process for data migration. The mirrorvg command would be used to migrate the operating system (rootvg) from the.
ESS to the DS8. 30. However, for the application/data volume groups, we chose to.
This would give us some level of control over how much additional I/O activity we could unleash on the running system. Some of the migrating systems were in production and we did not want to flood the I/O subsystem and cause unnecessary performance issues. Obviously before we could start, our storage team had to first attach and configure the. DS8. 30. 0 into our existing SAN.
Once this was completed, we worked with the storage. LUNs we would require for each of the AIX systems that were migrating to this new device. Our planning also captured each LPAR's hostname, the existing AIX hdisk names, the existing SDD (vpath) configuration, the World Wide Port Name (WWPN) for each FC adapter, the current FC adapter name (e. LUN configuration and the proposed new LUN configuration. With the storage carved up, we were able to assign the new LUNs to the existing AIX. Figure 2 below shows the DS8. SAN and a LUN from it has been allocated to an existing AIX LPAR.
The LUN appears to AIX as a hdisk device (hdisk. This disk has been allocated to an existing volume group (rootvg). Figure 2. IBM ESS to DS8.
Dedicated I/O - LVM Mirror - Migration state. Prior to migrating, we performed a backup of the system (including a mksysb). The. migration could execute while the applications were running on the system. However, at. some point after the migration, a reboot would be required.
The system boots from SAN disk. We will be migrating the system to a new SAN disk for the operating system. To ensure that the boot disk has migrated successfully we must make sure that we can boot the system on the new disk. The downside is that if this fails, we would need to restore the system from a mksysb backup. In hindsight (5 years later!), I could have suggested we use alt_disk_install (on AIX.
The alt_disk_install command (now replaced by the alt_disk_copy command in AIX 5. Using this method would have provided a more efficient back out path. Fortunately, we never had to initiate a back out during any storage migration. Before making any changes to the existing system, we documented the system.
The current disk, LVM and SDD (vpath) configuration was also captured.