Copyright © 2015 Juniper Networks, Inc. 1 Junos Fusion Enterprise

Copyright © 2015 Juniper Networks, Inc. 1

Junos Fusion Enterprise


Legal Disclaimer

This presentation sets forth Juniper Networks’ current intention and is subject to change at any time without notice. No purchases are contingent upon Juniper Networks delivering any feature or functionality depicted in this presentation.


Junos Fusion: One Technology, Multiple Products

One Technology , Many Use Cases

Junos Fusion Data CenterSimplified management

Plug n play

Junos Fusion Edge

Maximize the edge router slot utilization


Simplified management of wiring closets


Junos Fusion Enterprise Tomorrow’s enterprise: Simple, Smart, Flexible

Simple: one logical device to manage, plug-n-play, zero touch

Smart: open APIs, highly resilient, intelligent software upgrades

Flexible: investment protection, use current topology, flexible deployment models


Simple Smart Flexible

…


CascadePort

UpstreamPort

Terminology

Extended port

Yocto Linux

LFOS

AP

Satellite Device Cluster

Satellite Device (SD)

Aggregation Device (AD)

…


Supported Devices

Aggregation Device Satellite Devices

EX9200 EX4300: Mid-Level Satellite, Entry-Level Satellite


High-Level Software Architecture

Satellite Device

Linux Forwarding Engine Software

LLDPAPI(JSON)

Aggregation Device

IEEE802.1BR CSP

CSP: Control and Status Protocol

Yocto Linux


Control Plane Protocols

AggregationDevice

Satellite Satellite

Satellite Satellite LLDP IS-IS [SSMP, CSP, J-RPC]

LLDPLLDP

IS-IS

IS-IS

IS-IS

IS-IS

[SSMP, CSP, J-RPC][SSMP, CSP, J-RPC]

Discovery

LLDP

CSP

IP Connectivity

Provisioning


Extended Mode: Data Plane

Aggregation Device

Satellite Device

1 2

0 1 n

Ethernet Header

Payload Ethernet Header

Payload

Ethernet Header

PayloadIEEE

802.1BREthernet Header

PayloadIEEE

802.1BR

ECID: Port 1 ECID: Port 2

Ethernet Traffic

IEEE 802.1BR traffic


Mode of Deployment

Dual Aggregation DevicesSingle Aggregation Device

• Reduced port and installation costs

• Simple management; reduced network layers

• Easy to extend existing architecture

• Chassis-level redundancy

• Centralized point of management for access ports

• Aggregation devices remain independent


Single Aggregation Device

Junos Fusion is enabled per port,

not per device

State and statistic for ports on satellites are available on

aggregation device

Ports on Satellite can be configured as any Ethernet L3 or L2 encapsulation

Each satellite is seen as a line card

All access ports are seen as local ports

Configuration for all ports is done in Aggregation device

xe-101/0/1 xe-102/0/1

FPC 101 FPC 102

Aggregation devices remain independent

xe-0/0/2

Management of Satellites is done on Aggregation device

Redundancy is provided with other protocols


Dual Aggregation Devices

MC-LAG

Automation



Junos Fusion is enabled per port on the AD

States and statistics for extended ports are available on both

aggregation devices

Aggregation devices remain independent for ports not on satellites. No master/backup.

Extended ports can be configured as L2 only.

Each Satellite is seen as a line card per both Aggregation devices

All extended ports are seen as local

Configuration for all extended 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 Satellites is done on either of the Aggregation devices

Redundancy is embedded into the architecture



There is no concept of Master/Backup for Satellite management

Each SD has autonomous CSP sessions open to both ADs

SD is sending same information to both ADs

Each AD is pulling statistics and info from SDs

CSP sessions


Satellite Device/Satellite Device Cluster

• SD does not run Junos

• Windriver Yacto Linux as base OS

• Linux Forwarding Engine software runs as an application on top of the Linux OS

• No local switching on the SD

• 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 change in newer releases

…


Extended Mode

Extended

• All traffic is processed on Aggregation devices

• Full features-set of Aggregation devices available


Multicast Replication

Multicast Replication

• All multicast traffic L2/L3 is replicated on AD

• Default Mode


Class Of Service

1

2

3 4

5

1. Extended Port – Port level BA Classifiers

2. Uplink Port Schedulers

3. Extended port logical interface BA Classifiers, MF Classifiers and Policers

4. Extended port rewrite rules and cascade port schedulers

5. Honors forwarding class from AD and uses the extended port scheduler

AD

SD


Uplink Failure Detection


If Satellite device loses complete connectivity with Aggregation device once UFD feature is enabled, it brings down all ports except candidate uplink ports.


Satellite Registration – Plug-and-Play


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 config not necessary.

• Connectivity-based or Unique-ID based

• Configure the port leading to SD as “cascade-port”

• SD discovery and auto-provisioning of in-band management IP connectivity

• 1 loopback address per SD and 2 addresses per link between SD and AD

• Sync all extended port operational state between SD and AD


SD Registration – Multiple Satellites on a Cascade Port (Not Completely Plug-and-Play)

AD0

SD0(Slot-ID: 100)

SD1(Slot-ID: 101)

1. LLDP (Discovery + Physical Interface IP address

assignment from AD)

10.1.1.2

10.1.1.1

1. IS-IS (Neighbor and Topology Discovery + Physical Interface IP address

assignment)

10.100.1.1

10.100.1.2

10.101.1.2

10.101.1.1

2. SSMP

Learn following information from AD:

1. Stack Member-ID

2. Slot-ID

3. LB Address

4. Misc.)

4. SSMP

Learn following information from AD:

1. Stack Member-ID

2. Slot-ID

3. LB Address

4. Misc.)

[edit chassis]satellite-management { stack bldgB-floor7-closet-1 { stack-id 1; cascade-ports [xe-0/0/1]; fpc 100 { # Slot 100 assigned to SD named as “SD0” member-id 1; serial-number <sd0-sn>; } fpc 101 { # Slot 101 assigned to SD named as “SD1” member-id 2; serial-number <sd1-sn>; } fpc 102 { # Slot 102 assigned to SD named as “SD2” member-id 3; serial-number <sd2-sn>; } } redundancy-groups { chassis-id 1; group1 { redundancy-group-id 1 peer-chassis-id 2 icl ae0; stack [bldgB-floor7-closet-1]; } }}


xe 2/0/1

Auto LAG

Aggregation Device

Satellite DeviceSlot ID 100

xe 2/0/0

172.16.0.100

• No LAG configuration required between SD and AD

• Adding a new cascade port towards SD results in auto formation of a LAG bundle

• No traffic loss during addition of LAG members

• Single or dual-homed satellites


Flexible Deployment Models

Dual-homed to single Aggregation device*

Dual-homed to redundant Aggregation device

Single-homed to single Aggregation device*

Standard STP or LAG to non-Fabric devices

Fusion

Dual-homed via different stack members

… … … …

* Under Investigation


Unifying Enterprise Networks

EX9200

L4-7services

Finance

Sales

Engineering

Guest

Engineering VPN

Sales VPN

Finance VPN

Guest VPN B54User VLANs

Data Center Core Campus

Coherent virtual network (vNS)• Efficient Network Segmentation across Campus/Datacenter using

EVPN


ClosetFloor n Closet

IDF

Satellite Devices

ClosetFloor 0 Closet

…

EX4300

EX9200

Aggregation Devices

ClosetFloor n Closet

IDF

Satellite Devices

ClosetFloor 0 Closet

…

EX4300

EX9200

Aggregation Devices

JunosFusionData Center

… …

… JunosFusionEnterprise

JunosFusionEnterprise

Junos SpaceNetwork Director

Building 1 Building n

Unifying Enterprise Networks


Rolling Software Upgrades


Software Upgrade – Any Version Anywhere

Each component can run its own software version

Upgrade and downgrade can partial or span across long period of time

Satellites can be grouped into Upgrade Groups to simplify operations and management of large numbers of satellites

15.2R1

1.0 1.0 2.0


Software Upgrade

• SD software management from AD

• SD software image automatically upgraded when discovered

• Group SDs into different software upgrade groups for flexibility

• SDs in different software upgrade groups can have different image

Junos Fusion

Software UpgradeGroup 1

Software UpgradeGroup N


Product Comparison


Junos Fusion Data Center

Junos Fusion Edge

Enterprise Specific Features like 802.1X, PoE, LLDP-MED, MACsec, etc.

Yes1 No No

Satellite Device Cluster Yes No No

Extended Mode Yes Yes Yes

Local Switching No Yes Yes

Endpoints Connected to Multiple SDs

No Yes Yes

Remote Satellites No No Yes

L2 Multicast Egress Replication at SD

No Yes Yes

1. Some features not available at FRS


Junos Fusion Enterprise vs. Cisco IA

JFE Cisco Instant Access

Number of Extended Ports 6000 2000

Number of SDs 128 42

Number of SDs in a Cluster

10 5

AD High Availability AD redundancy based on MC-LAG (Independent

Control planes)

IA parent redundancy based on VSS

AD/SD Connectivity 40/10/1G 10G only

Special Stack Cables Required for Cluster

No Yes

Topology-Independent Components

All AD and SD devices can be used as part of JFE or

non-JFE deployments

6800ia can only be used in IA deployments. Some IA clients cannot be used in

non-IA deployments

Thank You

Documents

Copyright © 2015 Juniper Networks, Inc. 1 Junos Fusion Enterprise