MCSE Boot CAMP
 

MCSE Boot Camp Schedule Schedule  MCSE Boot Camp FAQ FAQ  MCSE Boot Camp Vibrant Why Vibrant   MCSE Boot Camp location Location  MCSE Boot Camp location Notes home                                                                                                                                               

MCSE Notes for Ethernet 10.

 

[Next] [Previous] [Top] [Copyright] [Books About Ethernet]

Quick Reference Guide to the Ethernet System

1.8 Signal Topology and Media System Timing


When it comes to how signals flow over the set of media segments that make up an Ethernet system, it helps to understand the topology of the system. The signal topology of the Ethernet is also known as the logical topology, to distinguish it from the actual physical layout of the media cables. The logical topology of an Ethernet provides a single channel (or bus) that carries Ethernet signals to all stations.

Multiple Ethernet segments can be linked together to form a larger Ethernet LAN using a signal amplifying and retiming device called a repeater. Through the use of repeaters, a given Ethernet system of multiple segments can grow as a "non-rooted branching tree." This means that each media segment is an individual branch of the complete signal system. Even though the media segments may be physically connected in a star pattern, with multiple segments attached to a repeater, the logical topology is still that of a single Ethernet channel that carries signals to all stations.

The notion of "tree" is just a formal name for systems like this, and a typical network design actually ends up looking more like a complex concatenation of network segments. On media segments that support multiple connections, such as coaxial Ethernet, you may install a repeater and a link to another segment at any point on the segment. Other types of segments known as link segments can only have one connection at each end. This is described in more detail in the individual media segment chapters.

"Non-rooted" means that the resulting system of linked segments may grow in any direction, and does not have a specific root segment. Most importantly, segments must never be connected in a loop. Every segment in the system must have two ends, since the Ethernet system will not operate correctly in the presence of loop paths.

FIGURE 1.1 Ethernet signal topology

The figure shows several media segments linked with repeaters and connecting to stations. A signal sent from any station travels over that station's segment and is repeated onto all other segments. This way it is heard by all other stations over the single Ethernet channel.

As shown here, the physical topology may include bus cables or a star cable layout. The three segments connected to a single repeater are laid out in the star physical topology, for example. The point is that no matter how the media segments are physically connected together, there is one signal channel delivering frames over those segments to all stations on a given Ethernet LAN.

- Round Trip Timing

Quick Reference Guide to the Ethernet System - 04 SEP 95
[Next] [Previous] [Top] [Copyright] [Books About Ethernet]

Generated with CERN WebMaker

 Vibrant Advantage :

MICROSOFT Training PartnerMCSE Camp No Prestudy
MCSE Camp Longest Duration Camp
MCSE Camp Chalk Talk TrainingRed Hat Training Partner
MCSE Camp Highest Passing Rate
MCSE Camp Bootcamp since 1999
MCSE Camp Guaranteed Certification ...

Testimonials :

MCSE Certification boot camp

The instructor taught real world experience and did not just teach us to pass the test. He knew the subject well and was encouraging. His lectures were very well delivered....

Colver Dennis, USA 

 |MCSE CampIndia InformationMCSE Camp|MCSE CampCard PaymentMCSE Camp|MCSE CampSite MapMCSE Camp|MCSE CampContactMCSE Camp|MCSE CampHomeMCSE Camp ref1 | Ref2 | MCSE Notes | Ether100 Notes
© Copyright 2007 MCSE Camp

A Shortcut for Defining the Network IDs

Acknowledgments

Adding Entries to WINS from an LMHOSTS File

Adding HOSTS

Adding Other Records

Address Reservations

Address Resolution Protocol

Addressing

Addressing with IP Version 6

Administering a WINS Environment

Advanced Configuration Options

An FTP Server Does Not Seem to Work

Announcement Periods

Architectural Overview of the TCP/IP Suite

ARP

Arpa-127.rev File

Assigning Host IDs

Assigning Network IDs

Authentication

Automatic Restoration

Backing Up the DHCP Database

Backing Up the WINS Database

BIND Boot File

b-node

Bridges

Broadcast

Broadcasts

Browsing in a TCP/IP Internetwork

Browsing in an IP Internetwork

Browsing in Windows NT

Browsing Over Subnets

Browsing Roles

Browsing Tools

Building a Multihomed Router

Building a Static Routing Table

Cache Command

Callback Security

Callback with Multilink

Classes Defined

Client Access

Client Requirements

CNAME Record

Collecting the Browse List

Common RAS Problems

Communicating Over TCP/IP

Compacting the DHCP Database

Compacting the WINS Database

Configure HOSTS Files

Configure LMHOSTS File

Configuring a Client for WINS

Configuring as an IP Forwarder

Configuring for Caching-Only