Director
Chapter 3
Configuring Filters Using the CLI
This chapter describes how to use the CLI to determine which monitoring tools are connected to which Network ports. It also explains how to create filters to limit the amount of traffic copied to Monitor ports, so the monitoring tools receive only the traffic that is of interest to them.
In this chapter, you will learn to:
•Copy traffic from any Network port to any Monitor port
•Aggregate traffic from any set of Network ports to any Monitor port
•Regenerate traffic from any aggregated set of Network ports to any set of Monitor ports
•Create filters
•Create complex filters
•View filters
•Work with configurable 10 Gigabit ports
•Understand filter interactions
For a complete listing of filter commands in the CLI, see Appendix B.
Syntax
In the CLI, Director ports are specified by
•n1.1, n1.2, n1.3 .. n1.12 – Network ports in the first DNM (the slot on the left); for
•n2.1, n2.2, n2.3 .. n2.12 – Network ports in the second DNM (the slot on the right); for
•m.1, m.2, m.3 .. m.10 – Monitor ports
•t1.1, t1.2 – Configurable 10 Gigabit ports (on the front panel)
•t2.1, t2.2 – Configurable 10 Gigabit ports (on the rear panel)
Most commands accept lists of ports. In port lists, port names are separated by commas and a dash
When you define a filter, you specify an action to be taken when the filter conditions are met. The action can be either drop or redir (meaning redirect). If the action is drop, then packets which meet the filter criteria are dropped, that is, they are not copied to any Monitor port. If the action is redir, then packets which meet the filter criteria are copied to all Monitor ports listed in the redir_ports=<portlist> argument.
25