Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

SETTING UP NFS ON INTEGRITY WITH OPENVMS 8.3

FRANK BABULJAK
Occasional Visitor

SETTING UP NFS ON INTEGRITY WITH OPENVMS 8.3

I set up a directory with all the protection open. I have set up a TCPIP MAP to it But when I try to go to it I get Mountd service not running. In the log it says operation MOUNT_POINT failed on file /dga2/marin2/mcfdtestdata. File system is not mapped.
Any help is apprieciated.
8 REPLIES
Steven Schweda
Honored Contributor

Re: SETTING UP NFS ON INTEGRITY WITH OPENVMS 8.3

What did you do? What were the actual MAP
and ADD EXPORT commands? (And any others you
may have used?)

"[T]ry to go to it" how, from where?
FRANK BABULJAK
Occasional Visitor

Re: SETTING UP NFS ON INTEGRITY WITH OPENVMS 8.3

map "/dga2" $1$dga2: (also map config)
add export "/dga2/marin2/mcfdtestdata"
/host=* /option=name_conv
add proxy FRANKB /uid=2 /gid=2 /host=*
FRANKB is in the authorize file.
I am running NFS from my PC to Itegrity.
I am able to do NFS when I connect to our Alpha.
Thanks
Martin Vorlaender
Honored Contributor

Re: SETTING UP NFS ON INTEGRITY WITH OPENVMS 8.3

Frank,

for NFS to work the PORTMAPPER service must be enabled.

HTH,
Martin
Steven Schweda
Honored Contributor

Re: SETTING UP NFS ON INTEGRITY WITH OPENVMS 8.3

> map "/dga2" $1$dga2:
> add export "/dga2/marin2/mcfdtestdata"

Is there any reason for the long path in the
"add export" while the "map" has only a short
path? I'm not an expert in this stuff, so I
have a simpler set-up where the paths being
mapped are the same as the paths being
exported:

TCPIP> show map
Dynamic Filesystem Map
Pathname Logical File System

/dka100 ALP$DKA100:
/dkb300 ALP$DKB300:
/dka0 ALP$DKA0:


TCPIP> show expo

File System Host name

/dka0 urt.antinode.org, [...]
/dka100 urt.antinode.org, [...]
[...]


The HELP says:

ADD

EXPORT

Adds an export entry, in the form of a UNIX path name, to the
export database for a Network File System (NFS) file system. The
path name is a name that is mapped to one of the following:
[...]


I interpret this to say that the "UNIX path
name" being exported must be "a name that is
mapped". You have tried to map one name and
export another.

> I am able to do NFS when I connect to our
> Alpha.

And what are the maps and exports on the
Alpha?
FRANK BABULJAK
Occasional Visitor

Re: SETTING UP NFS ON INTEGRITY WITH OPENVMS 8.3

On Integrity:

TCPIP> SH MAP
/dga2 $1$DGA2:

TCPIP> SH EXP
/dga2/marin2/mcfdtestdata *
Options: Name_cvt

TCPIP> SH PROX
FRANKB OND uid 2 gid 2 *

On Alpha: (works)

TCPIP> sh map
/dra3 $2$DRA3:
TCPIP> sh exp
/dra3/marin/testdata *
Options: Name_cvt

TCPIP> sh prox

FRANKB OND uid 4 gid 4 *

TCPIP SHOW SERVCE ON INTEGRITY

BIND TCP,UDP TCPIP$BInd Disabled
FINGER TCP TCPIP$FINGER Enabled
FTP TCP TCPIP$FTP Enabled
LPD TCP TCPIP$LPD Disabled
MOUNT TCP,UDP TCPIP$MOUNTD Enabled
NFS UDP TCPIP$NFS Enabled
PCNFS TCP,UDP TCPIP$PCNFSD Disabled
PORTMAPPER TCP,UDP TCPIP$PORTM Disabled
RLOGIN TCP not defined Enabled
TELNET TCP not defined Enabled

TCPIP> ENABLE SERVICE PORTMAPPER
REPLY:
INTERnet ACP Activate PORTMAPPER Server
INTERnet ACP Error during process startup, Nolisten Service Disabled - PORTMAPPE
R Server
INTERnet ACP Deactivate PORTMAPPER Server
Martin Vorlaender
Honored Contributor

Re: SETTING UP NFS ON INTEGRITY WITH OPENVMS 8.3

Frank,

>>>
TCPIP> ENABLE SERVICE PORTMAPPER
REPLY:
INTERnet ACP Activate PORTMAPPER Server
INTERnet ACP Error during process startup, Nolisten Service Disabled - PORTMAPPE
R Server
INTERnet ACP Deactivate PORTMAPPER Server
<<<

Does it work when you set it up using SYS$MANAGER:TCPIP$CONFIG ?

Does SYS$SYSDEVICE:[TCPIP$PORTM]TCPIP$PORTM_RUN.LOG have any more information on the startup failure?

cu,
Martin
IFX_1
Frequent Advisor

Re: SETTING UP NFS ON INTEGRITY WITH OPENVMS 8.3

Hi Frank,

You may want to try to do this:

$ tcpip sysconfig -r nfs noproxy_uid=-2 noproxy_gid=-2

Good luck.
FRANK BABULJAK
Occasional Visitor

Re: SETTING UP NFS ON INTEGRITY WITH OPENVMS 8.3

The problem has been solved.

Here is what I think happened.

Before we started NFS services on the Integrity we copied the authorize file from the Alpha. Which had the TCPIP$PORTM and other accounts in it. When we started the NFS sevices it did not build the sys$sysdevice:[tcpip$portm]directory. I created these directories that were missing and added in the login.com file. Then restart TCPIP and it is working now.

Thanks