network field day 10 - juniper networks part 4: junos fusion for data center
TRANSCRIPT
Copyright © 2015 Juniper Networks, Inc. 1
Junos Fusion For Datacenter Network Field Day 10
Damien Garros, Technical Marketing Engineer @damgarros #NFD10 #junosfusion
Copyright © 2015 Juniper Networks, Inc. 2
Junos Fusion For Datacenter
Simplify management of large number of devices
Protocols Driven infrastructure for higher resiliency
Overlay and orchestration tools integration
Path to IT-as-a-service / SDN
Plug-and-play provisioning
Copyright © 2015 Juniper Networks, Inc. 3
Simplicity at Scale
Junos Fusion for Datacenter
Configuration One point of configuration
Operation One point of management
Deployment Plug and Play provisioning of access devices
Copyright © 2015 Juniper Networks, Inc. 4
Manage it the way you want
Junos Fusion for Datacenter
Network Director
APIs Netconf / Restconf/ Yang
CLI Vmware NSX
Open Stack
Contrail
Copyright © 2015 Juniper Networks, Inc. 5
What are we doing differently ?
Protocol Driven Infrastructure Legacy Infrastructure
• All components are tight together
• Master brain to coordinate all components
• All components have similar capabilities
• One system
• All components are independent
• One “federation” not one “system”
• Components can have very different capabilities
Copyright © 2015 Juniper Networks, Inc. 6
Any version anywhere
Due to the protocol driven architecture Each components can run it’s own software version. Upgrade and Downgrade can be partial or span across long period of time Access devices can be grouped into Software Upgrade Group to simplify operations and management of large number of satellites
15.2R1 15.2R3
1.0 2.0 1.0 2.0 1.0 1.0
Copyright © 2015 Juniper Networks, Inc. 7
Very different component working as one
High logical scale High buffer
Features rich platform
High throughput Low latency
Power efficient
Manage as one
Copyright © 2015 Juniper Networks, Inc. 8
Universal SDN Gateway
Flexible scalable L2 POD design Interconnect with EVPN/VXLAN (TOR and vRouter) in IP CLOS fabric Edge Interconnect to WAN (EVPN, IP VPN Transport agnostic) Inter-POD connectivity with EVPN/VXLAN
EVPN-MPLS (WAN)
OVSDB VXLAN
EVPN-VXLAN
Copyright © 2015 Juniper Networks, Inc. 9
ACCESS DEVICES AGGREGATION DEVICES
Supported Aggregation and Access Devices
QFX10000 series EX4300 (1GE) QFX5100 (10GE/40GE)
LFOS
Copyright © 2015 Juniper Networks, Inc. 10
Active / Active Architecture
There is no concept of Master/Backup Neither for traffic not access devices management
Each access devices has autonomous sessions open to both aggregation devices
Each aggregation device is pulling statistics and info from all access devices
Copyright © 2015 Juniper Networks, Inc. 11
Junos Fusion - Modes of Operation LOCAL SWITCHING EXTENDED
• All traffic is processed on aggregation devices
• Full features-set of aggregation devices available
• L2 Traffic is processed at access level
• Traffic forwarding optimization
Copyright © 2015 Juniper Networks, Inc. 12 Copyright © 2015 Juniper Networks, Inc. 12
Satellites management for all traffic related aspects (config / statistics / ports state)
LAG synchronization between Aggregation devices (MC-LAG)
LLDP
802.1BR+
Configuration synchronization between Aggregation devices Netconf
Protocols Used Internally 1
2
3
4
Device management for non-traffic related aspects (chassis, environment, upgrade ..) json-rpc
5
Devices discovery and auto provisioning
1 2 3
4
5
1 2 3
ICCP
Copyright © 2015 Juniper Networks, Inc. 13
Junos Fusion for Datacenter Junos Fusion is enabled per port,
not per device
States and statistics for access ports are available on both
aggregation devices
Aggregation devices remain independent for ports not on access. No master/backup
Extended ports can be configured as L2 only.
Each access device is seen as a linecard per both aggregation devices
All access ports are seen as local
Configuration for all access ports is done in either aggregation device,
Shared configuration is synchronized.
xe-101/0/1 xe-103/0/1
xe-0/0/2 xe-0/0/2
FPC 101 FPC 103
Management of access devices is done on either of the aggregation devices
Redundancy is embedded into the architecture