I may have found the problem. On VM, we have four TCP/IP stacks -- the main TCPIP for VM/CMS and three secondary stacks (TCPIPT, TCPIPP and TCPIPD) which handle Linux. -T is for test with CTC's (so we can cycle it without affecting production work), -P is for production with CTC's and -D is for experimenting with Guest Lans. It used to be that both my Linux servers connected to -T. Now one connects to -T and one to -D. It also looks like -D isn't running a portmapper within it. No connection path available. Looks like I need to do some work on VM first. I'd really like to get the guest lans on the main stack, too.
Thanks to all who responded with ideas. "Great Minds discuss ideas. Average minds discuss events. Small minds discuss people." - Admiral Hyman Rickover Gordon Wolfe, Ph.D. (425)856-5940 VM Enterprise Servers, The Boeing Company > ---------- > From: Wolfe, Gordon W > Reply To: Linux on 390 Port > Sent: Friday, July 11, 2003 11:50 AM > To: [EMAIL PROTECTED] > Subject: Re: Guest Lans on SLES8 > > On the SLES8 system, > > ps -ax | grep port > 364 ? S 0:00 /sbin/portmap > rpcinfo -p > program vers proto port > 100000 2 tcp 111 portmapper > 100000 2 udp 111 portmapper > 100024 1 udp 1024 status > 100024 1 tcp 1024 status > 100003 2 udp 2049 nfs > 100003 3 udp 2049 nfs > 100003 2 tcp 2049 nfs > 100003 3 tcp 2049 nfs > 100021 1 udp 1026 nlockmgr > 100021 3 udp 1026 nlockmgr > 100021 4 udp 1026 nlockmgr > 100021 1 tcp 1027 nlockmgr > 100021 3 tcp 1027 nlockmgr > 100021 4 tcp 1027 nlockmgr > 100005 1 udp 1027 mountd > 100005 1 tcp 1028 mountd > 100005 2 udp 1027 mountd > 100005 2 tcp 1028 mountd > 100005 3 udp 1027 mountd > 100005 3 tcp 1028 mountd > dlnxtest:~ # mount -t nfs -o ro,intr linuxvm1:/xyz /mnt > mount: RPC: Port mapper failure - RPC: Unable to receive > > > On the SLES7 system (linuxvm1), > > ps -ax | grep port > 22731 ? S 0:00 /sbin/portmap > rpcinfo -p > program vers proto port > 100000 2 tcp 111 portmapper > 100000 2 udp 111 portmapper > > I'm not sure why the difference. I even did a "rcportmap restart" and got the same > thing. > > "Great Minds discuss ideas. Average minds discuss events. Small minds discuss > people." - Admiral Hyman Rickover > Gordon Wolfe, Ph.D. (425)856-5940 > VM Enterprise Servers, The Boeing Company > > > ---------- > > From: Sal Torres/SBC Inc. > > Reply To: Linux on 390 Port > > Sent: Friday, July 11, 2003 11:19 AM > > To: [EMAIL PROTECTED] > > Subject: Re: Guest Lans on SLES8 > > > > *** Reply to note of Fri, 11 Jul 2003 14:16:52 -0400 (EDT) > > *** by [EMAIL PROTECTED] > > rpcinfo -p should tell you if portmapper is working. > > > > Sal > > "Post, Mark K" <[EMAIL PROTECTED]> writes: > > >Gordon, > > > > > >None of those are the portmapper: > > ># ps ax | grep port > > > 98 ? S 0:00 /sbin/rpc.portmap > > > > > > > > >Mark Post > > > > > >-----Original Message----- > > >From: Wolfe, Gordon W [mailto:[EMAIL PROTECTED] > > >Sent: Friday, July 11, 2003 2:12 PM > > >To: [EMAIL PROTECTED] > > >Subject: Re: Guest Lans on SLES8 > > > > > > > > >Thanks Mark, > > > > > >It appears to be running on both the SLES8 and SLES7 servers. ps -ax | grep > > >rpc shows the same on both systems: > > > > > > 163 ? SW 0:00 /sbin/rpc.statd > > > 275 ? SW 0:00 [rpciod] > > > 278 ? S 0:00 /usr/sbin/rpc.mountd > > > > > >"Great Minds discuss ideas. Average minds discuss events. Small minds > > >discuss people." - Admiral Hyman Rickover > > >Gordon Wolfe, Ph.D. (425)856-5940 > > >VM Enterprise Servers, The Boeing Company> > > > > > >> ---------- > > >> From: Post, Mark K > > >> Reply To: Linux on 390 Port > > >> Sent: Friday, July 11, 2003 11:04 AM > > >> To: [EMAIL PROTECTED] > > >> Subject: Re: Guest Lans on SLES8 > > >> > > >> Gordon, > > >> > > >> You need to be running portmapper on the local system, as well as the > > >remote > > >> system. > > >> > > >> > > >> Mark Post > > >> > > >> -----Original Message----- > > >> From: Wolfe, Gordon W [mailto:[EMAIL PROTECTED] > > >> Sent: Friday, July 11, 2003 1:57 PM > > >> To: [EMAIL PROTECTED] > > >> Subject: Guest Lans on SLES8 > > >> > > >> > > >> As I posted to this list yesterday, I have been able to convert TCPIP > > >> communications on SLES8 under VM from VCTC over to Guest Lans. > > >> > > >> I have Telnet, ssh, samba, ftp and apache all working happily with guest > > >> lans. > > >> > > >> I can't seem to get nfs to mount a location on another (SLES7 with VCTC) > > >> server. This is a mount that worked before going to guest lans with the > > >> SLES8 server. > > >> > > >> The error message I get when trying to do the NFS mount is > > >> > > >> mount: RPC: Port mapper failure - RPC: Unable to receive > > >> > > >> I had updated the following files to get guest lans to work> > > >> /etc/sysconfig/network/ifcfg-hsi0 > > >> /etc/sysconfig/network/routes > > >> /etc/modules.conf > > >> /etc/chandev.conf > > >> and also the following with the new IP address: > > >> /etc/ssh/sshd_config > > >> /etc/samba/smb.conf > > >> /etc/hosts > > >> /etc/hosts.allow > > >> > > >> It looks like rpc isn't working right. I don't see anything in /etc/rpc > > >> (default from SLES8 install) that would be a problem. > > >> and if I do ps -ax | grep rpc I get > > >> 382 ? S 0:00 /sbin/rpc.statd > > >> 504 ? SW 0:00 [rpciod] > > >> 505 ? S 0:00 /usr/sbin/rpc.mountd > > >> > > >> I'm sure I've just missed something somewhere. Anyone have any ideas? > > >> > > >> "Great Minds discuss ideas. Average minds discuss events. Small minds > > >> discuss people." - Admiral Hyman Rickover > > >> Gordon Wolfe, Ph.D. (425)856-5940 > > >> VM Enterprise Servers, The Boeing Company > > >> > > >> > > > > > >
