|
I corrected the IP to 172.17.23.8.--
Still seeing the same result.
Loops thru the various SRC codes below for about an hour, then fails.
chsysstate -o on -k manual -m Server-9009-42A-SN**** -n Pencor08 DSLO
-i d -f Pencor08 DSLO -r lpar --ip 172.17.23.8 --netmask 255.255.255.0
--gateway
172.17.23.5 --serverip 172.17.23.5 --serverdir /V7R4OS --duplex auto
--mtu
1500
Paul
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Marc Rauzier
Sent: Saturday, June 20, 2020 4:50 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: IBM i Network Install to new V7R4 client LPAR using
Network File System - C2004130 load source not found.
Le 20/06/2020 à 00:32, Steinmetz, Paul via MIDRANGE-L a écrit :
(cut)Hello Paul
On the HMC, I created virtual Ethernet, one on the source, one onnew, both set to VLAN 11.
the
(cut)I believe there is a pure network issue here. The gateway must be in
chsysstate -o on -k manual -m Server-9009-42A-SNxxxx -n Pencor08
DSLO -i d -f Pencor08 DSLO -r lpar --ip 10.5.n.n --netmask
255.255.255.0 --gateway 172.17.23.5 --serverip 172.17.23.5
--serverdir /V7R4OS --duplex auto --mtu 1500
the same subnet as the IP address that you assign to "Pencor08 DSLO" LPAR.
--gateway must be in 10.5.n.n./255.255.255.0 subnet
If you want to keep the addresses like you wrote, you must have a real
router in this subnet, able to route to --serverip 172.17.23.5
If both --ip and --serverip are in the same subnetwork, as VLAN 11
used for both, looks to confirm, you should try to assign an unused
address to -ip, in the same subnet as --serverip such as 172.17.23.6.
Then, the --gateway can be any IP address in the same subnet, it will
never be used, still because --ip and --serverip are in the same subnet.
Something like (no need to specify --duplex and --mtu in my opinion):
chsysstate -o on -k manual -m Server-9009-42A-SNxxxx -n Pencor08 DSLO
-i d -f Pencor08 DSLO -r lpar --ip 172.17.23.6 --netmask yourmask
--gateway
172.17.23.5 --serverip 172.17.23.5 --serverdir /V7R4OS
Hope that helps
CA00E178 Initiating TFTP file transfer
CA00E177 Transfer failure due to TFTP error condtion
C2004130 Waiting for retry. A valid load source device was not found.
B2004158 A problem occurred during the IPL of a partition.
Marc
--
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@xxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
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.
midrange.com
