Module 3: Introduction to Physical, Data and Network Layer Flashcards
Switch
mechanism to connect links to form a larger network
multi-input, multi-output which transfers packets from an input to one or more outputs
physical layer: electrical signals
link layer: frames
network layer: packets (routers)
physical layer: repeaters
distance limitation
- electrical signal becomes weaker as it travels
- imposes a limit on the length of a LAN
repeaters join LANs together
- analog electronic device
- continuously monitors electrical signals on each LAN
- transmits an amplified copy
physical layer: hubs
multi-port repeater
joins multiple devices electrically
- do not necessarily amplify the signal
- broadcast traffic that arrives on every other port
very similar to repeaters
- also operates at the physical layer
limitations of repeaters and hubs
one large collision domain
cannot support multiple LAN technologies
ethernet: utilization > 30% is considered heavy due to collisions
what is a solution to the distance problem with switches and routers?
link layer bridges
- connects two or more LANs at the link layer
link layer switches
typically connects individual computers
- a switch is essentially the same thing as a bridge
- … though typically used to connect hosts, not LANs
like bridges, support concurrent communication
- e.g. host A can talk to C while B talks to D
what is the main idea of bridges/switches?
main idea is traffic isolation
bridge/switch breaks network into LAN segments
bridge/switch filters packets
- frame only forwarded to the necessary segments
- segments become separate collision domains
what are the advantages of bridges/switches over hubs/repeaters?
- only forwards frames as needed
- filters frames to avoid unnecessary load on segments
- sends frames only to segments that need to see them
- separate collision domains allow longer distances - joins segments using different technologies
- e.g. ethernet - made possible with buffer
- not complete heterogeneity
what are the disadvantages of bridges/switches compared to hubs/repeaters?
delay in forwarding frames
- store and forward: bridge/switch must receive and parse the frame and perform a lookup to decide where to forward
- solution: cut-through switching
–> look up destination address in header, determine output port, forward frame
–> no error detection
higher cost!
- more complicated (intelligence, memory buffers, high performance) devices that cost more money
why are switches so expensive?
high performance chips
memory requirements
intelligence capability makes it complex to build
bridge/switch forwarding table
protocol
self learning: building the table
self-learning: without intervention from network admins
when a frame arrives:
- inspect the source MAC address
- associate the address with the incoming interface
- store the mapping in the switch table
- use a time-to-live field to eventually forget the mapping (in case host moves to another network)
when frame arrives with unfamiliar destination
- forward frame out all of the interfaces
- except for the one where the frame arrived
- hopefully, this case won’t happen very often
flooding can lead to loops
flooding can lead to forwarding loops
- if the network contains a cycle of bridges
- either accidentally or by design for higher reliability
what is the solution for avoiding cycles?
spanning trees
ensure the topology has no loops
- avoid using some of the links when flooding
- … to avoid forming a loop
spanning tree
- sub-graph that covers all vertices but contains no cycles
- links not in the spanning tree do not forward frames
spanning tree algorithm