WP2'3 Advance Reservation Demonstration:

1
WP2.3 Advance Reservation DemonstrationDescripti
on and set-up

• DRAFT, v. 2.0
• DataTag Project, WP2.3

2
Outline

• Resource Managers
• Scenario 1 MPLS Manager
• Supported features
• Equipment
• Network set-up
• Traffic matrix
• Scenario 2 Light Path Manager combined with VLAN
  Manager (combined layer 1 and 2 demo)
• Network set-up

3
Resource Managers

• 1. Scenario 1 Light Path Manager combined with
  VLAN Manager
• AAA-based BoD (UvA)
• VLAN Manager
• Two administrative domains (simple inter-domain
  set-up)
• DataTag sites Starlight and UvA
• 2. Scenario 2 MPLS Manager
• Based on Diffserv services IP Premium, LBE and
  Best-effort
• DataTag sites Chicago, CERN, CNAF, (UCL,
  Karlsruhe?)
• Features
• extended VLAN/extended ethernet/extended VLAN
• COS support

4
MPLS Manager supported features

• Services
• Alternatives
• Layer 3 LSP router configuration
• Extended ethernet (Ethernet ccc) router and
  end-node configuration
• Extended VLAN ( LAN ccc) router, (switch) and
  end-node configuration
• Switch VLANs can be manually pre-configured or
  dynamically set-up on the intermediate layer 2
  switches
• Cabletron switch, the availability of suitable
  devices has to be verified at CERN and CNAF
• Two managers have to be activated in parallel, an
  agreement on the VLAN ID is needed (who does
  specify the ID?)
• Host interfaces manually configured

5
MPLS Manager supported features (cont)

• QoS support to the MPLS traffic of a given LSP
  (the exp field in the label of the ingress MPLS
  packets is set by the LSP head-end router)
• Marking the router enables packet marking and
  policing on the interface of the ingress router
  to which the source host is connected (input
  direction).
• Scheduling
• Manual configuration (diffserv path)
• Enabled on the output interfaces of the ingress
  routers, on the interfaces connecting the CEs of
  the source domain to the transit network domains
  and on each internal router interface which is
  subject to either short or long term congestion
• Service needed in the GEANT network
• IP Premium
• LBE
• End-to-end LSP set-up (no LSP stitching)

6
MPLS Manager supported features (cont)

• LSPs
• Unidirectional easy, it requires access to the
  local CE router
• Bidirectional
• simpler if both managers belong to the same
  domain (a single MPLS Manager can configure both
  the head and tail-end router)
• complex when the head and tail-end belong to
  different domains (this is the most common
  scenario)
• AAA inter-domain support
• two different MPLS Managers have to be triggered
• Pre-requisite the existence of the two static
  MPLS-capable diffserv paths (source domain -gt
  destination domain, destination domain -gt source
  domain) - from Topology DB or information system
• the requestor is authorized to use both
• the availability of bandwidth on both directions
  in the same time interval

7
MPLS Manager supported features (cont)

• The MPLS Manager prototype will work with Juniper
  devices (Cisco GSR supported in a second phase
  depending on time)
• User interfaces
• AAA Server
• EDG User Interface (interoperability)
• Applications
• Grid Ftp or other real-life application (for the
  exchange of traffic on the extended LAN ), TCP
• Traffic generator (iperf) for background traffic
  UDP
• Single domain 1 MPLS Manager at CERN controlling
  the M10 at CNAF and the M10 at CERN

8
MPLS Manager Equipment

• Equipment
• LSP end-points Juniper M10 CERN, Juniper M10
  CNAF (UCL GSR?, Cisco GSR Karlsruhe)
• Workstations 1 ws in Chicago, 2 ws at CERN, 2 ws
  at CNAF
• Storage systems at CERN and CNAF (?)
• CERN
• three Dual Xeon 3Ghz servers.Two have 4GB of
  RAM, one has 2GBEach server has around 14 x
  120GB disks sitting on  2 3ware controllers.Each
  has 2x1Gbps copper, 1x1Gbps MMF interfacesTwo of
  them have 10Gbps interface
• CNAF ? To be defined next week

9
Network set-up

• Three LSPs
• (Existing) Chicago CERN between the T320s, VLAN
  570 (static), best-effort
• CERN CNAF between the two M10s, VLAN 570
  (dynamic), IP Premium
• Three sites connected to same VLAN 570 (Chicago,
  CERN and CNAF)
• It could be extended to Karlsruhe
• CERN CNAF between the two M10s, VLAN ID to
  define, LBE

10
Network set-up (cont)
Storage
MPLS MgrAAAServerGARA
UCL?
WS
JANET
Marking/Policing and LSP set-up
LSP static, VLAN 570
C 7600
M 10
T 320
T 320
M 10
WS
GEANT
G-WIN
GARR

M 10
Karlsruhe?
LSP set-up
LSP static,VLAN 570, BE
Storage
LSP dynamic,VLAN 570, IPP
3com
WS
LSP dynamic,VLAN X, LBE
WS
11
MPLS Manager Traffic matrix
Storage
MPLS MgrAAAServerGARA
WS
LSP static, VLAN 570
C 7600
M 10
T 320
T 320
M 10
WS
GEANT
M 10
GARR
Storage
3com
WS
WS
12
Light Path Manager combined with VLAN Manager

• Equipment
• n. 2 Calient Photonic Cross Connect (Amsterdam
  and Starlight) control via TL-1
• n. 2 Cabletron SS6000 (Amsterdam) control via
  SNMP
• n. ? Workstations
• N. ? AAA Servers located at ?
• Two domains
• User applications

13
Light Path Manager Network set-up
Gogh
Pre-provisioned
?
454
454
?
calient
?1
?2
CernLight
NetherLight
14
Light Path Manager Alternative network set-up

• Combined layer 1 and layer 2 scenario

Calient
Cabletron
Cabletron