|
|
|
“Sample-based” Flow records will obscure information needed for Application Traffic Reporting.
Reconciling Directionality for Application Traffic Reporting and Active Measurement
The specific definition of appropriate active-measurement targets is configured via the application of access-lists (ACLs) to the overall “Top N” table that the EFC module constructs. Prior to the introduction of the application traffic reporting feature set, the task of appropriate ACL definitions was in some cases more convenient if EFC was presented uni-directional traffic flow data. (For example, only the interfaces on one side of the border routers would be configured as NetFlow sources.)
In the event that a production configuration such as this is updated to change the nature of the flow data presented to the EFC module for application traffic reporting, it will be necessary to review and modify the ACLs that define active measurement groups. Please contact Avaya support if you have any questions about these details.
Identification of Applications
CNA application traffic reporting bases “application” definitions on the observed TCP and UDP port information. There are three major classes of “Applications”:
Well known applications all start with lowercase letters, contain no spaces, and are up to (32) characters long.
User defined applications are configured within the EFC module via the combination of access list(s), and the user-defined-application name <application-name> command. User defined application names can be up to (32) characters long, and must start with an UPPERCASE letter.
Dynamically observed applications are identified with the syntax “port-xxxx”, where “xxxx” corresponds to the observed TCP/UDP port number.
|
|
|