Sponsored Content
Operating Systems HP-UX [HP UNIX B.10.20] NFS Client SubSystem fail Post 302934990 by beta911 on Thursday 12th of February 2015 07:39:28 AM
Old 02-12-2015
HP [HP UNIX B.10.20] NFS Client SubSystem fail

Recently moved a HP Unix B.10.20 system from US to Thailand, and everything is work well in US but after we changed:

1. set_parms ip_address (change the IP to TH range)
2. set_parms addl_netwrk (change the Subnet, Gateway, Domain name, DNS Svr Name, and DNS IP)
3. vi /etc/hosts (to commented entries and add new enteries.)

After rebooted encountered NFS Client Subsystem fail* during the post screen. Check the /etc/rc.log and it shown:


starting up the Automount daemon /usr/sbin/automount -f /etc/auto_master FAILURE CODE:1 mounting remote NFS file system.... "/sbin/rc2.d/S430nfs.client start" FAILED

Any expert can help to guide me through?

rgds,
beta911
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

NFS client subsystem hang up on boot

Hi, I have a Unix box running HP-UX 10.20 and it suddenly won't boot. Every time it goes down the boot checklist, it hangs on "NFS client subsystem" and just continues to say busy/wait. I have read something about the /etc/auto_master but don't quite understand what has to happen to fix it. ... (4 Replies)
Discussion started by: Asheley Ryan
4 Replies

2. Solaris

Solaris 9 as a nfs client -- centos as a nfs server.

Hello, I have a centos as nfs server, its name is centos_A. After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/* But, My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Discussion started by: bruceharbin
1 Replies

3. AIX

sftp : have to specify subsystem from client side

I have several ssh servers *running aix 5.3 and they respond to sftp requests just fine, but I have one that requires clients to specify the path to the sftp server using the -s flag which is*/usr/sbin/sftp-server I check the sshd_config across all servers and they are the same. *The other... (1 Reply)
Discussion started by: massdesign
1 Replies

4. AIX

HACMP and NFS client

Hi all, I know there are topics regarding this but didn't found the answer. I have two node HACMP cluster and the application that runs there relies on some NFS mount. The NFS server is some 3rd box that have nothing to do with the cluster. How can I mount the NFS shares only on the active... (5 Replies)
Discussion started by: emoubi
5 Replies

5. Red Hat

NFS mounting from client pc

The server ip is 10.2.2.24. I have installed nfs-utils package the i have edited /etc/exports i have added the following line /home 10.2.2.0/24(rw,sync,no_root_squash,no_all_squash) i have saved, i have started the nfs service, then i am trying to mount nfs sharing from client machine using... (1 Reply)
Discussion started by: ainstin
1 Replies

6. AIX

AIX NFS Server and NFS Client

Hi 2 ALL, try to run NFS Server in AIX 7.1 : 1. Step by step on NFS Server node mkdir /tmp/test chgrp staff /tmp/test chmod 775 /tmp/test-- create export directory (fs) mknfsexp -d /tmp/test -t ro exportfs -va show mount -e :/# exportfs -av exports: 1831-187 re-exported /tmp/test... (4 Replies)
Discussion started by: penchev
4 Replies

7. Red Hat

NFS client

Dear All , I have a NFS Server A and NFS client B. I have mounted the respective volume in NFS client. Now I wanted to make this volume as a NFS Server to another machine . Is this possible in Linux. Rgds Jegan R (3 Replies)
Discussion started by: jegaraman
3 Replies

8. Shell Programming and Scripting

Mount NFS Share On NFS Client via bash script.

I need a help of good people with effective bash script to mount nfs shared, By the way I did the searches, since i haven't found that someone wrote a script like this in the past, I'm sure it will serve more people. The scenario as follow: An NFS Client with Daily CRON , running bash script... (4 Replies)
Discussion started by: Brian.t
4 Replies

9. IP Networking

Connection to DB from client server through jdbc:Oracle:Oci8 fail

We tried to use to connect to DB using jdbc:Oracle:Oci8:@<SERVICE-A>. Connection fail / refuse with one DB .But its working with other databases. But through toad, jdbc thin client were able to connect. But this has happen suddenly and were able to connect previously. How to navigate this... (0 Replies)
Discussion started by: udara
0 Replies
set_parms(1M)															     set_parms(1M)

NAME
set_parms - set system initial identity parameters: hostname, date/time, root password, and networking SYNOPSIS
DESCRIPTION
The command is an interactive system set-up command that allows you to specify various "initial identity parameters" when first booting a newly installed operating system (whether preinstalled, or installed locally from media or an install server), and to revise these parame- ters later on a running system. Initial identity parameters are a minimal set of values required to bring a system to an initially useful state. They include the following: o system hostname o timezone for the system's location o date and time o root password o IP address, netmask o routemask, routing gateway, DNS, and NIS information o local language In a first-boot situation, is invoked automatically by For purposes, "first-boot" is defined as having no hostname set when the system starts up. This causes to step through all of its sub-areas to help you set all of the initial identity parameters. After the system has booted and is running, may also be called directly from the command line to step through all areas (via similar to how it works at first-boot, or to finish setting up a particular sub-area (the latter forms above). There are certain limitations to its actions when it's run after first-boot, as described see below. Note: The command only sets the root (superuser) password during "initial" processing, and then only if it is not already set. If so, it uses the command, so the effect is immediate. See the passwd(1) manpage. The command is also DHCP-aware. If you attempt to change DHCP-supplied data such as the hostname or IP address, issues a warning. If you continue with the changes, relinquishes the DHCP lease. On first-boot, asks if you would like to try getting set-up data from a DHCP server. However invoked, the command often knows and provides default values for many of the initial identity parameters, based on values specified to Ignite-UX in a previous or recent installation of the system or found in system configuration files. The command can be run only by the user with appropriate privilege. Options Each sub-area of is described below. In a first-boot situation all of the sub-areas are run sequentially. Special first-boot behavior is noted below if applicable, along with any special cases when invoking on a running system. When calling a sub-area directly, only a unique portion of the sub-area name is required to be given; for example, This allows the user to sequentially invoke all the sub-areas mentioned below. The user can configure multiple interfaces which are physically connected to the network using the Termi- nal User Interface (TUI). A in the user interface field indicates a lan which is not physically connected to the network. If lan interfaces are configured as DHCP, the options and are skipped. Set the system hostname: Validates a user-supplied hostname according to host-naming conventions and sets various system initialization variables to operate with that hostname. Particularly, edits to associate the new hostname with the current IP address of the system, if that can be determined. Note: It does not notify DNS (Domain Name Servers), etc. This higher level of configuration is handled later by broader configuration tools. WARNING: When changing the hostname, does not know about optionally-installed software. If any such software remembers the previous hostname, it might not work properly after the hostname is changed. A mechanism is provided that helps generalize the hostname changing function. The command calls, in sorted order, any exe- cutable commands found in the directory This occurs for both first-boot and non-first-boot calls. HP may in the future sup- ply special commands in this location. The system administrator may also supply custom commands (programs or scripts) for site installations using, for example, Ignite-UX. The system must be rebooted for any change to take full effect. Select a timezone based on your country of location. Also allows you to set a user-supplied timezone. The system must be rebooted for any change to take effect. Set the system date and time interactively: This is similar to calling as a privileged user, but without having to format a time specification string. The change takes effect immediately. Set or change the IP address and subnet mask for the system. This function edits the file to associate the new IP address with the current hostname. Note: it does not notify DNS (Domain Name Servers), etc. This higher level of configuration is handled later by broader configuration tools. If multiple lan interfaces are present, the user can select each LAN interface (network interface card or NIC) separately to configure it. The system must be rebooted for any change to take effect. Set the route mask (which defines the network and local subnet portions of a network address), set the routing gateway, and define access to the Domain Name System (DNS) and Network Information Service (NIS). First-boot: These changes take effect immediately, without a reboot, because starts networking after setting the parameters. Non-first-boot: A reboot is required for all of these changes to take effect. Allow the user to set the local language settings. The user can either select one of the languages from the menu or they can set new valid language. will verify whether the new language is installed. If it is not installed, the user must install the language before executing this option. set_parms, Ignite-UX or Cold Install After "cold-installing" HP-UX from tape, CD-ROM, or DVD, or using Ignite-UX to install HP-UX from any source including an install server, the file is generally left on the system. This file is used to communicate to and other tools the hostname, networking, and other informa- tion that was used during the installation, to make it easier to use any of these values as final system parameters. In particular, uses as defaults the shell-style variables in this file that begin with For example, indicates which LAN interface was used during a network cold install. This is the LAN interface that configures. In general, first looks in for default information, then in the system configuration files in the directory. If any parameter is defined in both locations, the latter takes precedence. If Ignite-UX is installed on your system, see the manpage entries for ignite(5) and instl_adm(4). In particular, read instl_adm(4) for descriptions of the and variables. Interaction with auto_parms During the boot-up sequence, always invokes which in turn detects the first-boot situation and it calls if either or both of these condi- tions are true. The starts its interface and, based on user input, might call back into to obtain and set up the management of a DHCP lease. After completes this and other system set-up tasks, control passes back to which completes the boot-up sequence using the newly- created system initial identity parameters. See the rc(1M) manpage for information about for invocation context in the first-boot case. If the system has multiple lan interfaces and the user wishes to configure some with DHCP and others with static IP, the user must invoke first to configure all the lan interfaces which they wish to configure as DHCP. The user should not allow the system to be rebooted while doing this configuration. Then the user should invoke to configure the remaining lan interfaces. also allows the user to specify the DHCP server from which to get hostname and networking parameters and Class ID. If multiple interfaces are configured with DHCP, there is a chance that multiple hostnames will be returned through different DHCP enabled lan interfaces. If hostname is not set in and none of the interfaces are configured with addresses, then the hostname returned by the interface is updated in FILES
The command itself. Common subroutines used by and the sub-area commands. Directory holding all of sub-area commands called by which runs them in sorted order. Directory containing any hostname-change commands defined by the user. These are standalone commands run, in sorted order, by when setting or changing the hostname. File set by Ignite-UX or Cold Install that contains networking and other system information used during the installation. System configuration files modified by AUTHOR The command was developed by HP. SEE ALSO
passwd(1), auto_parms(1M), dhcpdb2conf(1M), rc(1M), instl_adm(4), ignite(5). set_parms(1M)
All times are GMT -4. The time now is 07:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy