- 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
Support for Superspine Role
Starting with Release 2011, Contrail Networking supports the superspine role. Devices with the role superspine can function as either a lean device that provides only IP forwarding or as a route reflector that can establish iBGP sessions with the peers. Superspines can be connected to spines in a CRB topology or to border-leaves in ERB topology. If the superspine is a lean device, then the spines should function as route reflector. If the superspine is functioning as a route reflector then the spines and leafs can peer with the superspine through iBGP sessions. Superspine role is supported in both greenfield and brownfield deployments.
To configure a device as superspine, you need to assign the
Physical Role as superspine
and overlay role as lean
or Route-Reflector
. If you assign the role lean, only
IP forwarding will be supported and no iBGP session will be established
with the peers. If you assign the Route-Reflector role, then the spine
and leaf devices will establish iBGP sessions.

Hierarchical route reflector feature is not supported in Release 2011.