Configuring bge.conf

From: Mark de Roo (Mark.de.Roo_at_asml.com)
Date: 11/28/03

  • Next message: Cirus Gaspar: "SUMMARY: SunCluster 3.0 behaviour at shutdown"
    Date: Fri, 28 Nov 2003 10:33:41 +0100
    To: sunmanagers@sunmanagers.org
    
    

    Hi,

    The bge inferface (V210) can be forced to a certain speed and duplex
    via two methodes: ndd and bge.conf

    NDD Creating a script in /etc/rc2.d/S68net_tune
               #!/sbin/sh
               # /etc/rc2.d/S68net-tune
               PATH=/usr/bin:/usr/sbin
               # Force bge0 to 100fdx autoneg off
               ndd -set /dev/bge0 adv_1000fdx_cap 0
               ndd -set /dev/bge0 adv_1000hdx_cap 0
               ndd -set /dev/bge0 adv_100fdx_cap 1
               ndd -set /dev/bge0 adv_100hdx_cap 0
               ndd -set /dev/bge0 adv_10fdx_cap 0
               ndd -set /dev/bge0 adv_10hdx_cap 0
               ndd -set /dev/bge0 adv_autoneg_cap 0

    bge.conf Adding the following line to the file
               /platform/sun4u/kernel/drv/bge.conf

               adv_autoneg_cap=0 adv_1000fdx_cap=0 adv_1000hdx_cap=0 \
               adv_100fdx_cap=1 adv_100hdx_cap=0 adv_10fdx_cap=0 \
               adv_10hdx_cap=0;

    However, using bge.conf will force all instances of bge to the
    speed/duplex specified in the file.

    My question:

    Is it possible to do this per instance within the bge.conf file
    or can it only be done via NDD?

    I know it is possible for ce instances within the file
    /platform/sun4u/kernel/drv/ce.conf file using three
    parameters: name, parent, and unit-address.

    name="pci108e,abba" parent="/pci@21c,700000/pci@1" unit-address="0" \
    adv_autoneg_cap=0 adv_1000fdx_cap=0 adv_1000hdx_cap=0 \
    adv_100fdx_cap=1 adv_100hdx_cap=0 adv_100T4_cap=0 adv_10fdx_cap=0 \
    adv_10hdx_cap=0;

    I will summarize.

    Thanks,
    Mark

    -- 
    The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. ASML is neither liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt.
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers
    

  • Next message: Cirus Gaspar: "SUMMARY: SunCluster 3.0 behaviour at shutdown"

    Relevant Pages