Problem with full duplex mode.

[gjk]

Hello,

I have recently connected an Omni switch 6250-48 to Sun servers for a GSM company. This servers cover live traffic and the "IT" of this company insist on keeping the NIC configuration of this servers in forced 100 full duplex. When they do so the the Omni Switch when set to auto-negotiation detects 100 half duplex and lots of collisions are reported. From documentation I found out why.I have highlighted my case:
Autonegotiation Guidelines
Please note a link will not be established on any copper Ethernet port if any one of the following is true:
• The local port advertises 100 Mbps full duplex and the remote link partner is forced to 100 Mbps full
duplex.
• The local port advertises 100 Mbps full duplex and the remote link partner is forced to 100 Mbps half
duplex.
• The local port advertises 10 Mbps full duplex and the remote link partner is forced to 10 Mbps full
duplex.
• The local port advertises 10 Mbps full duplex and the remote link partner is forced to 10 half duplex.
This is due to the fact that when the local device is set to auto negotiating 10/100 full duplex it senses the
remote device is not auto negotiating. Therefore it resolves to Parallel Detect with Highest Common
Denominator (HCD), which is “10/100 Half” according to IEEE 802.3 Clause 28.2.3.1.

I wanted to know if anyone has encountered this before and knows a solution other than putting the server NIC to auto.

Many thanks

[one6f]

I wanted to know if anyone has encountered this before and knows a solution other than putting the server NIC to auto.

This is quite normal, simply put the switch port to 100Full and disable autonegotiation.

[gjk]

I already did but it didn't work till i rebooted the thing.
Thanks for your help.

[one6f]

Strange. Normally its enough copy/paste this block:

Code: Select all

interface 1/2 admin down
interface 1/2 alias "Server NIC"
interface 1/2 autoneg disable
interface 1/2 duplex full
interface 1/2 speed 100
interface 1/2 admin up

[gjk]

What i meant was that after rebooting the switch, it works fine and connection is established.
Many thanks.

[bitbin]

I would suggest enabling auto-negotiation on the solaris server instead of hard coding the speed and duplex.

http://www.brandonhutchinson.com/Solari ... tings.html