- 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
- How to Detach and Attach a VMI to VPG
- 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
Create Logical Routers
A logical router replicates the functions of a physical router. It connects multiple virtual networks. A logical router performs a set of tasks that can be handled by a physical router, and contains multiple routing instances and routing tables.
Follow these steps to create a logical router (LR).
The router_interface object (Virtual Port) is created as part of the LR creation and VN extension to Spines workflow. While planning the IP address for spines, you must be aware that an extra one IP address is required for the router_interface object which gets created automatically.