Sponsored Content
Operating Systems Solaris Change congestion protocol in Solaris 10 Post 302828309 by crusoe on Tuesday 2nd of July 2013 08:56:51 AM
Old 07-02-2013
Sun Change congestion protocol in Solaris 10

I have a client with a meshed Cisco backbone.
6500's on top, Nexus 7000 in the middle and 4500's in bottom.

Solaris 10 servers connected to the 4500's backing up to a RedHat Linux backup server connected to the Nexus 7000's. The traffic is routed from 4500 --> Nexus 7000 --> 6500 --> Nexus 7000 --> backup server.

Backup clients have 1 GbE interfaces, backbone is 10GbE and backup server has 10 GbE interfaces.

Speed is good for all backup clients but not for the Solaris 10 backup clients. They have a short spike for anything between 30 secs - 2 minutes and then falls down to about 250 kbps per save stream.

I heard this could probably be solved by changing the congestion protocol on the Solaris hosts as they are misaligned with RedHat congestion protocol. But I can't find how to change or look at that with Solaris 10???

Found an article that describes this for Solaris 11, but not for Solaris 10.

Anyone that can help me on how to do this on Solaris 10 or point me in any direction on how to solve this problem?
 

8 More Discussions You Might Find Interesting

1. OS X (Apple)

change network time protocol

by default, a mac syncs its time and date with time.apple.com (located system prefs->Date&Time). Is there a way in unix to change it to another address? my attempts to use ntpdate and ntpd have failed. (4 Replies)
Discussion started by: CBarraford
4 Replies

2. Solaris

change disk under solaris 6

hi every one , i want to change the failed disk under solaris 6 i know that it's different than other revisions but i havn't a procedure ,can someone help me plz? (5 Replies)
Discussion started by: lid-j-one
5 Replies

3. Solaris

Solaris ip Change

Hi all i changed ip of my sunfire V490 machine by using the ifconfig command i modified following files /etc/hosts /etc/netmasks /etc/defaultrouter /etc/inet/ipnodes still when i rebooted the server ip got change. can nyone tell me reasonwhy it happens....... (7 Replies)
Discussion started by: raynu.sharma
7 Replies

4. UNIX for Advanced & Expert Users

Looking for a Low-Latency TCP Congestion Avoidance Algorithm

I was looking at differnt types of TCP Congestion Avoidance algorithms and realized that they are almost all tailored toward "high speed networks with high latency" (aka. LFN) Anybody know of a Congestion Avoidance algorithm used in low-latency networks? (3 Replies)
Discussion started by: jjinno
3 Replies

5. Solaris

temperory ip change in solaris 9

Hi Admins, For testing purpose we are moving sun solaris 9 in to test vlan .So i need to change the ip, subnet mask and gateway temperorily. Below are the procedure m going to perform. 1. Backup of ifconfig -a , netstat -an, netstat -rn , netstat -in 2. Backup of... (5 Replies)
Discussion started by: newsol
5 Replies

6. IP Networking

When should TCP congestion avoidance be used?

I have a Cisco small business switch and I am wondering what I will gain (or lose) by enabling "TCP congestion avoidance". I read the definition of it but how does one know when one should use it? (0 Replies)
Discussion started by: herot
0 Replies

7. IP Networking

TCP initial congestion window (slow-start)

I have noticed that the initial congestion window in my traces is 8920bytes~=6*1448. rfc3390 states the initial cwand should be max 4000 bytes(around 3*1448). At first i thought it might be because i'm running my server on mac os x, so apple might have modified the tcp stack. Therefore I tried... (2 Replies)
Discussion started by: ddayan
2 Replies

8. Solaris

Transfer files from windows to solaris with winscp (file protocol:SFTP)

Hello, I have a couple of zip files to be copied from my local drive to a folder in solaris10 residing in a VM ware. i am using WINSCP, I tried to get hold of the solaris hostname or ip using ifconfig -a , hostname|nslookup etc. when i create a new session in WINSCP using that IP and port... (6 Replies)
Discussion started by: herbich1985
6 Replies
nisbackup(1M)						  System Administration Commands					     nisbackup(1M)

NAME
nisbackup - backup NIS+ directories SYNOPSIS
nisbackup [-v] backup-dir directory... nisbackup [-v] -a backup-dir DESCRIPTION
nisbackup backs up a NIS+ directory object on a NIS+ master server. Updates to the NIS+ database will be temporarily disabled while nis- backup is running. The backup-dir is a UNIX directory that must exist prior to running nisbackup. The nisbackup command can be used to backup an individual NIS+ directory object or all ( -a) of the NIS+ directory objects served by a master server. The NIS+ directory objects being backed up will be placed into subdirectories under the backup-dir directory. These subdirectories are named according to the NIS+ directory object they contain. nisbackup operates on individual NIS+ directory objects (for example, org_dir.wiz.com). This allows an administrator to selectively backup specific directories. The rpc.nisd(1M) process must be running on the master server with a stable NIS+ database for nisbackup to complete. nisbackup will not attempt to correct any corruption in the NIS+ database, so it is important that backups be done regularly as part of the NIS+ administra- tion. The first synopsis is used to backup a single NIS+ directory object or a list of NIS+ directory objects. The objects can be partially qual- ified or fully qualified. The machine on which the command is executing must be the master for the NIS+ directory objects specified. The second synopsis will backup all of the NIS+ directory objects that are served by this master. The -a option is the recommended method of backing up a master server, since it will backup all NIS+ directory objects that are served by this master. If this server is a master server for more than one domain, the backup will include NIS+ directories that belong to all of the domains served. Individual NIS+ direc- tory objects can be selected for restoring from a backup-dir created with the -a option. See nisrestore(1M). The -a option only includes directory objects for which this server is the master. It is possible, but not recommended, to configure a master server as a replica for other domains. The objects belonging to those replicated domains will not be backed up with the -a option. The backup of replicated objects must be run on the master server for those objects. Do not use the same backup-dir to backup different master servers. Each master server must have its own backup-dir. nisbackup will set the rpc.nisd(1M) to read only mode, which will disable updates to the NIS+ database. This is neccessary to ensure the consistency of the backup. For this reason, nisbackup should not be run while large numbers of updates are being applied to the NIS+ data- base. Update utilities such as nisaddent(1M) should not be run simultaneously with nisbackup. OPTIONS
-a Creates a backup of all NIS+ directory objects for which this server is a master. -v Verbose option. Additional output will be produced and sent to syslog(3C) upon execution of the command (see syslog.conf(4)). OPERANDS
backup-dir The directory into which the subdirectories containing the backed up objects are placed. This must be created prior to running nisbackup. directory The NIS+ directory object(s) being backed up. EXAMPLES
Example 1: Backup of the org_dir NIS+ directory object of the domain foo.com on a master server to a directory named /backup To backup the org_dir NIS+ directory object of the domain foo.com on a master server to a directory named /backup: master_server# nisbackup /backup org_dir.foo.com. Example 2: Backup of the entire NIS+ domain foo.com to a directory named /backup To backup the entire NIS+ domain foo.com to a directory named /backup: master_server# nisbackup /backup foo.com. org_dir.foo.com. groups_dir.foo.com. ctx_dir.foo.com. Example 3: Backup of an entire NIS+ database to a backup directory named /backup To backup an entire NIS+ database to a backup directory named /backup: master_server# nisbackup -a /backup EXIT STATUS
0 Successful completion. 1 An error occurred. FILES
/backup-dir/backup_list This ascii file contains a list of all the objects contained in this backup-dir directory. /backup-dir/directory-object A subdirectory that is created in the backup-dir that contains the NIS+ directory-object backup. /backup-dir/directory-object/data A subdirectory that contains the data files that are part of the NIS+ directory-object backup. /backup-dir/directory-object/last.upd This data file contains timestamp information about the directory-object. /backup-dir/directory-object/data.dict A NIS+ data dictionary for all of the objects contained in the NIS+ directory-object backup. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnisu | +-----------------------------+-----------------------------+ SEE ALSO
nis+(1), nisdefaults(1), nisrm(1), nisrestore(1M), rpc.nisd(1M), syslog(3C), nisfiles(4), syslog.conf(4), attributes(5) NOTES
NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html. SunOS 5.10 12 Dec 2001 nisbackup(1M)
All times are GMT -4. The time now is 03:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy