|
Interval before sending application data
|
SD-AVC requires a few minutes to learn from the network traffic before the application data is sent to the SD-AVC Network
Service and compiled at the network level. See SD-AVC and Application Recognition.
|
|
SD-AVC application rules pack less relevant for client-to-client traffic
|
SD-AVC provides application classification for server-based applications. The SD-AVC application rules pack is less relevant
for client-to-client traffic, which is more granular and dynamic. Client-to-client traffic is classified by NBAR2 running
on each network element.
|
|
Proxy or CDN
|
In the case of a proxy or content delivery network (CDN), multiple applications may use the same IP/port combination. The
network devices themselves classify such traffic fully. However, for these applications, the SD-AVC agent operating on a device
may report application data to the SD-AVC network service with a lesser degree of detail: they may be reported with less detailed
classification granularity or not at all.
|
|
Reported bandwidth of Unclassified Traffic Discovery
|
For traffic that appears in the Unclassified Traffic view, the reported bandwidth is based on samples and may not be accurate
in some cases. See Unclassified Traffic Analysis and Discovery.
|
|
High-stress flows may not be discovered by the Unclassified Traffic Discovery feature
|
High-stress flows that require a large amount of system resources may be excluded from the traffic reported in the Unclassified Traffic view. For example, the Timeline may show a high-bandwidth of unknown/generic traffic that is not reported in the table. This
is done to minimize the utilization of resources in case of high stress flows and skip the discovery mechanism. See Unclassified Traffic Analysis and Discovery.
|
Feedback