×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
First agreed that adding the secondary ASP is concurrent. ONLY issue is
if it is a system ASP (2-32) You cannot get IFS objects onto it unless
you IPL. I recommend an iASP in that case.
Now I looked at IBMs list. Comments.
1) Backups good.
2) Why do load source LAST? This is the time where you have the most
issues so do it FIRST because if it works the rest is easy. If you have
issues you're not stuck with all the new disks except the LS!
The Load Source typically is the drive with the LOWEST SAS address.
Remember if you have any doubt you can use service tools concurrent
maintenance to blink the light on it to be sure.
3) Why go into DST to start RAID on the new drives?? Get all that out of
the way before you shut down!! In fact you can DLPAR the stuff in. Well
you could if you didn't have the C10 card to install. :-) So in your
case you'll be coming up from power off anyway so DST is acceptable.
4) Once the load source copy is done, (It will take some minutes even
with SSDs as it formats the thing again and then copy the data.) IPL to
production!
5)Then go into SST and ADD all the remaining new disks WITHOUT BALANCE.
Just do ADD.
5) Finally use concurrent remove to take the old disks out of the ASP.
This will also take a while of course but we don't care. When it's done
those disks become 'non-configured' and are set for you to build your ASP.
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 7/20/2017 8:11 AM, Rob Berendt wrote:
Larry,
I am looking at the steps at
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzaly/rzalyloadsource2.htm
My concern with this is it assumes that I want to replace all the disks in
the existing two 5887's.
How do I adapt this technique to flag a drive in the new expansion units
as the new load source?
I see that task 9 does the copy load source.
I do not plan on doing tasks 11-13.
How do I change the system to point to the location of the new load source
disk after completing task 9?
And then after that I'll go back to task 8 and remove the old load source
unit.
And after everything checks out then I'll go back to adding the old SSD's
to a new secondary ASP. That may be after a little breather. Not time
critical. And I do not believe creating this secondary ASP will involve
DST (only SST). So it should be non disruptive.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.