Sponsored Content
Operating Systems Linux Red Hat "ERROR : failed to mount nfs source" Red Hat Kickstart Post 302444399 by regmaster on Wednesday 11th of August 2010 08:26:08 PM
Old 08-11-2010
Hi Jaysunn,

The issue some how solve by itself, I guess there could some error with network filer and we are still finding the RCA for this.

Thank you very much for your advice, it was very valuable for us to diagnose the error.

Regards,
Regmaster.
Junior Linux Administrator
 

9 More Discussions You Might Find Interesting

1. Linux

Red Hat kickstart from DVD?

Hello, I've spent 4-6 hours searching on Red Hat's website and googling looking for this and haven't found anything. But I can't believe it isn't there so I'm wondering if anybody knows where I can find the information. We are trying to set up kickstart through a DVD for use in remote... (2 Replies)
Discussion started by: rhfrommn
2 Replies

2. Red Hat

"SCRYPT" command in RED HAT 9

Hello, I wanted to simple command to encrypt a file. Using google I got a command "crypt". I could test it very well on Sun solaris. My red hat system says "command not found".Can you please tell me if I can find that package on the cd!!! (2 Replies)
Discussion started by: nsharath
2 Replies

3. UNIX for Advanced & Expert Users

Unusual NFS mount problem on only ONE client: Red Hat WS Rel 3

This is an unusual situation where I have an NFS server currently serving out MULTIPLE clients over several variants of Linux and UNIX successfully (world permissions) except for a SINGLE client. Even the other Linux (SuSE) clients in the same room are mounting successfully with defaults without... (6 Replies)
Discussion started by: neelpert1
6 Replies

4. Shell Programming and Scripting

Using "sed" to update RECURSIVELY a value within a directory in a Red Hat Machine

Hi All, I spent the whole morning trying to create a shell script ( using "sed" command ) that looks for a value in a directory and its sub directory than changes it with another value but couldn't find the way :( a first step, allowded me to trace all the files that contain it and even... (2 Replies)
Discussion started by: mehdi1973
2 Replies

5. AIX

Ssh installation error "RSA key generation failed"

While trying to upgrade ssh from v4.7 to v5.0 on AIX 5.3 TL9, I end up with the following error. Has anyone come across this? Note: openssl has been upgraded to 0.9.8.840 before this upgrade Bala (0 Replies)
Discussion started by: balaji_prk
0 Replies

6. UNIX for Dummies Questions & Answers

how to install "source" command!/ broken "login.cl"!

Hello, I am new to this forums and this is my first "asking help" message! i have 2 problems: 1- for unknown reasons the "source" command is not avalable in my system (UBUNTU). i can't either see it in my bin directory! 2- again for unknown reasons the "login.cl" file in the home... (0 Replies)
Discussion started by: astrosona
0 Replies

7. Solaris

Removing "Failed none for" error messages from sshd logs files

We have a number of system running the same patch level, OS version and sshd version. The systems also have the same sshd config and syslog.conf entries , however one of the systems keeps logging the following message everytime someone logs in: Nov 16 09:36:02 server389 sshd: Failed none for... (3 Replies)
Discussion started by: Mr_Webster
3 Replies

8. Ubuntu

[UBUNTU] mount.nfs fails in Ubuntu / Works on Red Hat!!!

Gurus, I want log in locally to my Lucid (10.04) workstation and have my code saved over the network on my samba account At work, all developers have samba user ids and when we were running Red Hat, we went thru the following procedure to get setup. * open a shell session to NFS server... (2 Replies)
Discussion started by: alan
2 Replies

9. UNIX for Dummies Questions & Answers

how to know if i use "Red Hat Enterprise Linux" or "Red Hat Desktop" ?

how to know if i use "Red Hat Enterprise Linux" or "Red Hat Desktop" ? (2 Replies)
Discussion started by: ahmedamer12
2 Replies
scconf_quorum_dev_netapp_nas(1M)			  System Administration Commands			  scconf_quorum_dev_netapp_nas(1M)

NAME
scconf_quorum_dev_netapp_nas - add and remove shared Network Appliance network-attached storage (NAS) quorum devices and change various NAS cluster quorum configuration properties or states. SYNOPSIS
scconf {-a|-c|-r} -q name=devicename otheroptions DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. A Network Appliance NAS device can be configured as a quorum device for Sun Cluster. The NAS configuration information consists of: o a device name, which must be unique across quorum devices o a filer name, which defaults to the device name if not specified o a LUN ID, which defaults to 0 if not specified To provide support for NAS devices as quorum devices, the administrator must install the quorum device support module provided by Network Appliance. If this module is not available, scconfprevents the addition of the quorum device. See Sun Cluster With Network-Attached Storage Devices Manual for Solaris OS for instructions about obtaining the support module. Additionally, the iSCSI license must be valid for the Network Appliance device. OPTIONS
The following options can be used for NAS quorum devices. See scconf(1M) for the list of supported generic options. See scconf_quo- rum_dev_netapp_nas(1M) for options that are specific to shared disk quorum devices. The add and remove forms of the command are used to add and remove NAS quorum devices to or from the configuration. The change form of the command is used for changing various properties of cluster quorum configuration. Before you add a quorum device, you must set up and configure the device and the logical unit number (LUN) on the device to be configured as a quorum device. For detailed procedures, see your Network Appliance documentation. For Sun Cluster requirements of device setup, see Sun Cluster With Network-Attached Storage Devices Manual for Solaris OS. After the quorum device is added, you cannot change the type. Add a NAS quorum device: -q -a name=devicename,type=netapp_nas[,filer=filer-name][,lun_id=0] Change a NAS quorum device's configuration: -q -c name=devicename,{maintstate | reset} Remove a NAS quorum device: -q -r name=devicename The -q option supports the following Network Appliance NAS-specific suboptions: filer=filer-name Specifies the name of the device on the network that you can use to access the NAS device when you are using rsh or telnet. lun_id=0 Specifies the LUN ID on the NAS device that will be a NAS quorum device. The LUN ID defaults to 0. When scconf is interrupted or fails while performing quorum-related operations, quorum configuration information can become inconsistent in the cluster configuration database. If an inconsistency occurs, either run the same scconf command again or run it with the reset option to reset the quorum information. EXAMPLES
Example 1 Adding Network Appliance NAS Quorum Devices The following scconf command adds the Network Appliance NAS quorum device qd1. -a -q name=qd1,type=netapp_nas,filer=nas1.sun.com,lun_id=0 Example 2 Removing Network Appliance NAS Quorum Devices The following scconf command removes the Network Appliance NAS quorum device qd1. -r -q name=qd1 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), clquorum(1CL), cluster(1CL), scconf(1M), scconf-quorum-dev-scsi(1M) Sun Cluster 3.2 10 Apr 2006 scconf_quorum_dev_netapp_nas(1M)
All times are GMT -4. The time now is 10:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy