Sponsored Content
Special Forums UNIX and Linux Applications High Performance Computing Normal (not crossover) cable for Sun cluster interconnect.. Post 302265290 by incredible on Saturday 6th of December 2008 11:48:01 AM
Old 12-06-2008
It does support on newer systems
 

9 More Discussions You Might Find Interesting

1. High Performance Computing

SUN Cluster Vs Veritas Cluster

Dear All, Can anyone explain about Pros and Cons of SUN and Veritas Cluster ? Any comparison chart is highly appreciated. Regards, RAA (4 Replies)
Discussion started by: RAA
4 Replies

2. IP Networking

Two Servers via ethernet crossover cable

Hi, I'm trying to communicate two servers (HP DLProliant 380 G5) via a crossover cable, but I don't get them to ping each other. I am working in RHEL 4. These are the steps I've performed: 1) Plugged the crossover cables in eth2. (note: The cable is brand new. Also I built one myself... (3 Replies)
Discussion started by: jrodriguez365
3 Replies

3. Solaris

Sun cluster and Veritas cluster question.

Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC. Am thinking how to migrate to sun cluster setup instead. My plan as follows leave the existing vcs intact as a fallback plan. Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies

4. Solaris

Cluster interconnect, adapter configuration

Hello I have problem with scinstall. I found information that i should`t configure public network before using scinstall. Each node configuration: 4 node, 3 network adapter on each node. 1 for public adapter and 2 for cluster interconnect. Two switches. After scinstall first node is... (1 Reply)
Discussion started by: time0ut
1 Replies

5. Solaris

Sun cluster

Any body can tell me where i can download sun cluster installation and configuration video. is there any option to install cluster in 32 bit virtual machine. please help (4 Replies)
Discussion started by: sunnybee
4 Replies

6. Solaris

Application running too slow on Sun SPARC T5440 but run normal on sun M3000

Hi all, I have application running on sun server T5440 4x8x1.4 GHz, 64 GB RAM, application running very slow though load average too low. when I install my application on another server SUN M3000 (One CPU 1x8x2.5GHz, 8GB RAM), application run smoothly. Here is my server T5440 info: ... (6 Replies)
Discussion started by: insatiable1610
6 Replies

7. Solaris

Sun cluster 4.0 - zone cluster failover doubt

Hello experts - I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts. (1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over) (2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies

8. Hardware

Cable for SUN x4200 DC

Hello, I have a spare SUN server X4200 with a DC PSU (oracle part number 300-2186) The PSU is the one in the photo I was looking in the net about what cable i can order but i couldn't find anything that fit there :) Any idea? Thanks! (2 Replies)
Discussion started by: @dagio
2 Replies

9. Solaris

Sun cluster v3.2 - Is this right?

Running Sun Cluster v3.2 it appears. Two clustered physcial servers both running Solaris 10. Both servers run a number of Oracle DBs etc. BUT I'm a bit concerned that its been set up but will never switch in the even of failure of one of the hosts? Some of the cluster groups we've... (3 Replies)
Discussion started by: psychocandy
3 Replies
rpc.mountd(8)						      System Manager's Manual						     rpc.mountd(8)

NAME
rpc.mountd - NFS mount daemon SYNOPSIS
/usr/sbin/rpc.mountd [options] DESCRIPTION
The rpc.mountd program implements the NFS mount protocol. When receiving a MOUNT request from an NFS client, it checks the request against the list of currently exported file systems. If the client is permitted to mount the file system, rpc.mountd obtains a file handle for requested directory and returns it to the client. Exporting NFS File Systems Making file systems available to NFS clients is called exporting. Usually, a file system and the hosts it should be made available to are listed in the /etc/exports file, and invoking exportfs -a whenever the system is booted. The exportfs(8) command makes export information available to both the kernel NFS server module and the rpc.mountd daemon. Alternatively, you can export individual directories temporarily using exportfs's host:/directory syntax. The rmtab File For every mount request received from an NFS client, rpc.mountd adds an entry to the /var/lib/nfs/rmtab file. When receiving an unmount request, that entry is removed. user level part of the NFS service. However, this file is mostly ornamental. One, the client can continue to use the file handle even after calling rpc.mountd 's UMOUNT proce- dure. And two, if a client reboots without notifying rpc.mountd , a stale entry will remain in rmtab. OPTIONS
-d kind or --debug kind Turn on debugging for kind. -F or --foreground Run in foreground (do not daemonize) -f or --exports-file This option specifies the exports file, listing the clients that this server is prepared to serve and parameters to apply to each such mount (see exports(5)). By default, export information is read from /etc/exports. -h or --help Display usage message. -o num or --descriptors num Set the limit of the number of open file descriptors to num. The default is 256. -N or --no-nfs-version This option can be used to request that rpc.mountd do not offer certain versions of NFS. The current version of rpc.mountd can sup- port both NFS version 2 and the newer version 3. If the NFS kernel module was compiled without support for NFSv3, rpc.mountd must be invoked with the option --no-nfs-version 3 . -n or --no-tcp Don't advertise TCP for mount. -P Ignored (compatibility with unfsd??). -p or --port num Force rpc.mountd to bind to the specified port num, instead of using the random port number assigned by the portmapper. -V or --nfs-version This option can be used to request that rpc.mountd offer certain versions of NFS. The current version of rpc.mountd can support both NFS version 2 and the newer version 3. -v or --version Print the version of rpc.mountd and exit. TCP_WRAPPERS SUPPORT This rpc.mountd version is protected by the tcp_wrapper library. You have to give the clients access to rpc.mountd if they should be allowed to use it. To allow connects from clients of the .bar.com domain you could use the following line in /etc/hosts.allow: mountd: .bar.com You have to use the daemon name mountd for the daemon name (even if the binary has a different name). For further information please have a look at the tcpd(8) and hosts_access(5) manual pages. SEE ALSO
rpc.nfsd(8), exportfs(8), exports(5), rpc.rquotad(8). FILES
/etc/exports, /var/lib/nfs/xtab. AUTHOR
Olaf Kirch, H. J. Lu, G. Allan Morris III, and a host of others. 25 Aug 2000 rpc.mountd(8)
All times are GMT -4. The time now is 10:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy