- play_arrow Overview
- play_arrow Zero-Touch-Provisioning
- play_arrow Fabric Configuration
- Image Management
- Onboard Brownfield Devices
- Onboard Greenfield Devices
- Device Import
- Create Virtual Network
- Create Logical Routers
- Create Network Policy
- Create Network IPAM
- Reconfigure Roles
- Managing Custom Roles
- View Node Profile Information
- Monitoring Fabric Jobs
- Terminating Ongoing Fabric Jobs
- Adding a Leaf or Spine Device to an Existing Fabric Using ZTP
- Grouping Fabric Devices and Roles Using Device Functional Groups
- Creating Layer 3 PNF Service Chains for Inter-LR Traffic
- Creating VNF Service Chains for Inter-LR Traffic
- Retaining the AS Path Attribute in a Service Chain
- Assisted Replication of Broadcast, Unknown Unicast, and Multicast Traffic
- Running Generic Device Operations Commands In Contrail Command
- Adding DHCP Server Information for Virtual Networks and Logical Routers
- Return Material Authorization
- Approaches to Enable External Connectivity for Overlay Networks
- Contrail Networking Supported Hardware Platforms and Associated Roles And Node Profiles
- play_arrow High Availability in Contrail Networking
- play_arrow Integrating VMware with Contrail Networking Fabric
- play_arrow Integrating OpenStack with Contrail Networking Fabric
- play_arrow Extending Contrail Networking to Bare Metal Servers
- Bare Metal Server Management
- How Bare Metal Server Management Works
- LAG and Multihoming Support
- Adding Bare Metal Server to Inventory
- Launching a Bare Metal Server
- Onboarding and Discovery of Bare Metal Servers
- Launching and Deleting a Greenfield Bare Metal Server
- Destination Network Address Translation for Bare Metal Servers
- Troubleshooting Bare Metal Servers
Collapsed Spine Architecture
Starting from Release 2011, Contrail Networking supports collapsed spine, which is an architecture, in which there is no defined leaf layer. In collapsed spine architecture, the Layer 3 IP-based underlay and the EVPN-VXLAN overlay, which are usually run on the leaf, are built on the spine switches. These spine devices also act as the border gateway.
Collapsed spine architecture is supported on the following devices running Junos OS release 20.2R2 or later:
QFX5120-32C—Can function as an L2 or L3 gateway
QFX10K—Can function as L2, L3, or DC gateway
Supported QFX10K devices:
QFX10002-72Q/36Q/60C
QFX10002-36Q
QFX10002-60C
QFX10008
QFX10016
Collapsed spine topology is supported in both greenfield and
brownfield deployments. To configure a device as collapsed spine,
you need to assign the physical role spine and overlay
role Collapsed-Spine.
Benefits
Collapsed spine architecture is useful for both enterprises and service providers that
want to move to an IP fabric-based architecture with an EVPN-VXLAN overlay
want to add two or more spine switches to ensure adequate bandwidth during maintenance window or to function as a backup in case of a spine failure.
have small datacenters with mostly northbound and southbound traffic movement
want to extend Layer 2 traffic across data centers.
have multi-vendor legacy ToR switches that do not support EVPN-VXLAN.