Solaris 9 ndd -set issues Post: 302827411

9 More Discussions You Might Find Interesting

1. IP Networking

ndd and le1

I am trying to set an interface to 100/Full, but the command I use are getting rejected. I think it is the last argument, but I don't know how to find the correct values. I am trying to use the following script, but change hme to le . echo "Setting hme interface 1: 100mb/full-duplex..." ...

2. Solaris

ndd help

Hi Guys, I need help with ndd. I was going through network FAQ but i have more questions then answers regarding ndd. #ndd -set /dev/hme instance 0 #ndd -set /dev/hme adv_100fdx_cap 1 #ndd -set /dev/hme adv_100hdx_cap 0 #ndd -set /dev/hme adv_10fdx_cap 0 #ndd -set /dev/hme adv_10hdx_cap 0...

3. Solaris

Questions related to ndd commands

Hello Gurus I would like to know more about ndd commands related to ethernet(NIC) like how to set link_status, link_speed & link_mode as I know how to check these value. And I also would like to know how to make these setting permanents after reboot as I know that these setting will vanish...

4. Solaris

ndd matters

Hi, I would like to know whether there is any config file that i can refer to for the result of 'ndd -get /dev/tcp tcp_time_wait_interval'? When i man 'ndd', there is one statement which is -> Each driver chooses which parameters to make visible using ndd. Does it answering my question above...

5. Solaris

ndd /dev/tcp help

Solaris 10 server (SunOS 5.10 Generic_137137_09) I have a services file configured in /etc in there windows clients connect to my server on port 6034-6037 when I do the following netstat | grep TestServices it pulls all the connections active for those ports so right now I have 10 clients...

6. Solaris

ndd -set /dev/tcp tcp_host_param

Following command was set up in startup script on Solaris 8 servers - improved network transfers of files from one server to the another (doubled transfer speed). ndd -set /dev/tcp tcp_host_param '10.140.20.10 sendspace 279600 recvspace 279600 timestamp 1' Now they are getting a new server...

7. Solaris

Solaris 8 vs Solaris 10 compatibility issues !

Hello, I recently upgraded our system from Solaris 8 to 10. It seems couple of binaries crashed in the new server Solaris 10. Before digging too much on it , from theory it sounds like any binary that is built on Solaris 8 (using gmake) is supposed to be compatible with Solaris 10 , right ? ...

8. UNIX for Dummies Questions & Answers

nLocal sendmail issues when hostname not set in official domain name

Hi, I'm having issues with sendmail when I try to send host to host mail. I've had to change the "my official domain name" line to mycompany.com to get the mails through the external spam filter, when a mail was sent with hostname.mycompany.com it was blocked. I had to change the Dj macro...

9. Solaris

Ndd adv_autoneg_cap showing read only

Hi, Recently, I had to disable autoneg in one of my servers having ixgbe1 interface. While using below command I got "Permission denied" error: ndd -set /dev/ixgbe1 adv_autoneg_cap 0 On investigating further I found that adv_autoneg_cap is showing as read-only parameter. Although it is...

LEARN ABOUT OPENSOLARIS

clprivnet

clprivnet(7)					     Sun Cluster Device and Network Interfaces					      clprivnet(7)

NAME

       clprivnet - SUNW,clprivnet Sun Cluster private network driver

SYNOPSIS

       /dev/clprivnet

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.

       The  SUNW,clprivnet  Sun  Cluster  private  network driver is a STREAMS pseudo driver supporting Sun Cluster resident applications that use
       standard Solaris interfaces to communicate over the Sun Cluster private network. By striping data traffic over all links, this driver opti-
       mally utilizes the bandwidth of the private network while supporting highly available, software fault-tolerant communication.

APPLICATION PROGRAMMING INTERFACE

       The driver is supported by the character-special device /dev/clprivnet, but is reserved for Sun Cluster internal operation and the standard
       Solaris network utilities. This interface must not be directly used for general application communication.

ADMINISTRATION

       The administration and configuration of the driver as a network interface is done completely by the Sun Cluster infrastructure internals.

FILES

       /dev/clprivnet

	   clprivnet special character device

       /usr/kernel/drv/clprivnet.conf

	   System-wide default device driver properties

Sun Cluster 3.2 						    05 Sep 2007 						      clprivnet(7)