|
This procedure describes how to configure PLM client LPAR's in
multiple domains with the PLM server and HMC sitting in different
domains than the client LPAR. This has typically caused RMC
authentication problems in the past and this procedure circumvents
it.
- Login as "root" to the client LPAR and create a .rhosts
file that contains entries for the PLM server using all
know short names, long names and associated IP
addresses. For example, client LPARS in the "mcc2"
network may require a ".rhosts" file that appears as
follows:
mx1apnim01 root
mx1apnim01-mc2 root
mx1apnim01-mcc2 root
mx1apnim01.man.mtxia.com root
mx1apnim01-mc2.man.mtxia.com root
mx1apnim01-mcc2.man.mtxia.com root
206.245.36.100 root
- Now configure the "inetd" daemon to provide "rsh" access and
refresh the "inetd" daemon
vi /etc/inetd.conf
refresh -s inetd
- Test rsh communication from the PLM server to the client LPAR:
rsh lparname-mc2.man.mtxia.com ls
- If this is successful, then test the RMC communications from the
PLM server and client LPAR:
CT_CONTACT=lparname-mc2.man.mtxia.com lsrsrc IBM.HostPublic
- If this is successful, then test the RMC communications from the
client LPAR to the PLM server. If unsuccessful, see the section
regarding rsct configuration resets.
CT_CONTACT=mx1apnim01-mcc2.man.mtxia.com lsrsrc IBM.HostPublic
- If this is successful, then perform the PLM setup. If unsuccessful,
see the section regarding rsct configuration resets.
- To perform a PLM setup from the PLM server run the following
command:
/etc/plm/setup/plmsetup lparname-mc2.man.mtxia.com root mx1apnim01-mcc2.man.mtxia.com
- Test the RMC PLM communications from the PLM Server to the client
LPAR.
CT_CONTACT=lparname-mc2.man.mtxia.com lsrsrc IBM.LPAR
- If unsuccessful, edit the "
/var/ct/cfg/ctrmc.acls "
file on the client LPAR and edit the "IBM.LPAR" stanza to containt the
following info:
IBM.LPAR:
* * rw
UNAUTHENT * rw
Troubleshooting:
RSCT configuration reset
- To reset the RSCT configuration on a client LPAR, run the following
commands:
cd /usr/sbin/rsct/install/bin
./uncfgct
./cfgct
./recfgct
cd /usr/sbin/rsct/bin
./rmcctrl -z
./rmcctrl -A
./rmcctrl -p
- Then rerun the "plmsetup" command before continuing and retest the
IBM.HostPublic communications in both directions.
- It may be necessary to remove the PLM server identities
from the trusted host list on the client LPAR:
cd /usr/sbin/rsct/bin
./ctsthl -d -n mx1apnim01
./ctsthl -d -n mx1apnim01-mc2
./ctsthl -d -n mx1apnim01-mcc2
./ctsthl -d -n mx1apnim01.man.mtxia.com
./ctsthl -d -n mx1apnim01-mc2.man.mtxia.com
./ctsthl -d -n mx1apnim01-mcc2.man.mtxia.com
- Then rerun the "plmsetup" command before continuing and
retest the IBM.HostPublic communications in both
directions.
|
|
|