- 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
Retaining the AS Path Attribute in a Service Chain
Service chaining allows two virtual networks to communicate with each other using a service policy or network policy. The VNs communicate through services instances defined in the network policy. Service instances can be physical network functions or virtual network functions.
For data to traverse between VNs, the BGP route attributes are modified according to the network policy. One such BGP attribute, is the AS path attribute. AS path is a sequence of autonomous systems that network packets traverse. By default, the AS path is nullified while leaking routes from the source to the destination network in a service chain. Starting with Contrail Networking Release 2011, you can configure the AS path to be retained in the routes re-originated from the destination VN to the source VN in a service chain. You also have the ability to enable or disable the path retention for selected service chains.
The AS path retention feature works only for virtual network functions.
You can enable or disable the Retain AS Path option while configuring the network policy. A network policy is unique to a service chain and configuring the knob at the policy level will apply that feature to that service chain and its component service instances defined by the policy. Even when service instances are shared between multiple service chains, the same service instance can behave differently in different service chains based on the Retain AS Path knob in the policy configuration.
To configure the AS Path attribute to be retained in the routes re-originated from the destination VN to the source VN in a service chain:
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.