Some More on Ethernet

 

Introduction.  Now we will present some more information on Ethernet.  We will present two main sections.  One on the structure of Ethernet frames.  The second presents more on how things actually work on Ethernets and some of their limitations.

Frame Structure.  The overall package containing data is called a frame in Ethernet parlance.  Frames are developed at Layer 2, the Data Link Layer, of the OSI model.  These are much of the basis for the packets that travel the Internet.

Each frame contains

  • header information
  • data information
  • trailer information

Last I knew there were four different frame types.

  • Ethernet 802.2
  • Ethernet 802.3
  • Ethernet II
  • Ethernet Snap

The two that are generally used on TCP/IP networks are Ethernet_II and Ethernet_SNAP.

The following diagram represents the basic structure of an Ethernet II frame type.

 

 

The fields are described a bit in the following outline
  • preamble
    • indicates the beginning of a frame
  • destination address
  • source address
  • type field
    • this identifies the protocol operating at the network layer
  • data
    • can be from 46 to 1500 bytes
  • trailer
    • used for cyclic redundancy test
    • works by treating data that is sent as a long polynomial
    • the computer divides this polynomial by a 16 or 32 bit polynomial
    • the quotient from this division is sent in the CRC
    • the receiving computer applies the same test to the incoming data to help improve the ability to validate whether the incoming data was properly received

Rules of Engagement.  There are two important rules of engagement that almost always need to be followed in order to get an Ethernet to function in desirable ways.  But first we need a definition, a collision domain, is a segment of a network in which messages will collide if two devices transmit at the same time.

  • the 5 - 4 - 3 rule for coax based Ethernet collision domains
    • 5 is the maximum number of thinnet or thicknet cable segments
    • 4 is the maximum number of repeaters/hubs that can be used to connect the cable segments
    • 3 is the maximum number of cable segments that can be populated.  The other two segments are purely for the purpose of extending the lengths of some segments
  • 10BaseT node capacity limitations

How does the 5 - 4 - 3 rule apply to twisted pair networks?  Many sources claim it is inappropriate to apply this rule to twisted pair networks.  Littlejohn Shinder states that one needs to apply the rule to twisted pair networks but in a slightly different fashion.

  • applying the 5 - 4 - 3 rule to UTP based Ethernet collision domains
    • a populated hub in a star bus network is a segment
    • 3 is the maximum number of cable segments that can be populated. 

Fortunately, we can create much larger Ethernet networks by using switches and routers to connect collision domains.  We'll get into how switches can be used to manage collisions and largely get rid of collision domains in future sections.

10BaseT Node Capacity.  The number of nodes per segment on a twisted pair star wired bus is exactly two.  This the computer or device at one end and the hub at the other.  The maximum number of nodes in a hub based network should not exceed 100 because of the exponential growth in the number of collisions after 100 nodes for 50 devices.  Some sources claim the number of devices shouldn't exceed 40.  These limits can be extended by using devices that make better use of available bandwidth such as switches.  But these limits obviously depend on the traffic intensities created by using the devices.