Virtual routing platforms allow carriers to take advantage of virtualization benefits while supporting SDN and NFV initiatives. They aim to provide carrier-grade routing functions with performance comparable to physical routers, using the same management systems and consistent behaviors. Virtual platforms are well-suited for new applications where physical routers cannot meet needs, and allow flexible, on-demand scaling and lower costs than physical routers. Both physical and virtual platforms have strengths and can form blended networks, with services placed based on requirements. Virtual platforms open new approaches to network design and service delivery.

1. Physical or Virtual?
Carrier grade virtual routing platform use cases
Sheryl Zhang, Juniper Networks
March. 20, 2015

2. Motivations
• Classical carrier routing platforms get virtualized with motivations of:
• Taking advantage of the benefits from virtualization
• Sharing the vision and supporting the key industry initiatives of SDN & NFV

3. Expectations
Goals
Share vision of SDN/NFV
Support for traditional services
Co-exist and easy integration in a
hybrid network (physical & virtual)
Operational simplicity
Network stability
Highly available
Execution
Comply with the SDN/NFV solution and architecture specification;
Carrier grade routing functions & maximum performance possible
with x86 server;
Supported by existing EMS/NMS/OSS&BSS, protocol support &
interoperability across network elements (multi protocols, multi-
vendors)
Minimum change in functions and behaviour between physical &
virtual platform, to reduce optional overhead like training or
operation system adjustments
Leverage decade of network SW development experience, apply
mature network software and standardized protocols to ensure
Apply carrier grade routing SW and proven network HA practice,
plus resilience/availability defined in NFVI specification

4. Virtualized carrier grade routing platforms
• Carrier grade routing features:
• Sophisticated routing, IP/MPLS, service support
• Complete feature parity and function consistency
between physical and virtual platforms;
• Leverage the same EMS/NMS
• Scalability and performance:
• High throughput 100M~100Gbps, &beyond?
• High control plane plane scale & performance
• Mature software
• Minimize the change in network software
development to maximize the benefit of
leveraging decade of SW development experience

5. Virtual platform is a new tool to the providers
• Physical and virtual are two options to the providers
• Common way of thinking regarding use cases is to look at the existing functions in the
network and try to place the virtual in the role where the physical platform stands, but
wait..., is that all?
• Before we draw conclusion on where and how to use the tools, or even think of
replacing one with another, it is important to first have a close look at the tools’
characteristics & capabilities
Vs.

6. Characteristics of virtualized network platform
Enable control
plane scale
New scale
model - Scale
out
Low entry cost
to start a new
service
Consistent
functions as
physical device
Agile, fast to
deploy, click to
launch
Same VM
mgmt as SW in
cloud
Same service
mgmt as HW in
network
Cloud-centric,
lower TCO -
economies of
scale

7. Physical vs. Virtual
Physical Virtual
High throughput, high density Flexibility to reach higher scale in control plane and
service plane
Guarantee of SLA Agile, quick to start
Low power consumption per throughput Low power consumption per control plan and service
Scale up Scale out
Higher entry cost in $ and longer time to deploy Lower entry cost in $ and shorter time to deploy
Distributed or centralized model Optimal in centralized cloud-centric deployment
Well development network mgmt system, OSS/BSS Same platform mgmt as Physical, plus same VM
mgmt as a SW on server in the cloud
Variety of network interfaces for flexibility Cloud centric, Ethernet-only
Excellent price per throughput ratio Ability to apply “pay as you grow” model
Each option has its own strength, and it is
created with different focus

8. Type of deployments with virtual platform
Traditional
function, 1:1
form
replacement
New applications
where physical is
not feasible or ideal
A whole new
approach to
a traditional
concept
Cloud CPE
Cloud based VPN
Service
Chaining GW
Virtual Private Cloud GW
Multi-function, multi-layer integration
w/ routing as a plug-in
SDN GW
Route Reflector
Services appliances
Lab & POC
Branch Router
DC GW
CPE
PE
Wireless LAN GW
Mobile Sec GW
Mobile GW
Focus of this presentation

9. Expand service with Cloud based VPN service
SP Network for
VPN Services
L3 VPN
L3 CPE
L3 PEL3 PE
Distributed DC
Border Node
VIP customer,
1Gbps VPN
L3 CPE
Access Node
Border Node
DC GW
DC GW
L3 PE
L3 PE
PW
PW
Access Node
Cloud PE Cloud PE
Cloud PE
Cloud PE
VIP customer,
1Gbps VPN
Service touch
point
Service touch
point
Service
touch point
L3 CPE
Small enterprise,
10Mbps VPN
L3 CPE
Virtual Router
Physical router
Service orchestration
controllers (SDN & NFV)
Choice of service
placement point

10. Choice of Service
placement point
Expand service with Cloud based VPN service
SP Network for
VPN Services
L3 VPN
L3 CPE
L3 PEL3 PE
Distributed DC
Border Node
VIP customer,
1Gbps VPN
L3 CPE
Access Node
Border Node
DC GW
DC GW
L3 PE
L3 PE
PW
PW
Access Node
Cloud PE Cloud PE
Cloud PE
Cloud PE
VIP customer,
1Gbps VPN
Service touch
point
Service touch
point
Service
touch point
• Carrier grade VPN service on virtual &
physical
• Quick to start a value-added service, no
dedicated HW, one click to launch
• Shorten service qualification time w/
independence from established infra
• On-demand instant scale w/ scale out model
• Lower TCO with cloud centric approach
• Expect service w/ different
service SLA tier
• Increase service coverage to
large number of users
• Scale service without scarifying precious
resource (like VRF) on physical box
• No service touch point on HW PE which
carries important VPN customers
• Lower risk in error, improve SLAL3 CPE
Small enterprise,
10Mbps VPN
Small enterprise,
10Mbps VPN
L3 CPE
Service orchestration
controllers (SDN & NFV)
• Physical & virtual are equal
resource for service
• Service orchestration controllers
help service placement in the
network
Virtual Router
Physical router

11. Key take-away with Cloud based VPN service
SP Network for
VPN Services
L3 VPN
L3 CPE
L3 PEL3 PE
Distributed DC
Border Node
VIP customer,
1Gbps VPN
L3 CPE
Access Node
Border Node
DC GW
DC GW
L3 PE
L3 PE
Access Node
Cloud PE Cloud PE
Cloud PE
Cloud PE
VIP customer,
1Gbps VPN
Service touch
point
L3 CPE
Small enterprise,
10Mbps VPN
Small enterprise,
10Mbps VPN
L3 CPE
Service orchestration
controllers (SDN & NFV)
Virtual Router
Physical router
Choice of Service
placement point
• Virtual or Physical, you can have both, and two platforms can form a seamless
blend to provide the same service but for different purpose;
• You can get the best of two worlds by using them wisely based on the strength
of each platform;
• The placement of services can be directed by higher level service orchestration
controllers based on the service requirements; It can be an one-time initiation
or dynamically changed on-demand;
• Virtual platform is a new tool, allow us to think differently & build the
network differently to solve a technical or business issue in a whole new
approach

12. Virtual DC GW overlay for service scaling
Scale Service chaining with a DC GW overlay when VRF(s) are mapped to service chains
With a overlay model using virtual platform, along w/ cloud centric scale-out model, there is a new
way to scale the services
vGW vGW vGW
DC GW
Service-chain-X1
Service-chain-X2
Service-chain-X3
Service-chain-Y1
Service-chain-Y2
Service-chain-Y3
Service-chain-Z1
Service-chain-Z2
Service-chain-Z3
Service-chain-T1,… Tn
100GE
10GE 10GE 10GE
Virtual Router
Physical router
• Service chains are
mapped to VRF(s)
• Typically there is a limit
of the # of vrf per box
Overall service chain (VRFs)
are distributed across vGW
for large scale
Physical GW handles high
volume traffic to DC, along
with specific VRF traffic for SLA
or throughput reason;

13. Improve operational efficiency & accelerate
service delivery time
Proof of concept, lab validation & SW certification • 100% mirroring between physical &
virtual platform (control plane, data
plane, AND software releases)
• Ideal to support
• Proof of Concept lab
• New service configuration/operation
preparation
• SW release validation
• Training lab for operational team
• Troubleshoot environment
• Immediate benefit to current network
deployment, significantly shorten the
service delivery time
• CAPEX or OPEX reduction for lab
• Quick launch & scale
Virtual
Physical
deployment

14. Virtual Route Reflector
• vRR can be used as Route Reflector and deployed the same way as the physical RR in the network
• vRR can act as both vRR or any typical router function with forwarding capability
Client 1
Client 2
Client 3
Client n
Virtual RR on VMs
On standard servers
Virtual RR
Virtual Router
Physical router

15. More use cases? The limit is our imagination
• Virtual platform is one more tool for network provider, and the use cases
are up to users to define
VPC GW for private,
public and hybrid cloud
Virtual Route Reflector
NFV plug-in for multi-
function consolidation
SW certification, lab validation, network
planning & troubleshooting, proof of concept
Distributed NFV Service Complex
Virtual BNG cluster
Virtual Mobile service
control GW
And more…
Cloud based VPN
vGW for service chaining

16. Summary
• A carrier grade virtual routing platform allows the continuous support of revenue-
generating services and network innovations down the road through
• Comprehensive network functions, superior performance, consistent function & behaviour with
physical platform, plus mature software
• In terms of deployment cases, virtual or physical, we can have both; to get the best of
two worlds, we should use them wisely based on the strength of each platform;
• Virtual platform is a new tool, and it allows us to think differently & build the network
differently to address both technical issues & business demands;

17. Thank you