Re: Cisco 4507R and Broadcom NetXtreme NICs
- From: Trendkill <jpmason@xxxxxxxxx>
- Date: Wed, 06 Jun 2007 19:46:10 -0000
On Jun 6, 3:33 pm, "stephen" <stephen_h...@xxxxxxxxxxxx> wrote:
"jw" <j...@xxxxxxxxxxxxxxx> wrote in message
news:46670847$0$4332$9a566e8b@xxxxxxxxxxxxxxxxxx
Ibm servers frequently have issues with auto negotiation.ports.
Check ALL your ibm servers for sp/dplx harcoding and errors on those
Trendkill wrote:
On Jun 6, 9:05 am, Inthemix88 <martinreye...@xxxxxxxxx> wrote:
Good morning all,
We are having an issue with Broabcom Gigabit NetXtreme Nics. One of
the NICs reports that it is connected at 100 Mb instead of 1000. We
are running a Cisco 4507R on the backend. Cisco IOS Version is 12.2
(20). I know this is not the latest version but all our switches run
the same IOS and we are having this problem only on 3 out of 8
buildings. Our servers are IBM 336 with the previously mentioned NIC
cards. We have replaced the motherboard on the IBM servers. We updated
the firmware on the NIC cards. Our NOS is Windows 2003 sp1. (We
updated one server to sp2, problem still exists). We have updated the
NIC card driver to the latest version. We swapped the cables out using
cat 5e and 6. We also tried different ports on the blade and switch
(we have 2 48 port gigabit blades).
If anyone can give us some feedback, it would be greatly appreciated.
Thanks in advanced,
Martin Reyes
LHRIC
Not to suggest the obvious, but have you hard coded both sides (switch
& server) to 1000/full per cisco best practices.
Not sure this is true for GigE.
although a lot of devices had problems with 100 Base-TX, the IEEE standard
says auto is mandatory for 1000 Base-T, since it is used to sort out master
/ slave etc.http://www.ethermanage.com/ethernet/autoneg.html
Even on GigE fibre where the 2 devices dont have to negotiate, some devices
will not work unless auto- negotiate is enabled on the other device
- I stumbled across this on a Foundry L3 switch recently, connecting to a
GigE on an SDH mux.
While auto/auto on
both sides is also acceptable (for gig only), you should really stick
to a plan of hard coding both sides as it makes for better long term
support, documentation, and maintenance.
i think with GigE you are likely to find at least as many places where
disabling auto is going to cause problems rather than solve them.
--
Regards
stephen_h...@xxxxxxxxxxxx - replace xyz with ntl
I agree with you, although if he's having issues with auto, he might
as well try hard-coding. There is no one answer with gig, but you
have to set both sides to the same regardless of which way you go. At
my previous employer, we had a lot of issues with IBM boxes on boot
and auto-mdix. The command was hidden, but we had tier 3 at TAC and
IBM on the phone and no one knew enough to own up. All I can tell you
is those damn Regattas were sending some kind of pulse that caused
auto-mdix to trip, and we eventually had to set auto-mdix to disable
on all our switch ports for these boxes. Fixed the problem right
away, although never got an official explanation.
.
- References:
- Cisco 4507R and Broadcom NetXtreme NICs
- From: Inthemix88
- Re: Cisco 4507R and Broadcom NetXtreme NICs
- From: Trendkill
- Re: Cisco 4507R and Broadcom NetXtreme NICs
- From: jw
- Re: Cisco 4507R and Broadcom NetXtreme NICs
- From: stephen
- Cisco 4507R and Broadcom NetXtreme NICs
- Prev by Date: Re: Cisco 4507R and Broadcom NetXtreme NICs
- Next by Date: Re: Cisco 4507R and Broadcom NetXtreme NICs
- Previous by thread: Re: Cisco 4507R and Broadcom NetXtreme NICs
- Next by thread: Re: Cisco 4507R and Broadcom NetXtreme NICs
- Index(es):
Relevant Pages
|
