Skip to main content

A new standard

A new standard (Optional)
4.2.9 This page discusses the new test standards for Category 6 cable.


On June 20, 2002, the Category 6 addition to the TIA-568 standard was published. The official title of the standard is ANSI/TIA/EIA-568-B.2-1. This new standard specifies the original set of performance parameters that need to be tested for Ethernet cabling as well as the passing scores for each of these tests. Cables certified as Category 6 cable must pass all ten tests.

Although the Category 6 tests are essentially the same as those specified by the Category 5 standard, Category 6 cable must pass the tests with higher scores to be certified. Category 6 cable must be capable of carrying frequencies up to 250 MHz and must have lower levels of crosstalk and return loss.

A quality cable tester similar to the Fluke DSP-4000 series or Fluke OMNIScanner2 can perform all the test measurements required for Category 5, Category 5e, and Category 6 cable certifications of both permanent links and channel links. Figure shows the Fluke DSP-4100 Cable Analyzer with a DSP-LIA013 Channel/Traffic Adapter for Category 5e.

The Lab Activities will teach students how to use a cable tester.

This page concludes this lesson. The next page will summarize the main points from the module.

Comments

Popular posts from this blog

OSI layers / Peer-to-peer communications / TCP/IP model

OSI layers 2.3.4 This page discusses the seven layers of the OSI model. The OSI reference model is a framework that is used to understand how information travels throughout a network. The OSI reference model explains how packets travel through the various layers to another device on a network, even if the sender and destination have different types of network media. In the OSI reference model, there are seven numbered layers, each of which illustrates a particular network function. - Dividing the network into seven layers provides the following advantages: • It breaks network communication into smaller, more manageable parts. • It standardizes network components to allow multiple vendor development and support. • It allows different types of network hardware and software to communicate with each other. • It prevents changes in one layer from affecting other layers. • It divides network communication into smaller parts to make learning it easier to understand. In the foll...

Advantages and disadvantages of link-state routing

Advantages and disadvantages of link-state routing 2.1.5  This page lists the advantages and disadvantages of link-state routing protocols. The following are advantages of link-state routing protocols:  Link-state protocols use cost metrics to choose paths through the network. The cost metric reflects the capacity of the links on those paths. Link-state protocols use triggered updates and LSA floods to immediately report changes in the network topology to all routers in the network. This leads to fast convergence times. Each router has a complete and synchronized picture of the network. Therefore, it is very difficult for routing loops to occur. Routers use the latest information to make the best routing decisions. The link-state database sizes can be minimized with careful network design. This leads to smaller Dijkstra calculations and faster convergence. Every router, at the very least, maps the topology of it...

Ports for services

Ports for services 10.2.2  Services running on hosts must have a port number assigned to them so communication can occur. A remote host attempting to connect to a service expects that service to use specific transport layer protocols and ports. Some ports, which are defined in RFC 1700, are known as the well-known ports. These ports are reserved in both TCP and UDP.  These well-known ports define applications that run above the transport layer protocols. For example, a server that runs FTP will use ports 20 and 21 to forward TCP connections from clients to its FTP application. This allows the server to determine which service a client requests. TCP and UDP use port numbers to determine the correct service to which requests are forwarded. The next page will discuss ports in greater detail.