<?xml version="1.0" encoding="UTF-8"?><rss version="2.0">
<channel>
<title>Ethernet</title>
<link>http://www.computersight.com/tags/Ethernet</link>
<description>New posts about Ethernet</description>
<item>
<title>ATM Implementation Scenarios</title>
<link>http://www.computersight.com/Communication-&amp;-Networks/ATM-Implementation-Scenarios.244879</link>
<description>
<![CDATA[<h3>ATM Distinguished Service Record</h3>
<p>Traditionally ATM has a long and distinguished service record for voice communications. It is also ideally suited to multiplexing environments and can be readily configured to carry VoIP traffic streams.</p>
<p>In fact today we find that most consumer ADSL2+ implementations do offer a choice of PPPoE or PPPoA as their transport protocols (at least here in Perth). PPPoA stands for Point-to-Point Protocol over Asynchronous Transfer Mode.</p>
<p>The importance of this cannot be overlooked as it means that ATM in some form or other will be with us for some time into the future. In fact the Japanese have just recently deployed a communications satellite with an onboard ATM switch. They obviously think there is life in ATM yet.</p>
<h3>Introducing Asynchronous Transfer Mode (ATM)</h3>
<p>Originally intended to be a unified networking strategy Asynchronous Transfer Mode (ATM) is a connection-oriented, circuit-switched, cell relay &amp;ldquo;Jack-of-all-trades&amp;rdquo; transport protocol that uses small uniform fixed-sized cells to redress Quality of Service (QoS) issues so important to voice/video communications and the multitude of streaming applications upon which we are all so dependant.</p>
<h3>ATM Origins and Development</h3>
<p>During development of the standards for the Asynchronous Transfer Mode (ATM), in the mid 1980s, the goals were to create a unified networking strategy that could act as an all-round transport system for real-time video and audio as well as for image, text and email. ATM is pretty much a &amp;ldquo;Jack-of-all-trades&amp;rdquo; transport system. The two groups primarily responsible for the development of the ATM standards were the International Telecommunications Union [ITU 2004] and the ATM Forum [ATM 2004].</p>
<p>Over time we have seen that the majority of implementations and uses that ATM has fulfilled have been primary concerned with telephony and IP networks. Ethernet and the Internet Protocol (IP) are packet-switched network technologies that use packets of variable size referred to as frames.</p>
<h3>ATM Protocol Basics</h3>
<p>In marked contrast to packet-switched networking technologies; ATM is a connection-oriented, Data Link Layer (OSI Reference Model Layer 2), circuit-switched, cell relay protocol that runs over Synchronous Optical Network (SONET) Physical Layer links (OSI Reference Model Layer 1) using cells of identical and never varying size. Consistent predictability is the underlying ethos here.</p>
<p>Being a connection-oriented channel-based technology means that ATM must always establish a &amp;ldquo;logical&amp;rdquo; connection between the two endpoints prior to commencement of data exchange. Significantly, ATM encodes data traffic into small uniform fixed-sized cells. ATM cells are always 53 bytes in size and are comprised of 48 bytes of data and 5 bytes of header information.</p>
<h3>ATM Cell Structure</h3>
<p>Regardless of the original size of the packets to be transmitted ATM breaks all packets, data, and voice streams into 48-byte chunks and then adds a 5-byte routing header to each one thereby making a total of 53-bytes for each and every cell. The 5-byte header is essential for later reassembly. During development of ATM it was considered that 10% (5 bytes) of each cell (payload) being dedicated to the header for routing information was more than sufficient.</p>
<p>ATM multiplexes these 53-byte cells instead of the larger packets and in so doing reduces the worst-case queuing jitter by a factor of almost 30, thereby removing the need for echo cancellers. I will discuss queuing jitter along with other types of jitter shortly.</p>
<h3>ATM Cell Formats</h3>
<p>ATM defines two different cell formats the Network-Network Interface (NNI) and the User-Network Interface (UNI). Most ATM links use the UNI cell format.</p>
<h3>ATM Adaption Layers (AAL)</h3>
<p>ATM Adaptation Layers (AAL) are the rules for segmenting and reassembling packets and streams into cells. It is the AALs that provide the support for the various services delivered by ATM.</p>
<p>Currently, there are five different AALs and the information concerning which one is being used for each cell on a cell-by-cell basis is not contained within the cell or in the cell header. Rather, this information is negotiated by or configured at the endpoints on a per-virtual-connection basis. Here are the five different AALs and their main uses:</p>
<ol>
<li>
<h4>AAL1</h4>
Constant Bit Rate (CBR) Services, Circuit Emulation</li>
<li>
<h4>AAL2</h4>
Variable Bit Rate (VBR) Services</li>
<li>
<h4>AAL3</h4>
Variable Bit Rate (VBR) Services</li>
<li>
<h4>AAL4</h4>
Variable Bit Rate (VBR) Services</li>
<li>
<h4>AAL5</h4>
Data Transport </li>
</ol>
<h3>ATM Connectivity</h3>
<p>Because ATM is a connection-oriented channel-based technology it must establish a &amp;ldquo;logical&amp;rdquo; connection between the two endpoints prior to commencement of data exchange. ATM does this by implementing Virtual Circuits, Channels, Paths and Identifiers as follows:</p>
<ul>
<li>
<h4>Virtual Circuits (VC)</h4>
Virtual Circuits (VC) are admirably suited to multiplexing scenarios. Simply by including an 8-bit or 12-bit Virtual Path Identifier (VPI) and a 16-bit Virtual Channel Identifier (VCI) pair in every ATM frame's header each Virtual Circuit (VC) is uniquely identifiable.</li>
<li>
<h4>Virtual Channel</h4>
An ATM Virtual Channel represents the basic means of communication between two end-points. Cells are given a unique identifier called the Virtual Channel Identifier (VCI) which is placed into the ATM cells' header. All ATM cells containing identical VCIs are transported in the same Virtual Channel.</li>
<li>
<h4>Virtual Path (VP)</h4>
A Virtual Path (VP) denotes the transport of ATM cells belonging to virtual channels which share a common identifier called a Virtual Path Identifier (VPI). The VPI is included in the header of every ATM frame. In other words a Virtual Path (VP) is a bunch of Virtual Channels (VC) connecting the same end-points. These will also have a common traffic allocation.</li>
<li>
<h4>Virtual Path Identifier (VPI)</h4>
The Virtual Path Identifier's (VPI) length varies depending on the interface it is sent on (inside the network or on the edge of the network. </li>
</ul>
<h3>ATM Traffic Contracts</h3>
<p>When an ATM circuit is set up each ATM switch is informed of the traffic class of the connection. These ATM contracts constitute part of ATM's Quality of Service (QoS) mechanisms. There are four basic types of contracts:</p>
<ol>
<li>
<h4>Constant Bit Rate (CBR)</h4>
A constant specified Peak Cell Rate (PCR) is set</li>
<li>
<h4>Variable Bit Rate (VBR)</h4>
An average cell rate is specified. This may peak at a certain predefined maximum level for a certain length of time before becoming problematic</li>
<li>
<h4>Available Bit Rate (ABR)</h4>
A minimum guaranteed rate is specified</li>
<li>
<h4>Unspecified Bit Rate (UBR)</h4>
Traffic is allocated all remaining transmission capacity </li>
</ol>
<h3>ATM Traffic Contract Delivery and Monitoring</h3>
<h4>Traffic Shaping</h4>
<p>The intended objective of traffic shaping is to ensure that cell flow will meet its traffic contract and is usually done at the entry point to an ATM network.</p>
<h4>Traffic Policing</h4>
<p>To maintain network performance it is possible to &amp;ldquo;police&amp;rdquo; virtual circuits against their traffic contracts. Basic policing works on a cell by cell basis, but this is sub-optimal for encapsulated packet traffic. If a circuit is exceeding its traffic contract, the network can either drop the cells or mark the Cell Loss Priority (CLP) bit (to identify a cell as being discardable farther down the line).</p>
<h3>Benefits of Using Small Fixed Size Cells</h3>
<p>The major benefits derived from using small data cells are a reduction in queue delay and jitter; particularly in multiplexing data streams. By using small, fixed-sized cells ATM is able to transport large data files all the while maintaining minimal queuing delays. Minimal queuing delays are essential to the delivery of both voice/video communications.</p>
<h4>Queue Delay</h4>
<p>Queue delay related issues include problems associated with end-to-end-round-trip delays and delay variance particularly when carrying voice traffic. High traffic volumes and/or congested networks along with the arrival variance associated with variable route routing are among the main causes of queue delay issues.</p>
<h4>Jitter</h4>
<p>Although jitter results from queuing delay issues deviations or displacement of various aspects of high frequency pulses such as amplitude, phase timing and signal pulse width as a direct result of electromagnetic interference (EMI) and crosstalk (noise) also cause jitter. Think of jitter as being the production of &amp;ldquo;jerky&amp;rdquo; results or in video applications flicker. By using small fixed-size cells ATM is able to overcome the effects of queue delay as well as other types/sources of jitter.</p>
<h4>Multi Purpose Transport Protocol</h4>
<p>Asynchronous Transfer Mode (ATM) carries many different data types and formats (text, audio, video, graphics, photos etc.) from a multitude of sources and of variable sizes. When combined with standard queuing strategies, maximum queuing delays were common. This is totally unacceptable where voice and real-time video traffic is concerned.</p>
<h3>Compression/Decompression Algorithms (Codec)</h3>
<p>Because of the way in which many Compression/Decompression Algorithmswork special considerations need to be implemented in order to ensure they work properly as intended including:</p>
<h4>Time</h4>
<p>The nature of time as we humans perceive it is an analogue continuum (that is to say time is a linear progression). Once past, there is no way as yet to recover the loss.</p>
<h4>Jitter and Queue Delay</h4>
<p>Jitter and queue delay are of great importance because of the nature and manner of operation of the compression/decompression (codec) algorithms used in the conversion of a digitalized data stream back into an analogue audio signal. This conversion process (digital-to-analogue) is very much a &amp;ldquo;real-time, on-the-fly&amp;rdquo; process and is more attuned to&amp;rdquo; just-in-time&amp;rdquo; transport protocols.</p>
<h4>Real-Time Streaming</h4>
<p>In order to produce reliable, consistently &amp;ldquo;acceptable&amp;rdquo; output the codec needs the data items (the digitized voice data) to be presented to it in a predictable, regulated and evenly spaced in time data stream, hence the term &amp;ldquo;real-time streaming&amp;rdquo;.</p>
<h4>Late Arrivals</h4>
<p>If the data arrives after its allotted position/reception window in the time sequence (relating to that part of the data-stream) the codec will simply drop it. Not surprisingly this is unacceptable for IP telephony. Remember to keep in mind that time is analogue in nature and once a &amp;ldquo;time window&amp;rdquo; elapses, the &amp;ldquo;lost&amp;rdquo; time becomes unrecoverable.</p>
<h4>Codec Packet Handling Options</h4>
<p>If the transport protocol is unable to present the data as and when the codec expects it, the codec, has no choice but to assume either silence, make a &amp;ldquo;best guess&amp;rdquo; or simply drop the packet. Any way is unacceptable where voice is concerned as the conversation rapidly becomes untenable and the message does not get through.</p>
<h3>ATM Deployment Indicators and Scenarios</h3>
<h4>ATM WAN Core Implementation</h4>
<p>ATM production environment implementations have over time proved to be very successful in the Wide Area Network (WAN) scenarios. Numerous telecommunication providers and Internet Service Providers (ISPs) have implemented ATM in their Wide Area Network (WAN) cores.</p>
<h4>Slow Links</h4>
<p>For slow links less than 2M-bit/s, ATM still makes sense, which is why many ADSL systems use ATM as an intermediate layer between the physical link layer and a Layer 2 protocol like PPP or Ethernet.</p>
<h4>Linear Audio and Video Streams</h4>
<p>Interest in using native ATM for carrying live video and audio has increased recently. It is in these environments, where ATM can deliver the low latency and very high Quality of Service (QoS) required for handling linear audio and video streams.</p>
<h4>Gigabit Ethernet</h4>
<p>Today we are finding that for both new WAN implementations and for existing WAN implementation upgrades, high speed, high performance Ethernet (Gigabit Ethernet, 10Gbit Ethernet, and Metro Ethernet etc.) are rapidly replacing ATM as the technology of choice.</p>
<h4>Relative Performance</h4>
<p>At the time ATM was designed, 155Mbit/s (135Mbit/s payload) over fiber-optic cable was very fast in comparison to the other carrier/transport technologies available at the time. Since then however; these other technologies have evolved and are now considerably faster than they once were.</p>
<h4>Jitter</h4>
<p>Today; a 1,500 byte (12,000 bit) full-size Ethernet packet takes only 1.2 &amp;micro;s to transmit across a 10Gbit/s optical network. With this sort of speed, jitter is no longer the issue it once was. By overcoming the potential adverse effects of jitter through this ramping up of network transfer speeds we have at the same time removed the need for using small uniform cells to overcome jitter.</p>
<h4>Complexity</h4>
<p>Unfortunately, due to ATM's complexity it proved to be unsuitable for deployment in many of the scenarios that its creators had originally intended.</p>
<h4>Converged Networks</h4>
<p>The speed and traffic shaping requirements of many converged networks are also proving to be very challenging for ATM.</p><a href="http://www.pheedo.com/click.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FATM-Implementation-Scenarios.244879"><img src="http://www.pheedo.com/img.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FATM-Implementation-Scenarios.244879" border="0"/></a>]]></description>
<pubDate>Sun, 07 Sep 2008 06:31:10 PST</pubDate></item>
<item>
<title>Technological Advances: Inventions From the Great Minds at MIT You May Have Never Known</title>
<link>http://www.computersight.com/Communication-&amp;-Networks/MITs-Greatest-Technological-Inventions-of-Our-Time.204739</link>
<description>
<![CDATA[<p>Ever wonder where the most amazing technical and architectural designs come from? If you guessed MIT, you'd be right.<br />I have compiled a list of inventions and creations that have stemmed from this educational powerhouse.</p>
<h3>Texas Instruments Inc.</h3>
<p><img src="http://images.stanzapub.com/readers/computersight/2008/08/10/260855_7.jpg" alt="" /></p>
<p>This device extends the battery life in certain types of medical tools, scales, and data acquisition applications.</p>
<h3>Rock &amp;amp; Roll Hall of Fame Building- I. M. Pei</h3>
<p><img src="http://images.stanzapub.com/readers/computersight/2008/08/10/260855_2.jpg" alt="" /></p>
<p>The architect tends to design buildings that depict the high-tech movement. He always works on larger scale projects and uses geometric designs to shape his buildings.</p>
<h3>The "Butterfly Effect" - Prof. Edward Lorenz</h3>
<p><img src="http://images.stanzapub.com/readers/computersight/2008/08/10/260855_3.jpg" alt="" /><br /> <br />Professor Lorenz realized that small differences in a forceful system such as the atmosphere could trigger unsuspected results. These explanations eventually led him to formulate what became known as the butterfly effect. "This term came from a paper he wrote in 1972 entitled Predictability: Does the Flap of a Butterfly's Wings in Brazil Set off a Tornado in Texas?"</p>
<h3>Bose stereo - Professor Amar Bose</h3>
<p><img src="http://images.stanzapub.com/readers/computersight/2008/08/10/260855_4.jpg" alt="" /><br />These stereo speakers are world-renowned for giving high-end performance despite their reticent size.</p>
<h3>Ethernet - Robert Metcalf</h3>
<p><img src="http://images.stanzapub.com/readers/computersight/2008/08/10/260855_8.jpg" alt="" /><br /> <br />Ethernet is a relationship between the unit frame-based computer networking technologies for (LANs). The Ethernet controls our access to certain types of data processing models, i.e. Internet.</p>
<h3>The Internet Archive - Brewster Kahle</h3>
<p><img src="http://images.stanzapub.com/readers/computersight/2008/08/10/260855_6.jpg" alt="" /><br /> <br />The Internet Archive (IA) consists of an online library containing the vast information on the Web and other multimedia resources. This information includes certain snapshots from various times from software, WebPages, audio visual and other sources.</p>
<h3>Rockman amplifier - Tom Scholz</h3>
<p><img src="http://images.stanzapub.com/readers/computersight/2008/08/10/260855_9.jpg" alt="" /></p>
<p>The Rockman is used in conjunction with headphones and an amplifier used for certain guitars. If any of you are familiar with Boston then you know who invented this.</p>
<h3>Spacewar, the first computer game-Steve Russell</h3>
<p><img src="http://images.stanzapub.com/readers/computersight/2008/08/10/260855_10.jpg" alt="" /><br /> <br />Spacewar was the first digital computer game of our time. The idea behind the game involved spaceships attempting to shoot each other while manipulating within the galaxy. I remember this game; I used to play it all the time on my Atari. I wish I still had it.</p>
<h3>Hypertext - Prof. Vannevar Bush PhD</h3>
<p><img src="http://images.stanzapub.com/readers/computersight/2008/08/10/260855_11.jpg" alt="" /><br />Hypertext is defined as words or text that leads the user to information associated with those words.</p>
<h3>GPS (Global Positioning System) - Ivan Getting</h3>
<p><img src="http://images.stanzapub.com/readers/computersight/2008/08/10/260855_12.jpg" alt="" /><br /> <br />The GPS uses satellites that transmit microwave signals. These signals enable receivers to determine certain types of pertinent information such as direction, time, speed and location.</p><a href="http://www.pheedo.com/click.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FMITs-Greatest-Technological-Inventions-of-Our-Time.204739"><img src="http://www.pheedo.com/img.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FMITs-Greatest-Technological-Inventions-of-Our-Time.204739" border="0"/></a>]]></description>
<pubDate>Sun, 10 Aug 2008 09:03:28 PST</pubDate></item>
<item>
<title>Optical Networking</title>
<link>http://www.computersight.com/Communication-&amp;-Networks/Optical-Networking.187591</link>
<description>
<![CDATA[<p>There are a number of very closely related standards that have been developed to describe the practical implementations of optical networking. A number of very different standards and implementations also exist. I will discuss the major players here.</p>
<h3>The Advantages of Fiber Optical Networking</h3>
<p>First of all, we must note that the biggest advantage of using fiber optic networking and hence the use of fiber optic cable as a transmission medium is the high degree of immunity to noise, cross-talk and Electromagnetic Interference (EMI) that this medium provides.</p>
<p><strong>Spanning Large Distances</strong> - With the fiber optic technologies currently available today signal degradation and regeneration issues are not what they once were and so the distance factor that so limits copper-based media is of negligible consequence where fiber optic transmission is concerned.</p>
<p><strong>Environmental Damage</strong> - Environment factors such as moisture and Radio Frequency Interference (RFI) are also not of the same criticality as they are for copper-based media. The reasons for fiber optic cable as a transmission medium providing a high degree of immunization to noise (EMI) as opposed to other transmission media all stem from the use of light to convey the information (signals) and the construction of the medium (the fiber optic cable).</p>
<p><strong>Security </strong>- Due to the degree of difficulty in &amp;ldquo;tapping&amp;rdquo; fiber optic transmission lines without being detected, fiber optic transmission media offer a more secure medium than copper-based or wireless technologies.</p>
<p>The result is that fiber optic transmission media are the media of choice when it comes to &amp;ldquo;long haul&amp;rdquo; applications such as intercontinental, cross-continental and oceanic (marine) backbone links. It is also the preferred medium for tier one ISP backbone links. This means that new WAN implementations and applications are now predominantly fiber optic cable based. Wireless rollouts being the major exception.</p>
<p>Additional information regarding fiber optic cable construction, signal propagation, signal regeneration, connectors, cable rollout and modes (single-mode and multi-mode fibers) can be found at <a href="http://www.scienceray.com/Technology/Applied-Science/Fiber-Optic-Cable.161801" target="_blank"><strong>Fiber Optic Cable</strong></a><strong>.</strong></p>
<p>I will now discuss the major standards and implementations of fiber optic networking starting with the Fiber Distributed Data Interface (FDDI) standard and then the Synchronous Optical Networking (SONET) and the Synchronous Digital Hierarchy (SDH).</p>
<h3>Fiber Distributed Data Interface (FDDI)</h3>
<p>FDDI which evolved from the IEEE 802.4 token bus timed token protocol is a fault tolerant 100Mbit/sec token passing counter-rotating dual ring LAN standard that permits data transmission between two end-point devices that can be many tens of kilometers apart.</p>
<p>As its name indicates, fiber optic cable is the main form of physical transmission medium used in FDDI. Although a copper-based implementation called, Copper Distributed Data Interface (CDDI) does exist. Although conceived as a LAN standard FDDI has also been used for MAN and WAN implementations.</p>
<p><strong>FDDI Topology</strong> - In essence FDDI is a ring network similar to IBM's Token Ring network but with a number of critical differences. The most noticeable of which is that a FDDI uses a dual-attached, counter-rotating token ring topology (see Figure 1: FDDI).</p>
<p><strong>Fault Tolerance</strong> - One ring acts as the primary transmission ring and in the original implementations was capable of delivering transmission speeds of up to 100Mbit/sec. The other or secondary ring was originally intended solely to act as a backup.</p>
<p><img src="http://images.stanzapub.com/readers/computersight/2008/07/29/239175_0.jpg" alt="" /></p>
<p>This meant that the secondary ring was inactive and remained so for as long as the primary ring was functional. In the event of failure of the primary ring the secondary ring would become active. Now all traffic goes to the secondary ring for transmission. It is this built-in redundancy that makes FDDI is a fault tolerant technology.</p>
<p><strong>Higher Effective Sustained Data Throughput</strong> - Another factor in FDDI's favor was that it used a much larger frame size than Ethernet which meant that it was capable of much higher effective sustained throughput rates than standard 100Mbit/sec Ethernet. Administrators also had the option of using the secondary ring for data transport rather than having it stand idly by thereby doubling transmission capacity to 200Mbit/sec.</p>
<p><strong>Coverage and Scalability</strong> - Not only can FDDI traverse large distances it also scales much better than 100Mbit/sec Ethernet. This means it provides superior support for expanding enterprise networks consisting of hundreds or thousands of users.</p>
<p><strong>Fiber Distributed Data Interface II (FDDI-II)</strong> - FDDI-II is a more recent development of FDDI that has added support for circuit-switched services thereby enabling FDDI to carry both voice and video signals as well. For more on FDDI including applicable standards please see <a href="http://www.computersight.com/Communication-%26-Networks/About-Fiber-Distributed-Data-Interface-FDDI.119192" target="_blank"><strong>About Fiber Distributed Data Interface (FDDI)</strong></a>.</p>
<h3>Synchronous Optical Networking - SONET</h3>
<p>Synchronous Optical Networking (SONET) is an established high-speed WAN alternative for communicating digital information using lasers or Light-Emitting Diodes (LEDs) over optical cable offered by several telecommunications companies.</p>
<p>SONET was originally developed to replace the Plesiochronous Digital Hierarchy (PDH) system for transporting large amounts of telephone and data traffic as well as providing the mechanisms that allow for interoperability between equipment from different vendors. The result is that there are multiple, very closely related standards that describe synchronous optical networking including:</p>
<p><strong>Synchronous Digital Hierarchy (SDH)</strong> - The SDH standard was developed by the International Telecommunication Union (ITU) and is documented in standard G.707 and its extension G.708. SDH is used throughout the world but not in North America</p>
<p><strong>Synchronous Optical Networking (SONET)</strong> - The SONET standard as defined by GR-253-CORE from Telcordia&amp;trade;. Primarily used exclusively in Canada and the USA where SDH has not been implemented, although it can be found in other countries.</p>
<p><strong>Synchronization is Key</strong> - Through the use of atomic clocks synchronous networking data transport rates are very tightly regulated which allows for entire inter-country networks to operate synchronously while greatly reducing the amount of buffering required between elements in the network. This reduction in overhead (buffering) translates into greater effective net data throughput rates.</p>
<p><strong>Encapsulation</strong> - Both SONET and SDH can be used to encapsulate earlier digital transmission standards, such as the PDH standard, or used directly to support either ATM or so-called Packet over SONET/SDH (POS) networking.</p>
<p><strong>Generic Transport Containers</strong> - SDH and SONET are generic all-purpose transport containers for moving voice and data rather than just communications protocols per sec.</p>
<h3>SDH and SONET Frame Structures</h3>
<p>Standard packet or frame oriented data transmission frames usually consist of a header and a payload with the header of the frame being transmitted first, followed by the payload and a trailer (e.g. CRC). With synchronous optical networking both the header, which is referred to as the overhead and the payload still exist but the big difference is that the overhead is not all transmitted before the payload, rather the transmission is interleaved.</p>
<p><img src="http://images.stanzapub.com/readers/computersight/2008/07/29/239175_1.jpg" alt="" /></p>
<p><strong>Interleaved Transmission</strong> - With interleaved transmissions the transmission of the conversation goes like this:</p>
<p>First of all, a portion of the overhead (header) is transmitted. This is followed by part of the payload. After which the next part of the overhead is transmitted. This is followed by the next part of the payload and so on until the entire frame has been transmitted. Figure 2: Interleaving above shows this.</p>
<p><strong>SONET Frame Size and Transmission Sequence</strong> - SONET frames are 810 octets in size, transmitted as 3 octets of overhead, followed by 87 octets of payload, nine times over until 810 octets have been transmitted. The total frame transmission time is 125 microseconds.</p>
<p><strong>SDH Frame Size and Transmission Sequence</strong> - SDH frames are 2430 octets in size transmitted as 9 octets of overhead, followed by 261 octets of payload, also nine times over until 2430 octets have been transmitted. Again the total frame transmission time is also 125 microseconds.</p>
<p>It doesn't take much brain power to see that SDH is capable of an effective data throughput rate three times that which the North American implementation of SONET can achieve.</p>
<h3>Ethernet over Fiber Optic Cable</h3>
<p>Today we see the Gigabit Ethernet over fiber optic cable and 10G Ethernet over fiber optic cable standards being the most common implementations of optical local area networks (LANs) currently being rolled out. They are also used extensively as the network core layer's transport medium of choice particularly Ethernet networks.</p>
<p>The majority of the big players in the networking hardware arena like Cisco, Juniper, and Redback etc all produce numerous products with fiber optic support including Ethernet over Fiber Optic modules. Note see <a href="http://www.computersight.com/Communication-%26-Networks/Network-Design-Hierarchies.178283" target="_blank"><strong>Network Design: Hierarchies</strong></a>for more about network design and the functions and features of a network's core layer<strong>.</strong></p><a href="http://www.pheedo.com/click.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FOptical-Networking.187591"><img src="http://www.pheedo.com/img.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FOptical-Networking.187591" border="0"/></a>]]></description>
<pubDate>Tue, 29 Jul 2008 07:33:24 PST</pubDate></item>
<item>
<title>Asynchronous Transfer Mode (ATM)</title>
<link>http://www.computersight.com/Communication-&amp;-Networks/Asynchronous-Transfer-Mode-ATM.122411</link>
<description>
<![CDATA[<h3>Introducing Asynchronous Transfer Mode (ATM)</h3>
 
<p>Asynchronous Transfer Mode (ATM) is a connection-oriented Data Link Layer (OSI Reference Model Layer 2), circuit-switched, cell relay protocol that runs over Synchronous Optical Network (SONET) Physical Layer (OSI Reference Model Layer 1) links. ATM encodes data traffic into small uniform (53 bytes; 48 bytes of data and 5 bytes of header information) fixed-sized cells.</p>
 
<h3>Origins of Asynchronous Transfer Mode (ATM)</h3>
 
<p>During development of the standards for the Asynchronous Transfer Mode (ATM), in the mid 1980s, the goals were to create a unified networking strategy that could act as an all-round transport system for real-time video and audio as well as image, text and email. A &amp;ldquo;Jack-of-all-trades&amp;rdquo; transport system if you will.</p>
 
<p>The two groups primarily responsible for the development of the ATM standards were the International Telecommunications Union [ITU 2004] and the ATM Forum [ATM 2004].</p>
 
<h3>Main Implementations of ATM</h3>
 
<p>The majority of implementations and uses that ATM has fulfilled have been primary concerned with telephony and IP networks.</p>
 
<p>Unlike Ethernet and the Internet Protocol (IP) which are packet-switched based network technologies, that use packets of variable size referred to as frames, ATM is a circuit-switched cell relay protocol that uses cells of identical and never varying size. Consistent predictability is the underlying ethos here.</p>
 
<h3>Benefits of Using Small Fixed Size Cells</h3>
 
<p>The major benefits of using small data cells were to reduce jitter in multiplexing data streams as well as overcoming problems associated with end-to-end-round-trip delays and delay variance particularly when carrying voice traffic.</p>
 
<p>The reason this is important is inherently due to the nature of operation of the compression/decompression (codec) algorithms used in the conversion of a digitalized data stream back into an analogue audio signal, which is very much a &amp;ldquo;real-time&amp;rdquo; process.</p>
 
<p>To be able to do an &amp;ldquo;acceptable&amp;rdquo; job the codec needs the data items (the digitized voice data) presented to it in an evenly spaced (in time) stream hence the term &amp;ldquo;real-time streaming&amp;rdquo;. The nature of time as we humans perceive it is an analogue continuum (that is to say time is a linear progression).</p>
 
<p>If the transport protocol is unable to present the data as and when the codec expects it, the codec, has no choice but to assume silence or make a &amp;ldquo;best guess&amp;rdquo;. Either way is unacceptable where voice is concerned as the conversation rapidly becomes untenable and the message does not get through.</p>
 
<p>If the data arrives late then the time sequence relating to that part of the data-stream will have passed and the codec will simply drop it. Once again, this is unacceptable for IP telephony. Remember that time is analogue by nature and once a &amp;ldquo;time window&amp;rdquo; elapses, the &amp;ldquo;lost&amp;rdquo; time becomes unrecoverable.</p>
 
<h3>Queue Delay and Jitter</h3>
 
<p>Asynchronous Transfer Mode (ATM) carries data from a multitude of sources and variable sizes including voice, audio and many other variable sized files. When combined with standard queuing strategies, maximum queuing delays were common.</p>
 
<p>Because ATM was designed to implement a low-jitter network interface this situation is intolerable whenever voice and video communications are to take place. The answer was to use small-fixed size cells (packet) to overcome the effects of queue delay.</p>
 
<p>With small fixed-sized cells, ATM is able to transport both large datagrams while still maintaining short/minimal queuing delays.</p>
 
<h3>Asynchronous Transfer Mode (ATM) Cell Structure</h3>
 
<p>ATM breaks all packets, data, and voice streams into 48-byte chunks, adding a 5-byte routing header to each one. The 5-byte header is essential for later reassembly.</p>
 
<p>The reason for the header being 5-bytes in length is that 10% of the payload of every cell is considered to be more than enough to dedicate to routing information.</p>
 
<p>ATM multiplexed these 53-byte cells instead of packets and in so doing reduced the worst-case queuing jitter by a factor of almost 30, removing the need for echo cancellers.</p>
 
<p>ATM defines two different cell formats the Network-Network Interface (NNI) and the User-Network Interface (UNI). Most ATM links use the UNI cell format.</p>
 
<p>Asynchronous Transfer Mode (ATM) Adaption Layers (AAL)</p>
 
<p>ATM Adaptation Layers (AAL) are the rules for segmenting and reassembling packets and streams into cells. It is the AALs that provide the support for the various services delivered by ATM.</p>
 
<p>Currently there are five different AALs and which one is in use for each cell is not included in the cell. Instead, it is negotiated by or configured at the endpoints on a per-virtual-connection basis.</p>
 
<ul>
<li> AAL1 - Constant Bit Rate (CBR) Services, Circuit Emulation</li>
 
<li> AAL2 - Variable Bit Rate (VBR) Services</li>
 
<li> AAL3 - Variable Bit Rate (VBR) Services</li>
 
<li> AAL4 - Variable Bit Rate (VBR) Services</li>
 
<li> AAL5 - Data Transport </li>
 
</ul>
<h3>Asynchronous Transfer Mode (ATM) Connectivity</h3>
 
<p>Being a connection-oriented channel-based technology means that ATM needs to establish a &amp;ldquo;logical&amp;rdquo; connection between the two endpoints prior to commencement of data exchange.</p>
 
<h4>Virtual Circuits (VC)</h4>
 
<p>By including an 8-bit or 12-bit Virtual Path Identifier (VPI) and a 16-bit Virtual Channel Identifier (VCI) pair in the ATM frame's header each Virtual Circuit (VC) is uniquely identifiable. Virtual Circuits (VC) are admirably suited to multiplexing scenarios.</p>
 
<h4>Virtual Channel</h4>
 
<p>An ATM Virtual Channel represents the basic means of communication between two end-points. Cells are given a unique identifier called the Virtual Channel Identifier (VCI) which is placed into the ATM cells' header. All ATM cells containing identical VCIs are transported in the same Virtual Channel.</p>
 
<h4>Virtual Path (VP)</h4>
 
<p>A Virtual Path (VP) denotes the transport of ATM cells belonging to virtual channels which share a common identifier called a Virtual Path Identifier (VPI) which is included in the header of every ATM frame. In other words a Virtual Path (VP) is a bunch of Virtual Channels (VC) connecting the same end-points, and have a common traffic allocation.</p>
 
<h4>Virtual Path Idetifier (VPI)</h4>
 
<p>The Virtual Path Idetifier's (VPI) length varies depending on the interface it is sent on (inside the nework or on the edge of the network.</p>
 
<h3>Asynchronous Transfer Mode (ATM) Traffic Contracts</h3>
 
<p>When an ATM circuit is set up each switch is informed of the traffic class of the connection. These ATM contracts constitute part of ATM's Quality of Service (QoS) mechanisms. There are four basic types of contracts:</p>
 <ol> 
<li> Constant Bit Rate (CBR) - A constant specified Peak Cell Rate (PCR) is set</li>
 
<li> Variable Bit Rate (VBR) - An average cell rate is specified. This may peak at a certain predefined maximum level for a certain length of time before becoming problematic</li>
 
<li> Available Bit Rate (ABR) - A minimum guaranteed rate is specified</li>
 
<li> Unspecified Bit Rate (UBR) - Traffic is allocated all remaining transmission capacity </li>
 </ol> 
<h4>Traffic Shaping</h4>
 
<p>The objective of traffic shaping is to ensure that cell flow will meet its traffic contract and is usually done at the entry point to an ATM network.</p>
 
<h4>Traffic Policing</h4>
 
<p>To maintain network performance it is possible to police virtual circuits against their traffic contracts. If a circuit is exceeding its traffic contract, the network can either drop the cells or mark the Cell Loss Priority (CLP) bit (to identify a cell as discardable farther down the line).</p>
 
<p>Basic policing works on a cell by cell basis, but this is sub-optimal for encapsulated packet traffic (as discarding a single cell will invalidate the whole packet).</p>
 
<h3>Asynchronous Transfer Mode (ATM) Deployment Scenarios</h3>
 
<p>ATM has proved very successful in the Wide Area Network (WAN) scenario and numerous telecommunication providers have implemented ATM in their Wide Area Network (WAN) cores.</p>
 
<p>For slow links less than 2Mb/s, ATM still makes sense, which is why many ADSL systems use ATM as an intermediate layer between the physical link layer and a Layer 2 protocol like PPP or Ethernet.</p>
 
<p>Interest in using native ATM for carrying live video and audio has increased recently. In these environments, low latency and very high quality of service are required to handle linear audio and video streams.</p>
 
<h3>Asynchronous Transfer Mode (ATM) the Future</h3>
 
<p>Currently the future for ATM does not look very bright as it seems that in all likelihood gigabit Ethernet implementations (10Gbit-Ethernet, Metro Ethernet) will replace ATM as a technology of choice in new WAN implementions.</p>
 
<p>At the time ATM was designed, 155 Mbit/s (135 Mbit/s payload) over fiber-optic cable was fast in comparison to other technologies but since then networks have become much faster. A 1500 byte (12000-bit) full-size Ethernet packet takes only 1.2 &amp;micro;s to transmit on a 10 Gbit/s optical network, removing the need for small cells to reduce jitter.</p>
 
<p>The complexity of ATM is another factor that makes deployment of ATM unsuitable in many of the scenarios that its creators had originally intended.</p>
 
<p>The speed and traffic shaping requirements of converged networks also challenges ATM.</p><a href="http://www.pheedo.com/click.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FAsynchronous-Transfer-Mode-ATM.122411"><img src="http://www.pheedo.com/img.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FAsynchronous-Transfer-Mode-ATM.122411" border="0"/></a>]]></description>
<pubDate>Sat, 10 May 2008 20:02:13 PST</pubDate></item>
<item>
<title>Network Cabling Guide: Shielded Twisted Pair </title>
<link>http://www.computersight.com/Communication-&amp;-Networks/Network-Cabling-Guide-Shielded-Twisted-Pair.114633</link>
<description>
<![CDATA[<h3>Introduction</h3>
 
<p>Now that we have covered the basics of twisted pair copper cable functionality as a transmission medium we will move right on into discussing the shielded varieties after which we will have a look at the unshielded varieties.</p>
 
<h3>The Shielding Layer</h3>
 
<p>The single biggest difference between shielded and unshielded twisted pair cables is the presence of the shielding layer. The whole idea of the shielding layer is to make the cable less susceptable to Electro-Magnetic Interference (EMI), noise/cross-talk and the signal degradation they cause.</p>
 
<h3>Shield Layer Implementations</h3>
 
<p>The main types of shielded twisted pair cable are defined by the manner of their construction as follows:</p>
 
<ul>
<li> <strong>One Pair Shielding</strong> - The shielding layer covers both members of a pair and only one pair at a time</li>
 
<li> <strong>Multiple Shielded Pairs</strong> - When a cable is composed of more than a single shielded pair the sets of pairs of wires are contained in a sheath which may or may not be shielded as well</li>
 
<li> <strong>Screening</strong> - When the shielding layer covers bunches of pairs it is referred to as screening. In the case of cables with small numbers of pairs this is usually implemented by manufacturers in the form of having only one shielding layer that is used to cover all pairs within the cable.</li>
 
<li> <strong>Screened Shielded Twisted Pair (S/STP)</strong> - Also known as Screened Fully Shielded Twisted Pair. The shielding layer covers both members of a pair and an additional shielding layer is added to cover the bunches of pairs.
   
<ul>
<li> <strong>Most Resilient</strong> - This is the type of shielded pair cable that is most resistant to the effects of external and internal interference</li>
 
<li> <strong>Most Expensive</strong> - The multiple layers of additional shielding have the predictable effect of making this type of cable the most expensive of all of the twisted pair cables that have been widely implemented into networks </li>
 
</ul>
</li>
 
</ul>
<h3>Grounding</h3>
 
<ul>
<li> <strong>Proper Grounding Essential</strong> - The shield layer must be grounded in order for it to work</li>
 
<li> <strong>Grounding Using the Shield Layer</strong> - Since the shielding layer is metalic it can also serve as a ground</li>
 
<li> <strong>Shield Failure</strong> - Engineers; through experience, know that using the shield as the ground has its draw-backs; shield functional failure being but one</li>
 
<li> <strong>Drain Wire</strong> - As a result shielded and/or screened twisted pair cable usually has an additional special purpose grounding wire; called a drain wire built in</li>
 
<li> <strong>Reliability and Effectiveness</strong> - Using a special purpose drain wire is far more effective and reliable</li>
 
<li> <strong>Drain Wire Becomes Essential</strong> - As cables become bigger and contain more and more collections of bundles of shielded twisted pair wires the drain wire becomes essential rather than a nice extra. </li>
 
</ul>
<h3>Cost Vs. Resilient Reliability</h3>
 
<p>The additional costs that are incurred when installing shielded varieties of twisted pair cable have; on a materials cost basis alone, proven to be the major reason for the smaller business and the home Local Area Network (LAN) alike to forego any potential resilience to interference that the use of shielded cable might endow their networks in order to reduce costs.</p>
 
<h3>Balanced Pair Differential Mode</h3>
 
<p>Don't forget that both STP and UTP use the twisted balanced pair differential mode transmission principles to help reduce the interference or crosstalk from other neighbouring pairs within a cable as well as that from external EMI sources.</p>
 
<h3>Twist Characteristics</h3>
 
<p>The period of the twist (which is usually the same as for UTP - 3  twists/inch) is designed to reduce EMI - Elector-Magnetic Interference from both; the other pairs of the same cable and exterior influences as well, thereby preserving the signal during its travel along the wire.</p>
 
<h3>Advantage of Shielded Twisted Pair (STP)</h3>
 
<ul>
<li> <strong>EMI</strong> - Less susceptable to the negative effects of EMI </li>
 
</ul>
<p>Disadvantages of Shielded Twisted Pair (STP)</p>
 
<ul>
<li> <strong>Manufacturing Costs</strong> - The extra shielding makes the cable considerably more expensive to manufacture</li>
 
<li> <strong>Production Volumes</strong> - Much smaller volumes of STP are produced in comparison to UTP and this disparity really impacts to-market expense and thus makes STP considerably dearer</li>
 
<li> <strong>Competitive Market-Place Environment</strong> - When combined with the greater cost to manufacture STP is considerably dearer than UTP</li>
 
<li> <strong>Availability</strong> - The enormous volumes of UTP produced mean that it is more readily available than STP</li>
 
<li> <strong>Bulky</strong> - It also makes the cable bulkier </li>
 
</ul>
<h3>Shielded Twisted Pair (STP) Usage Indicators</h3>
 
<ul>
<li> Mission critical applications</li>
 
<li> Environments with high levels of background EMI</li>
 
<li> Environments containing a high potential of electrical interference due to proximity of other wiring and electrical and electronic equipment</li>
 
<li> Environments where electro-magnetic surges are known to occur such as the turning on and off of devices that draw considerable voltage and current flow</li>
 
<li> Environments containing other sensative electrical and electronics equipment such as hospital intensive care units, coronary care units, surgical theaters and life support systems </li>
 
</ul>
<h3>STP Loses Niche Market Edge</h3>
 
<p>Today coaxial and fiber-optic cabling are the preferable options in these scenarios.</p>
 
<p>Standard Shielded Twisted Pair (STP)</p>
 
<ul>
<li> <strong>The Shield Layer</strong> - STP cabling includes metal shielding over each individual pair of copper wires which provides protection against external EMI</li>
 
<li> <strong>Token Ring Networks</strong> - the IBM Cabling System specifications for Token Ring Networks specified the use of 150 ohm shielded twisted pair cables </li>
 
</ul>
<p>When the Network Cabling Guide returns in Part 6 we will move straight into the most common of all copper-based transmission media; Unshielded Twisted Pair - (UTP), and there is a considerable range and diversity of performance capabilities to be found here. In fact Unshielded Twisted Pair (UTP) cabling is without doubt the predominant type of cable to have been used in computer networking applications to date. Until next time enjoy.</p><a href="http://www.pheedo.com/click.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FNetwork-Cabling-Guide-Shielded-Twisted-Pair.114633"><img src="http://www.pheedo.com/img.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FNetwork-Cabling-Guide-Shielded-Twisted-Pair.114633" border="0"/></a>]]></description>
<pubDate>Sun, 27 Apr 2008 02:38:17 PST</pubDate></item>
<item>
<title>Benefits of Transparent Bridging</title>
<link>http://www.computersight.com/Communication-&amp;-Networks/Benefits-of-Transparent-Bridging.113477</link>
<description>
<![CDATA[<p>The CCNA Summary Series continues with a look into the value and benefits that using transparent bridging brings to the party. Get the benefits of LAN segmentation the easy way through using transparent bridges; the network administrator's greatest plug "n" play friend.</p>
 
<h3>LAN Segmentation Using Transparent Bridges</h3>
 
<h4>Architecture Matters</h4>
 
<p>Transparent bridges can be used with Ethernet networks. Other architectures require different types of bridges. For example Token Ring networks use a type of bridging technology called source-route bridging.</p>
 
<h3>Reduced Outlay and Greater Return On Investment (ROI)</h3>
 
<p>It's all about more bangs for the buck! Today a compact workgroup switch that supports transparent bridging such as those from D-Link, 3Com, Netgear and others can be obtained for well under $100.</p>
 
<h4>Unmanaged Vs Managed <br /></h4>
 
<p>Switches that support transparent bridging can be of the managed or unmanaged varieties. The big difference; apart from the cost that is, is that unmanaged switches are a lot more user friendly than the managed variety.</p>
 
<h3>Improved Network Performance</h3>
 
<p>LAN segmentation using transparent bridges reduces the size of the network's collision domain(s) because it turns large collision domain(s) into a number of smaller collision domains with fewer machines per collision domain (LAN segment).</p>
 
<h4>Fewer Collisions <br /></h4>
 
<p>Reducing the number and frequency of collisions improves the network's data transfer speed and efficiency</p>
 
<h4>Reduced Competition</h4>
 
<p>Improved data transfer rates and shorter wait states because fewer machines per segment means less competition for the finite available transmission bandwidth</p>
 
<h3>More Effective Bandwidth Allocation</h3>
 
<h4>Improved Effective Available Network Bandwidth</h4>
 
<p>Fewer nodes per segment means each node effectively gets a greater &amp;ldquo;share&amp;rdquo; of the available bandwidth.</p>
 
<h4>Maximizing Returns <br /></h4>
 
<p>Since the available network bandwidth is a finite resource any measures that improve this aspect will have the greatest noticeable effect on the largest number of devices both individually and as a&amp;rdquo;collective&amp;rdquo;.</p>
 
<h3>More Responsive Network from the Users Perspective</h3>
 
<h4>Improved Network Responsiveness <br /></h4>
 
<p>Segmentation of large collision domains into a number of smaller collision domains will result in users noticing an increase in the responsiveness of the network in terms of a reduction in the amount of time that their computer takes to gain access to the transmission media in order to transmit the job that the user has requested.</p>
 
<h4>Faster Transmissions <br /></h4>
 
<p>Users will also see an overall improvement in the time taken to complete a data transmission or data reception task.</p>
 
<h4>Shared Internet Services Improved <br /></h4>
 
<p>Internet searches; for instance, will be done in shorter periods of time than was the case prior to the segmentation.</p>
 
<h3>Reduced Network Congestion</h3>
 
<p>Transparent bridging can greatly reduce network congestion &amp;amp; bottlenecks. Only traffic that belongs on a segment will be placed onto that segment by a device implementing transparent bridging. How transparent bridging works its magic is a topic that will be discussed in a future article of the CCNA Summary Series.</p>
 
<h3>Greatly Reduced Administrative Overheads</h3>
 
<h4>Reduced Installation Time <br /></h4>
 
<p>Because of the plug "n" play nature of transparent bridges administrators will spend far less time in installing this type of bridge or a switch.</p>
 
<h4>Switches and Transparent Bridging <br /></h4>
 
<p>Most switches today support transparent bridging. The main difference between these switches and the traditional transparent bridge is in port density. Switches have massively higher port densities than traditional transparent bridges. It's all a matter of evolution.</p>
 
<h4>Smaller Footprint</h4>
 
<p>With higher port densities a modern switch that supports transparent bridging will occupy less physical space and so are ideal to use as workgroup out-of-the-closet scenarios.</p><a href="http://www.pheedo.com/click.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FBenefits-of-Transparent-Bridging.113477"><img src="http://www.pheedo.com/img.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FBenefits-of-Transparent-Bridging.113477" border="0"/></a>]]></description>
<pubDate>Wed, 23 Apr 2008 17:13:49 PST</pubDate></item>
<item>
<title>The Magic of Transparent Bridging 2</title>
<link>http://www.computersight.com/Communication-&amp;-Networks/The-Magic-of-Transparent-Bridging-2.113475</link>
<description>
<![CDATA[<p>While not strictly part of the transparent bridging protocol; STP mode, the spanning tree algorithm, redundancy and loop avoidance are none-the-less critical to the efficient functioning and service provision of transparent bridging devices. The thing that they all have in common is their capacity to address the nightmares, havoc and general network crippling chaos that loops can cause.</p>
 
<p>I am also making mention of them here because due to their very nature transparent bridging devices are all about no administration. Plug "n" Play they most certainly are. But what do/can you do when loops enter the picture? Well; in most instances, you certainly can't interface with the software that is running on most of these local workgroup transparent bridges and switches because there is none.</p>
 
<p>The answer is not to be found blowing in the wind but rather in the form of built-in protocols and algorithms that take care of all of these issues while the device stays true to its &amp;ldquo;no user input required&amp;rdquo; philosophy.</p>
 
<h3>Loop Avoidance</h3>
 
<h4>Redundancy, Reliability, Robustness and Fail-Over</h4>
 
<p>For reasons of redundancy and the resultant increase in reliability and robustness that it delivers network segments may by configured to be reachable via more than one port (even if in a round-a-bout manner).</p>
 
<p>Reasons for Creating Networking Loops</p>
 
<ul>
<li> The implementation of redundant fail-over solutions is a major player in the creation of networking loops</li>
 
<li> For reasons such as the &amp;ldquo;safety-net&amp;rdquo; aspect of implementing multiple hot-swappable &amp;ldquo;just-in-case&amp;rdquo; &amp;ldquo;spare parts&amp;rdquo; devices</li>
 
<li> The idea that if a mission-critical device were to fail then the already installed and powered-up &amp;ldquo;spare&amp;rdquo; device can immediately jump into action thereby reducing the system and network outages cause by device failures would be negated. Unfortunately this is another culprit when it comes to loop creation. </li>
 
</ul>
<p>But what's all the fuss about?</p>
 
<ul>
<li> Loops cause great network chaos and all round confusion</li>
 
<li> Devices such as transparent bridges that operate at the data link layer (2) are particularly hard hit by the negative effects of network loops</li>
 
<li> Something had to be done to prevent them from totally crippling the network</li>
 
</ul>
<p>This is why loop avoidance is important. Correct configuration and physical connectivity are essential but the moment we introduce redundant pathways loops will exist even in the most simple of networks.</p>
 
<p>In fact loops can occur in a network with as few as two switches.</p>
 
<h4>The Spanning Tree Algorithm</h4>
 
<p>The Spanning Tree Algorithm is used by switches in Spanning Tree Protocol (STP) mode to counteract the effect of loops and redundant pathways. STP mode has meant that network administrators can introduce redundant pathways and redundant switches into their networks without creating loop-hell.</p>
 
<ul>
<li> When in Spanning Tree Protocol (STP) mode; switch ports that create redundant links will be selectively shut and for as long as the primary (lowest cost path) port remains available they will stay that way.</li>
 
<li> If the lowest cost port fails then the Spanning Tree Algorithm will be used to recalculate the network and the redundant pathway port will become active. The message will still get through. </li>
 
</ul>
<h4>Multi-Destination MAC Addresses</h4>
 
<ul>
<li> Frames intended for multiple destinations (transmit once-receive many) such as; broadcasts and multicasts, are forwarded through multiple ports by the transparent bridge.</li>
 
<li> Broadcasts will be flooded</li>
 
<li> Multicasts will be sent through the appropriate ports </li>
 
</ul>
<p>For Example:</p>
 
<ul>
<li> A multicast may be for two or three or however many different segments that need to be reached via more than one port of the transparent bridge or switch at a time</li>
 
<li> Those ports that do not have destination nodes for which the multicast is intended do not receive the transmission </li>
 
</ul>
<h4>Transparent Bridging Implementations</h4>
 
<p>The most common global implementation of transparent bridging today is in the form of integrated multiservice/multifunction devices such as ADSL broadband Modem Routers with built in switches. It is these devices that have enabled networks of all sizes to share their Internet connection among considerable numbers of hosts, nodes and users.</p>
 
<p>Benefits of Transparent Bridging Include</p>
 
<ul>
<li> Successful isolation of intra-segment traffic, thereby reducing the traffic seen on each individual segment. This is called filtering and occurs when the source and destination MAC addresses reside on the same bridge interface.</li>
 
<li> Filtering usually improves network response times, as seen by the user. The extent to which traffic is reduced and response times are improved depends on the volume of intersegment traffic relative to the total traffic, as well as the volume of broadcast and multicast traffic </li>
 
</ul>
<p>Learning, flooding and forwarding are all part of normal operation for a transparent bridge/switch and the decisions involved in carrying out these functions are accomplished through the building, maintenance and referencing of the associations of entries in the device's filter (forwarding) table.</p>
 
<p>Until next time, enjoy!</p><a href="http://www.pheedo.com/click.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FThe-Magic-of-Transparent-Bridging-2.113475"><img src="http://www.pheedo.com/img.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FThe-Magic-of-Transparent-Bridging-2.113475" border="0"/></a>]]></description>
<pubDate>Wed, 23 Apr 2008 17:10:03 PST</pubDate></item>
<item>
<title>The Magic of Transparent Bridging 1</title>
<link>http://www.computersight.com/Communication-&amp;-Networks/The-Magic-of-Transparent-Bridging-1.113472</link>
<description>
<![CDATA[<p>This series of articles is all about networking, protocols and CCNA exam content topics. Today we are going to investigate bridges, switches and switching methods a little more. To be more precise; we are going to discuss something that hubs can't do and that is transparent bridging.</p>
 
<h3>Transparent Bridging</h3>
 
<p>This is a &amp;ldquo;no-brainer&amp;rdquo; technology that delivers plug "n" play capabilities to users and key networking components like workgroup switches.</p>
 
<p>Transparent Bridging Benefits In a Nutshell</p>
 
<h4>Routers, Switches, and Bridges</h4>
 
<p>While routers interconnect networks, switches and bridges interconnect network segments and devices. Cisco&amp;reg; refers to this as the access layer and that is exactly what these devices do. They give the user or device access to network resources including the infrastructure such as transmission media.</p>
 
<p>You have got to get on the cable, before you can get to the gateway/router, before you can &amp;ldquo;surf&amp;rdquo; the net. We are going to check out a &amp;ldquo;no-brainer&amp;rdquo; way of doing this. It's called transparent bridging.</p>
 
<h4>Transparent Bridges</h4>
 
<p>Transparent bridges (including modern switches) are so named because their presence and operations are transparent to network hosts and users alike.</p>
 
<h3>Learning, Forwarding, and Filtering</h3>
 
<h4>Making Decisions</h4>
 
<p>In order to fully understand how a transparent bridge decides whether or not it should forward a frame and selects the appropriate interface on which to place that frame we need to take a look at the primary functions of a transparent bridge: learning, forwarding, filtering and loop avoidance.</p>
 
<h4>Loop Avoidance <br /></h4>
 
<p>Another role played by transparent switches is loop avoidance which is one of the topics that will be discussed in Magic of Transparent Bridging Part Two.</p>
 
<h4>Out-of-the-Box</h4>
 
<p>Because a new out-of-the-box transparent bridge has never been exposed to the network that it is about to be connected to I shall start by describing the learning process using a fresh out-of-the-box device first.</p>
 
<h3>Learning</h3>
 
<p>When transparent bridges are first powered on, they learn the network device locations (including workstations) by analysing the source Media Access Control (MAC) Address of all incoming frames from all attached networks.</p>
 
<h3>Memory</h3>
 
<p>Before anything can learn it needs to have the magic ingredient - MEMORY. Transparent bridging and the devices that use it are just like us in that their capacity to learn depends on:</p>
 
<ul>
<li> Writing to Memory - The ability to lay down memory in preparation for future recall</li>
 
<li> Reading from Memory - The ability to recall that which is stored in memory</li>
 
<li> Recall on Demand - The capacity to recall at will. It is this ability that allows you to randomly access the contents of memory or in computer lingo - Random Access Memory (RAM)</li>
 
<li> Selective Recall - The ability to selectively recall preferred memories at will</li>
 
<li> Application - The capacity to apply the contents of memory to the situation at hand</li>
 
<li> Being Smart - The being smart part is all about selecting the most appropriate memory item to recall with regards to your current dilemma </li>
 
</ul>
<h3>The Filter Table</h3>
 
<p>That part of memory that we are interested in here is the memory which the device (switch) uses in performing the process of transparent bridging. It is called a Filter Table. For reasons that will become obvious shortly the Filter Table is also known as:</p>
 
<ul>
<li> Forwarding Table</li>
 
<li> Media Access Control (MAC) Address Table</li>
 
<li> Hardware Address Table </li>
 
</ul>
<h3>Nomenclature and Misconceptions</h3>
 
<p>The important thing here is that all of the above listed names are indeed correct alternate names (synonyms) for the Filter Table. Furthermore; they are more or less interchangeable, it is however most definitely wrong to use the term Routing Table in reference to a transparent bridging device's Filter Table.</p>
 
<p>Filter Table Building Example:</p>
 
<p>Here is a short example of how a device uses transparent bridging to build its Filter Table:</p>
 
<ul>
<li> The transparent bridging device sees a frame arrive on Port 1</li>
 
<li> Examining the source address field of this frame the device learns that the transmission was from Host A</li>
 
<li> It concludes that Host A can be reached through the segment connected to Port 1</li>
 
<li> The transparent bridging device examines the contents of its Filter Table. Because this is a new device and this is the first network conversation that this transparent bridge has experienced there will be no entries in its Filter Table.</li>
 
<li> The transparent bridging device will now create a new entry in its Filter (forwarding) Table listing Host A as reachable via Port 1</li>
 
<li> Every time a frame arrives at the transparent bridging device this process is repeated</li>
 
<li> It is in this way that a transparent bridge builds its Filter Table
   
<ul>
<li> This is what is Referred to as the LEARNING Process </li>
 
</ul>
</li>
 
</ul>
<h3>Forwarding - Flooding</h3>
 
<p>Transparent bridges/switches examine incoming frames to determine their intended destination Media Access Control (MAC) Address they will then:</p>
 
<ul>
<li> Look-Up Their Filter Table - In transparent bridging mode the bridge/switch will always refer to its Filter Table (forwarding) to check for any entries relating to this MAC Address. Who knows? There may already be an entry indicating through which port this destination can be reached.</li>
 
<li> In our case we have a new transparent bridge. So; unless the frame is intended for Host A, the bridge will not have any entries corresponding to the intended destination MAC Address in its Filter Table </li>
 
<li> Because the transparent bridge doesn't know anything about this MAC Address it can not make the decision to forward the frame exclusively out of the one correct specific port</li>
 
<li> So; by default, whenever a transparent bridge encounters a frame with a destination MAC Address that it hasn't encountered before (the first time) it will &amp;ldquo;flood&amp;rdquo; the frame out of every port except the one on which it arrived.</li>
 
<li> Our device is no different and that is exactly what it does. It sends copies of the frame out every port except the one which it arrived on. </li>
 
</ul>
<h3>Forwarding - Filtering</h3>
 
<h4>Filter Table Building</h4>
 
<p>As more traffic transpires over time the transparent bridge will continue building its Filter Table.</p>
 
<ul>
<li> New entries are created for each new (learned) source MAC Address along with the corresponding port through which this address can be reached. </li>
 
</ul>
<h4>Known Source MAC Address and Port Entries</h4>
 
<p>Eventually the transparent bridge will lookup the source MAC Address of an incoming frame in its Filter Table and it will find an existing entry.</p>
 
<ul>
<li> If; the known entry (previously recorded) in the transparent bridge's Filter Table and the current frame's source MAC address and port number match, the transparent bridge will not need to add this source MAC address to its Filter Table. </li>
 
</ul>
<h4>Known Destination MAC Address and Port Entries</h4>
 
<ul>
<li> Now the transparent bridge examines the frame in order to determine the destination MAC address of the newly arrived frame</li>
 
<li> It will then check its Filter Table for any entries pertinent to the intended destination MAC Address of the current frame</li>
 
<li> This time it finds an entry that lists this particular destination MAC Address as being reachable via one of its (the bridge/switch) ports</li>
 
</ul>
<p>Since the destination MAC Address of the current frame is known to be contactable via a specific port on the transparent bridge/switch the switch/bridge will now be able to selectively place the frame onto the correct network segment via the appropriate port.</p>
 
<h3>Filtering</h3>
 
<p>Now instead of 'flooding` this frame out of all ports; bare the one through which it arrived, the transparent bridge/switch will be bale to selectively and exclusively forward the frame only out of the port indicated by its Filter Table as being the port via which this destination MAC can be reached.</p>
 
<p>This is what is known as filtering.</p>
 
<p>Only the segment on which the destination MAC Address resides now receives the transmission thereby allowing all other devices located on all other ports to be free to transmit themselves.</p>
 
<h3>Not Party To the Conversation</h3>
 
<p>This means that devices can transmit or receive simultaneously while other network conversations; that they are not party to, are in progress. The importance of this cannot be underestimated as it results in considerable improvements to network performance.</p>
 
<p>There is still one proviso however; and that is that only one conversation at a time can take place on a segment. The network is a one conversation at a time/segment network.</p>
 
<h3>Collision Domains - The Implications</h3>
 
<p>Suppose a device that uses transparent bridging has six ports and each of these ports is used to connect different devices or network segments. The result would be that:</p>
 
<ul>
<li> The network will now be comprised of six independent segments</li>
 
<li> All conversations between nodes on the same segment will remain confined to that segment. This is known as a collision domain. </li>
 
</ul>
<p>Now suppose that nodes on two different segments are having a conversation then:</p>
 
<ul>
<li> The transmission will be contained within those two segments</li>
 
<li> The other four segments are free to go about their own conversations</li>
 
</ul>
<p>By segmenting collision domains transparent bridge greatly improve network efficiency, performance and the potential available effective bandwidth.</p>
 
<h3>Improved Network Bandwidth and Efficiency</h3>
 
<p>Thus a six port transparent bridge can cater for three different two segment conversations simultaneously. Whereas prior to network segmentation only one conversation at a time could take place over the entire network. This is a much greater improvement in both efficiency and bandwidth while reducing the potential for collisions.</p>
 
<p>Such technologies as loop avoidance, redundancy, the spanning tree algorithm and STP mode will all be discussed in The Magic of Transparent Bridging Part Two. Until then enjoy!!</p><a href="http://www.pheedo.com/click.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FThe-Magic-of-Transparent-Bridging-1.113472"><img src="http://www.pheedo.com/img.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FThe-Magic-of-Transparent-Bridging-1.113472" border="0"/></a>]]></description>
<pubDate>Wed, 23 Apr 2008 17:05:11 PST</pubDate></item>
<item>
<title>Copper Cabling</title>
<link>http://www.computersight.com/Communication-&amp;-Networks/Copper-Cabling.110932</link>
<description>
<![CDATA[								<h3>Copper Cables</h3>
 
<p>Let's start with copper-based cables since they are the most common and the easiest to install. This is particularly true when making custom cable runs. Before I discuss the types of copper cable that are readily obtainable at most hardware or computer shops let us look at the categories of cable which you may encounter out there in the wild.</p>
 
<p>First of all I will start with the oldest types and then progressively discuss the more recent varieties. Please take note that it is highly possible that those just entering into the world of network cabling may not ever actually encounter some of the earlier types of copper cabling other than to remove them.</p>
 <img alt="" src="http://images.stanzapub.com/readers/computersight/2008/04/18/146324_3.jpg" />
<p>The reasons as to why this is so will be made clear at the appropriate time. For now though you can safely assume that being made of a considerably thick copper core does give the early coaxial cable scrap metal value.</p>
 
<h3>Coaxial Cable</h3>
 
<p>Coaxial cabling consists of a single central copper conductor core surrounded by a foam filler layer. Both layers are surrounded by a braided metal shield and then by another outer covering sheath usually plastic.</p>
 
<p>The inner foam layer; which is fire resistant, was also intended to provide insulation between the center conductor and the braided metal shield which acts to reduce (even block) any outside EMI from fluorescent lights, motors, and other computers. It also helps to make coaxial cable tear resistant which as you will soon learn has both an upside and a down-side.</p>
 
<p>The final layer; usually composed of some waterproof material such as plastic is there for overall protection and to provide resistance to environmental damage such as that which water might cause.</p>
 
<p>Coaxial cabling is notorious for being difficult to install but it is highly resistant to signal interference and can support greater cable lengths between network devices than twisted pair cable (STP &amp; UTP). One of the reasons for its difficult to install nature is due to the outer braided metal layer and the overall thickness in diameter of both the inner conducting signal carrying layer and the overall thickness of the entire cable as a package.</p>
 
<h3>Types of Coaxial Cable</h3>
 
<p>There are two types of coaxial cabling; with each being named for reasons that will soon become obvious:</p>
 <ol> 
<li> 
<h3>Thick Coaxial Cable</h3>
 </li>
 </ol> 
<ul>
<li> <strong>Thicknet</strong> - Also referred to as thicknet and was the first variant to be used with Ethernetnetworks</li>
 
<li> <strong>Thick Coaxial Cable</strong> has an extra protective plastic cover to assist in resistance (tolerating) to damp/humid environment tolerance by keeping moisture away from the center conductor. It is this extra layer that makes thick coaxial cable thicker than thin coaxial cable and hence the name.</li>
 
<li> Ethernet - When carrying Ethernet signals the term 10Base5 is used to describe the specifications to which the cable must adhere in order to be suitable</li>
 
<li> <strong>Ten</strong> - The 10 refers to the cable's maximum data throughput of up to 10 Megabits/sec</li>
 
<li> <strong>Base</strong> - The BASE tells us that this cable is intended for use with baseband signaling as opposed to broadband signaling.</li>
 
<li> Baseband signaling means signals and/or systems whose range of frequencies is measured from zero to a maximum bandwidth or highest signal frequency. Generally the entire spectrum range is used with every transmission. This meant that only one signal could be propagate across the medium at a time.</li>
 
<li> <strong>Five</strong> - The 5 refers to the maximum segment length being 461.5 meters (approximately 1600 feet or 500 yards)</li>
 
<li> <strong>Linear</strong> - In addition 10BASE5 cables had to be one linear run</li>
 
<li> <strong>Terminators</strong> - Another requirement was that 50 ohm resistive terminators had to be installed at both ends of a cable run</li>
 
<li> <strong>Transceivers</strong> - For 10BASE5 networks transceivers had to be installed at 2.5 meters. This was so as that reflections from multiple taps were not in phase which helped in reducing the amount of noise and signal degradation. Suitable attacment locations were marked on the cable.</li>
 
<li> <strong>N Connectors</strong> - Transceivers could also be connected by using N connectors at the end of a cable segment</li>
 
<li> <strong>T-Connectors</strong> - T-Connectors are not allowed</li>
 
<li> <strong>Attachment Unit Interface (AUI)</strong> - Transceivers are connected to nodes via an interface that was known as the Attachment Unit Interface (AUI) which is a 15-pin, double row D-Sub type of connectort that used clips rather than screws for cable resistance (to stop the cable from being accidently dislodged)</li>
 
<li> 10BASE5 coaxial cable is rather stiff and measured approximately 9.5 mm (0.375 inches) in diameter with an impedance of 50 ohms</li>
 
<li> <strong>100 Nodes</strong> - A 10BASE5 network segment can support up to 100 nodes</li>
 
<li> <strong>Thick coaxial cable</strong> was a great choice when running longer lengths in a linear bus network compared to 10BASE2 (thin coaxial cable)</li>
 
<li> <strong>Non-Flexible</strong> - Thick Coaxial Cable's greatest disadvantage is that it is very difficult to install because of its thickness and lack of flexibility </li>
 
</ul>
<ol> 
<li> 
<h3><strong>Thin Coaxial</strong> Cable</h3>
 </li>
 </ol> 
<ul>
<li> Thinnet - Also referred to as <strong>thinnet. </strong>When carrying Ethernet signals the term 10Base2 is often used</li>
 
<li> Ten - The 10 means that the cable was rated at a maximum data throughput rate of 10 Megabits/sec</li>
 
<li> BASE - The BASE tells us that this cable is intended for use with baseband signaling as opposed to broadband signaling. Baseband signaling means signals and/or systems whose range of frequencies is measured from zero to a maximum bandwidth or highest signal frequency. Generally the entire spectrum range is used with every transmission. This meant that only one signal could be propagate across the medium at a time.</li>
 
<li> Two - The 2 refers to the approximate maximum segment length of 200 yards (185 meters)</li>
 
<li> Thin Coaxial Cable - Was very popular in school networks, especially linear bus networks</li>
 
<li> Termination - Another factor that needs to be taken into consideration when working with coaxial cabling of all varieties is the need to terminate any cable segments that were not fixed to another device. </li>
 
<li> T-Connectors - When wiring a 10BASE2 network, special care has to be taken to ensure that cables are properly connected to all T-connectors and appropriate terminators are installed. </li>
 
<li> Installation Unfriendly - Although; easier to work with and install than thick coaxial cable it was still cumbersome and difficult to work with</li>
 <img alt="" src="http://images.stanzapub.com/readers/computersight/2008/04/18/146324_1.jpg" />
<li> Comparative Improved Flexibility - This state of affairs was due in part to the solid copper core and its relatively thick diameter and the outer mesh metal layer. You may have used Bar-B-Que gas bottles that used hoses that had an outer metal mesh layer and will therefore have encounter this problem before. 10BASE2 was more flexible than 10BASE5 but it was still a problem.</li>
 
<li> Single Point of Failure - A failure at any point of the network cabling tends to prevent all communications which made 10BASE2 difficult and time consuming to administer, manage, maintain and troubleshoot.</li>
 
<li> 10BASE2 Implementation - The characteristics of 10BASE2 and thin coaxial cable meant that it was ideal for small networks of 2-4 machines.</li>
 
<li> Competition - The main reason that we never saw wholesale rollout of 10BASE2 was that CAT 3 cable and the forthcoming CAT 5 cable were considerably cheaper and easier to install were being to build up a head of steam in terms of sales and general acceptance. As a result 10BASE2 was never really main-stream consumer first choice for use as a network medium. However; Its academic installation base did mean that it hung around for a long time. </li>
 
</ul>
<h3>Coaxial Cable Connectors</h3>
 <img alt="" src="http://images.stanzapub.com/readers/computersight/2008/04/18/146324_2.jpg" />
<p>The BNC connector is the most common type of connector to be found in association with coaxial cabling. BNC - Bayone-Neill-Concelman or bayonet connector.</p>
 
<p>There are also other types of connectors and adapters that have been used in networks that were using thin coax as their medium including: a T-connector, barrel connector, and terminator.</p>
 
<h3>Crimp</h3>
 
<p>As always it is the connectors on the cable that are the weakest points in any network and coaxial connectors are no exception. It is therefore particularly important to use coaxial BNC connectors that crimp rather than screw onto the cable as they consistently produce stronger and more reliable connectivity.</p>
 
<h3>Vampire Tap</h3>
 
<p>One of the major advantages of 10BASE5 cable was that it allowed for new connections to be made while all existing connections remained live (still in use). The device used to do this is called a vampire tap.</p>
 
<p>With practice the cabler was able to clamp the vampire tap onto the existing cable by forcing a spike inside the tap to pierce through the outer shielding layers to make contact with the solid copper core that performed the transmission and reception of the signal.</p>
 
<p>Other spikes; which bit into the outer conductor, were deployed at the same time as the copper core was being spiked when a special tool clamping/crimping tool was used to perform the clamping procedure. These clamps/crimps were readily available from hardware stores, electronics stores and electrical supplies stores.</p>
 
<p>It was not long before we began to see vampire taps built into the transciever because this allowed the use of more flexible multi-wire cables</p>
 
<p><strong>Repeaters</strong> - Repeaters are used in scenarios where there is a greater distance between machines than the manufacturer's cable specifications cite as being the maximum distance that this particular copper cable could be run if you hope to get any worthwhile service. In order to increase the maximum distance between nodes that the manufacturer's specifications stipulated as being so repeaters can be used.</p>
 
<p>In the next article we will be continuing our investigation of network cabling using copper-based cables by having a look at twisted pair cabling starting with shielded Twisted Pair (STP) and Unshielded Twisted Pair (UTP)</p>							<a href="http://www.pheedo.com/click.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FCopper-Cabling.110932"><img src="http://www.pheedo.com/img.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FCopper-Cabling.110932" border="0"/></a>]]></description>
<pubDate>Fri, 18 Apr 2008 05:41:22 PST</pubDate></item>
<item>
<title>Transmission Media</title>
<link>http://www.computersight.com/Communication-&amp;-Networks/Transmission-Media.110159</link>
<description>
<![CDATA[<p>For wired networks the cable is the medium through which information usually moves from one device, computer or network to another. There are several types of cable which are commonly used with LANs - Local Area Networks and today's topic will introduce the two most common cable transmission media - copper and fiber-optic cables. But first we will discuss why we need transmission media in the first place and how we got to where we are today.</p>
 
<h3>The Need for a Transmission Medium</h3>
 
<p>The first recognised computer network medium was known as sneaker-net. This was because way back when in the early days of computing those users who wanted to transfer or share data with other users would make a copy onto floppy disk and get up and go to the intended recipient and hand it to them.</p>
 
<p>The sneaker-net came into being as observers; usually other university types noted that the majority of these young computer types wore sneakers and since they used their sneakers as the primary means of transporting the data the term sneaker-net came into use. It was probably not meant in a complimentary way. The term &amp;ldquo;geek&amp;rdquo; hadn't even been thought of at the time or else the term may have been &amp;ldquo;geek-net&amp;rdquo; but we will never know.</p>
 
<p>Oh! And by the way the floppy disks that I am referring to here are the original floppy disks which were large, flat, round, non-rigid, discs of magnetic medium and not the small 3 1/2 &amp;ldquo; types that were and are still used by some people today.</p>
 
<p>The capacity of these disks; which was considered to be quite large at the time, was around 320 Kilobytes. The more modern varieties have a larger capacity with the high density varieties that can still be brought today having a standard capacity of 1.44 Megabytes.</p>
 
<p>Today most new machines do not even have a legacy floppy drive included which is probably just as well. They were not the most reliable of devices and by today's standards their storage capacity was miniscule. Today we might wonder just what use; if any, could a floppy disk be? Well back then computers were primarily code-oriented and the output of human "friendly" text was a considerable and notable achievement. Then we started to see a new and wonderful device being attached to the computer. It was called a keyboard.</p>
 
<p>Up until then input had been in the form of punch cards and tape. Except for the multi-mega resource endowed who were able to afford magnetic tape reels. But for the average enthusiast they keyboard and floppy disk drives were the rage. Then we saw another new device come into being; the monitor. Well; now things were really getting up to speed, we could read text (in monochrome of course) on a television type device. The world was really becoming a truly wondrous place.</p>
 
<p>Things only got better as hard disk drives that were &amp;ldquo;affordable&amp;rdquo; and compact enough for the smaller computer were mass produced. With capacities ranging up to 60 Megabytes these storage giants and they were big and heavy and most definitely not portable as we know the term today. Now we could load a program into the computer and store it on the internal hard drive and then whenever we wanted to start the machine would had the option to start the program stored on the hard drive and run with that.</p>
 
<p>As more programs were developed and the hard drive became larger we saw the introduction into mainstream; although still enthusiast computers the need to manage these programs and this need resulted in the creation of what I will loosely call the early disk operating systems. They were refined and added to as time progressed and the term for them became the abbreviation DOS which many of you may have heard of. It stands for Disk Operating System.</p>
 
<p>Initially this was either pre-installed or factory upgraded but later it became possible to install this disk operating system from floppy disk which had also evolved into larger than 360 Kilobyte capacity disks by then. In fact 720 Kilobyte disks were very popular by now. Well is it has a habit of doing time did not stand still and software progressed in its capabilities and size so that multiple disks were required to install the disk operating system and most other programs as well.</p>
 
<p>Fortunately manufacturers were introducing larger capacity hard drive and floppies were evolving into the 1.44 MB capacity disks we know today and all was well in the world. Software evolved further and became ever larger with ever increasing storage requirements.</p>
 
<p>Major corporations were using mainframes with large capacity magnetic reel storage which was wonderful from a storage capacity point of view but the manner in which it operated was linear which meant that much turning of tape was required to access various data when required. The answer of course was to schedule access to increase the efficiency of use but that had its limitations.</p>
 
<p>In the mean time some bright spark in the computer department was talking to the mother via long distance telephone when the thought occurred to them that if they could converse over such a long distance surely machines could do the same. Okay maybe not over long distance but across the room would be handy. So it's off to the communications department that our hero goes. Upon arrival he asked the guys down there the big question. The reply he got nearly made him wet his pants in excitement.</p>
 
<p>Machines have in fact been communicating quite well over long and short distances for quite some time now. &amp;ldquo;Go down to Wall Street and check it out for yourself&amp;rdquo; was the com guy's reply. No need; our hero knows that if he goes to executive accounts and finance there are machines there that are always in touch with the money men down-town. So it's off to finance that our hero goes.</p>
 
<p>Once there; merely observing the ticker tape machines was inspiration enough. Using the telephone lines was the inspiration that he had. So off to the lab and sometime later our hero has rigged-up a contraption using readily available parts; cheap was a prime motive here. And so the first basic modem came into being. At least we don't need to take disks out of one machine and transfer them to the machine next to it by hand any more.</p>
 
<p>With the passage of time this novelty become a storm and the military decided to get in on the act an established a special research project known as ARPA. The network they created was called ARPANET (not much in the way of imagination here). The important thing however; was that they created the protocols that permitted machines to communicate over very long distances with reasonable reliability.</p>
 
<p>The core of this set of protocols was the Transmission Control Protocol (TCP) which was responsible for getting the message through. With more devices joining the conversation it became obvious that some way of identifying each machine was needed. The identification of each machine on a machine to machine level had as with all electronic communications devices been achieved using a hardware address which we know as the Media Access Control address or MAC address and worked well for awhile.</p>
 
<p>As the factors of scaling-up the size of the networked computers became of more important it was soon realised that purely using MAC addresses for machines that were permanently connected in a smallish local network was not a problem. The troubles began when trying to connect each of these small networks on a sporadic periodic basis (only when needed).</p>
 
<p>So the idea of letting the machines on the smaller local network sort out their MAC addresses and using a different addressing structure to identify remote networks gained impetus. This was the beginnings of a logical addressing structure. Well as the years went by and more and more machines were being networked and more and more networks were being interconnected on a global scale this logical addressing structure evolved considerably.</p>
 
<p>The best part of it all was that the smart guys who created TCP did such a fine job that it has been used ever since and when the time came that the number of interconnected networks was getting to be humanly unmanageable manually some way to overcome this had to be found. We were also seeing a number of different architectures being developed by different groups more or less independently and in competition with one another. The result was that not all networks could connect with all of the other networks.</p>
 
<p>At around this point in time the number of home computers being sold was beginning to skyrocket and many who used networked computers at work desired the same for their home computers. Having already developed the Hypertext Transfer Protocol (HTTP) and the Hypertext Markup Language (HTML) academics and researchers could now confer with each other and here a greater degree of collaboration between these groups of individuals developed. Admittedly this may have at times been a little constrained and secretive but non-the-less it happened.</p>
 
<p>The military were also in the processes of extending and evolving their networks. Cutting the story short it became obvious that something had to be done to make everything capable of talking to everything else. It was at around this point that the Internet Architecture Board (IAB) and the Institute of Electrical and Electronics Engineers (IEEE) really came to the fore.</p>
 
<p>The IAB took responsibility for overseeing and formulating standards relating to the development of the Internet. The IEEE met in February of 1980 to discuss what needed to be done to produce uniformity if the Internet was going to truly develop.</p>
 
<p>They came to the realization that there were a number of different competing and incompatible network technologies and decided that due to the various different possible media available it was all too much for just one group to deal with and so they created a number of subcommittees each charged with the responsibility for the production of a set of standards covering a smaller area of technology that could be used by one and all. I guess they must have heard what the little general said &amp;ldquo;Divide and conquer&amp;rdquo;.</p>
 
<p>Thus we saw the formation of the 802 DOT committees and the standards that were produced by them have all evolved over time. Some are still widely in use today, some aren't, some have gone to better pastures and others are only just beginning to become mainstream while a few are yet to &amp;ldquo;arrive&amp;rdquo;. For example the network system originally developed by the Digital Corporation&amp;reg;, Intel&amp;reg; and the Xerox&amp;reg; Corporation was called Ethernet and the committee formed to deal with the standards for this type of network architecture was the 802.3 subcommittee.</p>
 
<p>Another was formed to handle wireless networking communications. This was the 802.11 subcommittee and just to illustrate the manner in which the number of changes that have occurred as these architectures have evolved over the years the 802.11 subcommittee has appended the 802.11 with a letter to distinguish one set of wireless networking technology standards from the others. The first was called 802.11a and we are currently seeing the finalisation and market implementations of the 802.11n standard today. That makes a total of 14 major standards of wireless networking technologies in less than 28 years.</p>
 
<p>Well now we get to the point where we have all sorts of networks and a variety of transmission media what is what and which do I use? These are the questions that we will begin to answer now.</p>
 
<h3>Transmission Media</h3>
 
<p>The cables used in cabled networks are usually either copper-based or fiber-optic transmission medium, the architecture, topology, protocol(s), and size of the network will determine which is chosen and what variety of each is preferential.</p>
 
<p>I would be amiss not to mention that there could be a mix and match of cabling and other transmission media such as wireless. Different segments of a network may consist of different transmission media. Generally it is easier to separate out segments with different transmission so as that each type of media and each category within that type of medium are contiguous for that local section of the network. There are many reasons as to why this is a good idea and I will be discussing them as we progress.</p>
 
<p>An obvious example would be when mixing copper-based cable networks with wireless or even fiber-optic cable network sections. It is not too difficult to understand how each of these different transmission media will propagate a signal in different ways and hence will have different specifications and physical and electronic requirements that need to be satisfied for an effective transmission to take place.</p>
 
<p>With respect to the various different varieties (or flavours if you will) of each type of media for now let us just accept that the same holds true and consider it to be fact. I will explain the reasons in greater detail later.</p>
 
<p>In Part three of the Network Cabling Guide we will dive into copper cabling technologies so see you soon.</p><a href="http://www.pheedo.com/click.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FTransmission-Media.110159"><img src="http://www.pheedo.com/img.phdo?x=&u=http%3A%2F%2Fwww.computersight.com%2FCommunication-%26amp%3B-Networks%2FTransmission-Media.110159" border="0"/></a>]]></description>
<pubDate>Wed, 16 Apr 2008 05:42:10 PST</pubDate></item>
</channel>
</rss>
