RE: Virtual Ethernet and NFS Image Catalogs

Kevin:

First you need: https://www-01.ibm.com/support/docview.wss?uid=nas8N1010898

That will have 90% of the instructions in it.

This might help as well:
ftp://ftp.software.ibm.com/systems/support/power/i/nfs_optical_upgrade.pdf

Here's my program to automate starting the NFS servers and set up the
directories:

PGM
ENDNFSSVR *ALL
MONMSG CPF0000
DLYJOB 15 /* ALLOW TO STOP */
STRNFSSVR *ALL
MONMSG CPF0000
DLYJOB 15 /* ALLOW TO Start */
NEXT:
CHGAUT OBJ('/ibmi') USER(*PUBLIC) DTAAUT(*RWX) SUBTREE(*ALL)
CHGNFSEXP OPTIONS('-i -o ro') DIR('/ibmi/v7r1/ptfs')
CHGNFSEXP OPTIONS('-i -o ro') DIR('/ibmi/v7r1/groups')
CHGNFSEXP OPTIONS('-i -o ro') DIR('/ibmi/v7r1/licpgm')
CHGNFSEXP OPTIONS('-i -o ro') DIR('/ibmi/v7r2/ptfs')
CHGNFSEXP OPTIONS('-i -o ro') DIR('/ibmi/v7r2/groups')
CHGNFSEXP OPTIONS('-i -o ro') DIR('/ibmi/v7r2/licpgm')
CHGNFSEXP OPTIONS('-i -o ro') DIR('/ibmi/v7r3/ptfs')
CHGNFSEXP OPTIONS('-i -o ro') DIR('/ibmi/v7r3/groups')
CHGNFSEXP OPTIONS('-i -o ro') DIR('/ibmi/v7r3/licpgm')
CHGNFSEXP OPTIONS('-i -o ro') DIR('/ibmi/v7r3/upgradeptf')

TFTP:
CHGAUT OBJ('/ibmi/v7r3/licpgm/BOOTP') USER(QTFTP) +
DTAAUT(*RX) SUBTREE(*ALL)
CHGTFTPA AUTOSTART(*YES) ALTSRCDIR('/ibmi/v7r3/licpgm/BOOTP')
endtcpsvr *tftp
strtcpsvr *tftp

ENDPGM





--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Kevin
Monceaux
Sent: Wednesday, May 08, 2019 1:39 PM
To: Midrange L <Midrange-L@xxxxxxxxxxxxxxxxxx>
Subject: Virtual Ethernet and NFS Image Catalogs

Midrange Fans,

I'm finally beginning work on getting our PTFs up to date. We have one host
and three guest i LPARs on a single managed system. All are running 7.2, so
NFS image catalogs are probably the way to go.

I've been exploring our virtual Ethernet setup, which was set up before I
got involved in such things. It looks like each LPAR has one virtual
Ethernet interface. As far as I can tell, they're not being used for
anything. They're not bridged to the outside world. I can ping LPAR to
LPAR using the virtual addresses. There are no host table entries for the
virtual addresses, and all our RDB directory entries point to physical
interface addresses. Their virtual LAN identifiers are set to *NONE.

Since all our LPARs are on a single box, setting the LPARs up to use virtual
Ethernet for LPAR to LPAR communications would probably be a good thing. If
I set that up, can the same virtual Ethernet interfaces be used for that and
NFS image catalogs, or do I need to add additional virtual Ethernet
interfaces? If I need to add additional virtual Ethernet interfaces for NFS
image catalogs, do they need to be on a separate subnet?