---
title: "Test a Cable"
slug: "testing-a-cable-gt"
tags: ["SFP", "ports", "Assurance Sensors", "Assurance Sensor GT", "Assurance Sensor GT-S"]
updated: 2022-04-04T19:43:48Z
published: 2022-04-04T19:43:49Z
canonical: "docs.crossworkassurance.cisco.com/testing-a-cable-gt"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.crossworkassurance.cisco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Testing a Cable

You can test the quality of copper cables, connectors and terminations attached to each unit. For this, the unit uses Time-Domain Reflectometry (TDR). You can quickly find opens, shorts, cable impedance mismatches, bad connectors and termination mismatches. If no problem in the cable is found, this test reports the cable length. If a problem is found, the test reports the distance at which the problem is detected.

---

***Note:** You can only test cables in use on RJ45 ports. SFPs (optical or electrical) are not supported.* 

---

**To test the quality of a cable and view results**

1. Access the page **Port ▶Cable**. A summary of all cable test results for all available copper ports is displayed. For more information on specific parameters, refer to the following table.
2. Click the **Connector** to test a cable.
3. Click the **Perform test** button to start the test.

The test should last only a few seconds and the status of each channel is updated as the tests are run.

**Cable Verification (Port ▶Cable)**

| Parameter | Description |
| --- | --- |
| Connector | The physical connector the port is using |
| Channel A Channel B Channel C Channel D | The results for each pair in a four-pair cable are presented in these four columns. |
| Status | The current status of the cable: - **GOOD:** Normal cable - **SHORT:** The positive and negative lines of the same pair are touching. The possible causes are: - **OPEN:** There is a cut on a pair. The possible causes are: - **FORCED:** A persistent noise in the channel. This can be caused by a link partner running in forced 10/100 Mbps. Cable length is not available in the *FORCED* state. - **FAIL:** The test failed. The link partner must lose the link in order to start the test. If the PHY receives a continuous signal during 125 ms, it reports the test result as FAIL. - **Impedance Mismatch Status:** Whenever the effective impedance is not 100 Ohms. The possible causes are: |
| Length | If no problem in the cable is found, this test reports the cable length. If a problem in the cable is found, this test gives the approximate distance at which the problem is detected. |

**© 2026 Cisco and/or its affiliates. All rights reserved.** For more information about trademarks, please visit: [Cisco trademarks](https://www.cisco.com/c/en/us/about/legal/trademarks.html)[](https://www.cisco.com/c/en/us/about/legal/trademarks.html) For more information about legal terms, please visit: [Cisco legal terms](https://www.cisco.com/c/en/us/about/legal/terms-conditions.html)