Heinrich Rebehn wrote:
[EMAIL PROTECTED]@mgEDV.net wrote:
some hints:
- the other switch seems to be cisco, too. (catalyst series, IOS)
- if the trunk contains more lines, check them for physical damage
(maybe 1
fails sometimes, 2 is ok)
- try to setup the cisco-switches for nonegotiate-trunki
[EMAIL PROTECTED]@mgEDV.net wrote:
some hints:
- the other switch seems to be cisco, too. (catalyst series, IOS)
- if the trunk contains more lines, check them for physical damage (maybe 1
fails sometimes, 2 is ok)
- try to setup the cisco-switches for nonegotiate-trunking to your box
- setup the
Stuart Henderson wrote:
On 2006/04/04 13:24, Rob Gault wrote:
The first thing I noticed is that SK0 is only at half duplex
OP says the cable is out. However "auto" and "duplex full" are
likely to not be compatible (they aren't for 10/100, though I'm
not sure about gig).
I will double check
On 2006/04/04 13:24, Rob Gault wrote:
> The first thing I noticed is that SK0 is only at half duplex
OP says the cable is out. However "auto" and "duplex full" are
likely to not be compatible (they aren't for 10/100, though I'm
not sure about gig).
> I am attaching ifconfig and dmesg output. The
On 04/04/06, Heinrich Rebehn <[EMAIL PROTECTED]> wrote:
> interface FastEthernet6/19
> description k307 n2340-19a
> switchport trunk encapsulation dot1q
> switchport trunk allowed vlan 16,86,182,231,232
> switchport mode trunk
> duplex full
>
> sk0: flags=8843 mtu 1500
>lladdr 00:13:d4:de:
The first thing I noticed is that SK0 is only at half duplex and you
have "duplex full" on the switch port. This can cause similar problems
to what you are describing. I've found it always best to set the speed
& duplex on both devices (switch and PC) when creating trunks. HTH
-Original Mes
6 matches
Mail list logo
