Associating Flow Monitor to an interface
You can attach two different wired AVC monitors with different predefined records to an interface at the
same time.
Procedure
PurposeCommand or Action
Enters global configuration mode.configure terminal
Example:
Step 1
Device# configure terminal
Enters the interface configuration mode.interface interface-id
Step 2
Example:
Device(config)# interface Gigabitethernet
1/0/1
Associates a flow monitor to the interface for
input and/or output packets.
ip flow monitor monitor-name { input |
output }
Example:
Step 3
Device(config-if) # ip flow monitor
flow-monitor-1 input
Returns to privileged EXEC mode.
Alternatively, you can also press Ctrl-Z to exit
global configuration mode.
end
Example:
Device(config)# end
Step 4
NBAR2 Custom Applications
NBAR2 supports the use of custom protocols to identify custom applications. Custom protocols support
protocols and applications that NBAR2 does not currently support.
In every deployment, there are local and specific applications which are not covered by the NBAR2 protocol
pack provided by Cisco. Local applications are mainly categorized as:
• Specific applications to an organization
• Applications specific to a geography
NBAR2 provides a way to manually customize such local applications. You can manually customize
applications using the command ip nbar custom myappname in global configuration mode. Custom
applications take precedence over built-in protocols. For each custom protocol, user can define a selector ID
that can be used for reporting purposes.
There are various types of application customization:
Generic protocol customization
• HTTP
• SSL
System Management Configuration Guide, Cisco IOS XE Bengaluru 17.4.x (Catalyst 9400 Switches)
201
Configuring Application Visibility and Control in a Wired Network
Associating Flow Monitor to an interface