Rob,
On the host LPAR, I believe you need to
WRKNWSSTG
11=Remove link for those being removed.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Monday, July 29, 2019 8:30 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Removing drives from a guested lpar.
I got these all matched up.
I'm removing 12 drives from one guest on one P9. Ensuring the remaining drives are spread evenly across NWSD's.
I'm removing 11 drives from another guest on a different P9.
I'm removing 4 drives from another guest on our P8.
I ran
STRASPBAL TYPE(*ENDALC) UNIT(... ... ...) STRASPBAL TYPE(*MOVDTA) TIMLMT(*NOMAX) PRIORITY(*LOW) CHKASPBAL to check on the status. Let that run.
The above steps were optional as I could have done this all in SST and actually have to finish it in SST using the same steps as if I didn't do the above. I knew that but I just wanted to do this anyway to get a head start. Just because.
Next working day...
CHKASPBAL to check on the status.
DSPLOG PERIOD((*AVAIL 072619)) MSGID(CPI1474 CPI1475) To get starting and ending times.
WRKDSKSTS
Balance is done but there's still ~1% on the drives being removed.
STRSST
3. Work with disk units
2. Work with disk configuration
12. Work with removing units from configuration 3. Remove units from configuration 2. Display status of remove operation When done the disks removed show up like new if try to add them to an ASP. They no longer show up in WRKDSKSTS.
Then I went to the host of the 'lesser' lpar.
WRKNWSSTG
Tried to remove them while the guest was live and the NWSD was varied on.
CPD8F59
Message . . . . : Network server storage still linked to network server
operating system
Cause . . . . . : The request is to remove the network server storage link
(RMVNWSSTGL), but the network server operating system commands to remove the
link have not been performed yet.
Recovery . . . : Perform the necessary network server operating system
commands to remove the network server storage link, then perform the
RMVNWSSTGL command again.
I assume that powering off the guest and varying off the NWSD is all I need now, eh?
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Monday, June 24, 2019 12:17 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Removing drives from a guested lpar.
Well, that is some fine thinking on your part with the 371 - 256 equaling 115. Thank you.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Kevin Bucknum
Sent: Monday, June 24, 2019 12:12 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Removing drives from a guested lpar.
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
That’s odd. Mine match but are small numbers. I wonder if it rolls over after 256? 371 - 256 is 115.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Monday, June 24, 2019 10:49 AM
To: Midrange Systems Technical Discussion
Subject: RE: Removing drives from a guested lpar.
Thank you.
I like the second link referred to in that document If there are multiple NWSDs, you should refer to document N1011369, Cross-Referencing (Device Mapping) Disk Units on i Hosted by i LPARs:
http://www.ibm.com/support/docview.wss?uid=nas8N1011369
Host
So if I have WRKNWSD MAIL1*
MAIL10 - Tape and optical so let's forget about him.
MAIL11 - CTL06
MAIL12 - CTL07
MAIL13 - CTL12
WRKHDWRSC TYPE(*CMN)
CTL06 - U9009.42A.7805730-V3-C371
CTL07 - U9009.42A.7805730-V3-C372
CTL12 - U9009.42A.7805730-V3-C373
And we use a naming convention in which C371 ties to C371 on the guest, for example
Host:
chhwres -r virtualio -m RACK1 -o a -p RACK1HST --rsubtype scsi -a "adapter_type=server,remote_lpar_name=MAIL1,remote_slot_num=371" -s 371
Guest:
chhwres -r virtualio -m RACK1 -o a -p MAIL1 --rsubtype scsi -a "adapter_type=client,remote_lpar_name=RACK1HST,remote_slot_num=371" -s 371 I verified, via our HMC, on the client, that the adapter id 371, matches the Partner Adapter 371.
This should tie in nicely with
Guest
1. Issue the STRSST command.
2. Select Option 3. Work with disk units 3. Select Option 1. Display disk configuration 4. Select Option 1. Display disk configuration status 5. Press F9 = Display disk unit details However, instead of seeing 371, 372, 373 I am seeing 115, 116, 117.
Serial Sys Sys Sys I/O
Unit Number Bus Card Board Bus Ctl
1 YVJAX4S34Q42 255 115 129 0 0
2 YL9QJDFU2KKS 255 116 129 0 0
3 YQLEVD2ZRW28 255 115 129 0 1
4 YBNJY7VHA5CN 255 115 129 0 2
5 YXN84ZEKH6XT 255 115 129 0 3
6 YXEVU4X64PKB 255 115 129 0 4
7 YPHTJ8CTL5GH 255 115 129 0 5
8 YHK759M5TSPU 255 115 129 0 6
9 Y8XHJRSN7G98 255 115 129 0 7
10 YA6PBY26RHAU 255 115 129 0 8
11 Y2DTKBLDX2N8 255 115 129 0 9
12 YB4UNLX85P99 255 116 129 0 1
13 YPRSV8L4SFCS 255 116 129 0 2
14 YVQZPTSP7NNE 255 116 129 0 3
15 YKP4FW4DWKUZ 255 116 129 0 4
16 YYAVZJ2DW272 255 116 129 0 5
17 YCGRMKMNLLPL 255 117 129 0 0
18 Y7V3U7FQY7VQ 255 117 129 0 1
I could work with this. But only because I know that 371 contains 10 storage spaces, which matches 115 0-9. 372 contains 6 storage spaces which matches 116 0-5. 373 contains 2 storage spaces which matches 117 0-1.
I'd rather see the card match the adapter id, as shown on that web site.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Kevin Bucknum
Sent: Monday, June 24, 2019 11:06 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Removing drives from a guested lpar.
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
https://www-01.ibm.com/support/docview.wss?uid=nas8N1011485
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Monday, June 24, 2019 9:57 AM
To: Midrange Systems Technical Discussion
Subject: Removing drives from a guested lpar.
IBM i hosting disk for IBM i.
I have a guest lpar in which the business has changed and it needs far less disk.
The hosting lpar has four NWSD's allocated for this guest. The first is for tape and optical. The other three are for disk.
I want to ensure that when I remove disks from the guest using STRASPBAL and/or STRSST on the guest that I can tie that back to WRKNWSSTG on the host. This is so that I can free up space on the host for use for other tasks.
I also want to ensure that the storage links are balanced across the NWSD's. Basically keeping the 'arms' balanced across those NWSD's.
So, how do I tie the items which appear on the host when I run WRKNWSSTG NWSSTG(MAIL1*) with the items which appear on the guest when I run SST and get information like:
Type. . . . . . . . . . . . : 6B22
Model . . . . . . . . . . . : 050
Level . . . . . . . . . . . : 0
Serial Number . . . . . . . : YVJAX4S34Q42 Resource Name . . . . . . . : DD001
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
[
https://www.medtronsoftware.com/img/MedtronMinilogo.bmp] Kevin Bucknum
Senior Programmer Analyst
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
https://www.medtronsoftware.com
CONFIDENTIALITY NOTICE
This document and any accompanying this email transmission contain confidential information, belonging to the sender that is legally privileged. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information to any other party and is required to destroy the information after its stated need has been fulfilled. If you are not the intended recipient, or the employee of agent responsible to deliver it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or action taken in reliance on the contents of these documents is STRICTLY PROHIBITED. If you have received this email in error, please notify the sender immediately to arrange for return or destruction of these documents.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
[
https://www.medtronsoftware.com/img/MedtronMinilogo.bmp] Kevin Bucknum
Senior Programmer Analyst
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
https://www.medtronsoftware.com
CONFIDENTIALITY NOTICE
This document and any accompanying this email transmission contain confidential information, belonging to the sender that is legally privileged. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information to any other party and is required to destroy the information after its stated need has been fulfilled. If you are not the intended recipient, or the employee of agent responsible to deliver it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or action taken in reliance on the contents of these documents is STRICTLY PROHIBITED. If you have received this email in error, please notify the sender immediately to arrange for return or destruction of these documents.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
