Restrictions for Service Groups
-
Only EFP service instances, routed sub-interfaces and aggregate port-channel sub-interfaces can be added as members of service groups.
Each service instance or sub-interface can belong to only one service group at time.
-
The service group must exist before any member can join the group.
-
All members of a service group must reside on the same physical interface or same aggregate port-channel interface.
-
Sub-interfaces or service instances that are members of a service group cannot have a QoS policy applied to the interfaces, even if the service group does not have a QoS policy applied.
-
MPOL is not supported on aggregate port-channel when policy is applied on aggregated port-channel main interface, port-channel sub-interface cannot be attached by any policy, or be configured as a member of a service-group.
-
Sub-interface belongs to service group and sub-interface applied with service-policy cannot be configured on the same aggregate port-channel simultaneously.
-
Each sub-interface belongs to only one service group at a time.
-
Interfaces that are a member of a service group cannot have a QoS policy applied.
-
A batch configuration including both "define service-group" and "add sub-interface to service-group" may result in membership error, and vice versa in the unconfiguration.
So it is recommended to define the service-group before adding subinterfaces or service instances to it, and removing them from the service-group before deleting the service-group or deleting the subinterfaces or service instances.