1000 FD setting

[M.Thomas]

How do i change my NIC card to 1000 base-t setting? it is currently on 100 FD. I need to convert this to 1000 base -t. Please can you provide the steps,

Thanks

Thomas

[Mel Burslan]

You simply CAN NOT. Gigabit speed can not be hard set to 1000. You just let your inteface float and if the other side, i.e., switch port, is set to 1000 base-t, you will attain gigabit speeds. If it is not getting there, talk to your network admins. Some switches, even ig they are gigabit capable, comes with their ports set 100BT. They may need to change the equipment settings on the networking end.

[M.Thomas]

so i just change these settings to 100 FD and autoneg on and if it is a gig switch then i will get the speed correct? The most important is autoneg on -correct? i am going to use SAM to make thses changes.

Thanks

Mthomas

[M.Thomas]

also if i go to sam and list the interfacesif it says 1000 then it is Gig capable right?

Thanks

Mthomas

[IT_2007]

you can only enable 1000 on Gig cards.

ioscan -fnClan will show you all lan cards and it's description.

Setting autonegotiation on is not good if your switch isn't configured for it. To achieve high speed for 100MB cards, set autonegotiation off.

For Gig cards, auto negotiation on is default and can't change it to off.

you can edit /etc/rc.config.d/hpigelanconf for Gig cards and hpbtlanconf for 100MB ethernet cards. Don't have to use SAM.

[M.Thomas]

these are gig cards..
\# ioscan -fnC lan
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
lan 0 0/1/2/0 igelan CLAIMED INTERFACE HP PCI 1000Base-T Core
lan 1 0/2/1/0 iether CLAIMED INTERFACE HP A7012-60001 PCI/PCI-X 1000Base-T Dual-port Adapter
lan 2 0/2/1/1 iether CLAIMED INTERFACE HP A7012-60001 PCI/PCI-X 1000Base-T Dual-port Adapter
#

[IT_2007]

Ok. You need to talk to your network team to achieve 1000MB speed because your cards are capable of 1000MB but switch port may not be configured for 1000MB.

Once they set it for 1000MB then you can configure in /etc/rc.config.d/hpigelanconf for lan0 card to set autonegotiation on with 1000FD.

For lan1 and lan2 if you want to use them, configure in /etc/rc.config.d/hpetherconf file.

[rick jones]

How 100Base-T Autoneg is supposed to work:

When both sides of the link are set to autoneg, they will "negotiate"
the duplex setting and select full-duplex if both sides can do
full-duplex.

If one side is hardcoded and not using autoneg, the autoneg process
will "fail" and the side trying to autoneg is required by spec to use
half-duplex mode.

If one side is using half-duplex, and the other is using full-duplex,
sorrow and woe is the usual result.

So, the following table shows what will happen given various settings
on each side:

Auto Half Full

Auto Happiness Lucky Sorrow

Half Lucky Happiness Sorrow

Full Sorrow Sorrow Happiness

Happiness means that there is a good shot of everything going well.
Lucky means that things will likely go well, but not because you did
anything correctly :) Sorrow means that there _will_ be a duplex
mis-match.

When there is a duplex mismatch, on the side running half-duplex you
will see various errors and probably a number of _LATE_ collisions
("normal" collisions don't count here). On the side running
full-duplex you will see things like FCS errors. Note that those
errors are not necessarily conclusive, they are simply indicators.

Further, it is important to keep in mind that a "clean" ping (or the
like - eg "linkloop" or default netperf TCP_RR) test result is
inconclusive here - a duplex mismatch causes lost traffic _only_ when
both sides of the link try to speak at the same time. A typical ping
test, being synchronous, one at a time request/response, never tries
to have both sides talking at the same time.

Finally, when/if you migrate to 1000Base-T, everything has to be set
to auto-neg anyway.

[Marvin Strong]

I believe you will need cat5e cable for copper to achieve 1000, in addition to eveything else mentioned above.