Examples

The following table provides examples for using the dynamic filter commands.

Example

Description

capture start global * capture start global user USER1 capture start global addr-prefix 1.1.1.1 capture start global addr-prefix 1.1.1.1/24 capture start session-agent 172.1.1.1 addr-prefix 10.10.10.10 capture start int-ev local-rejection capture start int-ev short session

Captures all session data. Captures all session data for USER1. Captures all session data for IP address 1.1.1.1. Captures all session data for IP address 1.1.1.1 using netmask of 24. Captures session data for SA 172.1.1.1 at IP address 10.10.10.10. Captures session data for interesting events that occur that are of type local-rejection. Captures session data for interesting events that occur that are of type short-session.

The following flow chart shows the dynamic filter process.

Note:

Dynamic filters are only removed after a reboot/switchover of the Oracle® Enterprise Session Border Controller.

Issuing another dynamic command may or may not affect previous dynamic commands that were already initiated. If you issue a dynamic command with a <main filter> object, and then issue another command with the same <main filter> object, the new command tasks precedence. If you issue a dynamic command with a different <main filter> object, then the Oracle® Enterprise Session Border Controller uses both <main filter> commands to monitor traffic.

For example, if you enter the following dynamic command:

ORACLE# capture start realm1 user 123

and then enter:

ORACLE# capture start realm2 user 123

The Oracle® Enterprise Session Border Controller monitors realm1 AND realm2 with user 123.

To stop dynamic filter commands, you can initiate the capture stop <main filter> command. For example:

ORACLE# capture stop realm1 user 123

To stop configured filters, you must manually remove them from the ACLI configuration.