VLAN. MPLS. Path for L3/L2 services data. Ether. VLAN data IP. Ether. VLAN. Hitless bandwidth change by LCAS. Flow Control. (IEEE802.3x). 10GE. Layer-1.
BoD 2010 Osaka, April 23th, 2010
Expansion of Bandwidth-on-Demand Capabilities in Japanese Academic Backbone Network Shigeo Urushidani, Michihiro Aoki, Motonori Nakamura, Michihiro Koibuchi, Kensuke Fukuda, Yusheng Ji, Shunji Abe, and Shigeki Yamada
National Institute of Informatics (NII)
1
Outline 1. Layer-1 bandwidth-on-demand (BoD) service in SINET3 2. Resource managements for Layer-1 BoD services 3. Demand for BoD services 4. Service parameters of Layer-2 BoD services 5. Initial implementation image of Layer-2 BoD services 6. Conclusion 2
Outline 1. Layer-1 bandwidth-on-demand (BoD) service in SINET3 2. Resource managements for Layer-1 BoD services 3. Demand for BoD services 4. Service parameters of Layer-2 BoD services 5. Initial implementation image of Layer-2 BoD services 6. Conclusion 3
SINET3: Science Information Network 3 SINET3 is the Japanese academic backbone network launched in April 2007 for more than 700 universities and research institutions. It has 63 edge and 12 core nodes and deploys Japan’s first 40 Gbps lines between Tokyo, Nagoya, and Osaka. It has two 10 Gbps international lines to the U.S.A. and two other lines to Asia.
Los Angeles New York
Nagoya Osaka Tokyo
: 40 Gbps : 10 to 20 Gbps : 1 to 20 Gbps : Core Node : Edge Node
Japan’s first 40 Gbps (STM256) lines 4
Service Features in SINET3
High Priority Best Effort
QoS
QoS-guaranteed
SINET3 emphasizes four service aspects: transfer layer, virtual private network (VPN), quality-of-service (QoS), and bandwidth on demand (BoD). L1 BoD L1VPN
L3VPN (QoS)
VPLS (QoS) L2VPN (QoS)
Multicast (QoS)
VPN
Application-based QoS
L3VPN
VPLS L2VPN
Multicast IPv4/IPv6 dual stack IP (L3)
Ethernet (L2)
Transfer Layer
Dedicated (L1) 5
Virtual Service Networks in SINET3 Each service is provided on the corresponding virtual service network on a single network platform. Each virtual service network uses its own routing and signaling protocols and has its own high-availability functions.
SINET3 Virtual Service Network 1 (IPv4/IPv6 dual stack) VPN 2-1
VPN 3-1
VPN 4-1
VPN 5-1
Virtual Service Network 2 (L3VPN) Virtual Service Network 3 (L2VPN) Virtual Service Network 4 (VPLS) Virtual Service Network 5 (L1VPN/ L1 BoD)
VPN 2-2
Since Apr. 2007
VPN 3-2
VPN 4-2
VPN 5-2
Since Dec. 2007
Since Feb. 2008
6
Network Structure of SINET3 Layer-1 BoD Server
Layer-2 BoD Server
User Side L1-OPS
Control and management plane
data
IP Ether
IPv4/IPv6
L3
data
data
IP Router IP VLAN Ether
data
data
data
VPLS
IP VLAN Ether
data
IP
data
IP MPLS
data
VLAN Ether MPLS
data
VLAN Ether MPLS
L3VPN
Ether data
L2VPN
: Virtual Router
IPv4/IPv6
IP Ether
L3VPN
L2
L2 MUX
VLAN Ether
Ether data
VLAN Ether
Hitless bandwidth change by LCAS
L2VPN VPLS 10GE
L1
L1 BoD
Path for L3/2
Path for L3/L2 services
L1VPN
Edge L1Switch Edge node
STM64/ STM16
Flow Control (IEEE802.3x)
Core L1Switch Core node
STM256/ STM64
Bandwidth on Demand (BoD) Service SINET3 provides bandwidth-on-demand (BoD) service as part of layer-1 services. Users can specify the destinations, duration, bandwidth with granularity of 150Mbps (VC-4), and route option, via simple Web pages. BoD server receives path setup requests from users and triggers layer-1 path setup. Hokkaido Web-based Interface (Destination, Duration, Bandwidth, & Route option)
User 1 Gbps (13:00-14:00)
Fukuoka
Layer-1 BoD Server Layer-1 path setup trigger
Osaka
On-demand layer-1 path
Tokyo
SINET3 8
Core network topology and initial BoD users The BoD server finds an appropriate route from among several candidate routes. The BoD server usually gets the end-to-end path bandwidth from parallel and multiple routes for effective resource utilization by using virtual concatenation (VCAT) functions. Kyushu Univ.
Fukuoka
Yamaguchi Univ.
Hiroshima
Doshisha Univ.
Hokkaido Univ.
Kyoto
Kanazawa
Sapporo
: IP Router : L2 MUX
Tokyo2
: L1 Swictch
Matsuyama
Osaka
Osaka Univ.
Nagoya
NIFS
Tokyo1
NAOJ
NII
Tsukuba
KEK
Sendai
9
Outline 1. Layer-1 bandwidth-on-demand (BoD) service in SINET3 2. Resource managements for Layer-1 BoD services 3. Demand for BoD services 4. Service parameters of Layer-2 BoD services 5. Initial implementation image of Layer-2 BoD services 6. Conclusion 10
Resource managements for Layer-1 BoD services The layer-2/3 traffic on each link has a very analogous daily pattern. The available bandwidth is set at a larger value at night and weekends. The default and assigned bandwidths are preset at the requisite min bandwidth. Exceeds its default value: the BoD server sets the assigned bandwidth to the max requested bandwidth. The LCAS functions are activated at the start and finishing times.
Link bandwidth
: Default bandwidth for L1 : Available bandwidth for L1 : Assigned bandwidth for L1
: Requested bandwidth for L1 : LCAS activation
L1
L2/3
Layer-2/3 traffic Mon Tue Wed 22:00 8:00
Thu
Fri
Sat
Sun 11
Screen examples for bandwidth management for layer-2/3 services Set the default and available values on a simple Web screen: taking into account the traffic volume trend of the layer-2/3 services Set the default/available value for layer-2/3 services: [the link bandwidth] – [the default/available value for layer-1 services] (Link bandwidth - Default bandwidth) Link
(Link bandwidth - Available bandwidth)
Weekday Weekend
Holiday
Event day
12
Outline 1. Layer-1 bandwidth-on-demand (BoD) service in SINET3 2. Resource managements for Layer-1 BoD services 3. Demand for BoD services 4. Service parameters of Layer-2 BoD services 5. Initial implementation image of Layer-2 BoD services 6. Conclusion 13
Demand for BoD services The layer-1 BoD services: • The layer-1 resource assignment is a nice approach for accommodating data-intensive applications • a little over-engineered for another users • wait for the path establishment for an order of minutes • Prepare physically separate ports for the services
Layer-2 BoD services: • a fine bandwidth granularity • set up a high-quality path in less time • use the services over the in-use ports as well as unused ports • in-use ports by using tagged VLAN and QoS control capabilities
14
Outline 1. Layer-1 bandwidth-on-demand (BoD) service in SINET3 2. Resource managements for Layer-1 BoD services 3. Demand for BoD services 4. Service parameters of Layer-2 BoD services 5. Initial implementation image of Layer-2 BoD services 6. Conclusion 15
Service parameters of Layer-2 BoD services Simple Web screens for the reservations similar to those of the L1 BoD services. Input the connection style, the source and destination nodes, and the duration Push the “next” key.
Web Screen Image (1) Connection style
VPN
Extranet
SRC/DST Node
SRC Node
Start time
----Y ----M ----D ----H ----M
Finish time
----Y ----M ----D ----H ----M
DST Node
Next
16
Service parameters of Layer-2 BoD services Indicate the available bandwidth and the rough delay between the specified nodes. Select the source/destination ports, the VLAN type from “port” and “tagged” along with a user VLAN ID Input the required bandwidth. up to 150 Mbps (tentative value) with a granularity of 1 Mbps.
Web Screen Image (2) Available bandwidth and rough delay between specified nodes during duration are as follows. Available bandwidth: -- Gbps SRC/DST Port1 VLAN1
SRC Port Port
delay: -- msec DST Port
Tagged
VLAN ID
Mbps
Bandwidth Route
Minimum delay (default)
Additional Port
Yes/No
SRC/DST Port2
SRC Port
VLAN2 Bandwidth Route
Port
DST Port Tagged
VLAN ID
Mbps Minimum delay (default) Reserve Request
17
Outline 1. Layer-1 bandwidth-on-demand (BoD) service in SINET3 2. Resource managements for Layer-1 BoD services 3. Demand for BoD services 4. Service parameters of Layer-2 BoD services 5. Initial implementation image of Layer-2 BoD services 6. Conclusion 18
Initial implementation image of Layer-2 BoD services Layer-2 BoD services rely on a layer-2 BoD server: (1)receives the user requests, (2)manages the network resources, (3)orders layer-2 multiplexers and IP routers to setup/release end-to-end layer-2 paths Add one more virtual router in each IP router in order to avoid any influence being put on the existing services.
(1)
Layer-2 BoD Server
(2)
Control and management plane
data
VLAN Ether user user
NETCONF
NETCONF
(3)
(3) data
User
VLAN Ether user user
User
Source L2 MUX
Ingress IP Router
egress IP Router
Destination L2 MUX
: L2 on-demand path : Virtual Router for L2 BoD
: Primary MPLS path : Secondary MPLS path
19
Initial implementation image of Layer-2 BoD services Simply sets up a VLAN circuit: • an internal VLAN tag between a layer-2 multiplexer and the virtual router • the VLAN circuit over a MPLS path between the virtual routers Primary MPLS paths: on the minimum delay routes between all of the virtual routers for quality reasons. Secondary MPLS paths: on the disjoint routes for reliability reasons. Layer-2 BoD Server Control and management plane NETCONF data
VLAN Ether user user
data
NETCONF
VLAN Ether (NW) user
data
VLAN Ether MPLS MPLS VLAN Ether (NW) user (VC) (NW) VR NW
data
VLAN Ether (NW) user
data
User
VLAN Ether user user
User
Source L2 MUX
Ingress IP Router
egress IP Router
Destination L2 MUX
: L2 on-demand path : Virtual Router for L2 BoD
: Primary MPLS path : Secondary MPLS path
20
Initial implementation image of Layer-2 BoD services Mark the user priority bits of the internal VLAN tag with an EF class (or AF class) value at the source layer-2 multiplexer Copy to the EXP bits of the MPLS labels in the ingress IP router Copy to the user priority bits of the internal VLAN tag in the egress IP router QoS control is performed at each device by using the user priority bits of the internal VLAN tag and the EXP bits of the MPLS labels. Layer-2 BoD Server Control and management plane NETCONF data
VLAN Ether user user
data
NETCONF
VLAN Ether (NW) user
data
: QoS Identifier
VLAN Ether MPLS MPLS VLAN Ether (NW) user (VC) (NW) VR NW
data
VLAN Ether (NW) user
data
User
VLAN Ether user user
User
Source L2 MUX
Ingress IP Router
egress IP Router
Destination L2 MUX
: L2 on-demand path : Virtual Router for L2 BoD
: Primary MPLS path : Secondary MPLS path
21
Initial implementation image of Layer-2 BoD services The network configuration protocol : NETCONF: candidate control protocol ( L2 BoD server ,layer-2 multiplexers and IP routers to set up/release VLAN circuits) The network resource management for L2 BoD services: similar to that of L1 BoD services. Database of the L2 BoD server: • the available bandwidths for L2 BoD services • the delay values on a link-by-link basis Calculate the end-to-end available bandwidth along with the total delay between the specified sites in response to a user request Reflect the resource reservation results and performs admission control for user requests.
22
Outline 1. Layer-1 bandwidth-on-demand (BoD) service in SINET3 2. Resource managements for Layer-1 BoD services 3. Demand for BoD services 4. Service parameters of Layer-2 BoD services 5. Initial implementation image of Layer-2 BoD services 6. Conclusion 23
Conclusion The current status for the BoD capabilities in SINET3. • The layer-1 BoD services have been used as full-scale services. • The network resources have been flexibly assigned depending on the user requests and traffic volume of the layer-2/3 services. The near-future plan for the BoD capabilities. • Approaching layer-2 BoD services for small amounts of bandwidth. • Presented the initial implementation image. • After confirming the stability of the control protocols, we will launch a trial service in our network.
24
Thank you for your attentions !
25
