Setting up nfs on newly built workstation

[MarkSyder]

Hi everybody.

I've just inherited four workstations from a different office. They very kindly installed HP-UX 10.20 on all four of them from the same ignite tape. How do I know this? Two of them won't boot because the processor is too new for the operating system to recognize and the other two have the same machine id! My only recourse is to completely rebuild them.

I have managed to get one of them accessing the network, but not to mount a remote directory. I have done the following:

edited /etc/rc.config.d/nfsconf so that NFS_CLIENT=1, AUTOMOUNT=1, and AUTO_MASTER=/etc/auto_master

edited /etc/auto_master to add the lines
/users auto.users
/vol auto.vol
as per a working workstation

added the directory I want it to mount to /etc/exports on the remote server and rerun exportfs -av

manually created /vol and /tmp_mnt/vol with the same ownership and permissions as a working workstation

rebooted the workstation.

Yet still it tells me that the directory does not exist. I've pored my way through HP's online documentation and looked for similar threads on this forum but can't find anything to help with the problem I've got. Help appreciated.

Mark Syder (like the drink but spelt different)

[Steven E. Protter]

Shalom Mark,

This is 11i, right?

Perhaps the /etc/exports on the nfs server has hostname/ip limits in its configuration.

It would be helpful to see the configuration files to see if we can spot a problem.

Permissions on the folders you created on the working system same as the ones that don't work?

hostname different

I'd like to see the exact error text if possible.

SEP

[MarkSyder]

Shalom Steven.

The exporting server is 11i, the workstation is a 10.20 that I have managed to set up on the network. I'm trying to take an ignite backup over the network prior to installing 11i via ignite.

/etc/exports hostname/ip limits: how would I tell?

Configuration files - I'll post them separately.

Permissions are the same.

Error message: ksh: /vol/ign_backups: not found

Mark

[Steven E. Protter]

NFS can build some security into /etc/exports

example:

/share/mysql 192.168.0.41(rw,async,no_root_squash) 192.168.0.40(rw,async,no_root_squash)
/share/web 192.168.0.41(rw,async,no_root_squash) 192.168.0.40(rw,async,no_root_squash)

The mysql and web share above only allow two IP addresses on the internal network access.

Means someone else on the network can't see or change squat. Means if someone manages to get through the firewalls they can't do anything because they didn't come from those hostnames.

This kind of stuff could be responsible for problems with NFS mounts.

Might be some useful data in /var/adm/syslog/syslog.log

:-)

SEP

[MarkSyder]

I'm not sure how sensitive the company is about server/workstation names being made publically known in case of hackers, but I'll err on the side of caution by quoting a line from /etc/exports with the names blanked out:

/ign_backups -access=(several group and individual host names separated by colons - all work except for the new one).

Would it perhaps be useful to add the new workstation to one of the groups in netgroup that can see the directory?

Mark

[MarkSyder]

Thanks Steven.

Definitely no host/ip limit in /etc/exports.

Nothing useful in /var/adm/syslog/syslog.log. I should have mentioned that I'd already looked there!

Mark

[MarkSyder]

I've no idea what's changed but it's working this morning.

Thanks again for the suggestions Steven.

Mark