Read without ads and support Scribd by becoming a Scribd Premium Reader.
See Premium Plans
 
 
C
H A P T E R
1
Ethernet Basics
 
 Auto-MDIX 
(automatic medium-dependent interface crossover) detects the wrongcable and causes the switch to swap the pair it uses for transmitting and receiving,which solves the cabling problem. (As of publication, this feature is not supported onall Cisco switch models.)
 
By default, each Cisco switch port uses
 Ethernet auto-negotiation
 
to determine thespeed and duplex setting (half or full). The switches can also set their duplex settingwith the
duplex
interface subcommand, and their speed with
 — 
you guessed it
 — 
the
speed
interface subcommand.
 
Cisco switches (and many other devices) can sense the speed using the
 Fast Link Pulses (FLP)
 
of the auto-negotiation process. However, if auto-negotiation isdisabled on either end of the cable, the switch detects the speed anyway based on theincoming electrical signal.
 
CSMA/CD
The original Ethernet specifications defined the
Carrier Sense Multiple Access with Collision Detection (CSMA/CD)
algorithm to deal with the inevitable collisions. CSMA/CD minimizesthe number of collisions, but when they occur, CSMA/CD defines how the sending stationscan recognize the collisions and retransmit the frame. The following list outlines the steps inthe CSMA/CD process:
1.
A device with a frame to send listens until the Ethernet is not busy (in other words, thedevice cannot sense a carrier signal on the Ethernet segment).
 
 
2.
When the Ethernet is not busy, the sender begins sending the frame.
3.
The sender listens to make sure that no collision occurred.
4.
If there was a collision, all stations that sent a frame send a jamming signal to ensure thatall stations recognize the collision.
5.
After the jamming is complete, each sender of one of the original collided framesrandomizes a timer and waits that long before resending. (Other stations that did not createthe collision do not have to wait to send.)
6.
After all timers expire, the original senders can begin again with Step 1.
Collision Domains and Switch Buffering
A
collision domain
is a set of devices that can send frames that collide with frames sent byanother device in that same set of devices.By definition of the term,
Ethernet hubs
:
■
 
Operate solely at Ethernet Layer 1
■
 
Repeat (regenerate) electrical signals to improve cabling distances
■
 
Forward signals received on a port out all other ports (no buffering)
As a result of a hub’s logic, a hub creates a single
 collision domain
.
Switches, however,create a different collision domain per switch port.
 
Switches have the same cabling and signal regeneration benefits as hubs, but switchesdo a lot more
 — 
including sometimes reducing or even eliminating collisions bybuffering frames. When switches receive multiple frames on different switch ports,they store the frames in memory buffers to prevent collisions.
 
The only devices that could create a collision are the switch port and the oneconnected device
 — 
and they each have a separate twisted pair on which to transmit.Because collisions cannot occur, such segments can use full-duplex logic.
 
When a switch port connects to a hub, it needs to operate in
HDX mode(LoopbackCircuitry)
, because collisions might occur due to the logic used by the hub.
 
 
Ethernet Layer 2: Framing and Addressing
Search
Search History:
Searching...
Result 00 of 00
00 results for result for
  • p.
    • Notes
    Load more