64teq Education Innovators - Virtual Event May 2015

A look at SDN in the Campus and Switch Stacking.

Transcript

1. EtherealMind.COm Workshopping the Campus LAN VIRTUAL SESSION - May 2015
2. About EdTech Innovators • We have run a few physical events in central London, people liked them. • How do we include other people ? Getting to places can be challenging • Virtual Events will happen a 3 to 4 times a year. • Suggest topics, we will cover them.
3. Panelists ‣ Hosts: ‣ Greg Ferro, Freelance Network Architect - http:// etherealmind.com ‣ Steve Wilde, 64TEQ Education ‣ Panel: ‣ Phil Sugars - Lead Technology Specialist, ULT ‣ Rob Carter - ICT Lead, OAT ‣ Amit Samani - Brocade - http://www.datacenterfuture.com/ blog/author/amit-samani/
4. Housekeeping • Open Microphone. Please mute yourself if in noisy location • Open discussion • Ask questions !!! • use the GoToMeeting interface • or just speak up • Let us know what you would like to see in future events
5. EtherealMind.COm Agenda 1. About Virtual Events 2. Software Defined Networking 3. Switch Stacking
6. Virtual Events @ 64Tq • We have run a few physical events in central London, people liked them. • How do we include other people ? Getting to places can be challenging • Virtual Events will happen a 3 to 4 times a year. • Suggest topics, we will cover them.
7. EtherealMind.COm Agenda 1. About Virtual Events 2. Software Defined Networking 3. Switch Stacking
8. network Server Client network © Greg Ferro 2015 Most people see the network like this Manage Flow configuration centrally, state managed locally Router, Switch = Forwarding Tables Firewalls, Load Balancers = Connection table App Server Controller App OS App OS App App Desktop Controller App
9. App Network Controller App network Server Client network © Greg Ferro 2015 SDN Operation Manage Flow configuration centrally, state managed locally Router, Switch = Forwarding Tables Firewalls, Load Balancers = Connection table App Server Controller App OS App NOS N.App NOS N.App OS App App Desktop Controller App • Centralised point of management and operatinal control
10. Forward © Greg Ferro 2014 Control Management Device Planes of Operation Packet In Packet Out Routing Protocols Spanning Tree, TCAM SSH, SNMP, Command Line, Operating System PHY, Buffers, Crossbar, Software/hardware architecture
11. Network Controller “Control Plane” Network Network Network Network © Greg Ferro 2014 Network Controller Forward Forward Forward Forward Mgmt Mgmt Mgmt Mgmt
12. Network Controller Network Network Network Network © Greg Ferro 2014 API Forward Forward Forward Forward Mgmt Mgmt Mgmt Mgmt Monitoring Application Path Application Analytics Application Cloud Orchestrator eg. OpenStack Cloud and Application Integration Network integrated with end-to-end orchestration of IT Infrastructure • Network operation can be unified with VMware ESX & Microsoft Hyper-V • Network becomes “programmable” in the same way that servers & desktops are managed using software applications
13. Example: Analytics • Flow based operations drive new approaches to monitoring • network visibility using SNMP is limited • Flow based tools proven better e.g. Netflow, sFlow but hard to use today Network Controller Network Network © Greg Ferro 2014 Forward Forward Mgmt Mgmt Visibility Application Router Router Router Router Analytic Data Analytic Data Analytics and Visibility Streaming APIs and Data Modelling
14. Flows Not Packets • Frames and Packets use “hop by hop” path selection 1 Hop-by-Hop Packet Networking Each hop is self-selecting and configuring © Greg Ferro 2015 Router Server Client Router Source Destination 2 Router Router
15. Flow States • In reality, the network holds state in device memory Packet and Frames on WAN Links © Greg Ferro 2015 Router Server Client Router Data Stream from Server to Client Data Stream from Client to Server Flow States In Network Devices Flow State in Network Devices Protocol sessions between server & client create state in devices 1 2 4
16. Flow Tables • We can configure these flow tables directly. • Each vendors does it differently. • Existing protocols do this today. - - MPLS VXLAN VLAN Tag VLAN or MPLS tag Flow Record Flow Record SRC/DST IP, TCP Port Flow Record © Greg Ferro 2015 Output Output Output Input Input Input VLAN Trunk Overlay Edge MPLS Edge Flow Table and Actions Internal handing for each packet in a network device
17. Discussion on SDN
18. SD-LAN • SDN in the Data Centre is established and maturing slowly • SDN in the Campus is emerging
19. SD-LAN • User Controls - Identity, Authentication & Management • Risk Free Path Management (compared to OSPF or STP) • deprogram a path to perform upgrades/replacement during hours • Combined Wired & Wireless • QoS/Voice that actually works
20. SD-LAN - Inspection • Inspection - per Flow redirection to security engines • malware, proxy, content • As traffic volumes grows exponentially, can’t inspect everything. • Use heuristics / analytics capability to detect flows for inspection • Each network device (switch) have agents to perform edge inspection
21. SD-LAN QoS/Voice • DiffServ “per packet” QoS doesn’t work very well. If at all. • Per Flow QoS has better technology. • Inspection/Detection in Edge devices • Combined with controller/applications • Dynamic, Policy Based QoS is shipping today
22. The End of The Tree • Ethernet forces “tree-based Distribution Distribution Distribution Distribution Access Access Access Access Access Access Access Access Core Core X X X X X X X X X X X X Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr Svr 3 Tier Spanning Tree Network © Greg Ferro 2014 EtherealMind.com
23. Spending Patterns Connectivity Services Business Value © Greg Ferro 2015 $’s Network Budgets Today (Pre-SDN) Budget mostly spent on hardware and bandwidth for connectivity Connectivity Services Business Value Visibility Mobility Operability © Greg Ferro 2015 $’s Network Budgets Tomorrow (Post-SDN) Budget increasingly spent on software and services
24. EtherealMind.COm Agenda 1. About Virtual Events 2. Software Defined Networking 3. Switch Stacking
25. Switch Stacking • Topics • Why do we stack ? • Two Types of Switch Stacking • Design Issues
26. Why Stack ? • Reduce number of devices • Configuration in one place • Monitoring/Polling simplified • reduce operational cost
27. Stacking Basics • Single “manager”, multiple forwarders • Control place synchronisation
28. © Greg Ferro 2015 Control Plane Synchronisation Many Physical as one Logical Device Network Network Network Network Forward Forward Forward Forward Local Local Local Master Network Network Network Network Forward Forward Forward Forward Mgmt Mgmt Mgmt Mgmt Independent Devices Control Plane Sharing - STP, OSPF etc © Greg Ferro 2015 Data Flows Device state uses STP, OSPF to share configuration information One device becomes “master” and sends state to other devices in stack
29. Stacking & MLAG • Reduce Spanning Tree risk • “FAT TREE” designs Svr Svr Svr Svr Core Core Distribution Distribution Access Access Unifying Control Planes Svr Svr Svr Svr Core Distribution Access Fat Tree © Greg Ferro 2014
30. Stacking Technology • Two types of stacking technlogies - • Physical - uses dedicated cables • Virtual - uses Ethernet network to combine
31. • high bandwidth but nonstandard physical connections • close together • obsolete now - high speed Ethernet cheaper, better © Greg Ferro 2015 Physical Switch Stack Dedicated Connections Between Switches Switch Switch Switch Switch
32. • Uses Ethernet connections to synchronise control planes • Not distance constrained • Up to 12 units in a stack © Greg Ferro 2015 Logical Switch Stack In-Band Connections Using Ethernet Switch Switch Switch Switch
33. 64 Teq • 64TEQ Education - provide IT Hardware, Software and Professional Services to Schools, Colleges and Academy Trusts. • Website: http://64teq.education • Ed-Tech Innovators • Networking and Tech Events • Online Virtual Events
34. EtherealMind.COm § thanks to questions / discussion or just have a coffee