Fortinet Document Library

Version:

Version:

Version:

Version:


Table of Contents

Administration Guide

Download PDF
Copy Link

Cable diagnostics

NOTE: There are some limitations for cable diagnostics on the FS-108E, FS-124E, FS-108E-POE, FS-108E-FPOE, FS-124E-POE, FS-124E-FPOE, FS-148E, and FS-148E-POE models:

  • Crosstalk cannot be detected.
  • There is a 5-second delay before results are displayed.
  • The value for the cable length is inaccurate.
  • The results are inaccurate for open and short cables.

You can check the state of cables connected to a specific port. The following pair states are supported:

  • Open
  • Short
  • Ok
  • Open_Short
  • Unknown
  • Crosstalk

If no cable is connected to the specific port, the state is Open, and the cable length is 0 meters.

For supported models, see Supported models.

Using the GUI:
  1. Go to Switch > Port > Physical.
  2. Select Cable Diagnostic for the appropriate port.
  3. Select Continue to start the cable diagnostics.
    NOTE: Running cable diagnostics on a port that has the link up will interrupt the traffic for several seconds.
  4. Select Back to Physical Ports to close the Cable Diagnostics window.
Using the CLI:

Use the following command to run a time domain reflectometry (TDR) diagnostic test on cables connected to a specific port:

diagnose switch physical-ports cable-diag <physical port name>

 

NOTE: Running cable diagnostics on a port that has the link up will interrupt the traffic for several seconds.

For example:

# diagnose switch physical-ports cable-diag port1

 

port1: cable (4 pairs, length +/- 10 meters)

pair A Open, length 0 meters

pair B Open, length 0 meters

pair C Open, length 0 meters

pair D Open, length 0 meters

 

Use the following command to check the medium dependent interface crossover (MDI-X) interface status for a specific port:

diagnose switch physical-ports mdix-status <physical port name>

 

For example:

# diagnose switch physical-ports mdix-status port1

 

port1: MDIX(Crossover)

Cable diagnostics

NOTE: There are some limitations for cable diagnostics on the FS-108E, FS-124E, FS-108E-POE, FS-108E-FPOE, FS-124E-POE, FS-124E-FPOE, FS-148E, and FS-148E-POE models:

  • Crosstalk cannot be detected.
  • There is a 5-second delay before results are displayed.
  • The value for the cable length is inaccurate.
  • The results are inaccurate for open and short cables.

You can check the state of cables connected to a specific port. The following pair states are supported:

  • Open
  • Short
  • Ok
  • Open_Short
  • Unknown
  • Crosstalk

If no cable is connected to the specific port, the state is Open, and the cable length is 0 meters.

For supported models, see Supported models.

Using the GUI:
  1. Go to Switch > Port > Physical.
  2. Select Cable Diagnostic for the appropriate port.
  3. Select Continue to start the cable diagnostics.
    NOTE: Running cable diagnostics on a port that has the link up will interrupt the traffic for several seconds.
  4. Select Back to Physical Ports to close the Cable Diagnostics window.
Using the CLI:

Use the following command to run a time domain reflectometry (TDR) diagnostic test on cables connected to a specific port:

diagnose switch physical-ports cable-diag <physical port name>

 

NOTE: Running cable diagnostics on a port that has the link up will interrupt the traffic for several seconds.

For example:

# diagnose switch physical-ports cable-diag port1

 

port1: cable (4 pairs, length +/- 10 meters)

pair A Open, length 0 meters

pair B Open, length 0 meters

pair C Open, length 0 meters

pair D Open, length 0 meters

 

Use the following command to check the medium dependent interface crossover (MDI-X) interface status for a specific port:

diagnose switch physical-ports mdix-status <physical port name>

 

For example:

# diagnose switch physical-ports mdix-status port1

 

port1: MDIX(Crossover)