Routing Flashcards

1
Q

Lowest OSI layer that deals with end to end transmissions

A

Network Layer

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What determines the path the network takes

A

Routing Algorithms

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What do Routing Algorithms do

A

Decide what path the network takes AND decides which output line an incoming packet should be transmitted on

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Store and Forward

A

Packets sent to nearest router and that router verifies it and sends it onto the next router until it arrives at destination

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Implementation of connectionless service

A

Packets injected into datagram network individually and routed independently. Packets called datagrams.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Implementation of connection oriented service

A

AKA Label-Switching. Path from source to destination setup for packets to be sent.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What does a connection oriented service avoid (In comparison to connectionless)

A

Avoids having to choose a new route for each packet

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Differences between VC and Datagram

A

VC needs setup phase, Datagram wastes space with address. VCs guarantee QoS but are vulnerable to crashes.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Routing vs Forwarding

A

Which routers to use vs What happens when packet arrives.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Handles incoming packets

A

Routing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Handles routing tables

A

Forwarding

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Routing Algorithm Features

A

Correctness, Simplicity, Robustness, Stability, Fairness, Efficiency.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Routing Algorithms should handle changes of

A

topography and traffic

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Two classes of routing

A

Nonadaptive and Adaptive

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Non-Adaptive

A

Do not base their decisions over estimates of network topology. Don’t respond to failures. Route computed in advance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Adaptive

A

Vary routing decisions according to changes in topology and traffic. Dynamic routing algorithms differ in where they obtain info from.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Optimality Principle

A

If Router A is on the optimal path from router B to router C then the optimal path from A to C falls on the same route

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Sink trees

A

Used by algorithms, not necessarily unique.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Shortest Path Algorithm

A

Build a graph of the network with each node being a router and each edge being a communication line. Measure length by hops.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Dijkstra Algorithm

A

Finds shortest path between source and all destinations. Labeled by distance. Uses temporary and permanent paths

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Permanent Path

A

A path is made permanent when they are 100% known to be the shortest route.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Flooding

A

Every incoming packet is sent out on every outgoing line besides the one it arrived on.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Problem with flooding

A

generates a lot of duplicate patterns and will become infinite without countermeasures

24
Q

Shortest Path first protocol uses

25
How to fix flooding
Add a hop count in packet header, decrement it at every hop and discard when = 0
26
If sender doesnt know path length
Initialize it to worst case
27
A better flooding technique
Flood Damming
28
Flood Damming
Having routes keep track of which packets have already been flooded. Can do this by putting a sequence of numbers on packet.
29
Flooding uses
ensures packets are delivered to every node, all messages transmitted can be received by other stations in range
30
Flooding Benefit
No other algorithm can produce shorter delay
31
Load balancer
Distributes incoming HTTP requests amongst servers in server farm to avoid overloading any one server
32
Load balancer in UNIX
Generates 3 load average numbers
33
System Load
Amount of computational work that a computer system performs.
34
Load Average
Represents average system load over a period of time
35
Idle computer load number
0. Each process using or waiting for CPU increases by 1
36
Load average in single CPU systems
percentage of system utilization
37
How to get percentage system utilization with multiple CPUs
Load average/No. of CPUS
38
Why do busy sites employ 2 web servers
Can switch between them if one gets swamped
39
Facebook load balancer computes
load and determines which cluster to point each ISP's user to. Handles traffic balancing and network optimization.
40
Components of Load balancer
DNS load balancer and Software load balancer
41
TinyDNS
by Bernstein Handles. Contains authorative nameserving. Only Clients are recursive nameserving - interpolates with relevant DNS standards.
42
Authorative Nameserving
via UDP, no recursive nameserving and does not respond to TCP
43
Facebook decision engine
Cartographer
44
Cartographer
Gathers info on topology, latency, bandwidth etc to determine best cluster point for each ISP. Pushes new DNS maps to server when cluster load is to be adapted to. Reacts to internal FB network problems and can deal with localized outages.
45
DNS Load Balancer consists of
central GLB decision engine, and open source C DNS server
46
Central GLB decision engine
making all traffic balancing decisions and generates DNS map.
47
Open Source C DNS Server
DNS traffic, directs users to clusters based on lookup table on DNS map.
48
Authorative DNS Service
Allows others to find your domain
49
Recursive DNS
allows you to resolve other people's domains
50
When choosing a load balancer keep in mind:
Sticky or Stateless, and Software or Hardware
51
Sticky
routes user back to same server during the life of a session
52
Stateless
routes to most available server, based on internal algorithms
53
Software Load Balancer
Like NLB, effective but not fine grained like hardware
54
Hardware Load Balancer
Offloads all processing off web servers but can be complex to configure and administer
55
Web accelerators
Can cache pages, static assets and do RR load balancing for backend
56
Factor for sites with growing traffic
availability of solution into hosting provider selection process.