Restrictions for external AppQoE service nodes

• Only Cisco Catalyst 8000V instances can be configured with the service node role.

• When Cisco Catalyst 8000V is configured as a service node, it can’t act as a service controller, even though Cisco Catalyst 8000V supports the service controller role.

• Only one service cluster is supported per site.

• Only one service context is supported per device. Within a service context, only one AppNav controller group (ACG) is allowed, and that group can contain only one AppNav controller (service controller). Service nodes are organized into service node groups (SNGs); each SNG must be named starting with SNG-APPQOE followed by an index (for example, SNG-APPQOE1), with valid indices from 1 to 31 (plus one default SNG-APPQOE at index 0). A maximum of 64 service nodes can be configured per device across all SNGs. For the Integrated Service Node (ISN) cluster type, each SNG is limited to one service node.

• Only one service node group is supported per AppQoE cluster.

• VRRP is not supported for service controller to service node connectivity.

• A dedicated VRF needs to be setup for the service nodes and service controllers.

• Although handling of asymmetrical flows isn’t built into AppQoE, you must configure flow symmetry for all stateful features in Cisco SD-WAN Manager.

• If a service controller fails, the flows handled by that service controller are reset.

• AppQoE Service Nodes is not supported for Cisco Catalyst 8000V when deployed on Cisco Enterprise Network Function Virtualization Infrastructure Software (NFVIS) on CSP devices.

• When you are migrating from IPv4 to IPv6 or vice-versa, you need to remove all the AppQoE configurations and re-apply the configurations with the required IP format.

• Ensure that the bootstrap configuration for the Cisco Catalyst 8000V instance being configured as the AppQoE service node is modified as follows:

  • Exclude any controller groups from the TLOC interfaces ( exclude-controller-group 0 )

  • Ensure that the configuration includes omp shutdown

  Note

  This configuration prevents the AppQoE service node from participating in the SD-WAN data plane. The absence of this modification in the bootstrap configuration leads to generation of alarms indicating that OMP and Control Connections are down in Cisco SD-WAN Manager. However, the alarms are harmless and can be ignored if the recommended configuration is absent from bootstrap configuration.

Restrictions for AppQoE Services with IPv6 Addresses

Minimum supported releases: Cisco IOS XE Catalyst SD-WAN Release 17.14.1a and Cisco Catalyst SD-WAN Manager Release 20.14.1

The restrictions for AppQoE service nodes with IPv6 addresses are:

• The control plane of an AppQoE cluster operates on either IPv4 or IPv6 traffic.

• The control plane of an AppQoE cluster that operates on IPv6 traffic supports only external service nodes.

• IPv6 traffic on Internal Service Nodes (ISN) does not support UTD.