Lines Matching full:cable

88       detected, indicating potential Layer 1 issues like a cable fault,
127       may indicate a physical layer issue such as a faulty cable, interference,
316     **PSE**. Check for potential issues such as a short circuit in the cable,
320     established, proceed with further diagnostics by performing **Cable
325 Cable Diagnostics
328 Use `ethtool` to test for physical layer issues such as cable faults. The test
329 results can vary depending on the cable's condition, the technology in use, and
330 the state of the link partner. The results from the cable test will help in
334 - **Command:** `ethtool --cable-test <interface>`
344     Cable test completed for device eth1.
348   This indicates an open circuit or cable fault at the reported distance, but
350   **"Troubleshooting Based on Cable Test Results"** section for further
358     Cable test completed for device eth0.
365   B, the cable test may be disrupted. Refer to the **"Troubleshooting Based on
366   Cable Test Results"** section for a detailed explanation of these issues and
369 For detailed descriptions of the different possible cable test results, please
370 refer to the **"Troubleshooting Based on Cable Test Results"** section.
372 Troubleshooting Based on Cable Test Results
375 After running the cable test, the results can help identify specific issues in
376 the physical connection. However, it is important to note that **cable testing
381 In some cases, this can introduce **blind spots** in the current cable testing
383 physical state of the cable. For example:
386   cable but also occur if the cable is properly attached to a powered-down link
390   **forced slave mode**, even though there is no actual short in the cable.
401 and manually verify cable issues as needed. Physical inspections may help
408   - The cable is functioning correctly, and no issues were detected.
416     mode**, since cable tests usually only pass in this mode. For some
417     **10BaseT1L** PHYs, an "OK" result may occur even if the cable is too long
423   - An **Open Circuit** result typically indicates that the cable is damaged or
427       still get an "Open Circuit" result even if the cable is functional.
429     - **Next Steps**: Inspect the cable at the fault length for visible damage
436     pair of wires, typically caused by physical damage to the cable.
438     - **Next Steps**: Replace or repair the cable and check for any physical
446     - **Next Steps**: Replace or repair the damaged cable. Inspect the cable for
452     discontinuity in the cable. This can happen when a part of the cable has
453     abnormal impedance (e.g., when different cable types are spliced together
454     or when there is a defect in the cable).
456     - **Next Steps**: Check the cable quality and ensure consistent impedance
457       throughout its length. Replace any sections of the cable that do not meet
463     complete due to excessive noise on the cable, which can be caused by
467       interference (EMI) near the cable. Consider using shielded cables or
468       rerouting the cable away from noise sources.
476     - **Next Steps**: Inspect the cable manually if possible, or use alternative
486       the cable manually if necessary.
491 If the cable test passes but the link is still not functioning correctly, it’s
617 indicate issues with the cable, PHY configuration, or environmental factors.
669     may indicate cable or environmental issues that require further
745     not supported, you may need to rely on physical inspections (e.g., cable
767 But before you throw in the towel (or the Ethernet cable), take a deep breath.