remote mounting

[chad_c]

Hi. I would like to manually remote mount the following file system.

/arc/sys_backups/txnnm3

Note: I am mounting from one HPUX11.11 server to another HPUX11.11 server

How can i do this?

Regards,
Chad

[Sandy Chen]

Hi Chad,

You can do this using NFS, for more details you can see NFS and exports manual

How to enable it is:
On the file server:
1. # /sbin/init.d/nfs.core start
2. # /sbin/init.d/nfs.server start
3. Put these lines on /etc/exports

/arc/sys_backups/txnm3 -rw,anon=2,access=

4. # exportfs -av

On the client:
1. # /sbin/init.d/nfs.core start
2. # /sbin/init.d/nfs.client start
3. # mount :/arc/sys_backups/txnm3

Regards,
Sandy

[chad_c]

Hi Sandy,

Thanks for the response. I walked through the above, which makes sense. Then retried.

For some reason, I'm still getting the following:

nfs mount: get_fh: txovo:: RPC: Rpcbind failure - RPC: Timed out

We used to be able to do this. Does anyone know if installing ssh or sftp would cause this time out to occur? That is the only thing that has changed since we were last able to do this.

Regards,
Chad

[Dave Olker]

Hi Chad,

Let's back up a little and try something simple. From the NFS client system can you issue the following commands:

# rpcinfo -p
# showmount -e

and post the results of those two commands?

Thanks,

Dave

[chad_c]

Dave,

Results are as follows:

rinnm5# rpcinfo -p txovo
rpcinfo: can't contact portmapper: RPC: Rpcbind failure - RPC: Failed (unspecif)
rinnm5# showmount -e txovo
showmount: txovo: RPC: Rpcbind failure - RPC: Timed out
rinnm5#

[Dave Olker]

Hi Chad,

> rinnm5# rpcinfo -p txovo
> rpcinfo: can't contact portmapper: RPC:
> Rpcbind failure - RPC: Failed (unspecif)
> rinnm5# showmount -e txovo
> showmount: txovo: RPC: Rpcbind failure -
> RPC: Timed out

Is the portmapper/rpcbind running on the NFS server? If you log into txovo and issue the same commands:

# rpcinfo -p txovo
# showmount -e txovo

What do you get? Does a ps listing show rpcbind or portmap running?

Regards,

Dave

[chad_c]

Dave,

Results of the above commands

txovo# rpcinfo -p txovo
program vers proto port service
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
100024 1 tcp 49152 status
100024 1 udp 49153 status
100021 1 tcp 49153 nlockmgr
100021 1 udp 49154 nlockmgr
100021 3 tcp 49154 nlockmgr
100021 3 udp 49155 nlockmgr
100021 4 tcp 49155 nlockmgr
100021 4 udp 49156 nlockmgr
100020 1 udp 4045 llockmgr
100020 1 tcp 4045 llockmgr
100021 2 tcp 49156 nlockmgr
100068 2 udp 49167 cmsd
100068 3 udp 49167 cmsd
100068 4 udp 49167 cmsd
100068 5 udp 49167 cmsd
100083 1 tcp 49157 ttdbserver
805306352 1 tcp 781
100005 1 udp 49192 mountd
100005 3 udp 49192 mountd
100005 1 tcp 49272 mountd
100005 3 tcp 49272 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
395946 1 udp 876
395946 1 tcp 877
395947 1 udp 893
395947 1 tcp 894
395946 2 udp 876
395946 2 tcp 877
txovo#


txovo# showmount -e txovo
export list for txovo:
/var/opt/ignite/recovery/archives/rinnm2 rinnm2
/var/opt/ignite/recovery/archives/rinnm3 rinnm3
/var/opt/ignite/recovery/archives/rinnm1 rinnm1
/var/opt/ignite/recovery/archives/rinnm4 rinnm4
/var/opt/ignite/recovery/archives/rinnm5 rinnm5
/var/opt/ignite/recovery/archives/txnnm1 txnnm1
/var/opt/ignite/recovery/archives/txnnm2 txnnm2
/var/opt/ignite/recovery/archives/txnnm3 txnnm3
/var/opt/ignite/recovery/archives/txnnm4 txnnm4
/var/opt/ignite/recovery/archives/txnnm5 txnnm5
/var/opt/ignite/recovery/archives/riovo riovo
/var/opt/ignite/recovery/archives/txovo txovo
/arc/sys_backups/txnnm1 txnnm1
/arc/sys_backups/txnnm2 txnnm2
/arc/sys_backups/txnnm3 txnnm3
/arc/sys_backups/txnnm4 txnnm4
/arc/sys_backups/txnnm5 txnnm5
/arc/sys_backups/txovo txovo
/arc/sys_backups/rinnm1 rinnm1
/arc/sys_backups/rinnm2 rinnm2
/arc/sys_backups/rinnm3 rinnm3
/arc/sys_backups/rinnm4 rinnm4
/arc/sys_backups/rinnm5 rinnm5
/arc/sys_backups/riovo riovo
/cdrom (everyone)
/var/opt/ignite/clients (everyone)
txovo#

[Peter Nikitka]

Hi,

there may be a name resolution problem between the hosts rinnm5 and txovo.

Did you try a ping/telnet/ssh between these servers?

Try vice verse
nslookup rinnm5
nslookup txovo

Else try with FQN -
nslookup rinnm5.
nslookup txovo.


mfG Peter

[chad_c]

**NOTE: the ssh command to txnnm5 returned a bad packet length error:

txovo# ping rinnm5
PING rinnm5: 64 byte packets
64 bytes from 156.24.39.56: icmp_seq=0. time=45. ms
64 bytes from 156.24.39.56: icmp_seq=1. time=45. ms

----rinnm5 PING Statistics----
2 packets transmitted, 2 packets received, 0% packet loss
round-trip (ms) min/avg/max = 45/45/45
txovo# ssh rinnm5
Local: Bad packet length 1349676916.
txovo# nslookup rinnm5
Using /etc/hosts on: txovo

looking up FILES
Name: rinnm5
Address: 156.24.39.56

txovo# nslookup txovo
Using /etc/hosts on: txovo

looking up FILES
Name: txovo
Address: 10.5.25.51

txovo#

[spex]

Hi Chad,

From rinnm5, see if you can get rpcinfo for a different server. This should tell you if the problem is with rinnm5's RPC interface. What does '/etc/netconfig' look like?

PCS

[chad_c]

spex,

Yes. I can rpcinfo -p all other servers except txovo server.

regards,
chad

[Dave Olker]

One other thing to try would be to collect a network trace of the rpcinfo from the client to a working server and then an rpcinfo from the client to the failing server and then compare the two commands in the network trace to see if you can see any differences between the responses from the working and failing server.

If you want to collect a nettl trace of an rpcinfo -p command from the client to the working and failing servers I'd be happy to look at it. I'd just need the IP addresses of the failing and working servers so that I could filter the trace to isolate those respective packets.

Regards,

Dave

[Geetha_1]

Check if these processes are running...

#ps -ef| grep rpcd
#ps -ef | grep portmap ( in HP-UX 10.20 )
#ps -ef | grep rpcbind ( in HP-UX 11.X )
#ps -ef | grep nfsd

If some of these processes are absent you will have a problem with remote mount.
Geetha.

[chad_c]

.

[chad_c]

dns issue
resolved to correct hostname \ ip