- play_arrow Overview
- play_arrow Zero-Touch-Provisioning
- play_arrow Managing Data Center Devices
- Data Center Interconnect
- Logical Router Interconnect
- Configuring Data Center Gateway
- Virtual Port Groups
- Configuring Virtual Port Groups
- Using Static, eBGP, PIM, and OSPF Protocols to Connect to Third-Party Network Devices
- Configuring Storm Control on Interfaces
- Creating Port Profiles, Storm Control Profiles, sFlow Profiles, or Telemetry Profiles by Cloning
- Configuring EVPN VXLAN Fabric with Multitenant Networking Services
- Edge-Routed Bridging for QFX Series Switches
- Activating Maintenance Mode on Data Center Devices
- Viewing the Network Topology
- Viewing Hardware Inventory of Data Center Devices
- Viewing Configuration of Devices Deployed in Contrail Fabric
- Detecting and Managing Manual CLI Configuration Changes
- Certificate Lifecycle Management Using Red Hat Identity Management
- Collapsed Spine Architecture
- Support for Superspine Role
- 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
Device Import
You can import devices or onboard devices to an existing fabric by using the Contrail Command user interface (UI).
Contrail Networking Release 2011 also supports topology discovery when you run the onboard device job.
Follow these steps to import devices by using the Contrail Command UI.
- Click the Onboard icon as show in Figure 1.Figure 1: Onboard Fabric Device
The Onboard devices pop-up is displayed.
- From the Onboard devices pop-up, you can:Figure 2: Onboard Devices Pop-up
Select and import certain types of interfaces to the device(s).
To import a particular type of interface, select the check box next to the type of interface. Uncheck all check boxes to import all types of interfaces.
If a particular interface is not displayed as a option, you can select regex while adding advanced interface filters as described in the following step.
Add advanced interface filters.
You can create an interface filter to filter interfaces to be included in the fabric. By default, all interfaces identified as participating in Contrail are imported into the fabric during the fabric provisioning process. If an interface filter is set, the fabric provisioning process includes the interfaces that are participating in Contrail and that match the interface filter in the fabric.
To add advanced interface filters, click +Add. The Operation and Expression fields are enabled.
Select regex from the Operation list. Enter filter characters in the Expression field.
The Expression field supports all characters, including metacharacters, that are allowed in Python regex filters. For example, you can enter ^xe in the Expression field to filter out all 10Gbps xe interfaces from the fabric.
Import configured interfaces.
Select the Import Configured Interfaces check box only if configured interfaces need to be imported into the fabric in addition to runtime interfaces.
With some exceptions, a configured interface is an interface that has been configured in the Junos OS software. A runtime interface is an interface that has not been configured in Junos OS. Only runtime interfaces are imported into the fabric by default.
With Contrail Networking Release 2011, topology discovery job is also initiated when you run the onboard devices job.
Follow these steps to view physical interfaces connected to the device you just onboarded. You can view fabric links from the results of the topology discovery job as well.
Navigate to Infrastructure>Fabrics.
The Fabrics page is displayed.
Click the name of the fabric to view the list of fabric devices.
Select the device that was onboarded by selecting the check box next to the name of the device.
Click Action>Reconfigure Roles as shown in Figure 3.
Figure 3: Reconfigure Roles
Click Autoconfigure to reinitiate the auto-configuration job.
The Autoconfigure page is displayed.
The Autoconfigure progress bar on the Discovered devices page displays the progress of the auto-configuration job. Once the auto-configuration job is completed, click Next. The Assign Telemetry Profiles page is displayed.
(Optional) Assign telemetry profiles. For more information, see Assign Telemetry Profiles.
Click Finish to exit the wizard.
From the list of devices that is displayed, click the name of the device that you just onboarded.
The device overview is displayed.
Click the Physical Interfaces tab to view the physical interfaces of the selected device.
Figure 4: Topology Discovery
Interfaces that are connected to other devices in the fabric are marked as Fabric as seen in Figure 4. Interfaces that are connected to external devices are marked as External. Interfaces that are not initially connected to a fabric device or external device but belong to a Virtual Port Group are marked as Access. Interfaces without a type are default interfaces.
(Optional) To view logical interfaces and hardware inventory of the device you just onboarded, click the Logical Interfaces tab and Hardware Inventory tab respectively.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.