MDI/MDI-X Status on Catalyst 3560g

[Vincent Tamet]

Hi,

I'm searching the way to know if a cable plugged in the Gi0/1 is crossover or not.

I'm found the command:

show controllers ethernet-controller Gi0/1 phy (witch not really help me in this case)
show interfaces transceiver properties (witch give me only if the option is active or not)
Operational Auto-MDIX: on

I done a "diff" we a crossover cable and a straight one.
The "Aux 1000Base-X Status" specially sound nice but not really human readable.
Someone hnow the right way to do this ?
Or have the table to decode what ?


Best regards

Code: Select all

vincent@sistemes-vincent:~$ diff /tmp/titi1 /tmp/titi3
11c11
<  0006: 0005 Auto-Negotiation Expansion            :  0000 0000 0000 0101
---
>  0006: 0007 Auto-Negotiation Expansion            :  0000 0000 0000 0111
18c18
<  0011: 2300 Phy Extended Status                   :  0010 0011 0000 0000
---
>  0011: 0321 Phy Extended Status                   :  0000 0011 0010 0001
20c20
<  0013: 0000 False Carrier Sense Counter           :  0000 0000 0000 0000
---
>  0013: 0003 False Carrier Sense Counter           :  0000 0000 0000 0011
22,23c22,23
<  0019: 8514 Auxiliary Status Summary              :  1000 0101 0001 0100
<  001A: 0000 Interrupt Status                      :  0000 0000 0000 0000
---
>  0019: F514 Auxiliary Status Summary              :  1111 0101 0001 0100
>  001A: 240E Interrupt Status                      :  0010 0100 0000 1110
26c26
<  001D: 07AB Spare Control Register                :  0000 0111 1010 1011
---
>  001D: 06EC Spare Control Register                :  0000 0110 1110 1100
49c49
<  001C: 68C0 Auto-Negotiation Debug                :  0110 1000 1100 0000
---
>  001C: 68FD Auto-Negotiation Debug                :  0110 1000 1111 1101
51c51
<  001C: 700C Aux 1000Base-X Status                 :  0111 0000 0000 1100
---
>  001C: 721C Aux 1000Base-X Status                 :  0111 0010 0001 1100

[jeye]

If you hard code the speed and duplex on both end of the cable, and the link goes down, then it is a straight cable.
Hard coding speed and duplex on both switch will turn off auto MDIX.


HTH,
jerry

[Vincent Tamet]

Thanx for the anwser.
Anyway do you know a solution without risk of cut ?

[jeye]

You can try the following command, but it will bounce the port while it is testing
test cable-diagnostics tdr int x/x
and then
show cable-diagnostics tdr int x/x

Here is the sample outpt for a straight cable

Code: Select all

Rack1SW1#test cable-diagnostics tdr int g0/13
TDR test started on interface Gi0/13
A TDR test can take a few seconds to run on an interface
Use 'show cable-diagnostics tdr' to read the TDR results.
Rack1SW1#
*Mar  4 13:04:28.547: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down
*Mar  4 13:04:29.554: %LINK-3-UPDOWN: Interface GigabitEthernet0/13, changed state to down
*Mar  4 13:04:32.792: %LINK-3-UPDOWN: Interface GigabitEthernet0/13, changed state to up
*Mar  4 13:04:34.805: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Rack1SW1#
Rack1SW1#show cable-diagnostics tdr int g0/13
TDR test last run on: March 04 13:04:24

Interface Speed Local pair Pair length        Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Gi0/13    1000M Pair A     1    +/- 1  meters Pair B      Normal             
                Pair B     0    +/- 1  meters Pair A      Normal             
                Pair C     1    +/- 1  meters Pair C      Normal             
                Pair D     2    +/- 1  meters Pair D      Normal             
Rack1SW1#

HTH,
jerry

[Vincent Tamet]

OK,

First for this command we need the "no switport nonegociate" option, if not the result don't reflect the reality !!!
Another one without cut ?

Cross-over:

Code: Select all

sw-core01#test cable-diagnostics tdr int Gi0/2
TDR test started on interface Gi0/2
A TDR test can take a few seconds to run on an interface
Use 'show cable-diagnostics tdr' to read the TDR results.

sw-core01#show cable-diagnostics tdr int Gi0/2
TDR test last run on: March 01 08:22:48

Interface Speed Local pair Pair length        Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Gi0/2     auto  Pair A     0    +/- 4  meters Pair A      Normal
                Pair B     1    +/- 4  meters Pair B      Normal
                Pair C     1    +/- 4  meters Pair C      Short
                Pair D     0    +/- 4  meters Pair D      Short

Straight one:

Code: Select all

Interface Speed Local pair Pair length        Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Gi0/1     100M  Pair A     1    +/- 4  meters Pair A      Normal
                Pair B     1    +/- 4  meters Pair B      Normal
                Pair C     0    +/- 4  meters Pair C      Short
                Pair D     0    +/- 4  meters Pair D      Short

[jeye]

no switport nonegociate is not a requirement of this command. switport nonegociate is for DTP negotiation. Not sure what you mean?

http://www.cisco.com/en/US/docs/switche ... #wp1989134

You are having pair status of Short? is it wired correctly?


Regards,
jerry

[Vincent Tamet]

Your right for the "switport nonegociate".
I do all the test, but i don't leave time to have the correct anwers.
The last command gave result differents the first seconds (During the MDI/MDI-C detection think), and then later give always the same result.

Thank a lot for you help.
Finaly i do the job last week, with my eyes. I have deconnectat all wire and look the color for all wires.