PM
To: [EMAIL PROTECTED]
Subject: Large Collisions on Vlan1 [7:12961]
What does it mean when the sh int vlan1 output shows large collisions? For
example on a 2924 XL with an ISL trunk to a 6509 I go the ff output upon
issuing the SH INT VLAN1 command:
0 output errors, 19108404 collisions, 0
What does it mean when the sh int vlan1 output shows large collisions? For
example on a 2924 XL with an ISL trunk to a 6509 I go the ff output upon
issuing the SH INT VLAN1 command:
0 output errors, 19108404 collisions, 0 interface resets
Message Posted at:
Massive collisions implies half duplex transmission on interfaces expecting
full duplex access. I'll have to check this out, but I think you might have
duplex setting programmed as negotiate on both sides of trunk. Seems to me
that some platforms will default back to half-duplex and thus the
PM
To: [EMAIL PROTECTED]
Subject: Large Collisions on Vlan1 [7:12961]
What does it mean when the sh int vlan1 output shows large collisions? For
example on a 2924 XL with an ISL trunk to a 6509 I go the ff output upon
issuing the SH INT VLAN1 command:
0 output errors, 19108404 collisions, 0
Massive collisions implies half duplex transmission on interfaces expecting
full duplex access. I'll have to check this out, but I think you might have
duplex setting programmed as negotiate on both sides of trunk. Seems to me
that some platforms will default back to half-duplex and thus the
the 6500) and also manually set the link to full duplex.
-Original Message-
From: Kwame [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 19, 2001 12:25 PM
To: [EMAIL PROTECTED]
Subject: Large Collisions on Vlan1 [7:12961]
What does it mean when the sh int vlan1 output shows large co
:[EMAIL PROTECTED]]
Sent: Thursday, July 19, 2001 2:37 PM
To: [EMAIL PROTECTED]
Subject:Re: Large Collisions on Vlan1 [7:12961]
The counters won't clear. I used the ff command:
CLEAR COUNTERS VLAN1
I'm still seeing the same number of collisions on vlan1. Here's my trunk
Subject: Large Collisions on Vlan1 [7:12961]
What does it mean when the sh int vlan1 output shows large collisions?
For
example on a 2924 XL with an ISL trunk to a 6509 I go the ff output upon
issuing the SH INT VLAN1 command:
0 output errors, 19108404 collisions, 0 interface resets
Karen E Young wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
FYI - its a bad idea to enable portfast on any port that connects to a
multiport device (hub, router, or switch). It can cause problems with
spanning tree and routing loops. It seems to me that I've seen it
interfere
At 09:27 PM 7/19/01, Michael L. Williams wrote:
Karen E Young wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
FYI - its a bad idea to enable portfast on any port that connects to a
multiport device (hub, router, or switch). It can cause problems with
spanning tree and routing
-Learning-Forwarding) only when the (hub) uplink port is
initialized, not for each client off of the hub.
Hope that helps,
Ejay
-Original Message-
From: Michael L. Williams
To: [EMAIL PROTECTED]
Sent: 7/19/01 9:27 PM
Subject: Re: Large Collisions on Vlan1 [7:12961]
Karen E Young wrote
Collisions on Vlan1 [7:12961]
What does it mean when the sh int vlan1 output shows large collisions? For
example on a 2924 XL with an ISL trunk to a 6509 I go the ff output upon
issuing the SH INT VLAN1 command:
0 output errors, 19108404 collisions, 0 interface resets
Message Posted at:
http
Well, of course.. an entire other network could be connected to the hub
=) ..I guess the main thing to keep in mind is that it's fine to use
portfast on a switchport that only endstations connect to, whether
directly to the endstation or to a hub full of endstations.
Mike W.
13 matches
Mail list logo
