Skip to main content

Network Basics: Ethernet Configurations

Network Basics: Ethernet Configurations

Ethernet has a variety of possible configurations, standard, fast and gigabit. Each version operates at different speeds and use different types of media. All the versions of Ethernet are compatible with each other, so you can mix and match them on the same network by using devices such as bridges, hubs, and switches to link network segments that use different types of media.

Standard Ethernet

Standard Ethernet is the original Ethernet and the slowest. It runs at 10 Mbps, which was considered fast in the 1970s but is now considered slow and obsolete.
Standard Ethernet comes in four incarnations, depending on the type of cable used to string the network together:
  • 10Base5: The original Ethernet cable was thick (about as thick as your thumb), heavy, and difficult to work with. It's seen today only in museums.
  • 10Base2: This thinner type of coaxial cable (it resembles television cable) became popular in the 1980s and lingered into the early 1990s. Plenty of 10Base2 cable is still in use, but it’s rarely installed in new networks. 10Base2 (like 10Base5) uses a bus topology.
  • 10BaseT: Unshielded twisted-pair cable (known as UTP) became popular in the 1990s because it’s easier to install, lighter, and more reliable, and it offers more flexibility in how networks are designed. 10BaseT networks use a star topology with hubs at the center of each star. Although the maximum length of 10BaseT cable is only 100 meters, hubs can be chained together to extend networks well beyond the 100-meter limit.
    10BaseT cable has four pairs of wires that are twisted together throughout the entire span of the cable. However, 10BaseT uses only two of these wire pairs, so the unused pairs are spares.
  • 10BaseFL: Fiber-optic cables were originally supported at 10 Mbps by the 10BaseFL standard. However, because faster fiber-optic versions of Ethernet now exist, 10BaseFL is rarely used.

Fast Ethernet

Fast Ethernet refers to Ethernet that runs at 100 Mbps, which is ten times the speed of Standard Ethernet. The following are the three varieties of Fast Ethernet:
  • 100BaseT4: The 100BaseT4 protocol allows transmission speeds of 100 Mbps over the same UTP cable as 10BaseT networks. To do this, it uses all four pairs of wire in the cable. 100BaseT4 simplifies the task of upgrading an existing 10BaseT network to 100 Mbps.
  • 100BaseTX: The most commonly used standard for office networks today is 100BaseTX, which transmits at 100 Mbps over just two pairs of a higher grade of UTP cable than the cable used by 10BaseT. Most new networks are wired with the higher-grade cable, Category 5, or better cable.
  • 100BaseFX: The fiber-optic version of Ethernet running at 100 Mbps is called 100BaseFX. Because fiber-optic cable is expensive and tricky to install, it isn’t used much for individual computers. However, it’s commonly used as a network backbone.

Gigabit Ethernet

Gigabit Ethernet is Ethernet running at a whopping 1,000 Mbps, which is 100 times faster than the original 10 Mbps Ethernet. Gigabit Ethernet was once considerably more expensive than Fast Ethernet, so it was used only when the improved performance justified the extra cost. However, today Gigabit Ethernet is the standard for nearly all desktop and laptop PCs.
Gigabit Ethernet comes in two flavors:
  • 1000BaseT: Gigabit Ethernet can run on Category 5 UTP cable, but higher grades such as Category 5e or Category 6 are preferred because they’re more reliable.
  • 1000BaseLX: Several varieties of fiber cable are used with Gigabit Ethernet, but the most popular is called 1000BaseLX.

Comments

Popular posts from this blog

Duplicate IP Address has been Detected Rule

A duplicate IP address has been detected on the network Rule Knowledgebase Summary This rule generates an alert when Windows® detects that he local machine’s IP address is in conflict with one or more identical IP addresses on the network. Until the IP address conflict is resolved, remote clients and applications may have difficulty accessing resources on any of the effected computers. Additionally, the local computer may not be able to access network resources. Related Events This rule generates an alert whenever the following events occur and are recorded in the System Event Log: The system detected an address conflict for IP address %2 with the system having network hardware address %3. The local interface has been disabled. Source: TCPIP; Event ID: 4198; The system detected an address conflict for IP address %2 with the system having network hardware address %3. The local interface has been disabled. Source: TCP...

Schedule Automatic backup config in Cisco Nexus

Schedule Automatic backup config in Cisco Nexus Nexus-Sw1(config)#feature scheduler   //Enable scheduler service in Nexus Nexus-Sw1(config)#scheduler job name backup-daily      // Job Name Nexus-Sw1(config)#scheduler aaa-authentication username abcd password abcd@123     // AAA - Authentication for Job created above (If AAA configured) Nexus-Sw1(config)#scheduler job name backup-daily copy running-config tftp://192.168.1.23/$(SWITCHNAME)-cfg.$(TIMESTAMP)         //IP of TFTP SERVER , file will saved with switch name and timestamp exit Nexus-Sw1(config)#scheduler schedule name backup-daily   // Setup Schedule to run for the JOB Nexus-Sw1(config-schedule)# time ?   daily    Specify a daily schedule   monthly  Specify a monthly schedule   start    Specify a future time schedule   weekly   Specify a weekly schedule...

VMware CPU and Memory Reservations: Fixing Insufficient resources to satisfy configured failover level for HA

Source Knowledge From :-  http://geekswing.com/geek/vmware-cpu-and-ram-reservations-fixing-insufficient-resources-to-satisfy-configured-failover-level-for-ha/ VMware CPU and Memory Reservations: Fixing Insufficient resources to satisfy configured failover level for HA This post comes from a few days of poring over manuals as well as some technical support. This is a good one. The error came from trying to power on a VM in our VMware cluster and we would get these errors: “Insufficient resources to satisfy configured failover level for HA” And this alert on our cluster “Insufficient resources to satisfy HA failover level on cluster vmCluster in vmTST” Our way of thinking was we had to power one off to power another one on. But that didn’t work. Here we is the actual solution. (p.s. Great VMware HA education for me on this one!) PROBLEM SOURCE: VMware HA is turned on and you are violating constraints VMware HA is turned on, and you have i...