|
Larry,
Since you mentioned virtual disks, should virtual disk also have disk protection, such as RAID-5?
If so, then these would be protected twice, once on the host and also on the quest.
I have a 2 small guest LPARs, only one virtual disk. In this situation, not enough disks for a parity set.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DrFranken
Sent: Tuesday, December 08, 2015 8:06 AM
To: Midrange Systems Technical Discussion
Subject: Re: Need to create ASP2 to for testing SSD/HDD mixture
Aha! Somehow I had the idea that these were virtual disks to a hosted partition. That not being the case you are of course correct!
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 12/8/2015 1:16 AM, Steinmetz, Paul wrote:
Larry,--
< Had you deleted those disk units from your host and the re-created
them the ADD would have taken just seconds. Of course you would have
spent the time creating them on your host partition so pretty likely a
wash there.>
My intention here, (not previously stated) was to remove disks from the ASP, without stopping parity, using the existing parity set.
To delete disks, I would have had to stop parity, which requires an IPL to DST.
After parity was deleted, disks could have been deleted.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
DrFranken
Sent: Monday, December 07, 2015 8:18 PM
To: Midrange Systems Technical Discussion
Subject: Re: Need to create ASP2 to for testing SSD/HDD mixture
See comments in line.
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 12/7/2015 5:48 PM, Steinmetz, Paul wrote:
Here are the processes I used to create and test ASP2, using existing DASD, no IPL needed.
This was a sandbox LPAR, 8205, .3 CPU, 8gb mem, CEC controller, 8 571gb 10k spinney in CEC.
1) STRASPBAL TYPE(*ENDALC) UNIT(6 7 8)
2) STRASPBAL TYPE(*MOVDTA) TIMLMT(*NOMAX) PRIORITY(*MEDIUM) - This took a while 10-20 hours.
Could have skipped these two steps and saved some time. Step 3 below does all of that and is a bit more efficient at it. It's much more efficient if you IPL to DST but as you stated you didn't want to do that you're good.
3) STRSST, 3. Work with disk units , 2. Work with disk configuration
, 12. Work with removing units from configuration ; 3. Remove units
from configuration ; 4=Remove unit from configuration 6,7,8
4) Using Ops Navigator New Disk Pool Wizard , Configuration and
Service, Hardware, Disk Units, (prompts you to login via SST) ; Disk
Pools ; New Disk Pool, Created ASP2, (Unchecked Protect data in this
pool because disk already protected via Raid5) Add New Disk, (added
6,7,8 to ASP 2. This also took a while 10-20 hours)
Had you deleted those disk units from your host and the re-created them the ADD would have taken just seconds. Of course you would have spent the time creating them on your host partition so pretty likely a wash there.
5) Tested a RSTLIB, forcing the RSTASP to ASP 2, worked with no issue.
6) Tested a RSTLIBBRM command, failed with BRM2112
BRM2112 Diagnostic 30 12/07/15 10:51:13.252644 Q1AMS QBRM *STMT QIJSCEC QIJS *STMT
From module . . . . . . . . : Q1AMS
From procedure . . . . . . : send__11q1aMsgOS400FRC8I0StringQ2_10q1aMessage
10q1aMsgTypePviRiCQ2_10q1aMessage11q1aMsgStackRC15q1aBrmsQualName
Statement . . . . . . . . . : 278
To module . . . . . . . . . : QIJSCEC
To procedure . . . . . . . : QIJSCEC
Statement . . . . . . . . . : 48700
Message . . . . : ASP 00002 not valid.
Cause . . . . . : BRMS does not recognize 00002 as a valid ASP name or
number. Either the ASP description is not defined or an auxiliary storage
pool device is being specified when only system (1) or basic user (2-32)
ASPs are valid. Recovery . . . : Use the Work with ASP Descriptions using
BRM (WRKASPBRM) command to determine whether the ASP description exists and
verify the parameter supports use of auxiliary storage pool devices.
Clearly a BRMS error. With system ASPs (2-32) only a number is valid and with iASPS (33 & up) only a name is valid. So BRMS seems in error requiring a name for something that does not have one. ASPs 2-32 also do not have an ASP Device.
7) WRKASPBRM revealed two ASPS. By default, *NONE is auto created as the name for ASP 2. BRMS did not like this.
ASP ASP ASP ASP Hierarchy Migration
Name Number Type Class Priority Eligible
*SYSTEM 00001 *SYSBAS *NONE *YES
*NONE 00002 *SYSBAS *NONE *YES
8) 2=Change the ASP name from *NONE to SLICES (this can be anything, not actually referenced on the RSTLIBBRM command) Currently checking with BRMS group for the restore rules on ASP Name)
*SYSTEM 00001 *SYSBAS *NONE *YES
SLICES 00002 *SYSBAS *NONE *YES
9) Reran RSTLIBBRM command, successful restore of the entire library to ASP2.
10) Need to finish restoring 30 remaining app libraries to ASP2.
11) Then let the testing begin.
Overall well done!
--
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Steinmetz, Paul
Sent: Thursday, December 03, 2015 3:13 PM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: Need to create ASP2 to for testing SSD/HDD mixture
I need to create ASP2 for testing SSD/HDD mixture.
What would be the easiest way to do this using current existing disks.
Can a client LPAR have 2 ASPS.
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.