1. Identify what was actually tested

Start with a small route sketch. Identify the client, its wired or wireless connection, switches, router and test server. An internet speed test can include the local network, broadband access and the path to a remote server. A local throughput test stays within the selected LAN path, which can still contain several devices and cable segments. Neither isolates one cable simply because that cable is on the route.

A port-status display concerns the connection to that port’s immediate peer. A passive cabling test uses the instrument and adapters to assess a defined cabling configuration. Record both endpoints and which cords are included. For this guide, “5 Gbps” means an Ethernet link rate, not a 5G cellular service or a promised internet download result.

2. Read negotiated link speed as a link-state observation

When the equipment reports a negotiated rate, it tells you the operating rate established between those interfaces at that time. Preserve the device model, port identifier, peer and time alongside the value. Also distinguish an advertised capability or configured setting from the actual operational link state.

A 5 Gbps link can be useful evidence that the equipment established that mode on the tested path. It is not a measurement of every cabling performance parameter, and a brief link-up does not demonstrate sustained error-free operation. Check error counters and stability over the agreed observation period when operational performance is part of the requirement. Do not rename the screenshot “Cat6A certification.”

3. Interpret throughput with the endpoints and settings

Throughput is the rate of data delivered at the layer measured by the tool. Application payload throughput normally differs from the nominal Ethernet link rate because framing and protocol traffic also consume capacity. Avoid assuming a universal percentage difference: the protocol, packet size, direction and test design matter.

With a tool such as iperf3, preserve the client and server versions, transport protocol, duration, direction and stream count. Record the output from the relevant endpoints, not only a selected headline number. A TCP result and a UDP result need their own interpretation; for UDP, the configured send rate alone is not proof that the receiver received that rate without loss.

If throughput is lower than expected, examine endpoint CPU and NIC capacity, other traffic and every device on the route. Latency, loss and TCP behavior can also matter. Reproduce the test on a controlled wired path and change one suspected factor at a time. A slow result is a reason to investigate; it does not identify the cable as the cause.

4. Separate verification, qualification and certification

Fluke Networks distinguishes three testing purposes. Verification checks basic connectivity such as wiremap and continuity. Qualification assesses support for a specified network application within the tool’s capabilities. Certification measures cabling performance against selected standards-based limits. The instrument model, functions and chosen test mode determine the evidence available.

A qualification result is useful for assessing an existing link for an upgrade, but it is not a standards-compliance certification report. Qualification methods differ between instruments; do not assume every qualifier sends application traffic or supports every multi-gig rate. Check the manufacturer’s documented capabilities for the actual model and firmware.

Even a certification instrument needs the correct setup. Confirm the category or class, standard and edition, test limit, adapters and configuration. Depending on the selected limit, measurements can include insertion loss, return loss and crosstalk parameters. A pass against a lower-category limit does not establish compliance with a higher-category requirement. Here “certification” means field cabling testing, not a third-party product approval mark.

5. Match the evidence to the acceptance decision

Use this comparison when reviewing a supplier’s proposed report package. These are evidence categories, not interchangeable pass labels. For every record, attach the tool identity, configuration, link ID, date, result and stated limitation. The table gives procurement review guidance rather than a universal test specification.

For example, if a contract requires Cat6A permanent-link certification, a report showing 5 Gbps link-up plus a successful application test leaves that contractual evidence missing. The installer must provide the specified certification records or obtain an explicit, documented change to the acceptance requirement. This is a decision example, not a claim about an actual installation.

6. Put the test scope into the purchase documents

Separate the fixed cabling from the final assembled channel. A permanent-link test normally covers the installed fixed portion and its terminations, excluding equipment and patch cords at the ends. A channel test includes the specified patch and equipment cords. The tester adapters and reference planes must match the selected configuration. Directly terminated or special layouts need their applicable method, not an assumed conventional permanent-link setup.

Treat factory product testing and on-site installed-link testing as separate deliverables. ZION’s 7241011 CAT6A patch-cord page includes a production test reference using a Fluke instrument. Ask which report, test configuration and delivered item that reference covers; do not use a product-page statement as the acceptance record for the completed site channel.

When patch cords are replaced after channel testing, or terminations are reworked, record the change and apply the agreed retest rule. Keep the original result, corrective action and final accepted record traceable to the same link. Request the cable, connectivity and testing scopes together so that the materials order and handover requirement agree.

ZION copper structured cabling solution · 7241011 CAT6A patch cord and production test reference

7. Prepare the upgrade enquiry

Preparing a multi-gig cabling upgrade? Send your link layout, cable category, channel length, target application and required acceptance reports. Ask ZION to review matching cable and connectivity options for your project.

Frequently asked questions