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



Paul:



OK, but what the message is telling you is wrong is the host and guest partition numbers do not match what the HMC is telling them.



Try it. Change the PTNNBR to 4 (your guest partition number) and see if it works. (what do you lose by trying it?)



The guest device and the host device adapter numbers must be matched up on the HMC as well so the NWSD can see the guest partition. Meaning if the host device adapter number is 81, and the guest device adapter is 91, then the HMC needs to show those two pointing to each other. The other option is to leave them be *ANY which means you may, or may not, get them realigned at the next IPL of the host. In my opinion, bad practice.



--

Jim Oberholtzer

Agile Technology Architects



From: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Sent: Monday, June 1, 2020 9:00 AM
To: 'midrangel@xxxxxxxxxxxxxxxxx' <midrangel@xxxxxxxxxxxxxxxxx>; 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Newly created NWSD fail to vary on CPDB1AD , reason code 0013 - Resource name does not match partition.



Below is the command I used to create the NWSD.

This works for my other LPARs.

The only difference is the resource was created via chhwres instead of an IPL via the profile.

PTNNBR is set to 1, my host LPAR, for all my other NWSDs, and they are all working.



CRTNWSD NWSD(P080) RSRCNAME(CTL30) TYPE(*GUEST +

*OPSYS) PTNNBR(1) RSTDDEVRSC(*ALL) +

PWRCTL(*NO) TEXT('PENCOR08 VSCSI 80')



From the help text



Specifies the number of the logical partition to be used by this

integrated server.



Notes:



1. When Server connection specified *GUEST for the Network server

type (TYPE) parameter either the Partition (PARTITION) or

Partition number (PTNNBR) parameter can be specified but both

parameters cannot be specified.



2. When Server connection specified *GUEST for the Network server

type (TYPE) parameter and RSRCNAME is specified, the Partition

(PARTITION) and Partition number (PTNNBR) parameter can be set to

*NONE.



Paul



From: midrangel@xxxxxxxxxxxxxxxxx <mailto:midrangel@xxxxxxxxxxxxxxxxx> <midrangel@xxxxxxxxxxxxxxxxx <mailto:midrangel@xxxxxxxxxxxxxxxxx> >
Sent: Monday, June 01, 2020 9:37 AM
To: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx <mailto:PSteinmetz@xxxxxxxxxx> >; 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx <mailto:midrange-l@xxxxxxxxxxxxxxxxxx> >
Subject: RE: Newly created NWSD fail to vary on CPDB1AD , reason code 0013 - Resource name does not match partition.



Paul,



No, the host should not need to be booted, it fact at this point I would recommend against that.



So the partition number is 4. On the NWSD CRTNWSD command in this example:



CRTNWSD NWSD(SALSSTG) RSRCNAME(CTL02) TYPE(*GUEST +

*LINUXPPC) ONLINE(*YES) VRYWAIT(*NOWAIT) +

SHUTDTIMO(31) PARTITION(*NONE) PTNNBR(9) +

CODEPAGE(437) MSGQ(QGPL/SALS) POOL(*BASE) +

TCPPORTCFG(*NONE) TCPRTE(*NONE) +

TCPHOSTNAM(*NWSD) TCPDMNNAME(*SYS) +

TCPNAMSVR(*SYS) RSTDDEVRSC(*ALLTAPE +

*ALLOPT) IPLSRC(*PANEL) IPLSTMF(*NONE) +

IPLPARM(*NONE) PWRCTL(*NO) SRVOPT(*NONE) +

TEXT('SALS Storage Emulation')



Note: “PARTITION(*NONE) PTNNBR(9)” in the command.



In your case the PTNNBR should be “4”.



You should be able to use the CHGNWSD command to change those two parameters



--

Jim Oberholtzer

Agile Technology Architects



From: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx <mailto:PSteinmetz@xxxxxxxxxx> >
Sent: Monday, June 1, 2020 7:48 AM
To: 'Jim Oberholtzer' <midrangel@xxxxxxxxxxxxxxxxx <mailto:midrangel@xxxxxxxxxxxxxxxxx> >; 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx <mailto:midrange-l@xxxxxxxxxxxxxxxxxx> >
Subject: RE: Newly created NWSD fail to vary on CPDB1AD , reason code 0013 - Resource name does not match partition.



For this new LPAR, these were created with the below.



chhwres -r virtualio -m Server-9009-42A-SN***** -o a -p Pencor05 Production -s 80 --rsubtype scsi -a adapter_type=server, remote_lpar_id=4 , remote_slot_num=80

chhwres -r virtualio -m Server-9009-42A-SN***** -o a -p Pencor05 Production -s 81 --rsubtype scsi -a adapter_type=server, remote_lpar_id=4 , remote_slot_num=81

chhwres -r virtualio -m Server-9009-42A-SN***** -o a -p Pencor05 Production -s 82 --rsubtype scsi -a adapter_type=server, remote_lpar_id=4 , remote_slot_num=82



They are the only NWSDs that appear in the GUI under Virtual storage on the host LPAR.

My other NWSD for my other LPARS do NOT appear under Virtual storage, they were NOT created with chhwres, but by an IPL via the profile.



Maybe an IPL of the host is required?



Paul



From: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx <mailto:midrangel@xxxxxxxxxxxxxxxxx> >
Sent: Monday, June 01, 2020 4:53 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx <mailto:midrange-l@xxxxxxxxxxxxxxxxxx> >
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx <mailto:PSteinmetz@xxxxxxxxxx> >
Subject: Re: Newly created NWSD fail to vary on CPDB1AD , reason code 0013 - Resource name does not match partition.



Either the partition name or number on the NWSD does not match what the HMC is reporting to the host partition for the guest partition. I always use the partition number as opposed to name so if we change the name on the HMC for any reason you don’t build in a failure. The number will not change short of major surgery to the configuration.









On Sun, May 31, 2020 at 7:40 PM Steinmetz, Paul via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx <mailto:midrange-l@xxxxxxxxxxxxxxxxxx> > wrote:

The newly created NWSD fail to vary on, reason code 0013 - Resource name does not match partition.
Not sure how to resolve this issue.

Message ID . . . . . . : CPDB1AD
Date sent . . . . . . : 05/31/20 Time sent . . . . . . : 11:25:40

Message . . . . : Network server P080 vary on failed.

Cause . . . . . : The network server failed to vary on with reason code
00000013. Reason codes and their meanings follow:

--0013: Resource name does not match partition.

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 <mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.