- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
09-02-2014 07:15 AM
Hi,
I was getting complains for slow download speed, so I tried to change the speed setting on interface from auto to 1000, but the interface went down.
Link status:
Runtime link speed/duplex/state: unknown/unknown/down
Configured link speed/duplex/state: 1000/auto/up
when I set it back to auto, it goes half duplex and speed 100
Link status:
Runtime link speed/duplex/state: 100/half/up
Configured link speed/duplex/state: auto/auto/up
thanks,
B
09-02-2014 07:24 AM
Bestorf,
There should be issue with other end of interface configuration. It should have been configured in 100/Half.
You should hard code other end with 1000/Full just like this one.
Regards,
Hardik Shah
09-02-2014 07:29 AM
Try to configure both in 1000/Full and see behavior.
Any incompatibility can cause in-consistent results.
Regards,
Hardik Shah
09-02-2014 07:34 AM
For more information on 802.3 specifications, refer to the following: IEEE-SA -IEEE Get 802 Program - 802.3: Ethernet
Cannot Commit when Interfaces are Set to 1000/full
Autonegotiation is a requirement for using 1000BASE-T[11] according to Section 28D.5 Extensions required for Clause40 (1000BASE-T).[12] At least the clock source has to be negotiated, as one endpoint must be master and the other endpoint must be slave.
09-02-2014 07:49 AM
in one side is the Cisco switch with this config:
!
interface FastEthernet0/2
switchport mode trunk
speed 100
duplex full
spanning-tree portfast trunk
ip dhcp snooping trust
!
on the other side PAN has this config:
X@PA-500> show interface ethernet1/4
Link status:
Runtime link speed/duplex/state: 100/half/up
Configured link speed/duplex/state: auto/full/up
even though it is configured to full duplex, it goes to half.
09-02-2014 07:56 AM
The far end is only a FastEthernet (100) interface - so you won't be able to set the PA to 1000.
Just force the PA to 100 / full duplex and you'll be fine.
09-02-2014 08:30 AM
Yes that interface is connected to FastEthernet, but the other one was in GigabyteEthernet.
However the problem with half duplex was because the interface was in VWire and in order to work in fullduplex both VWire interfaces had to be configured for fullduplex. It is strange though that Link Duplex Auto goes to Half by default.
thanks everyone for comments and suggestions.
09-02-2014 08:36 AM
Well, you had the Cisco forced to 100/full. This doesn't force the negotiation to 100/full - but instead turns negotiation off altogether. Your PA tried negotiating; couldn't get anything back from the other end and (rather stupidly really) guessed half duplex.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!