Sponsored Content
Operating Systems AIX Network Perforamnce - It's just slow! Post 303033114 by hicksd8 on Saturday 30th of March 2019 06:15:04 AM
Old 03-30-2019
So you seem to be convinced that this is an ethernet problem. What have you checked?

What about maximum payload configuration? I've seen major issues caused by payload being set to 1502 instead of 1504, for example.
Are some boxes configured to use jumbo packets and others not?
I assume a single chattering ethernet adapter cannot be the issue because the problem is widespread across multiple boxes.
Have you tried putting a wireshark on the traffic to see what's going on?
Do your switches have LED's that tell you what speed has been negotiated?
Have you checked the spec of the ethernet adapters to see what they are capable of?
Stupid question: I assume there is no MS-Windows influence in this at all as they always have network issues with very large files?
Do you have one network device that doesn't handle jumbo packets?

Sorry, more questions than answers I know. Please give more information if you can.
This User Gave Thanks to hicksd8 For This Post:
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

network speed is slow

Hello, everyone: i encounter a problem these days , pls help me ,thanks in advance. my env: machine: ES40 A ES40 B os: true64 Unix 4.0f note: src.tar 8M network card speed 100M my problem: ... (3 Replies)
Discussion started by: q30
3 Replies

2. AIX

How to send big files over slow network?

Hi, I am trying to send oracle archives over WAN and it is taking hell a lot of time. To reduce the time, I tried to gzip the files and send over to the other side. That seems to reduce the time. Does anybody have experienced this kind of problem and any possible ways to reduce the time. ... (1 Reply)
Discussion started by: giribt
1 Replies

3. Programming

Help in developing a Network Appliation to monitor pc in a network

I am developing a Network Appliation to monitor computers in a network. Specs are App monitors the current web page viewed in each system App also can shutdown the computer in the network App can show all process run by each computer in the network I am now confused how to start my... (2 Replies)
Discussion started by: valaparambil88
2 Replies

4. IP Networking

ssh server is attachable from local network not from another network

hello i have a ubuntu ssh server that i can acess from any of my comnputers but only if they are on the same wireless network as the server. i tested trhis my tehtehring my samsung blackjack to my windows partition and installing openssh to windows it works when windows is on the wireless but no... (1 Reply)
Discussion started by: old noob
1 Replies

5. Solaris

Unavailable/Slow Network Paths in $PATH

At work, I'm in a Solaris environment working with csh, and $PATH is populated with anywhere between 10 and 20 entries. Last week, every command I issued (even "ls") took several seconds, if not an entire minute, to run. Once I moved "/home/sybase/bin" to the end of $PATH, certain commands... (2 Replies)
Discussion started by: acheong87
2 Replies

6. Red Hat

slow network on RHEL5

hey guys, We have two Sun x2100 servers running RHEL5 in a test environment. Both servers are fresh OS installs and hooked up to the same network switch. When ssh'ing to one server, there is a significant delay, while ssh'ing to the other server, the connection is almost instant. We are... (2 Replies)
Discussion started by: amheck
2 Replies

7. UNIX for Advanced & Expert Users

Slow printing to network printers using CUPS

Hi Guys, I've inherited a mess of an infrastructure in my new job, there hasn't been a sys admin in post for about a year, so things are falling apart. The first thing to break after I started was the printer server. I have it working again, and people can print, however it's very slow, slower... (0 Replies)
Discussion started by: rudigarude
0 Replies

8. Solaris

Solaris 11.1 Slow Network Performance

I have identical M5000 machines that are needing to transfer very large amounts of data between them. These are fully loaded machines, and I've already checked IO, memory usage, etc... I get poor network performance even when the machines are idle or copying via loopback. The 10 GB NICs are... (7 Replies)
Discussion started by: christr
7 Replies

9. Red Hat

Network becomes slow and return fast only after restart network

Hi, I have 2 machines in production environment: 1. redhat machine for application 2. DB machine (oracle) The application doing a lot of small read&writes from and to the DB machine. The problem is that after some few hours the network from the application to the DB becomes very slow and... (4 Replies)
Discussion started by: moshesa
4 Replies
nfs_manual_setup(7)					 Miscellaneous Information Manual				       nfs_manual_setup(7)

NAME
nfs_manual_setup - Describes how to manually set up the Network File System (NFS) DESCRIPTION
This reference page describes how to manually set up the Network File System (NFS). Setting up NFS includes configuring the following: Servers Clients, using /etc/fstab Clients, using Automount or AutoFS Setting Up Servers Use the following procedure to set up an NFS server: Create the /etc/exports file and add the appropriate entries to it. The entries that you add are site-specific but their syntax should be as follows: pathname [-root=0] [-root=hostlist [-anon=uid] [-rw=hostlist [-ro] identifier_1 ... identifier_n You can use the number sign (#) as a delimiter to add comments. For more informa- tion, see the exports(4) reference page and the Network Administration manual. Add the following information to the /etc/rc.con- fig.common file by using the /usr/sbin/rcmgr command, which has the following syntax: /usr/sbin/rcmgr set variable value Indicate that this system is a server, by entering the following command: # /usr/sbin/rcmgr set NFSSERVING 1 (A zero (0) in place of the 1 indicates that this system is not a server.) Specify the number of nfsd server threads you want to run on the system. Separate symbols are used for UDP threads and TCP threads. For example, to run 8 TCP threads and 4 UDP threads, enter the following commands: # /usr/sbin/rcmgr set NUM_TCPD 8 # /usr/sbin/rcmgr set NUM_UDPD 4 You can run up to 128 server threads for both transports combined. Although 8 server threads for each transport is usually adequate, if NFS client performance is slow, a possible solution is to increase the number of server threads. Set the NONROOTMOUNTS parameter. Setting this parameter to 0 specifies that only root users on the client systems can mount file systems. Setting it to 1 specifies that anyone on the client systems can mount file systems. The following command specifies that users must be running as root to mount file systems from the server: # /usr/sbin/rcmgr set NONROOTMOUNTS 0 Specify whether you want to run the PC-NFS daemon. PC-NFS software provides personal computers on your network with the same capabilities as NFS. PC-NFS is based on the client/server model. The client software runs on the per- sonal computer. The server software runs on the Tru64 UNIX server. Instructions for setting up the PC-NFS client software is pro- vided with the PC-NFS software documentation. To specify that you want to run the PC-NFS daemon, enter the following command: # /usr/sbin/rcmgr set PCNFSD 1 You must then export the directories you want to mount on the PC client to the client. Also, you must export the /usr/spool/pcnfs directory to the PC client for the client to be able to utilize network printing. For information on exporting directories, see the Network Administration manual. Specify whether you want to run the NFS locking service to allow clients to set advisory record locks on files exported to them. To specify that you want to run the NFS locking service, enter the following command: # /usr/sbin/rcmgr set NFSLOCKING 1 Note, by default, 7 nfsiod daemons are run on all NFS systems. To turn this client service off, enter the following command: # /usr/sbin/rcmgr set NUM_NFSIOD 0 The /usr/sbin/rcmgr command appends the information to the end of the /etc/rc.config.common file. For more information on the rcmgr utility, see the rcmgr(8) reference page. Make sure that one of the following is true for client systems to which you are exporting file systems: They have an entry in the /etc/hosts file of the server. Their host information is in the hosts database, if the network is serving host information with NIS or DNS. The server specifies the client's Internet address instead of its host name in its /etc/exports file and the mountd daemon is not configured to run with Internet address checking turned on. Start the NFS daemons by entering the following command: # /sbin/init.d/nfs start # /sbin/init.d/nfsmount start To stop the NFS daemons, enter the following command: # /sbin/init.d/nfs stop Using the /etc/fstab File to Set Up Clients Use the following procedure to set up an NFS client, using the /etc/fstab file: Edit the /etc/fstab file. Unless you are using an automatic mounting service, such as Automount or AutoFS, edit the /etc/fstab file to contain an entry for each file system that you want to mount on your system if you want it mounted automatically. Specify the file system you are mount- ing, the server you are mounting it from, the permissions with which it is mounted, and the local mount point for it. The syntax for entries in the /etc/fstab file is as follows: fs_spec@server fs_file fs_vfstype fs_mntopts fs_freq fs_passno For more information, see fstab(4). The following is a sample /etc/fstab file: /usr/dist@host1 /usr/dist nfs ro,bg 0 0 share/man@host2 /usr/share/man nfs ro,bg 0 /usr/staff/h0@host3 /nfs/host3/usr/staff/h rw,bg 0 /usr/staff/h1@host3 /nfs/host3/usr/staff/h1 nfs rw,bg 0 0 Create a local mount point for each remote file system that you specified in the /etc/fstab file. The local mount points must correspond exactly to the fs_file field in the /etc/fstab file. In the preceding example, the client system uses the /etc/fstab file to mount the remote file system /usr/share/man from host2. The /etc/fstab entry specifies that the local mount point is also called /usr/share/man on the client system. While this is the easiest way to name the local mount point, it can have any name. To create the /usr/share/man mount point, enter the following command: # mkdir /usr/share/man Make sure that one of the following is true for server systems from which you are importing file systems: They have an entry in the /etc/hosts file of the client. Their host information is in the hosts database, if the network is serving host information with NIS or DNS. Edit the /etc/rc.config.common file by using the /usr/sbin/rcmgr utility. Add the following information to the /etc/rc.config.common file: Whether this system is an NFS server (a system can be both a client and a server). The number of nfsiod daemons that you want the system to run. To specify that you want this system to run 7 nfsiod daemons, enter the following command: # /usr/sbin/rcmgr set NUM_NFSIOD 7 You can run up to 64 nfsiod daemons. Although 7 nfsiod daemons is usually adequate, if NFS read and write performance is slow, you can increase the number of nfsiod daemons. Optionally, you can turn on the NFS locking service, if you want to be able to set advi- sory record locks on NFS-mounted files. To do this, enter the following command: # /usr/sbin/rcmgr set NFSLOCKING 1 Note that the NFS locking service must also be running on the server. The /usr/sbin/rcmgr command appends the information to the end of the /etc/rc.config.common file. For more information on the rcmgr utility, see rcmgr(8). Start the NFS daemons by entering the following command: # /sbin/init.d/nfs start # /sbin/init.d/nfsmount start If you are using Automount or AutoFS on this system, you should complete the steps in the Network Administration manual before starting the NFS daemons. If you need to stop the NFS daemons, enter the following command: # /sbin/init.d/nfs stop Administering Automount and AutoFS Maps You can customize Automount and AutoFS maps to suit your environment and either administer them locally, distribute them using NIS, or both. For information on creating and administering Automount and AutoFS maps, see the Network Administration manual. RELATED INFORMATION
Commands: autofsd(8), automount(8), mountd(8), nfsconfig(8), nfsd(8), nfsiod(8), rpc.lockd(8), rpc.statd(8) Files: advfs(4), cdfs(4), fstab(4) Network Information: nfs_intro(4) Network Administration, Technical Overview delim off nfs_manual_setup(7)
All times are GMT -4. The time now is 04:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy