The SRv6 FPE type is required for the termination and origination of SRv6 services. The following guidelines apply for the SRv6 FPE:
An internal or external Port Cross-Connect (PXC) can be used for the SRv6 FPE.
The SRv6 origination or termination FPE cannot be shared with other applications, but the same physical ports can be used when configuring PXC ports for multiple FPEs of different applications.
As an example of how two FPEs can share the same physical port (therefore the same bandwidth), define two PXC ports, both sharing the same underlaying physical port; for instance:
FPE 1 is associated with PXC-1 and FPE 2 is associated with PXC-2, where PXC-1 and PXC-2 are both assigned to port 1/1/1
Some considerations about the SRv6 termination FPE follow:
It is configured per locator.
Multiple locators can optionally use the same or different FPE.
Received SRv6 traffic for a specific (local) locator is redirected to the SRv6 termination FPE interface-a.
Some considerations about the SRv6 origination FPE follow:
There is only one SRv6 origination FPE supported per system.
The SRv6 origination and termination FPEs are always different.
SRv6 FPE redundancy and load-balancing:
Each FPE can use a LAG composed of as many PXC ports as needed (there is no specific limitation in the number of PXC members per LAG).
LAG members can be PXC ports in the same or a different card.
The following CLI is required to create the FPE of type srv6 origination or termination and apply it to a locator. All locators may be associated with the same or a different FPE.
configure
+--fwd-path-ext
+--fpe <fpe-id>
+--application
+--srv6 <origination|termination>
+--interface-a
+--qos <network-policy-id>
+--interface-b
+--mtu <1280-9786>
+--qos <network-policy-id>
configure
+--router
| +--segment-routing
| | +--segment-routing-v6
| | | +--origination-fpe <fpe>
| | | +--source-address <ipv6-address>
| | | +--locator <locator-name>
| | | | +--termination-fpe <fpe>