Hi, I got an Netra T1 server, configured the 2 NICs, the first is eri0, second eri1. The bandwidth is terrible, like 0.5-2.0 kb/sec. Anyway advice is helpful, as I dont have a clue what the problem might be. Alex

I tested some more, and I found out that ftp from my Netra T1 server to another machine is ok, eq 400 kb/sec + Alex

Hi, I have the same problem with my 4 Sun Fire Servers V880. Speed of 400K/s is not good performance for network. I have 44.000 Kbits/s now after applying these Tips. Permanent solution has not been tested anymore. Be carefull. Good luck @+ Eddy (eddy.legrain@minsoc.fed.be) 1) For display information about speed and mode of NIC in the Sun Fire V880 servers ------------------------- At the root user type : For the first NIC (eri0) ndd -set /dev/eri instance 0 ndd -get /dev/eri linK_speed ndd -get /dev/eri link_mode For the second NIC (eri1) ndd -set /dev/eri instance 1 ndd -get /dev/eri linK_speed ndd -get /dev/eri link_mode and so on for the next NIC Result for - link_mode is 0 for Half duplex and 1 for Full duplex - link_speed is 0 for 10Mb/s and 1 for 100Mb/s Default values are 100 Mb/s and Half duplex 2) For modify in the fly (loss at next reboot of server) --------------------------- To perform a hard set of the link_speed and link_mode parameters for eri0, several other parameters must be set with the ndd -set command. In these parameter names, 10 or 100 refers to link_speed, fdx or hdx refers to link_mode, and autoneg refers to autonegotiation capability. The setting corresponding to the desired mode should be set to "1" and all other parameters should be set to "0." (adv_autoneg_cap=1 is the default.) For example, to set eri0 to 100/full duplex: ndd -set /dev/eri instance 0 ndd -set /dev/eri adv_100T4_cap 0 ndd -set /dev/eri adv_100fdx_cap 1 ndd -set /dev/eri adv_100hdx_cap 0 ndd -set /dev/eri adv_10fdx_cap 0 ndd -set /dev/eri adv_10hdx_cap 0 ndd -set /dev/eri adv_autoneg_cap 0 3) To set value at each reboot of the server - NOT TESTED - ndd -set commands can be used in the /etc/rc2.d/S69inet initialization script to set the interface mode during boot rather than allowing autonegotiation. This can be useful if one of the interfaces is connected to an older switch that is not autonegotiating the line speed or mode correctly. The line speed and mode can also be set for all eri interfaces on the system by setting the following in the /etc/system file and rebooting. (Note: The following are Sun's official recommendations. It may not be necessary to set every parameter to either 0 or 1, but it is easiest to get support when following instructions to the letter.): 100 Mb, full duplex: set eri:eri_adv_autoneg_cap=0 set eri:eri_adv_100fdx_cap=1 100 Mb, half duplex: set eri:eri_adv_autoneg_cap=0 set eri:eri_adv_100fdx_cap=0 set eri:eri_adv_100hdx_cap=1 10 Mb, full duplex: set eri:eri_adv_autoneg_cap=0 set eri:eri_adv_100fdx_cap=0 set eri:eri_adv_100hdx_cap=0 set eri:eri_adv_10fdx_cap=1 set eri:eri_adv_10hdx_cap=0 10 Mb, half duplex: set eri:eri_adv_autoneg_cap=0 set eri:eri_adv_100fdx_cap=0 set eri:eri_adv_100hdx_cap=0 set eri:eri_adv_10fdx_cap=0 set eri:eri_adv_10hdx_cap=1 4) Hardware Testing ------------------- One elementary test for the ethernet hardware is to invoke the watch-net-all command from the ok> PROM monitor prompt. This performs some simple diagnostics and listens on the ethernet port. Since this is at a much lower level than the driver level, it can be used to distinguish between hardware and software problems. Debug Mode The hme, qfe and be ethernet drivers can be switched into debug mode. This can be done in the /etc/system file by adding a line like : set hme:hmedebug=1 Alternatively, this can be done on a live system using adb : adb -kw /dev/ksyms /dev/mem hmedebug/D (to display current value) hmedebug/W 1 (be careful to use uppercase "W") Debug mode permits the driver to display messages to the console. Some of the messages are informational, others are error messages. When examining the messages, remember that you are seeing one system's view of the network, and that this bias needs to be taken into account.

CORRECTION! For cards like hme #3 would work, but the eri syntax is different. For example in /etc/system: #100 Mb, full duplex: set eri:adv_autoneg_cap=0 set eri:adv_100fdx_cap=1 is the correct method.