topic RE: debug autonegotiation problem in ExtremeSwitching (EXOS/Switch Engine)

debug autonegotiation problem

M_Nees — Thu, 19 May 2016 17:08:00 GMT

We have some clients with gigabit TP NIC on a X450-G2 (EXOS V16.1.3.6 patch1-4) - but they only connect with 100MB full duplex. (i investigate the problem via trial and error)
My concern is now - how can i troubleshoot this from switch CLI?

1) How can i see more what happenend regarding autoneg on that specific port - how can i increase log level to debug this ?
Which log modul have to be modified ?

2) On enterasys Switches (EOS) i could determine via "set port advertise" which speed or duplex modes are advertised to the partner AND which speed / duplex the partner offers.

System(rw)->show port advertise ge.4.36
ge.4.36 capability advertised remote
----------------------------------------------10BASE-T yes yes no
10BASE-TFD yes yes no
100BASE-TX yes yes no
100BASE-TXFD yes yes no
1000BASE-X no no no
1000BASE-XFD no no no
1000BASE-T no no no
1000BASE-TFD yes yes no
other no no yes
pause yes no no
Apause yes no no
Spause yes no no
Bpause yes yes noHow can i achieve this with EXOS ?

Regards

RE: debug autonegotiation problem

BradP — Thu, 19 May 2016 17:17:00 GMT

Hi Matthias,

I know there is a way through the EXOS shell/debug mode in order to see what speeds are being advertised on our port as well as which speeds are being advertised on the wire. Please open up a GTAC case and we can get it sorted out.

Thanks
Brad

RE: debug autonegotiation problem

M_Nees — Thu, 19 May 2016 17:26:00 GMT

Hi Brad,

open a GTAC is currently cumbersome.

Can you please tell me how can i increase the log level for autonegotiation on a TP port.

Securestack can check the cable through a cable-test / cable-check command - are there any change to have that on EXOS ?

Regards,
Matthias

RE: debug autonegotiation problem

BradP — Thu, 19 May 2016 17:31:00 GMT

Hi Matthias,

I'll open a case on your behalf and then email you. Stay tuned.

RE: debug autonegotiation problem

Erik_Auerswald — Thu, 19 May 2016 17:34:00 GMT

Hello Matthias,

1. To get some info about what the port negotiated, use:
show ports [portlist] configuration no-refresh
show ports [portlist] information detail2. EXOS send any supported speed/duplex mode during autonegotiation, unless configured otherwise. This configuration uses the following command:
configure ports PORTLIST auto on speed SPEED duplex DUPLEXThis supports one setting only, not a set of settings as on EOS.

Best regards,
Erik

RE: debug autonegotiation problem

BradP — Thu, 19 May 2016 18:20:00 GMT

Just to circle back, after a remote session, we were able to confirm that the partner device was advertising 10Mfd, 100Mfd, but not 1000Mfd. A feature request was also opened to expose those commands into the standard CLI instead of needing debug mode.

RE: debug autonegotiation problem

M_Nees — Thu, 19 May 2016 18:22:00 GMT

Brad help we via a remote session and getting via interal debug commands (protected via one-time password challenge) to get what the related TP port is advertising and what the partner offers.

Thanks.

RE: debug autonegotiation problem

Baris_Karabacak — Thu, 21 Jul 2016 18:10:00 GMT

Hi all,

I've a similar case so I think it fits to this case.

Following Situation: If I connect the Printer HP Laserjet M402dn directly to the data socket which is patched to the X450-G2 then the Printer ist not working. But with a D-Link 5 port unmanaged Switch (DGS-105) between Printer and X450 it works. It camed out that if I adjust the Network port on the Printer and X450 to 100 Mbit/s full Duplex than the Printer is available. However the possibilities on the printers Webpage are shown below. It has automatic sense, crossover detection, 10,100 and 1000Mbit/s Connection Speed. May I ask how to find out with Troubleshooting why the X450 and the printer can't auto negotiate with each other? By the way connecting a PC directly to the data socket works.

Update:
The 3rd picture shows some crc errors on command 'show ports rxerrors'. But the counters are not counting on every data packet. Unfortunately I can't find out when it counts up. What could the fault be?

To round up my issue:
I would like to know how to find out what or which thing is the cause for this behavior.
Can anyone help me, please? Thank you in advance.

RE: debug autonegotiation problem

M_Nees — Tue, 08 Jan 2019 00:41:00 GMT

Are there any chances related to this topic in recent EXOS 22.6 ?

Today one of my customers have a similar problem.
Link to a special measurement device is not going UP. Device should run with 10 MBit/s and Full Duplex.
But this device is running on other switches.
Used Switch X450-G2 - EXOS 22.6-Patch-1-1

I am not able to analyse the problem with the EXOS onboarded debugging (without opening a GTAC Case).

I use this debug commands:

code:

enable log debug-mode
configure log filter DefaultFilter add events vlan.msgs severity debug-data
configure log filter DefaultFilter add events HAL.Port severity debug-data
configure log filter DefaultFilter add events DM.Card severity debug-data
configure log filter DefaultFilter add events HAL.Device severity debug-data
configure log filter DefaultFilter add events HAL.Msg severity debug-data
configure log filter DefaultFilter add events HAL.Transceiver severity debug-data
configure log target console filter DefaultFilter severity Debug-Data

System is connected:

code:

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+                            C A U T I O N                            +
+  cablediag will momentarily interfere with traffic on active ports  +
+-----------------------------------------------------------------------+
+  Ports: 40                                                          +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Do you want to continue cable diagnostics? [y/N]: y
Collecting port cable diagnostic information may take a moment...
port 40: cable (4 pairs, length +/- 10 meters)
       pair A Ok, length 39 meters
       pair B Ok, length 36 meters
       pair C Short, length 36 meters
       pair D Short, length 36 meters

Link does not come up:

code:

sh port 40 configuration no-refresh
Port Configuration
Port    Virtual   Port Link Auto  Speed     Duplex  Flow Load  Media
        router    State State Neg Cfg Actual Cfg Actual Cntrl Master Pri Red
================================================================================
40      VR-Default E      R   ON   10      FULL                   UTP
================================================================================
> indicates Port Display Name truncated past 8 characters
Link State: A-Active, R-Ready, NP-Port Not Present, L-Loopback
Port State: D-Disabled, E-Enabled, L-License Disabled
Media: !-Unsupported, $-Unlicensed
Media Red: * - use "show port info detail" for redundant media type
Flow Cntrl: Shows link partner's abilities. NONE if Auto Neg is OFF


conf port 40 auto off speed 10 duplex full
sh port 40 configuration no-refresh
Port Configuration
Port    Virtual   Port Link Auto  Speed     Duplex  Flow Load  Media
        router    State State Neg Cfg Actual Cfg Actual Cntrl Master Pri Red
================================================================================
40      VR-Default E      R  OFF   10      FULL                   UTP
================================================================================
> indicates Port Display Name truncated past 8 characters
Link State: A-Active, R-Ready, NP-Port Not Present, L-Loopback
Port State: D-Disabled, E-Enabled, L-License Disabled
Media: !-Unsupported, $-Unlicensed
Media Red: * - use "show port info detail" for redundant media type
Flow Cntrl: Shows link partner's abilities. NONE if Auto Neg is OFF

Any suggestions ?

RE: debug autonegotiation problem

BradP — Tue, 08 Jan 2019 00:58:00 GMT

Is the connected device using autonegotiation? If so, use the command "configure port auto on speed 10 duplex full".

RE: debug autonegotiation problem

M_Nees — Tue, 08 Jan 2019 04:53:00 GMT

Hi B-rad,

as you see in the output - auto on speed 10 duplex full was my first shot ...

Are there any advices how i can make debugging more verbose to see why the link does not come up ?

RE: debug autonegotiation problem

BradP — Tue, 08 Jan 2019 05:50:00 GMT

As we did last time, I think we would have to go the GTAC route.

Regards,
Brad

RE: debug autonegotiation problem

M_Nees — Wed, 09 Jan 2019 16:11:00 GMT

Doing this by GTAC Case is currently really the only option.

But solving such kind of issues need to be in minutes by some verbose build-in diagnostic commands -
NOT within hours or days by opening a GTAC Case (and doing complicated internal debugs)!

It seems during the last 2 years this topic was not addressed by EXOS Team.