SummaryInformation on Ignoring traffic and how to set up an ignore policy on the Exinda, or how to use the 'ignore internal to internal' option
OverviewIn certain networks, there could be some traffic that the user does not want to optimize, monitor or control. This traffic should be set to "IGNORE" by the Exinda. Any policy that is set to 'ignore' does not count towards any virtual circuit or circuit bandwidth limit; it is evaluated and sent through before bandwidth allocation is done.
This traffic can be:
- Any internal to internal traffic on the LAN
- DMZ traffic communicating with internal LAN
- Any application that need not be controlled
Ignoring such traffic can be done in the following ways:
1. If the traffic is internal to internal
Exinda ignores "internal to internal" traffic by default from optimization, control and monitoring.
The subnet to be ignored can be set as an "internal" network object and all the other internal subnets it is communicating with can be set as "internal" network objects as well. Since the Exinda ignores internal to internal traffic by default, all this traffic will be ignored
2. If the traffic is Internal to External
Create the specific network objects and add them to a policy in the Exinda. Mark that policy for "ignore". This way, as soon as flows match this policy, all the interesting traffic for the defined network object/application will be "ignored.
Additional InformationPlease note:
With the 2nd procedure, traffic is still seen in Real Time Monitoring hitting the policy. This does not exclude it from Monitoring.
With Procedure 1, traffic is excluded from monitoring as well
There is an exception in Procedure 1. Any ICMP traffic on the Exinda will not be ignored, even if it is internal-internal.