e1000g0 is running speed of 100mbps on T5220 with Solaris 10
Installed.
e1000g0 is not able to auto-negotiate. Switch has set to auto for both
interface.
while the other interface e1000g1 is running as 1000mbps.

Can Anyone help?

> e1000g0 is running speed of 100mbps on T5220 with Solaris 10 installed.
> e1000g0 is not able to auto-negotiate.

What speed is shown by the command "dladm show-dev"?
The interface is certainly capable of autonegotiation.  Verify /kernel/
drv/e1000g0.conf

> Switch has set to auto for both interface, while the other interface e1000g1 is running as 1000mbps.

What kind of switch are you using?  Double-check the config and reset
the port.

ITguy wrote:
>> e1000g0 is running speed of 100mbps on T5220 with Solaris 10 installed.
>> e1000g0 is not able to auto-negotiate.
> 
> What speed is shown by the command "dladm show-dev"?
> The interface is certainly capable of autonegotiation.  Verify /kernel/
> drv/e1000g0.conf
> 
>> Switch has set to auto for both interface, while the other interface e1000g1 is running as 1000mbps.
> 
> What kind of switch are you using?  Double-check the config and reset
> the port.


ISTR that there were, as usual, ambiguities in the standard which were 
interpreted differently by various vendors.  IFF autonegotiation works, 
use it!  Otherwise forcing BOTH ends to 1000 Full Duplex MAY be the only 
way to get it to work.

On 06/25/09 19:34, ITguy wrote:
>> e1000g0 is running speed of 100mbps on T5220 with Solaris 10 installed.
>> e1000g0 is not able to auto-negotiate.
> 
> What speed is shown by the command "dladm show-dev"?
> The interface is certainly capable of autonegotiation.  Verify /kernel/
> drv/e1000g0.conf
> 
>> Switch has set to auto for both interface, while the other interface e1000g1 is running as 1000mbps.
> 
> What kind of switch are you using?  Double-check the config and reset
> the port.

all good advice.  technical details/best practices for gigabit autoneg:

www.sun.com/blueprints/0704/817-7526.pdf

you can also use kstat to pull out capabilities, advertised and active 
parameters for the interface and the switch.

kstat -p e1000g:1:mac to display. substitute ":X" with the instance in 
question.  1 is active, zero is inactive:

e1000g:1:mac:adv_  for the interfaces advertised parameters

example:

e1000g:1:mac:adv_cap_1000fdx    1
e1000g:1:mac:adv_cap_1000hdx    0
e1000g:1:mac:adv_cap_100fdx     1
e1000g:1:mac:adv_cap_100hdx     1
e1000g:1:mac:adv_cap_10fdx      1
e1000g:1:mac:adv_cap_10hdx      1
e1000g:1:mac:adv_cap_asmpause   1
e1000g:1:mac:adv_cap_autoneg    1
e1000g:1:mac:adv_cap_pause      1


e1000g:1:mac:cap for the interfaces available parameters (not always the 
same as the advertised parameters if interface is being forced; also 
helps identify a 10/100 vs a 10/100/1000 Mbps capable card)

example:

e1000g:1:mac:cap_1000fdx        1
e1000g:1:mac:cap_1000hdx        1
e1000g:1:mac:cap_100fdx 1
e1000g:1:mac:cap_100hdx 1
e1000g:1:mac:cap_10fdx  1
e1000g:1:mac:cap_10hdx  1
e1000g:1:mac:cap_asmpause       1
e1000g:1:mac:cap_autoneg        1
e1000g:1:mac:cap_pause  1


e1000g:1:mac:lp_cap_ for the link partner (switch) advertised 
parameters.  This will only show full info when the link is 
autonegotiated, which is required for copper gigabit.  If all zeros, 
there is a problem/no link.

e1000g:1:mac:lp_cap_1000fdx     1
e1000g:1:mac:lp_cap_1000hdx     0
e1000g:1:mac:lp_cap_100fdx      1
e1000g:1:mac:lp_cap_100hdx      1
e1000g:1:mac:lp_cap_10fdx       1
e1000g:1:mac:lp_cap_10hdx       1
e1000g:1:mac:lp_cap_asmpause    1
e1000g:1:mac:lp_cap_autoneg     1
e1000g:1:mac:lp_cap_pause       1

You can also check /var/adm/messages for link up/link down messages from 
the driver.

Richard B. Gilbert <rgilbert88@comcast.net> wrote:
> ISTR that there were, as usual, ambiguities in the standard which
> were interpreted differently by various vendors.  IFF
> autonegotiation works, use it!  Otherwise forcing BOTH ends to 1000
> Full Duplex MAY be the only way to get it to work.

My recollection is that while there may have been ambiguities and
certainly implementation issues in the days when 100BT was king, by
the time GbE came along it was all pretty well resolved, and thusfar
while my life may be charmed (I have some but not massive exposure to
Solaris and its drivers, and virtually all my switches are ProCurve)
I've yet to see an autoneg issue with GbE NICs.

Doesn't GbE require that autoneg be enabled?  Not necessarily that all
possible speeds and duplex settings be advertised, but that autoneg be
enabled?  I suppose that comp.dcom.lans.ethernet would be one place to
get that question resolved.

rick jones
-- 
firebug n, the idiot who tosses a lit cigarette out his car window
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...

Rick Jones wrote:
> Richard B. Gilbert <rgilbert88@comcast.net> wrote:
>> ISTR that there were, as usual, ambiguities in the standard which
>> were interpreted differently by various vendors.  IFF
>> autonegotiation works, use it!  Otherwise forcing BOTH ends to 1000
>> Full Duplex MAY be the only way to get it to work.
> 
> My recollection is that while there may have been ambiguities and
> certainly implementation issues in the days when 100BT was king, by
> the time GbE came along it was all pretty well resolved, and thusfar
> while my life may be charmed (I have some but not massive exposure to
> Solaris and its drivers, and virtually all my switches are ProCurve)
> I've yet to see an autoneg issue with GbE NICs.
> 
> Doesn't GbE require that autoneg be enabled?  Not necessarily that all
> possible speeds and duplex settings be advertised, but that autoneg be
> enabled?  I suppose that comp.dcom.lans.ethernet would be one place to
> get that question resolved.
> 
> rick jones

I've never done it!  With that disclaimer: autonegotiation is the way to 
go IF IT WORKS.  Sometimes it doesn't!  Autonegotiation is MOST likely 
to fail with older hardware.  When autonegotiation fails, you can try 
setting both ends to 10/100/1000 FD or HD as you prefer.  Just be sure 
that both ends are set the SAME!  Document what you did so that people 
will know, even if you walk in front of a speeding truck or are shot by 
a jealous husband.

Someday an unambiguous standard will be adopted and successfully 
implemented and we can all die of shock! ;-)