Embed Size (px)
Citation preview
Junos Fusion Christoph Plum, [email protected] Engineer
Juniper Unite – The Cloud Enabled EnterpriseUnite and Secure the Enterprise Network
CAMPUS CLOUD BRANCH
SIMPLICITY + SECURITY + AUTOMATION
Junos Fusion
Centralized Networkand Policy Control
Transform Your Network
Tomorrow’s Network: Simplified Architecture that Scales
Virtually collapse layers of network
Simple to manage platform
Centralized configuration, provisioning, management, and policy
Junos FusionYour Entire Enterprise Network: One Logical Device
…
Aggregation Device – Logical “Routing Engine”
Satellite Devices – Logical “Line Cards”
“Logical”“Physical”
Juniper Enterprise Architectures
HyperScalability
Virtual Chassis
Virtual Chassis Multi-tier Junos Fusion EVPN / IP Fabric
Flexibility | 1GbE/10GbE/40GbE
Multi-Fabric LAG | Multi-version support
Virtual Network
Scalability | Open
Common Building Blocks
EX2300/3400/4300Access Switches
EX9200Core Switches
EX4600Agg Switches
Juniper Data Center Fabric Architectures
JUNOS: one common operating system for all fabrics
<4,260Servers < 1,500 Servers 10,000+<6,000 Servers
Layer 2 Scale-out
Virtual Chassis | MC-LAG
VCF Junos Fusion IP Fabric
Flexibility | 1/10/40GbE
Virtual Network
Highly Simplified Datacenter SaaS, DiY, web-scale
Enterprise SDDC
ContrailCloudPlatform
Hyper Scalability
NetworkDirector
NetworkDirector
NetworkDirector
Multi-Fabric LAG | Multi-Version | Open
Junos Fusion – One TechnologyJunos FusionProviderEdge
Junos Fusion Datacenter
Junos Fusion Enterprise
MX QFX10002 EX9200
QFX5100QFX5100(48T,48S,24Q,96S)QFX5100(48SH,
48TH)
EX4300-48T/24T/32F
EX4300
EX4300
EX3400
EX2300
Satellite Device/Satellite Device Cluster
• SD does not run Junos• SNOS (Satellite Network OS) software runs as an
application on top of the Linux OS• Junos Fusion Enterprise supports Satellite Device Cluster
– Eliminates the need to connect every SD to the AD– Multiple SDs can be deployed behind a Cascade port– 10 SDs in a cluster; this may increase in newer
releases…
128 Line cards; 6000 ports; One switchshowchassishardware|grepFPCFPC2REV07750-049611CABZ4317EX920032x10GSFP
showchassishardwaresatellite|grepFPCFPC111REV06650-044935PF3713480444EX4300-24PFPC112REV11650-044930PD3714120047EX4300-48PFPC121REV10650-044930PD3713490410EX4300-48P
showinterfacesterse|matchge |exceptdown|excepteth-switchge-111/0/12upupge-111/0/13upupge-112/0/10upupge-112/0/12upupge-112/0/13upupge-121/0/10upupge-121/0/34upup
AD0 AD1
SD111
SD112
SD121
SD113
SD114
High-Level Software Architecture
SatelliteDevice
Satellite Network OS
LLDP API(json-rpc)
AggregationDevice
IEEE802.1BR CSP
Yocto Linux
Junos Fusion Enterprise - Topology Options
Non-Fusion switch using MC-LAG
Junos Fusion DC - Topology Options
LAG across SDSingle HomedSD
Non-Fusion switch using MC-LAG
Multiple Deployment Options
Modes of Deployment Modes of Operation Satellite Connections
Single Aggregation Device
Dual Aggregation Device
Extended mode Single Satellite Device (SD)
Cluster of SDs (JFE only)Local Switching (JFD only)
Dual Aggregation Devices
MC-LAG
Automation
Satellite Provisioning
SD Registration – Single Satellite (Plug-and-Play)
Aggregation Device
Satellite DeviceSlot ID 100
xe 2/0/0
10.2.0.2
10.2.0.1
172.16.0.100
LLDPCSP
• SD is auto discovered. SD specific confignot necessary.
• Configure the port leading to SD as “cascade-port”
• SD discovery and auto-provisioning of in-band management IP connectivity
• SD is automatically converted from Junos to SNOS
• No configuration required on the SD
SD Cluster Registration – Multiple Satellites on a Cascade Port (Not Completely Plug-and-Play)
[edit chassis]satellite-management {
cluster Closet1 {cluster-id 1;cascade-ports [xe-2/0/1];fpc 100 { # Slot 100 assigned to SD named as “SD0”
member-id 0;system-id 10:0e:7e:a1:3f:20;
}fpc 101 { # Slot 101 assigned to SD named as “SD1”
member-id 1;system-id 10:0e:7e:a1:3f:21;
}fpc 102 { # Slot 102 assigned to SD named as “SD2”
member-id 2;system-id 10:0e:7e:a1:3f:22;
}}
Aggregation Device
SD100
xe 2/0/0
SD101
SD102
Software Upgrade Group
1.0 1.0 1.02.0 1.02.0
• Devices grouped into SUGs
• Inside a group, satellites run same version
• New satellite part of an SUG automatically updated
• SDs in SD cluster are part of an automatically created group for the cluster
• Different types of satellites can be part of a single SUG
Fusion Management
Junos Fusion Management Options• CLI
• Single AD: Manage entire fabric via AD• Dual AD:
• Use configuration synchronization feature• Changes only need to be executed on one AD
• Network Director• ND ensures synchronization between both ADs
Junos FusionRoadmap / Summary
Fusion Licensing
• Junos Fusion Enterprise does not require licenses• Junos Fusion DC requires licenses for SNOS based SKUs
– No license required if customer purchased a JUNOS based ToR– License is required for the SNOS based ToR
• QFX5100-48sh• QFX5100-48th
– One license per provisioned SD– Apply the same license keys on both AD– Soft licenses; Not tied to serial number
Products comparison
Aggregation Device (AD) QFX10002 EX9200
Satellite Device (SD) QFX5100, EX4300 EX4300, EX3400, EX2300, QFX5100
Mode of deployment Dual AD Dual AD/Single AD
License per SD Yes for SNOS SKU only No
Extended Mode Yes Yes
Local Switching Mode Yes No
Satellite Cluster support No Yes
L2 Multicast egress replication on SD Yes No
Use case specific features FCoE, DCB POE,802.1x,LLDP-Med,MACSec
Junos Fusion Datacenter
Junos Fusion Enterprise
Fusion Enterprise AD Platforms
Summit 1RU*(1H 2018)
• 8x10GbE• 4x100GbE
EX9204• 120x10GbE• 12x100GbE
EX9208/EX9214• 440x10GbE• 44x100GbE
Summit 3RU*(1H 2018)
• 196x10GbE BO• 24x100GbE
NewBundle
* Roadmap
Junos Fusion - Summary• Manage campus / data center network as single fabric• Single point of management• Scale up to
• 128 SDs / 6000 Access Ports (Fusion Enterprise)• 64 SD / 3000 Access Ports (Fusion Data Center)
• Zero touch provisioning of new satellites / RMA• Flexible deployment options / migration paths• Software Upgrade Group• No licensing for JFE / HW only SKUs for JFD• Network Director integration
Thank youThank you
