Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
external-header-nav
keyboard_arrow_up
close
keyboard_arrow_left
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Support for Superspine Role

date_range 18-Jul-23

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.

Note:

Hierarchical route reflector feature is not supported in Release 2011.

external-footer-nav