Outlines the configuration limitations and constraints that apply to service insertion implementation.
Adhere to the following limitations when configuring service insertion to ensure proper functionality and avoid configuration conflicts.
-
A service chain can include up to four service types. Each service type can have multiple instances of the service, either as high availability pairs that are load-balanced by the feature, or behind a third-party load balancer.
-
The services in a service chain must be in a single VPN.
-
If you are using a dual stack service in a service chain, every service in that service chain must have a dual stack high-availability pair.
-
A specific device interface should not be used for more than one service in a particular service chain.
-
A specific interface can be used in different service chains only if it is used for the same service type in each of the service chains.
-
All the interfaces and tunnels for the services in a service chain should be part of the VPN in which the service chain is defined.
-
More than one tracker should not be associated with a given interface. For example, if endpoint-tracker tracker1 is associated with GigabitEthernet1, a different tracker cannot be associated with GigabitEthernet1.