Loading...
Loading...
If a timer policy has a protocol or port specific rule, with idle-timeout configured as "unspecified" and "all-other" rule as well, the timeout applied to the flow must be the Idle Timeout as configured in default "Protocol Profiles" configuration.
The idle timeout policy enforcement does not happen as expected with this specific rule combination.
1. If a timer policy configuration has a protocol or destination port specific rule with idle-timeout configured as "unspecified" and if there is an "all-other" rule as well configured in the same policy and 2. A connection that matches timer policy rule with "unspecified" idle-timeout value.
It is recommended not to have any Timer Policy Rule with "unspecified" timeout value.
None
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.