one interface is fastethernet and other is gigabitethernet . i tried to hardcore the duplex setting and speed 100 but as it is taking only half-duplex due to which i am getting collisions and output drops.
as you have mentioned that you hardcoded the duplex settings (but its showing as "auto" in the interface config you have pasted, i hope you have changed it to "auto" once the hardcoded "full duplex" didnt work)) and SP is saying that it is getting "full duplex" negotiated (but not hardcoded) at his end.
I would definately recommend you that if you are going to hardcode the speed & duplex settings then hardcode it to "full duplex" at both ends rather than "auto" at SP end and you making it "full duplex" at your end.
once its full duplex on both ends then clear the counters and check for the errors on the interface.
If you are NOT facing the similar problem on your giginterface then let it be as auto duplex on the both ends and check the duplex it negotiate with other end.
In my experience if you hard code speed then duplex will not negotiate (negotiation of duplex is dependent on negotiation of speed). And if duplex is not negotiated then the default is to do half duplex. If you are going to code speed then code duplex.
Also the solution I have mentioned to hardcode the duplex at both ends is from my experience only.
As Rick suggested from his expereince that if speed is set then duplex wonnt be negotiated.
I agree with this as I think when we say auto-negotiation, we talk about both speed and duplex and if we set speed as manual that means autonegotiation is off and duplex wonnt be negotiated so set to default i.e. "half duplex"
I hope I got this explanation correct.
I got this interested link which clearly tell what to do and not to do with duplex and speed setting. It consider desktop NIC and cisco catalyst switch for reference and I hope it will be applied to OTHER NETWORK DEVICES ALSO WHICH SUPPORT AUTONEGOTIATION STANDARD(IEEE 802.3u)
"i made the previous statement in capitals as this what i think, correct me if i am wrong with above statement":)
it also explain why your giginterface goes down when you try to hardcode the duplex only at your end, it says:- combination of "auto" and "hardcode" on two connected device's giginterface will make the interface go down..
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...