And here's the show port I forgot!!
(enable) sh port 2/26
Port Name Status Vlan Duplex Speed Type
- -- -- -- -- -
2/26 Temp Driver server connected 990 full 100 10/100BaseTX
Port AuxiliaryVlan AuxV
Are you sure switch and NIC are the same speed and duplex? Looks like port
speed/duplex mismatch.
""Patrick Donlon"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Hi Everyone
>
> I trying to find some information on some Ethernet errors that I see on a
> port, see the text be
Positive, if you look at the show port (on the other mail) you'll see there
are no collisions
Thanks
""Steven A. Ridder"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Are you sure switch and NIC are the same speed and duplex? Looks like
port
> speed/duplex mismatch.
> ""Pat
Then try switching ports, shutting it down, different PC, etc,. It's
probably the PC then
""Patrick Donlon"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Positive, if you look at the show port (on the other mail) you'll see
there
> are no collisions
>
> Thanks
>
>
> ""Steven A
:36 AM
To: [EMAIL PROTECTED]
Subject: Re: ethernet errors explained [7:33687]
Positive, if you look at the show port (on the other mail) you'll see there
are no collisions
Thanks
""Steven A. Ridder"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
It's a RS6000 not a PC, I think it's running AIX
""Steven A. Ridder"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Then try switching ports, shutting it down, different PC, etc,. It's
> probably the PC then
> ""Patrick Donlon"" wrote in message
> [EMAIL PROTECTED]">news:[EM
You appear to have the inline power module for ip phones. I had a
problem once on a server where I disabled the power on the port and this
resolved the errors.
C6509> (enable) set port inlinepower 2/26 off
Dave
Patrick Donlon wrote:
>
> And here's the show port I forgot!!
>
> (enable) sh p
Dave tried that one first as I thought it was the most interesting, but
sadly
(enable) set port inline 2/26 off
Feature not supported on module 2.
I'll go back to basics first Ole.
Thanks for the replies
Pat
""MADMAN"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> You appea
Patrick Donlon wrote:
> Positive, if you look at the show port (on the other mail) you'll see there
> are no collisions
As the port is in full duplex, the fact that it doesn't show any
collisions doesn't mean anything, as it doesn't look for them. I agree
with the previous poster: triple-check t
At 09:35 AM 1/30/02, Patrick Donlon wrote:
>Positive, if you look at the show port (on the other mail) you'll see there
>are no collisions
This side is set (or auto-negotiated) to full duplex. Receiving while
sending is not an error. This side should never report a collision. That
doesn't mean
3:38 PM
Subject: Re: ethernet errors explained [7:33687]
> At 09:35 AM 1/30/02, Patrick Donlon wrote:
> >Positive, if you look at the show port (on the other mail) you'll see
there
> >are no collisions
>
> This side is set (or auto-negotiated) to full duplex. Receiving while
are errors.
(side note: you can run 10/full on CAT3 wiring without errors) If there are,
I would replace the NIC as the next step.
- Original Message -
From: "Priscilla Oppenheimer"
To:
Sent: Wednesday, January 30, 2002 3:38 PM
Subject: Re: ethernet errors explained [7:33687]
Are your systems connected by any type of punch down blocks. I have
experience may of
these errors due to crosstalk (like Priscilla stated) caused by bad punch
down blocks.
The only way i was able to see the sources causing the problems was with a
lan fluke.
Ko
Priscilla Oppenheimer wrote:
> A
I think the NIC is bad - have you tried changing to another port on the
switch and see if the errors move with it
-Original Message-
From: Patrick Donlon [mailto:[EMAIL PROTECTED]]
Sent: 30 January 2002 16:36 PM
To: [EMAIL PROTECTED]
Subject: Re: ethernet errors explained [7:33687
You can also get these nice kind of hard-to-troubleshoot issues if your
cables are not wired properly; i.e. 'crossed or mismatched pairs' on some
cable-testers.
Specifically - if the pinout is such that the wrong wires are being twisted
around each other ... would normally work just fine for reall
31, 2002 11:12 AM
To: [EMAIL PROTECTED]
Subject: RE: ethernet errors explained [7:33687]
You can also get these nice kind of hard-to-troubleshoot issues if your
cables are not wired properly; i.e. 'crossed or mismatched pairs' on some
cable-testers.
Specifically - if the pinout is suc
EMAIL PROTECTED]]On Behalf Of
Bolton, Travis
Sent: Thursday, January 31, 2002 10:36 AM
To: [EMAIL PROTECTED]
Subject: RE: ethernet errors explained [7:33687]
I would change out the cat 5 cable and also move the cable to a different
port/card on the switch. If you are still experiencing problems then I
17 matches
Mail list logo