1. End-host Initiated GMPLS Signaling Demo
Xiangfei Zhu

2. Dynamic circuit setup and release demonstration
Developed a software program called circuit-requestor for CHEETAH end hosts
Usage:
User logins to a CHEETAH end host
Requests the setup of a dedicated 1Gb/s Ethernet-SONET-Ethernet circuit to another CHEETAH end host
Runs application, such as file transfer
Uses circuit-requestor program to release circuit

3. CHEETAH end-host software – includes circuit-requestor + daemons
DNS
server
End host
DNS lookup
Circuit-requestor
Application
OCS client
socket
CHEETAH Daemon (CD)
CD API
RSVPD API
socket
C-TCP API
RSVP-TE
messages
RSVP-TE Daemon
(RSVPD)
User space
Kernel space
C-TCP
Steps:
DNS lookup (to support our scalability goal)
Circuit setup signaling procedure (RSVP-TE)

4. Demo configuration H UVa CUNY NCSU ORNL PoP Raleigh PoP Atlanta PoP
NYC
HOPI
Force10
CUNY
Foundry
UVa
UVa
Catalyst
4948
Mvstu H 1G
WASH
HOPI
Force10 1G 1G H H
cuny-h1
cuny-h2
NCSU
NCSU
M20
2x1G
MPLS tunnels
CUNY
WASH
Abilene
T640
Orbitty Cluster
Centuar
FastIron
FESX448
ORNL PoP H
Force10
E300
switch 1G
1GFC
Wukong H
UCNS
X1(E) 1G
3x1G VLAN
OC192
OC192
GbE 1G 1G 1G
GbE
10GbE
OC192
1-8-33
MCNC
Catalyst
6500 1G
1-7-33
1-8-34
1-6-1
1-7-1
Zelda 1G
1-8-35 1G H
1-7-34 1G 1G
Zelda H
1-7-35
1-8-36
1-7-1
1-8-1
1-7-36
1-6-17
1-7-17
1-8-37 1G 1G
1-8-38 1G
Cheetah-ornl
1-8-39 H
Wuneng
Juniper
T320
OC-192 lamda
cheetah-nc
Raleigh PoP
Atlanta PoP
OC-192 lamda 1G
GbE
10GbE
OC192
Zelda H
Zelda 1G
1-7-33 H 1G
1-7-34
Zelda H
1-7-35
1-6-1
2x1G
MPLS tunnels
Juniper
T320 1G
1-7-36
1-7-1
Direct fibers
1-7-37 1G
1-7-38
1-6-17
VLANs
1-7-39
Cheetah-atl
MPLS tunnels

5. Circuit-requestor usage
To setup a new circuit: circuit-requestor setup domain-name-of-called-host bandwidth [holding-time]
Default holding-time: 10 mins
Max holding time: 1 hour
Limit call holding time for fair bandwidth sharing
To renew an existing circuit: circuit-requestor renew session-id [new-holding-time]
Release unused circuits if there is no renewal
To release an existing circuit: circuit-requestor release session-id
To check the status of the CHEETAH trunk: circuit-requestor status

6. Measurements
Signaling delays incurred in setting up a circuit between zelda1 and wuneng across the CHEETAH network.
Circuit type
End-tend circuit setup delay (s)
Processing delay for Path message(s) at sn16k-nc
Processing delay for Resv message(s) at the sn16k-nc
OC-1
OC-3
1Gb/s EoS
Round-trip signaling message propagation plus emission delay between sn16k-atl and sn16k-nc: 0.025s

7. Why the initial DNS lookup?
Verify called end host is on CHEETAH network and to obtain MAC address of the second (CHEETAH) NIC
Why is MAC address necessary?
Need to program ARP table to avoid wide-area ARP lookups

8. IP and MAC addressing issues
Our completed Control-Plane Network Design document describes
Why we chose static public IP addresses for the second (CHEETAH) NICs at end hosts
Choose addresses based on CHEETAH host’s location – i.e., allocate address from enterprise’s public IP address space allocation (e.g., UVA hosts: x.x)
Reason: Scalability
Impact:
After dedicated circuit is setup:
far end NIC has IP address from a different subnet
Default setting of IP routing table entries will indicate that such an address is only reachable through the default gateway

9. Our solution: automatically update IP routing and ARP tables
Update IP routing and ARP tables at both end hosts as last step of circuit setup
Analogous to switch fabric configuration
Routing table update
Add an entry indicating the remote host is directly reachable through the second (CHEETAH) NIC
ARP table update
Add an entry for the MAC address of the remote CHEETAH NIC

10. Addressing in the CHEETAH network
Whether private and/or dynamic IP addresses can be assigned to the data-plane and control-plane interfaces in GMPLS networks?
Data-plane Addresses
Static
Need to be “called” by other clients
Public
Globally unique
Scalable to multiple autonomous-systems
Private IP addresses sufficient if goal for CHEETAH is to create a small eScience network
Control-plane Addresses
Configured in Traffic-Engineered (TE) link
Same scalability reason