Automatic Cut-Through Paths System and Network Engineering Research - - PowerPoint PPT Presentation

automatic cut through paths
SMART_READER_LITE
LIVE PREVIEW

Automatic Cut-Through Paths System and Network Engineering Research - - PowerPoint PPT Presentation

Automatic Cut-Through Paths System and Network Engineering Research Project 2 Class 2005 - 2006 Lourens Bordewijk Ren Jorissen Agenda AMS-IX network Problem definition Cut-through path RBridges Additional solution


slide-1
SLIDE 1

Automatic Cut-Through Paths

System and Network Engineering Research Project 2 Class 2005 - 2006 Lourens Bordewijk René Jorissen

slide-2
SLIDE 2

Agenda

  • AMS-IX network
  • Problem definition
  • Cut-through path
  • RBridges
  • Additional solution
  • Conclusion
slide-3
SLIDE 3

AMS-IX network (1)

SARA

psw-sar-01 Customer <= 1 GE

NIKHEF

psw-nik-02 Customer <= 1 GE

Telecity

psw-tel-02 Customer <= 1 GE

Global Switch

Customer <= 1 GE psw-nik-02

stub-sar-02 MG8 stub-nik-05 RX16 stub-nik-06 RX16 stub-tel-03 MG8 stub-sar-01 MG8 stub-tel-02 MG8

edge BI15K edge BI15K edge BI15K edge BI15K edge BI15K edge BI15K edge BI15K

stub-glo-02 RX8 stub-glo-01 RX8 core-nik-04 RX16 core-tel-03 RX16

psw-nik-03 psw-sar-02 psw-tel-03

slide-4
SLIDE 4

AMS-IX network (2)

  • VLANs
  • Internet, multicast...
  • Quarantine
  • Virtual Switch Redundancy Protocol
  • Foundry Networks proprietary
slide-5
SLIDE 5

AMS-IX network (3)

  • Customer statistics
  • Number of customers: 240
  • Number of routers: 390
  • Traffic statistics
  • Average load: 90 Gb/s
  • Peak load: 150 Gb/s
slide-6
SLIDE 6

Problem definition (1)

  • Cut-through switching
  • Layer two network
  • Loops
  • Broadcast
  • Spanning tree
slide-7
SLIDE 7

Problem definition (2)

  • Management
  • Thresholds
  • Sampling
  • Computation
  • Configuration
slide-8
SLIDE 8

Cut-through path (1)

  • Why
  • Lessen load on core switches
  • Lessen traffic congestion
  • Involves less jitter
  • More bandwidth capacity
  • More efficient traffic streams
slide-9
SLIDE 9

Cut-through path (2)

  • How
  • Sampling process
  • Filtering process
  • Trigger
  • Control server architecture
slide-10
SLIDE 10

sFlow (1)

  • What
  • Packet-based sampling technology
  • From layers two till seven
  • Provide information about switch ports, MAC addresses,

VLANs, IP addresses and ICMP/TCP/UDP/AS-based information

slide-11
SLIDE 11

sFlow (2)

  • Why
  • Supported by the Foundry switches
  • Inspecting all packets costs extensive CPU power
  • Can handle volume of high speed backbone links
  • Provides a result with

quantifiable accuracy

slide-12
SLIDE 12

Resource information

  • SNMP
  • Data transfer
  • CPU utilization, memory utilization
  • CAM statistics and process utilization
  • Logging
slide-13
SLIDE 13

Sampling process

  • When
  • A load of more than 90% for 30 minutes on a certain switch

port

  • A constant data flow of more than 4 Gb/s for 30 minutes on a

certain switch port

  • Determine the exact values after further research
slide-14
SLIDE 14

Filtering process (1)

  • How
  • Starts when first sFlow data from a switch is collected

SSwitch DSwitch VLAN SPort DPort SMAC DMAC Count Priority STime TTL

slide-15
SLIDE 15

Filtering process (2)

  • Sort flows based on priority and packet count
  • Per DSwitch, than per SPort & SSwitch and than per VLAN
  • “Priority & packet count” must reach threshold before the TTL

ends, (decisions taken after TTL period)

slide-16
SLIDE 16

Filtering process (3)

  • Combine the total flows per SPorts from the SSwitch
  • Calculate average
slide-17
SLIDE 17

Filtering process (4)

  • Example:

TTL

slide-18
SLIDE 18

Bandwidth prediction

  • Traffic cycle
  • Several algorithms for bandwidth prediction
  • Forecast traffic flows with long lifetime
  • Use for setting priority
slide-19
SLIDE 19

Cut-through creation (1)

  • How (1)
  • Huge amount of traffic is flowing between two customers
  • Flow triggers cut-through path creation
  • Create a new VLAN
  • Photonic switch connects two edges
slide-20
SLIDE 20

Cut-through creation (2)

  • How (2)
  • Create MAC filter based on destination MAC addresses
  • Configure an egress filter on switch port
  • Encapsulate Internet VLAN tagged frames with the new

VLAN tag

  • 802.1ad (Provider Bridges)
slide-21
SLIDE 21

Cut-through creation (3)

  • How (3)
slide-22
SLIDE 22

Control server architecture (1)

  • Why
  • To collect data
  • Consider the priorities
  • Makes calculations
  • Automatically configures a dynamic cut-through path
  • To manage all resources
slide-23
SLIDE 23

Control server architecture (2)

  • How
  • Separate networks, one private
  • Control process must be physically separated from the filtering

process

  • Validate all configuration steps (roll back)
  • Control server should be redundantly for failover in the event of

a system failure

slide-24
SLIDE 24

Control server architecture (3)

slide-25
SLIDE 25

RBridges (1)

  • Transparent Interconnection of Lots of Links (TRILL)
  • Problems
  • Inefficient paths
  • Convergence
  • Backup paths
  • Ethernet extensions
  • Required properties
  • Services
  • Loop mitigation
  • VLAN
  • Security
slide-26
SLIDE 26

RBridges (2)

  • Advantages of routers and bridges
  • “Routing” on layer two
  • Full mesh possible
  • Ethernet frame encapsulation
  • Hardware or firmware
  • Approximately 2 years
slide-27
SLIDE 27

RBridges (3)

  • General operations
  • Peer and topology discovery
  • Designated RBridge election
  • Ingress RBridge Tree computation
  • Link-state routing
  • Advertisements
slide-28
SLIDE 28

RBridges (4)

  • Ingress / Egress RBridge
  • Encapsulation
  • Decapsulation
slide-29
SLIDE 29

RBridges (5)

  • Hop-by-hop vs. edge-by-edge
  • Different headers
  • Forwarding
  • Unicast
  • Broadcast
  • Multicast

R1 R2 R3

slide-30
SLIDE 30

Additional solution (1)

  • Two uplinks
  • Secondary path
  • Adding customer routing tables
slide-31
SLIDE 31

Additional solution (2)

slide-32
SLIDE 32

Conclusion (1)

  • Capacity problem (approx. in 1,5 year), best solution?
  • 100 Gb/s capable switch ports
  • RBridges
  • Full mesh layer two topology
  • Uses all paths efficiently
  • No STP and VSRP needed
  • 1 to 2 years
slide-33
SLIDE 33

Conclusion (2)

  • Interim solution could be the use of VLANs
  • Automatically configured cut-through VLANs, when specific

traffic flow reaches threshold

  • Control architecture takes care of the sampling, filtering,

computation and triggering process

slide-34
SLIDE 34

Future

  • Further research to determine thresholds
  • Development software
  • Build test environment
  • Other technologies
  • GMPLS
  • Looks like a solution
  • No hardware support
slide-35
SLIDE 35

Questions

Thanks for the attention