Re: Virtual Ethernet and NFS Image Catalogs

I've not seen that.

I apologize. I read it all the way through this time. This makes sense.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jim Oberholtzer
Sent: Friday, April 5, 2019 10:40 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Troubleshooting failure of new virtual optical drives on IBM i Host lpar failing to appear on IBM i guest lpar

The resource names will get you into trouble too. They have a bad habit of changing when IPLs are done. Some will argue they don't change, until of course they do......

If you do it as I suggest, who cares.


--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Friday, April 05, 2019 9:16 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Troubleshooting failure of new virtual optical drives on IBM i Host lpar failing to appear on IBM i guest lpar

Jim,
I had no plans on using a device name but the resource name instead. I do understand the difference. I've even used STRSST to rename resource names to suit me.
I was just asking if I should name the resource name and not use
Allowed device resources . . . . ALWDEVRSC OPTVRT01, OPTVRT02...
Restricted device resources . . RSTDDEVRSC *NONE
But use
Allowed device resources . . . . ALWDEVRSC *UNRSTD
Restricted device resources . . RSTDDEVRSC *NONE
instead

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jim Oberholtzer
Sent: Friday, April 5, 2019 10:04 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Troubleshooting failure of new virtual optical drives on IBM i Host lpar failing to appear on IBM i guest lpar

Rob:

No don't specify a device name, that'll cause real heartache. Here is an example of what Larry was saying:

(*** added for clarity)


CRTNWSD NWSD(V7R2BASE) RSRCNAME(CTL37) TYPE(*GUEST +
*OPSYS) ONLINE(*YES) VRYWAIT(*NOWAIT) +
SHUTDTIMO(31) PARTITION(*NONE) PTNNBR(11) +
CODEPAGE(437) MSGQ(QGPL/V7R2BASE) +
POOL(*SHRPOOL50) TCPPORTCFG(*NONE) +
TCPRTE(*NONE) TCPHOSTNAM(*NWSD) +
TCPDMNNAME(*SYS) TCPNAMSVR(*SYS) +
*** RSTDDEVRSC(*ALLTAPE *ALLOPT) +
IPLSRC(*PANEL) IPLSTMF(*NONE) +
IPLPARM(*NONE) PWRCTL(*NO) SRVOPT(*NONE) +
TEXT('V7R2 Base Load Partition')
CRTNWSD NWSD(V7R2BAS1) RSRCNAME(CTL39) TYPE(*GUEST +
*OPSYS) ONLINE(*NO) VRYWAIT(*NOWAIT) +
SHUTDTIMO(31) PARTITION(*NONE) PTNNBR(11) +
CODEPAGE(437) MSGQ(*JOBLOG) +
POOL(*SHRPOOL50) TCPPORTCFG(*NONE) +
TCPRTE(*NONE) TCPHOSTNAM(*NWSD) +
TCPDMNNAME(*SYS) TCPNAMSVR(*SYS) +
**** ALWDDEVRSC(*ALLTAPE *ALLOPT) +
IPLSRC(*PANEL) IPLSTMF(*NONE) +
IPLPARM(*NONE) PWRCTL(*NO) SRVOPT(*NONE) +
TEXT('V7R2BASE Second set of SCSI devices')


The " RSTDDEVRSC(*ALLTAPE *ALLOPT) " stops that device from emulating tape/optical

On the second one, V7R2BAS1, that one WILL emulate tape/Optical... Set that as the alternate.

In this example I also push the memory that is used to manage the virtualization off to *SHRPOOL50 as opposed to leaving it in *BASE which I
consider bad practice. Clearly *SHRPOOL50 need some memory.

--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Friday, April 05, 2019 8:53 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Troubleshooting failure of new virtual optical drives on IBM i Host lpar failing to appear on IBM i guest lpar

About your point two. Are you saying that the NWSD for optical should not
say:
Allowed device resources . . . . ALWDEVRSC *UNRSTD
Restricted device resources . . RSTDDEVRSC *NONE
But instead should individually name them like the following:
Allowed device resources . . . . ALWDEVRSC OPTVRT01, OPTVRT02...
Restricted device resources . . RSTDDEVRSC *NONE

About your point 1. I have varied off a NWSD supporting disk (accidentally) but then varied it back on. Other than a hang during that time it didn't seem to create any ill effects. But I accept your point.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of DrFranken
Sent: Friday, April 5, 2019 9:30 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Troubleshooting failure of new virtual optical drives on IBM i Host lpar failing to appear on IBM i guest lpar

Two things neither more important than the other.

1) NEVER share optical or tape on the same NWSD as disk. Wye? Because you cannot vary the thing off and change it if it has disk on it. If it has only optical and tape you can vary off change vary on, test, muck, break etc with no harm to the guest.

2) Be vewy vewy careful about DEVICE vs RESOURCE. On the NWSD when it asks what you are sharing or excluding it's asking for RESOURCE names.
When you delete virtual optical on the host (e.g. DLTDEvD OPTVRT01) and then create a new one (e.g. CRTDEVOPT BOB ) it will get a NEW resource name such as OPTVRT02. That resource name needs to be in the NWSD NOT "BOB".

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 4/5/2019 9:23 AM, Rob Berendt wrote:

I am having an issue seeing virtual optical drives created on my host
lpar

of IBM i on my guest lpars of IBM i.

I am told they should just automatically appear.

One of the things IBM had me check was that QAUTOCFG was enabled on
the

guest.

They also had me delete any existing virtual optical drives on the
guest

pointing to the host as potential conflicts.

IBM also had me go to the host and run WRKNWSD guestname* Only one
should have
Allowed device resources . . . . ALWDEVRSC *UNRSTD
Restricted device resources . . RSTDDEVRSC *NONE
The others should have:
Allowed device resources . . . . *UNRSTD
Restricted device resources . . *ALLOPT
To change these you should
- power off the guest.
- vary off the appropriate NWSD's
- make the changes.
- vary on the NWSDs
- Start the guest

IBM also said that if you ever want to do an OS upgrade from these
optical drives, and therefore need to boot from it, then you should do
the following
- change your guest's partition profile on the HMC to change the
Tagged

I/O's Alternate Restart Device to where the optical drives are served up.
On this lpar it happens to be the same as the load source drive.

- activate the guest from profile
- disable any other alternate installation devices you may have
created (like the tape drive you originally restored this lpar from)
using the steps "Disabling an alternate installation device" found at
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzarm/sc41530
4.pdf

I followed these steps. I also deleted and recreated the virtual
optical

drives on the host to serve up these image catalogs. However I do not see any new optical drives on the guest. Help.

Also:
Should I change all NWSDs to
Restricted device resources . . *ALLOPT
And create a new NWSD just for optical only? This is one way to

differentiate between load source and optical. This would also entail changing the guest lpar profile to tag this new nwsd as the alternate restart device.

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
--
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

--
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