The following section describes operational considerations for deploying Application Telemetry, including general considerations, followed by a summary of platform-specific considerations.
The following list describes general Application Telemetry operational considerations:
When you enable Application Telemetry, it is globally enabled on all ports. You cannot disable the feature on a per-port basis.
Application Telemetry supports IPv4 and IPv6 packets, although host monitoring is available for IPv4 hosts only.
Application Telemetry filter rules are not user configurable. However, an updated app-telemetry.pol file can be installed through the ExtremeCloud IQ Site Engine.
If a user-created filter rule (ACL) conflicts with an Application Telemetry defined filter, the user-created rule always takes precedence.
There are two configurable sFlow collectors (Collector 1 and Collector 2). However, Application Telemetry uses Collector 1 only and you must configure it before enabling Application Telemetry.
Application Telemetry supports Segmented Management Instance interfaces VLAN and CLIP. Segmented Management Instance interface OOB is not supported.
Application Telemetry supports user created VRFs when you configure a Segmented Management Instance CLIP interface as the source IP.
You can use the onboarding VLAN to manage the switch and enable Application Telemetry without any additional management or routing interface configuration.
This section provides a summary of other operational considerations.
|
Attribute |
Supported |
|---|---|
|
Flows that ingress standard VLAN ports |
Yes |
|
Flows that ingress UNI ports |
Yes |
|
Flows that ingress NNI ports and egress UNI ports (Layer 2 VSN) |
Yes |
|
Flows that ingress NNI ports and egress UNI ports (Layer 3 VSN) |
Yes |
|
Flows that ingress NNI ports and terminate locally |
Yes |
|
Flow that ingress NNI ports and egress NNI ports |
No |
|
Flows on DvR Controllers or DvR Leafs |
Yes |
|
Attribute |
Supported |
|---|---|
|
GRT |
Yes |
|
VRF |
Yes (with management CLIP) |
|
Fabric Connect – Layer 2 VSNs |
Yes When the Analytics Engine is reachable over a Layer 2 VSN, the GRE packets are encapsulated with MAC-in-MAC (IEEE 802.1ah) at the originating BEB. The MAC-in-MAC header is removed at the terminating BEB and the original GRE packet is sent to the collector. Note: the MAC-in-MAC encapsulation plus the GRE encapsulation adds 60 bytes to the original packet. If the original packet is close to the maximum transmission unit (MTU), the mirrored copy can exceed the MTU and be dropped. |
|
Fabric Connect – IP Shortcut Routing |
Yes |
|
Fabric Connect – Layer 3 VSNs |
Yes (with management CLIP) |
|
Attribute |
Operation |
|---|---|
|
If you enable sFlow and Application Telemetry simultaneously on the same port |
The switch sends the sFlow datagrams and Application Telemetry packets to the collector. |
|
Attribute |
Operation |
|---|---|
|
IPv6 security filters or IPv6 source guard |
Supported on VSP 7400 Series only. |
|
Attribute |
Operation |
|---|---|
|
Mirroring resources |
Only 3 mirror ports can be configured for general port mirroring |
|
If rx port mirroring is enabled on a port, and Application Telemetry is enabled, when a packet that matches one Application Telemetry entry criterion comes to this port |
The switch generates the remote mirrored packet, and the port-based mirroring copy. |
|
Attribute |
Operation |
|---|---|
|
If you enable uRPF mode on the switch |
The MTU values for both IPv4 and IPv6 packets on the same VLAN are always matched. Different Layer 3 MTU sizes on the same VLAN are not allowed in uRPF mode. |
|
Attribute |
Operation |
|---|---|
|
If packets match both user defined filters (ACLs) and Application Telemetry rules, and if both rules have counters |
Both counters incremented |
|
Attribute |
Operation |
|---|---|
|
smb, kerberosasreq2 and kerberostgsreq packet types |
kerberosasreq2 and kerberostgsreq packet types supported. Smb – not available |