RE: catalyst 6000 [7:20244]

This sounds like a classical auto-negotiation issue. If the server is capable of supporting 100FDX then hard code it as well as the Catalyst, and the messages should stop. Another thing to look at, is the port counters, if you see lots of FCS errors, that is usually a tell-tell sign. HTH

Re: catalyst 6000 [7:20244]

You could try disabling PAGP and all that good stuff with the set port host command. Dave ndabarasa michel wrote: hello, i need a help from the list. i have a switch (catalyst6000) as a central node in a physical star topology. the other nodes are three catalyst2948. they are

Re: catalyst 6000 [7:20244]

set port host disables negotiation for ether channnel, trunking, and stp. I would also recommend to set speed and duplex manually. Alex MADMAN wrote: You could try disabling PAGP and all that good stuff with the set port host command. Dave ndabarasa michel wrote: hello, i need a

Re: catalyst 6000 [7:20244]

a lot of thanx. i disabled the pagp thing On Tue, 18 Sep 2001 10:14:13 -0400 MADMAN wrote: You could try disabling PAGP and all that good stuff with the set port host command. Dave ndabarasa michel wrote: hello, i need a help from the list. i have a switch (catalyst6000) as