Sponsored Content
Full Discussion: ufsrestore T5240
Operating Systems Solaris ufsrestore T5240 Post 302437490 by m_aftab on Thursday 15th of July 2010 08:19:57 AM
Old 07-15-2010
1. Boot from CD
2. Start network services
3. access remote drive or use NFS to restore
 

9 More Discussions You Might Find Interesting

1. Solaris

raidctl on SUN T5240

Setting up a T5240 with two disks c1t0d0 and c1t1d0. I am trying to use raidctl but when I issue. raidctl -l I get Controller 1 Disk: 0.0.0 Disk: 0.1.0 So I try raidctl -c '0.0.0 0.1.0' -r 1 1 and I get "Array in use." I try (4 Replies)
Discussion started by: photon
4 Replies

2. Solaris

cannot plumb nxge on T5240

its a fresh installation. during the OS setup, it did not prompt for IP, netmask and gateway. using Solaris 10 08/07 update 4. I tried to plumb manually but encountered no such interface error. but nxge interfaces can be greped from the /etc/path_to_inst file. getting similar error on... (3 Replies)
Discussion started by: incredible
3 Replies

3. Solaris

T5240 netmgmt port not blinking

I was trying to configure the netmgmt from the serial and set commitpending to true. However, the netmgmt port is not up and blinking. I tried to connect using my notebook directly to the netmgmt port and am not able to ping as well. Previouly i was doing the firmware upgrade using the webconsole.... (20 Replies)
Discussion started by: incredible
20 Replies

4. Solaris

SUN T5240 vs M3000

Hi, We are planning to buy new server for our data center. Sun T5240 or M3000 which one have better performance, we are going to create many dt sessions in this server. So, i need your suggestions. RJS (4 Replies)
Discussion started by: rajasekg
4 Replies

5. Solaris

Bizarre Sun T5240 behavior

Hi - I have a T5240 with 7 LDOMS configured. One night, network comm was broken somehow. Nobody was doing anything on the machine at the time. Here is what I saw in messages: WARNING: nxge3 : nxge_dma_mem_alloc: ddi_dma_mem_alloc kmem alloc failed WARNING: nxge3 : nxge_alloc_rx_buf_dma:... (2 Replies)
Discussion started by: pyroman
2 Replies

6. Solaris

Disable multithreading option on T5240

Hi Gurus Can any one tell me the process of disabling the multithreading option on T5240 server and my OS is on LDOM, having one physical processor with 8 core & 8 thread per core Regards (3 Replies)
Discussion started by: amity
3 Replies

7. Solaris

Cannot configure RAID on T5240

Hi ! I've been given a T5240 with 4 disks and 2 HBA cards (but no array connected). I did a factory reset on SP and NVRAM clean on OBP because the server had been used before. I boot cdrom in single mode and try to create a hw mirror with disks from c1... but only c2 is seen by raidctl. ... (2 Replies)
Discussion started by: delavega
2 Replies

8. Solaris

Question: # of ldoms on T5240 with 2 T2 US 8 core

I have a T5240 with 2 T2 US 8 core.. Theoretically how many ldoms can I configure? (5 Replies)
Discussion started by: Iftikhar Barrie
5 Replies

9. Solaris

Using a Modem on a T5-2 or a T5240

Hi Folks, Just a quick question - hopefully! I have an application currently running on a V890 with Solaris 9, I'd like to move this to either one of our T-5's or one of the T5240's in a Legacy container on an LDOM - but the fly in the ointment is the application still uses a standard Hayes... (3 Replies)
Discussion started by: gull04
3 Replies
nfsd(1M)																  nfsd(1M)

NAME
nfsd - NFS daemon SYNOPSIS
#_conn] listen_backlog] protocol] device] [nservers] DESCRIPTION
is the daemon that handles client file system requests. Only users with sufficient privileges can run this daemon. The daemon is automatically invoked if and in the file. By default, starts over the TCP and UDP transports for version 2 and version 3, and over TCP for version 4, if NFS version 4 is enabled. One can change this with the option. A previously invoked daemon started with or without options must be stopped before invoking another command. Administrators wanting to change startup parameters for should make changes (as root user) to the NFS default file (see nfs(4)). Adminis- trators can either edit this file or use the command to make changes. Options The following options are supported: Start a NFS daemon over all available connectionless and connection-oriented transports, including UDP and TCP. Equivalent to set- ting the parameter to in the NFS default file. This sets the maximum number of connections allowed to the NFS server over connection-oriented transports. By default, the number of connections is unlimited. Equivalent to the parameter in the NFS default file. Set connection queue length for the NFS TCP over a connection-oriented transport. The default value is 32 entries. Equivalent to the parameter in the NFS default file. Start a NFS daemon over the specified protocol. Equivalent to the parameter in the NFS default file. Start a NFS daemon for the transport specified by the given device. Equivalent to the parameter in the NFS default file. Operands The following operands are supported: This sets the maximum number of concurrent NFS requests that the server can handle. This concurrency is achieved by up to nservers threads created as needed in the kernel. nservers should be based on the load expected on this server. 16 is the usual number of nservers. If nservers is not specified, the maximum number of concurrent NFS requests will default to 1. Changing the value of nservers requires stopping and restarting Equivalent to the parameter in the NFS default file. Notes A directory service that provides service name data base support must have the following service entries in its database: If the kernel tunable (see nfs_portmon(5)) is set to 1, then clients are required to use privileged ports (ports < IPPORT_RESERVED) to receive NFS services. This tunable is set to 0 by default. Use (see kctune(1M)) to set this tunable. By default, the NFS version 4 server is disabled. In order to enable it you must stop the NFS server. As root, either use the command (see setoncenv(1M)) or edit to set the parameter to 4. EXIT STATUS
Daemon started successfully. Daemon failed to start. WARNINGS
Manually starting and restarting is not recommended. If it is necessary to do so, use the NFS server start/stop script FILES
client machine pointer to an open-but-unlinked file. shell script for starting startup parameters for directories used by the server to manage client state information; these directories should not be removed. AUTHOR
was developed by Sun Microsystems, Inc. SEE ALSO
kctune(1M), mountd(1M), setoncenv(1M), getservent(3N), nfs(4), nsswitch.conf(4), services(4), sharetab(4), nfs_portmon(5). nfsd(1M)
All times are GMT -4. The time now is 08:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy