Hi Brian,

Thanks for being the first among many, many admins, hopefully :) to 
provide feedback. Much appreciated. Admins, keep 'em coming ;^)


Brandorr wrote:
> Questions
> 
>    1. Please provide a one-line or two-line overview of your
> networking environment.
>    Cisco shop, with F5 load balancers.
> 
>    2. Do you frequently change or upgrade your network interface cards?
>    No
> 
>    3. Do you modify existing NIC configuration or adjust the tunables?
> If yes, how frequently do you perform these tasks?
>    When we discover unexpected performance issues with new product.
> 
>    4. What tools or commands do you use to administer NICs? Are you
> satisfied with the existing tools? ifconfig netstat. It depends on
> what we are using them for. I would like to be able to use ifconfig to
> list interfaces that haven't been configured/probed yet.
> 
>    5. What do you like about the current methods to administer NICs?
> Please be as specific as possible. The only thing is that I know them,
> they work well from the commandline and are scriptable.
> 
>    6. What do you dislike about the current methods to administer
> NICs? If you are dealing with something other than IP the interfaces
> are completely different.
> 
>    7. What are the typical NIC tunables or properties that you monitor
> most of the time?
> 
>       (I haven't personally been responsible for these settings in 5
> years, but this is our most current standard).
>        # TCP           tunable                         value
>         #
>         $NDD_SET_TCP    tcp_max_buf                     4194304
>         $NDD_SET_TCP    tcp_cwnd_max                    2097152
>         $NDD_SET_TCP    tcp_xmit_hiwat                  65536
>         $NDD_SET_TCP    tcp_recv_hiwat                  65536
>         # $NDD_SET_TCP  tcp_xmit_hiwat                  400000
>         # $NDD_SET_TCP  tcp_recv_hiwat                  400000
>         $NDD_SET_TCP    tcp_conn_req_max_q              16384
>         $NDD_SET_TCP    tcp_conn_req_max_q0             16384
>         $NDD_SET_TCP    tcp_keepalive_interval          30000
>         $NDD_SET_TCP    tcp_time_wait_interval          60000
>         $NDD_SET_TCP    tcp_fin_wait_2_flush_interval   135000
>         $NDD_SET_TCP    tcp_strong_iss                  2
>         #
>         # UDP           tunable                         value
>         #
>         $NDD_SET_UDP    udp_max_buf                     4194304
>         $NDD_SET_UDP    udp_xmit_hiwat                  65536
>         $NDD_SET_UDP    udp_recv_hiwat                  65536
> 
> As far as reading is concerned we will use it generally only when we
> are troubleshooting. (At least that's the case for me).
> 
>    8. Do you have scripts that run at boot time which set ndd parameters?
>       Yes
> 
>    9. Do you write custom drivers?
> 
>       No
> 
> If yes, please provide any feedback about the following proposal by
> the Brussels project:
> 
> 
>       The Brussels project aims to provide a simpler and cleaner
> interface for GLDv3 drivers by using the dladm command. When GLDv3
> drivers register with the GLDv3 framework, these drivers drivers will
> provide function pointers for setting() and getting() properties.
> Subsequently, the dladm command can be used to send the appropriate
> system calls to trigger the registered set() and get() functions.
> 
> Overall, I like the idea of a standard driver interface model for
> networking cards.
> 
>   10.   Do you use Link Aggregation ("Trunking")?
>          Yes
>   11.  Do you use WiFi?
>         No, but Laptop users will need this.
>   12. Have you used the dladm as a configuration tool, such as dladm
> set-linkprop?
>         No
>       If yes, what do you like and dislike about this interface?
>   13. Are you interested in a GUI-based version of the dladm command?
>        Not personally. It is probably a good idea though.
>       If yes, what features would you like to be included in the
> GUI-based version?
>   14. Should the GUI-based tool be capable of tweaking all of the
> available NIC properties?
> 
>        Yes, especially if it is hooked into a good tooltips/help
> section. (Best option to have a basic and advanced modes of operation.
> 
>       If no, what selected properties should be configurable by the
> GUI-based tool, while the rest by a command line syntax?
> 
>   15. To configure the MTU property, would you prefer to select from a
> list of set values that is provided by the GUI, or would you prefer
> typing the value in an input field?
> 
> No opinion. (If you can't decide you could always use a pulldown list
> with another option).
> 
>       If you favor selecting from a list of given values, what MTU
> values do you suggest in addition to 1500 (for default) and 9000 (for
> jumbo frames support)?
> 
> On 10/16/07, Raoul Carag <Raoul.Carag at sun.com> wrote:
>> We set up a documentation page for the Brussels project. An overview of
>> the project is found here:
>>
>> http://www.opensolaris.org/os/project/brussels/
>>
>> To provide a user-friendly tool for configuring NIC drivers, we need to
>> hear from you. Your feedback and comments would help the team know how
>> to develop the tool to respond to admin needs .
>>
>> We put up a questionnaire and would appreciate if you would spare some
>> moments to answer them and send your comments to us. To access the
>> questionnaire, go to:
>>
>> http://www.opensolaris.org/os/project/brussels/Documentation/survey/
>>
>> A draft of administrative procedures resulting from the implementation
>> of Brussels is also available for review here:
>>
>> http://www.opensolaris.org/os/project/brussels/Documentation/procs/
>>
>> Feedback about this draft is also welcome.
>>
>> Thanks in advance.
>>
>> _______________________________________________
>> sysadmin-discuss mailing list
>> sysadmin-discuss at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss
>>
> 
> 

Reply via email to