Software Defined Networking (SDN)
Software Defined Data Center (SDDC)
An Overview & Avaya’s Strategy
Ed Koehler – Director – Distinguished Systems Engineer
Gary Cattarin – Consulting Systems Engineer
IAUG Newport Rhode Island – November 2013
Certain statements contained in this presentation are forward-looking statements. These
statements may be identified by the use of forward-looking terminology such as "anticipate,"
"believe," "continue," "could," "estimate," "expect," "intend," "may," "might," "plan," "potential,"
"predict," "should" or "will" or other similar terminology. We have based these forward-looking
statements on our current expectations, assumptions, estimates and projections. While we believe
these expectations, assumptions, estimates and projections are reasonable, such forward looking
statements are only predictions and involve known and unknown risks and uncertainties, many of
which are beyond our control. These and other important factors may cause our actual results,
performance or achievements to differ materially from any future results, performance or
achievements expressed or implied by these forward-looking statements. For a list and description
of such risks and uncertainties, please refer to Avaya's filings with the SEC that are available at
www.sec.gov/. Avaya disclaims any intention or obligation to update or revise any forward-looking
statements, whether as a result of new information, future events or otherwise.
© 2013 Avaya Inc. All rights reserved.
2
2
Before Arrival at the Theatre
Precedes Even “Setting the Stage”
 Confusion reigns on SDN and SDCC – What are they?
 Our intent today
– Define the terms, including bits like OpenFlow
– What is the relevance? Initiatives? Motivations?
– What’s the Open Networking Foundation?
– What is the market up to?
– What is Avaya up to?
– Application-Driven Networking Framework
– Leveraging and expanding on SDN & SDCC
– Enhancing the quality of experience for a flexible workforce
© 2013 Avaya Inc. All rights reserved.
3
Software-Defined Networking
Setting the Stage
© 2013 Avaya Inc. All rights reserved.
4
Software-Defined Networking
Where has it come from and who’s driving it
 Perception that “today’s”
networks are sub-optimal
 Desire to:
SDN Early Adopters
– Abstract and Orchestrate
– Centralize
– “Simplify”
– Commoditize
 Open Networking Foundation
© 2013 Avaya Inc. All rights reserved.
5
Challenges that SDN is meant to address
 Network Complexity
 Reduced Time-to-Service; Agility and Simplicity
 Changes in Applications Architecture
 Virtual Machine Mobility
 Multi-Touch Configuration (e.g. VM Activation)
 Scale-Out Connectivity
 Multi-Tenant
 Multi-Vendor Technologies
 Vendor Dependence
 Policy and Quality
© 2013 Avaya Inc. All rights reserved.
6
Technology In Evolution
Software-Defined Networking is work-in-progress…
Fabrics
Fabric
Connect
SDN
TRILL????
ATM to the Desktop
© 2013 Avaya Inc. All rights reserved.
‘Hype Cycle’ is a term coined by Gartner.
7
The current SDN landscape
Fabric
Open Daylight
© 2013 Avaya Inc. All rights reserved.
Openflow
Network Virtualization
Overlays
SDN
OpenStack
8
What is OpenFlow?
 A technology that allows a centralized controller to
tell network switches where to send traffic
– Network programmed independently of individual switches
– Remove brains to external server; dumb fast switches
– Less reliance on vendors, customers can customize network
 Good idea? New idea? Maybe?
– Remember ATM LANE? Centralized wireless controllers?
– Co-inventor Martin Casado publicly stated it makes sense in
certain use cases, not others
 SDN definition has sometimes shifted to that of OpenFlow
– Separation of control and forwarding
– Software control over hardware
– OpenFlow is but one way to implement SDN; there are others
© 2013 Avaya Inc. All rights reserved.
9
What is OpenStack?
 Think OpenFlow kicked up a level
– Orchestrates more than just the network
 Enables centralized control of resources (compute,
storage, and networking) with a single graphical
interface
 Offers consistent operations in a multi-vendor Data
Center environment (multiple hypervisors, storage
array’s etc)
 We’ll revisit in more depth
© 2013 Avaya Inc. All rights reserved.
10
Background Summary
Software-Defined Networking Takeaways
1. SDN is still an emerging concept
2. SDN does not equal OpenFlow
3. There are many directions that SDN can still go in
© 2013 Avaya Inc. All rights reserved.
11
Software-Defined Networking
Avaya’s Direction
© 2013 Avaya Inc. All rights reserved.
12
Avaya’s SDN Goal
Software-Defined Networking
Enable simple and agile automated service
delivery for applications and users across any
combination of physical and virtual components.
Step 1 – SIMPLIFY THE NETWORK!!!!!
© 2013 Avaya Inc. All rights reserved.
13
Avaya’s SDN Strategy
1. Leverage OpenStack to enable rapid service creation via a
common orchestration interface
2. Deploy Fabric Connect (an enhanced implementation of Shortest
Path Bridging) to link virtual/physical infrastructure and enable
flexible network services at any scale
3. Provide public access (APIs) into an orchestration interface
allowing customized interaction with Fabric Connect
4. Extend orchestration and Fabric Connect to deliver end-to-end
service creation and delivery
5. Incorporate additional tools that automate service creation and
delivery through interaction with the application layer
© 2013 Avaya Inc. All rights reserved.
14
CHANGING THE LANDSCAPE
© 2013 Avaya Inc. All rights reserved.
15
Network as a Service (NaaS)
© 2013 Avaya Inc. All rights reserved.
16
Insight
For what’s it’s worth, you can think of multicast
routing as the first Software Defined Network.
A receiver wants to join a multicast stream, so the
network hears the request and makes the
necessary changes to accommodate this request.
The application is dictating network behavior!
- a certain Distinguished Avaya Engineer
© 2013 Avaya Inc. All rights reserved.
17
1
9
2
8
7
What
if you
could…
6 5
© 2013 Avaya Inc. All rights reserved.
3
4
1. Deploy
Spanning Tree
Free Network
2. Reduce by 3x
times or more
latency in the
data center
4. Simplify and
scale your
multicast – PIM
FREE
5. Enable Secure
Guest, BYOD
Access control
all at once
3. Increase &
monitor real-time 6. Deliver 50ms
Network quality
network-wide
recovery times
7. Offer
multitenant
services
8. Eliminate
maintenance
windows
9. Eliminate
human errors
in the network
core
18
Avaya Fabric Connect
 Multiservice without multiple protocols: replace 6 protocols with 1
 Extends across distances: no complex protocol stitching
 Sub-second recovery for all services including Multicast: eliminates protocol overlays
 Cost-effective for companies of any size: extends to small Core and remote Branches
 Topology agnostic: works with star, ring, tree, etc…
 Based on open standards: IEEE 802.1aq / IETF RFC 6329
L3 Virtualization
Large flooding domain
Single logical switch
VLAN based virtualization
150m distance limitation
(beyond needs MPLS)
VPLS
L2 Virtualization
L2 Multi-Pathing
L2 Loop-Free Topology
© 2013 Avaya Inc. All rights reserved.
STP
Juniper
QFabric
OTV
Brocade
VCS
L3 Virtualization
Cisco
FabricPath
VLAN-based virtualization
IETF TRILL
IP and IP Multicast Shortcuts
Protocol stitching for
extension across distances
MPLS
Root bridge dependent
Avaya Fabric Connect (SPB)
Application Extensions
19
SPB vs TRILL / Fabric Path / Traditional + MPLS
Traditional Protocol Stack
MPLS layers
e.g. RFC4364
Layer 3 Virtualized Protocol
Unicast Service Infrastructure
Cisco‘s
OTV
Layer 2 Virtualized
Unicast Service
e.g. VPLS
Protocol
Infrastructure
Layer 3 Multicast
Service
e.g. PIM
Protocol
Infrastructure
Layer
Unicast
UC3 IGP
Service
(IS-IS
or OSPF)
e.g. RIP/OSPF
Protocol
Infrastructure
e.g. 802.1q/D
Layer 2
802.1D/Q
TRILL /
Protocol
Virtualized
(STP/VLAN)
FabricPath
Infrastructure
Service
Ethernet
© 2013 Avaya Inc. All rights reserved.
Physical
Infrastructure
Connectivity Services independent from Infrastructure
Top – Down Vertical dependency
e.g. Draft Rosen
Layer 3 Virtualized Protocol
Multicast Service Infrastructure
SPB’s simplicity
Horizontally Independent
Layer 3
Virtualized
Multicast
Service
Layer 3
Virtualized
Unicast
Service
Layer 3
Multicast
Service
Layer 3
Unicast
Service
Layer 2
Virtualized
Service
IP/SPB, SPBm/SPBm
Protocol Infrastructure
Ethernet
Physical
Infrastructure
20
Is OpenFlow the Whole Answer?
 OpenFlow and Fabrics are two different problems
– Trying to solve both at once is suboptimal & complex
– Example: Q Fabric based on Open Flow concepts
– Big distance limitation
– Doesn’t solve fabric problem well, needs MPLS
– Needs complicated technology to implement, worse to extend
 Open Flow solves the orchestration problem
– Not appropriate for the fabric problem
 Fabric Connect (SPB) solves the fabric problem
– Doesn’t pretend to be the orchestrator
 Separate the Fabric and SDN
– Failing to do so makes implementing each harder
© 2013 Avaya Inc. All rights reserved.
21
How is the Market Responding?
 SDN concept: “Gray Boxes” & custom code
– Great for Google & Amazon, but what about you?
 IBM & HP OpenFlow
– Packaged solution on proprietary hardware
– Not the epitome of open SDN
 Cisco Application Centric Infrastructure (ACI)
– SDN perceived as a huge threat
– Spun-out Insieme to attack the problem independent of internal
land-mines; bought back the start-up on completion
– Surprise! Solution is based on proprietary hardware
“Cisco's software-defined networking solution seems to answer
one question: How to sell more Cisco products to enterprises”
– InfoWorld
© 2013 Avaya Inc. All rights reserved.
22
Game-Changing Functionality with unmatched Simplicity
Three pillars of value to Fabric Connect
Fast
Flexible
Secure
© 2013 Avaya Inc. All rights reserved.
•
•
•
•
Provision at the “edge”
One Configuration Command
Optimized Link State Protocol
Fast to Converge, heal,& add, delete, move services
• Extend services anywhere seamlessly
• True service virtualization with ease
• L2, L3, Multicast, VRFs…
• As much service isolation as needed
• Carrier type virtualization, zero complexity
• Network Invisibility to users
23
Competitors believe network virtualization & SDN
is just for the data center, we know it is just the beginning
Virtual
Services
Fabric
Campus
Edge
Campus
Core
CRM
CRM
Financial
Financial
Optimizing the end user experience means addressing the network end to end
© 2013 Avaya Inc. All rights reserved.
24
Extend the Fabric to your Branches
Remote
Branch
Fabric
Department 2 Zone
Virtual
Services
Fabric
Department 1 Zone
Campus
Edge
Campus
Campus
Core
CRM
CRM
Financial
Financial
Optimizing the end user experience means addressing the network end to end
© 2013 Avaya Inc. All rights reserved.
25
Insight
The fundamental different between our SDN and the
competition is that we are simplifying the network first
through Fabric Connect, then automating and orchestrating
via OpenStack.
The competition is focusing on automating – but with
solutions that still require network and protocol overlays.
They aren’t adequately addressing network complexity first.
- Avaya SDN Program Manager
© 2013 Avaya Inc. All rights reserved.
26
Evolution to Fabric Connect
Establishes the Foundation
Users
Efficiency
 Using All Paths and Bandwidth
 Requirement to optimize
East/West traffic with ToR
solutions
 Average web page accesses
12 databases..!
VSP 9K
Flexibility
 Physical Topology Independent
 Service Virtualization L2/L3
Data Center Fabric
 Any service Anywhere, Anytime
Servers
 Network Virtualization with Scale
Servers
Servers
Servers
VM Mobility
Servers
Servers
Virtualized
Servers
Servers
Virtualized
Servers
Servers
 Transparent Network Services
 Removing Boundaries
 Simplified Powerful Infrastructure
© 2013 Avaya Inc. All rights reserved.
27
Avaya Collaboration Pods
Rapid deployment of real-time apps through pre-integrated solutions
Applications
Networking
Integrated
Solution
Compute
Storage
Integrates best of breed network, compute, storage,
management and applications as a single solution
offering
© 2013 Avaya Inc. All rights reserved.
28
Collaboration Pod for Avaya Aura VE
 Applications / compute
– VMware ESXi 5.0 on VMware compatible servers
– Avaya Aura Virtualized Environment and
orchestration software preloaded
– Avaya Aura Messaging Server (optional)
2 x G450 Gateway’s
Messaging Server (optional)
2 x SBC (optional)
1 x SBC Mgmt (optional)
 Networking:
– VSP 7000 Top of Rack Switch & ERS 4826GTS
– FABRIC CONNECT READY!
 Management :
2 x VSP 7024
2 x ERS 4826
KVM
3 x Servers
– Avaya Pod Orchestration Suite, VMware’s
vCenter/ EMC’s UniSphere
 Gateway:
– G450 Gateway
 Storage:
– EMC VNX 5300 (Ethernet or iSCSI adaptors)
 Security:
EMC VNX 5300
– IDE with client software for BYOD as part of POS
– SBC Enterprise (optional)
© 2013 Avaya Inc. All rights reserved.
Sample configuration
29
Today’s Data Center Silos
Example Applications
 Independent provisioning of:
– Virtual Machines
CRM Web App’s HR
– Server Adapters
– Storage Partitions
– Networks
– Appliances
Compute
Network
Storage
L4-7 Virtual
appliances
 Equates to:
– Delayed time-to-service
– Complexity across disparate
systems and functional teams
 Certain elements have
evolved while other haven’t
– Mix of physical and virtual elements
– Network clearly lagging
© 2013 Avaya Inc. All rights reserved.
30
The Evolution to the Software-Defined Data Center
Example Applications
Software-Defined Data Center
 Virtualization of infrastructure and
service components, by application
CRM Web App’s HR
 Common orchestration via single,
common user interface
Integrated Orchestration
 Goals:
– Provide equivalent functionality and
reliability to existing hardware
environments
– Allow applications to span both physical
and virtual resources
 Achieved by the integration of
Orchestration & Fabric
Fabric to interconnect disparate resource pools
Evolution not Revolution
© 2013 Avaya Inc. All rights reserved.
31
OpenStack for Orchestration
What is it?
• Open source software for building
private and public clouds
• Global community of over 10k
contributors from 125 countries
• Delivers a scalable cloud operating
system
Values
• Enables centralized control of resources (compute, storage, and networking)
with a single graphical interface
• Offers consistent operations in a multi-vendor Data Center environment
(multiple hypervisors, storage array’s etc)
© 2013 Avaya Inc. All rights reserved.
32
OpenStack at a Glance
Horizon Dashboard
(Graphical Orchestration Interface)
Nova
Neutron
Cinder/Swift
Hypervisor
Network
Storage
Orchestrates
VM resources
© 2013 Avaya Inc. All rights reserved.
Orchestrates network services
and appliances using VLANs
(fka Quantum)
Orchestrates block and
storage resources
33
A closer look at the network
The challenge with the current VLAN model
 Use of VLAN’s can
lead to “islands” –
stranded resources
Too many
touch points
and lack of
scale
Loops
 Virtual appliance
requirements – service
chaining and mobility
 Not flexible – topology
dependence
 Hop by hop service
provisioning
 Limited to 4096
VLANs
How to move VMs across subnets or Data Centers?
VLAN model is complex, rigid and lacks scale
© 2013 Avaya Inc. All rights reserved.
34
The Power of Avaya Fabric Connect
Avaya Fabric Connect solves current VLAN challenges
 Creates the virtual
backplane for the DC
 Logical topology
separate from physical
End-point
provisioning
with
massive
scale
Loadbalanced
Loop-free
network
VM mobility across subnets and across Data Centers
 Unrestricted VM
mobility across DCs
 End-point provisioning
 16 million service
instances
 Integrated multitenancy
Network as agile as the virtualized compute
© 2013 Avaya Inc. All rights reserved.
35
Avaya SDDC Solution Overview
Avaya Orchestration Suite
(with value-added applications: health status, monitoring, troubleshooting)
North/South
integration
via
OpenStack
Horizon Dashboard
(Graphical Orchestration Interface)
Nova
Neutron
Cinder/Swift
Compute
Fabric Connect
Storage
Data Center 1
© 2013 Avaya Inc. All rights reserved.
Data Center 2
Cross-platform
capability for
integration with other
systems
36
Insight
SPB is the foundation you have to have in order to
deliver SDN or SDDC or the promise of OpenStack.
In some ways, SDN is the FUD certain firms use to
hide their huge miss with their fabric delivery.
- another distinguished (but not Distinguished) Avaya Engineer
© 2013 Avaya Inc. All rights reserved.
37
Avaya SDDC Value:
Cloud Services, in Minutes, with Massive Scale
Turning up a new service:
1
Create Application Profile
2
Create Domain
3
Launch Application
4
Leverage Fabric to build the end to
end service
What it looks like:
Automation of service
provisioning
Virtual Service Network
Private Cloud
© 2013 Avaya Inc. All rights reserved.
38
Insight
SDN is a method. SPB is a fabric technology.
SDN can work very effectively with SPB, particularly with our
enhanced version in Fabric Connect. SPB compliments SDN by
taking it out of the Data Center and enabling true cloud extensions.
Other vendors are still trying to figure out the DC.
SDN does not require OpenFlow as many would have you believe.
Again, SDN is a method, Openflow is a technology.
SPB provides everything Openflow does and much more.
- The Distinguished Avaya Engineer
© 2013 Avaya Inc. All rights reserved.
39
Avaya’s Software-Defined Enterprise
Server
Access
Data Center
1 Core
CRM Virtual Service Network
Campus
Core
Server
Distribution
(optional)
Avaya UC Virtual Service Network
Server
Server
Access
Server
Data Center
2 Core
Secure Guest Virtual Service Network
Video Surveillance Virtual Service Network
Server
Coordinate service delivery endto-end in minutes
© 2013 Avaya Inc. All rights reserved.
Extend the service chain from
the application to the user
40
Extending the Architecture End to End:
Avaya’s Application-Driven Networking Direction
Server
Access
Data Center 1 Core
Distribution
(optional)
Campus Core
Video Surveillance Service or Video
Conferencing (Room)
Server
Secure Contact Center
Access
Server
Server
Access
Data Center 2 Core
Secure Guest Access Service
(BYOD)
Server
Auto-Provisioned Flare
Collaboration
Server
True automation through direct
interaction with applications
© 2013 Avaya Inc. All rights reserved.
Contain automation within
corporate guidelines,
regulatory, etc
41
Solving SDN Challenges Today
Network Complexity
Changes in Applications Architecture
Virtual Machine Mobility
Delivered today:
Avaya Fabric Connect
Multi-Touch Configuration (e.g. VM activation)
Scale-Out Connectivity
Reduced Time-to-Service
Multi-Tenant
Multi-Vendor Technologies
Vendor Dependence
Policy and Quality
© 2013 Avaya Inc. All rights reserved.
Enhanced today:
Avaya Fabric Connect
OpenStack enhancements
Coming soon:
OpenStack integration /
Open APIs
Today and evolving…
42
The Avaya Difference
 Simplicity and Agility
– Deploy new applications and services with a single user interface
– Legacy network complexity is eliminated; Network is as agile as the compute environment
 Cloud Services, in Minutes, with Massive Scale
– Cloud-based services deployed in 4 simple steps; scalable to 16 million unique instances
 End-to-end Services across Data Centers
– Seamless service creation across multiple geographically dispersed Data Centers
 Single and Multi-Tenant
–
Multi-tenancy integrated within the Fabric (no protocol overlays required)
 Open Foundation
– Works in a multi-vendor environment (different hypervisors, storage)
– Network Fabric based on IEEE/IETF standards
– Open APIs from Fabric for future flexibility in integrating into additional SDN ecosystems.
© 2013 Avaya Inc. All rights reserved.
43