NetRAIN 100 Mpbs full duplex static

[Mathias Schmassmann]

With this NetRain configuration:

nr0: flags=c63
NetRAIN Attached Interfaces: ( ee0 ee2 ) Active Interface: ( ee0 )
inet 10.1.5.22 netmask ffffffc0 broadcast 10.1.5.63 ipmtu 1500

Which is the correct setting, for example in inet.local, for a static 100 Mpbs full duplex setting?

a) Setting the two interfaces ee0,ee2:
lan_config -i ee0 -s 100 -x 1
lan_config -i ee2 -s 100 -x 1

b) Setting the interface nr0:
lan_config -i nr0 -s 100 -x 1

Thanks.

Mathias

[Michael Schulte zur Sur · Accepted solution]

Hi,

when you have netrain configured, you can not set the speed individually but must use the netrain device.

greetings,

Michael

[Mathias Schmassmann]

Thanks. I will use b).

The documentation for NetRAIN configuration simple says: "If you use Ethernet adaptors, they must all be of the same speed."

So I did not know if I had to set the adapters individually or not.

Mathias

[Ralf Puchner]

It is not a good idea to use the intel cards without autoneg....

[Michael Schulte zur Sur]

Matthias,

I overlooked that you use ee cards.
Is there any reason for not using auto sensing? We use only that at ma work.

greetings,

Michael

[Mathias Schmassmann]

Yes, there is. The problem is "autonegotiation mismatches". To maximize switch performance, usually either both ports autonegotiate speed and duplex or manually set the speed and duplex parameters for the ports on both ends of the connection.
All ports in the network core are statically set to 100Mbps/full. Sometimes we notice that when the servers are set to autonegotiate they will come up on their end with 100 Mbps/half. On the other hand, when the servers are set to static and the port on the network core are set to autonegotiate sometimes the ports on the network core will negotiate at 100 Mbps/half. Better to set a standard that states if you want the best connectivity from your server's perspective then statically set your NIC. This guarantees consistency across the board and helps up define a standard.

Mathias

[Rob Leadbeater]

Hi Mathias,

What you say regarding fixing network speeds on both the core and the adapter is *usually* correct, but from experience this is not true of Intel cards in Tru64 boxes.

The only way I could get some DS25s working correctly when connected to some Cisco Catalyst switches was to set both ends to auto-negotiate. Attempting to fix either or both ends, caused problems.

Cheers,
Rob

[Mathias Schmassmann]

Michael posted the answer which solved my problem. Thanks.