-
The IP SLA sender egress and ingress VLAN should match. Ensure to configure VLAN translation in the same context.
-
Layer 3 IP SLA is not supported on external traffic direction.
-
Only DSCP-based marking is supported for IP Target operations.
-
The session duration is limited to multiples of 10; user input is rounded down to the nearest multiple of 10.
-
Layer 2 Color-Aware IP SLA is not supported for external traffic direction.
-
The bridge-domain target type is not supported for external traffic direction.
-
Color-Aware SLA for bridge-domain target type is not supported.
-
Since SAT traffic is intrusive, any other traffic is dropped for a particular EFP.
-
IPv6 address is not supported as a destination address.
-
Layer 3 SLA Loopback is not supported for labelled incoming packets.
-
For layer 3 Loopback, if the target type is service instance, the core and access side EFP should have the same encapsulation.
-
For layer 3 Loopback, if the target type is VRF, only encapsulation untagged is supported. The loopback session is not supported for the VRF target types even for same encapsulation on access and core EFPs.
-
For layer 3 Loopback, if the target type is bridge domain, only encapsulation untagged is supported. The loopback session is not supported for the bridge domain target types, even for the same encapsulation on access and core EFPs.
-
For two-way mode, the Multicast destination support is not available for IP SLA (layer 3 SLA).
-
IP SLA does not support enabling a signature.
-
SLA on the target with Custom Ethertype encapsulation is not supported.
-
SLA on the target with 802.1ad enabled is not supported.
-
Quality of Service (QOS) on any target type with IP SLA is not supported on layer 2 and layer 3 routers.
-
Simultaneous terminal SAT session and terminal loopback session cannot be performed on the same Ethernet EFP.
-
Multiple active sessions are not supported on the same Ethernet EFP.
-
For operations with passive measurement mode and target type EFP, the same destination MAC address cannot be used for any other traffic on a port as the loopback MAC Address Tables (CAM) tables contain the channel numbers and the destination MAC address. As a result, multiple SLAs with the same destination MAC address, on the same port active at the same time, are not supported for passive measurement mode.
-
For operations with two-way measurements, any one of the parameters, namely, port, destination MAC address, and encapsulation VLANs, should be different for SLA sessions that are simultaneously active.
-
Scaling is dependent on the availability of the terminal SAT session, terminal loopback session, and egress Span session.
-
For layer 2 virtual forwarding instance (VFI) or Switched Virtual Interface (SVI), only target type EFP and generator or measurement type terminal sessions should be used.
-
For operations with EFP using XConnect, only the target type EFP and terminal sessions for Tx and Rx statistics are supported.
-
Terminal and facility loopback sessions use different entries in the MAC Address tables (CAM) tables.
-
For layer 2 internal sessions with Rx statistics, either only four non-color-aware sessions, or one color-aware session and one non-color-aware session are supported.
-
When an internal SAT session is active, at the same time and on the same Ethernet EFP, an internal loopback session cannot be started.
-
For IMIX traffic, packet sizes of 64 bytes, 512 bytes, and 1518 bytes are supported. These packet sizes are forwarded in the ratio 7:4:1.
-
For operations with a port channel as target type, only one member link is supported.
-
When the source MAC address is not configured on layer 2 SLA, any one system reserved MAC of 16 MAC addresses is used.
-
For operations with SLA in PPS mode, an additional packet is forwarded.
-
For operations with layer 2 and layer 3 SLA on Trunk EFP, outer VLAN tag of the packet is mandatory.
-
While a SLA session is in progress, dynamic addition of MAC access lists (ACLs) does not affect the SLA traffic.
-
Priority tag SLA in external direction is supported only when the inner tag and outer tag are marked as priority tags.
-
Facility loopback session cannot be started on a port configured as a SPAN source.
-
Terminal SLA session cannot be started on a port configured as a SPAN destination.
-
Facility SLA session cannot be started on a port configured as a SPAN source.
-
Source MAC address should not be configured as multicast or broadcast MAC address.
-
PIM Sparse mode is not supported for traffic generator mode and passive mode.
-
SAT session fails with proper syslog messages for the following reasons:
-
Facility session cannot be started on a port configured as a Span source.
-
Terminal session cannot be started on a port configured as a Span destination.
-
Source MAC address should not be multicast or broadcast MAC address.
-
Only interface or service instance is supported for external session.
-
VLAN or Bridge-domain service types are not supported for facility Traffic Generator.
-
VLAN or Bridge-domain service types are not supported for facility Traffic Measurement.
-
EFP or Trunk EFP or bridge-domain is shut.
-
The following table shows the supported egress and ingress QOS on the sender side core interface for Ethernet and IP target SLA.
Table 5 IP SLA and Type of QOS supported
IP SLA
|
Type of QOS
|
Supported on sender side core interface
|
IP Target SLA
|
Egress
|
Yes
|
IP Target SLA
|
Ingress
|
No
|
Ethernet Target SLA
|
Egress
|
No
|
Ethernet Target SLA
|
Ingress
|
Yes
|
-
The following table shows how Ethernet Target SLA with multicast or broadcast source MAC address is supported on different operational modes.
Table 6 Multicast or Broadcast MAC support criteria for SLA
Source or destination MAC address
|
Operational mode
|
Support for Ethernet Target SLA
|
Multicast or broadcast source MAC address
|
Traffic generator mode
|
Not supported
|
Passive measurement mode
|
Two-way statistics collection mode
|
Multicast or broadcast destination MAC address
|
Traffic generator mode
|
SLA generates the traffic
|
Passive measurement mode
|
SLA receives the traffic
|
Two-way statistics collection mode
|
Not supported
|
-
Service Activation layer 3 Loopback is not supported with the target interface belonging to ASIC 1 in RSP2.
-
Generation of burst traffic is not supported; therefore, configuration of CBS and EBS is not supported.
-
IP SLAs configured with start-time now keyword need to be restarted after reload.
-
The minimum supported value for rate step is 1024 pps.
-
PPS mode is not supported with IMIX packet size.
-
When the pseudowire control-word is switched off, the Frame Transfer Delay (FTD) could not be calculated. By default, the control-word is switched on.