Displays throughput and efficiency across the different inspection tiers of this device. Use this information to diagnose certain performance-related issues. On a stack device, the device's stacking statistics are displayed.
Inspection Tier | Description | ||
Stack : Segment Ports | For TPS 8200TX/8400TX and TPS TXE Series devices, the following
information is displayed when stacking is enabled:
|
||
Stack : Stack Ports | For TPS 8200TX/8400TX and TPS TXE Series devices, the following
information is displayed when stacking is enabled:
|
||
Tier 1 | Inspection bypass and Intrinsic HA L2FB are handled here, preventing traffic from
going to the next tier. It also handles the rate limiter, inspection bypass rules,
jumbo packet shunting, and hardware watchdog timer.
|
||
Tier 2 | Load balances flows through the KS threads and handles traffic management trusts and
block filters will prevent traffic from proceeding to the next tier.
Ratio to next tier accounts for Traffic Management Trust and Block rules and Traffic normalization filters.
TCP ACKs are trusted by default, and reduces Tier 2 ratio to next tier.
|
||
Tier 3 | This tier is designed to search for suspicious traffic that needs to
undergo deep inspection. This section handles IPv6 + GRE and Mobile IPv4
tunnels. IP reassembly, maintaining connection table, and TCP state
tracking is handled here. If triggers are found it determines what
filters need to be checked against the packet or flow then it turns on
soft-reroute for the flow, and, if necessary, sends it for deep packet
inspection.
This section displays how much traffic KS threads and IP
reassembly will inspect. Ratio to next tier shows what percentage of
traffic needs TCP reassembly or is suspicious (matched a trigger).
|
||
Tier 4 | This tier performs TCP reassembly and threat verification
which includes header-based checks, protocol decoders, content search,
and regular expression matching. Also, action handling occurs here
whether the packet is dropped, rate limited, or rate limited in the
connection table.
Tuning is required if congestion is occurring or if an
IPS is being operated close to its maximum rated throughput. The
deeper a flow is inspected the more processing is required, so the
most performance gains can be attained by optimizing the KS threads
at this level (Tiers 3 and 4). The three most process intensive
operations are:
For supported TPS devices with a TOS v5.3 or later, the
following information is displayed when SSL inspection is enabled:
|
||
Tier 5 | For supported TPS devices with a TOS earlier than v5.3, the
following information is displayed when SSL inspection is enabled:
|