This table on the Application Flows tab displays unidirectional flow data stored in memory. It displays the raw, non-aggregated flow data received
from the flow sensors on the network. It presents flow data for real-time troubleshooting purposes, and is not designed for historical long-term flow collection. A check mark (
) in the table denotes a tracked application or a tracked site.
Hover over an application in the table to display switch data, which is an accumulation of multiple switches into single flow record, as well as the path that flow has taken.
By default, the top 100 entries are displayed in the table. However, you can change this value using the Max Rows field at the bottom of the view.
Text at the bottom of the table shows Base Flows, using X number of days, hh:mm:ss format, and including Current Load and Peak Load calculations in flows per second.
Following are definitions for the table columns:
Flow Summary
Rest the cursor over the first column in the table and select the 
arrow to open the Flow Summary window for a specific flow. Flow summary information can include response times, Uniform Resource Identifier, and header data for the flow. In the Flow Summary window, use the Gear menu 
to access additional functionality such as the ability to modify the application fingerprint or create a policy rule.
Client/Server Flows
Identifies whether the flow is a Client Flow 
or a Server Flow 
. The client/server direction of a flow is calculated by the ExtremeAnalytics engine. Hover over the icon to see a tooltip with more information.
Source Address
The IP address or hostname of the system where the flow originated. Select on the Source address link to open a PortView for the client or server (if it is in the database) or a PortView for the switch configured as the NetFlow sensor.
Source Port
Either the TCP or UDP port on the client/server handling the flow.
Destination Address
The IP address or hostname of the system that received the flow.
Destination Port
Either the TCP or UDP port on the system that received the flow.
Application
The name of the application as identified by the ExtremeAnalytics engine using the Fingerprint database.
Application Group
The flow application group to which the application belongs.
Application Info
Additional information about the flow provided by the ExtremeAnalytics engine.
Type
The content type of a flow, such as sound, video, or text. Select on the Type icon to open the flow's URI.
Network Response
The response time (in milliseconds) that it took for the TCP request to complete.
Application Response
The response time (in milliseconds) that it took the application request to complete.
Site
The site where the flow originated.
Detailed Site
The client's switch IP and switch port (wired), or controller IP, AP, and SSID (wireless).
Device Family
The operating system family for the client end-system.
User
The username used when the client system connected.
Profile
The ExtremeControl profile assigned to the client end-system.
Protocol
The connection type protocol used by the flow.
Last Seen Time
The last time the flow was seen.
Duration
The amount of time that the flow was active.
Rate
The average bandwidth for the flow based on the flow duration.
Packets
The number of packets in this flow. For flows collected via Application Telemetry, this number can be estimated.
Bytes
The number of bytes in this flow. For flows collected via Application Telemetry, this number can be estimated.
NetFlow Records
The number of NetFlow records for this flow.
Flow Source
The IP address of the NetFlow source switch, Application Telemetry source switch, or wireless controller sending the Flow data to the Flow collector.
Input Interface
The interface receiving the flow on the Flow sensor.
Output Interface
The interface transmitting the flow on the Flow sensor.
TOS
The DSCP (Diffserv Codepoint) value for the flow. The TOS/DSCP value is used to configure quality of service for network traffic.
TTL
The TTL (IP Time to Live) value of the flow. The TTL field indicates the maximum number of router hops the packet can make before being discarded. The TTL field is set by the packet sender and reduced by every router on the route to its destination. When the value hits zero, the packet is dropped.
For information on related help topics: