PCA

To verify that the PCA is successfully capturing TCP packets, evaluating the data, and forwarding hits to downstream consumers, you must verify that capture is properly configured and enabled in the PCA Web Console.

• Console Tab: Verify that capture is enabled and is capturing packets from the network.
• Summary Tab: Review the following:
  1. Machine Health section identifies each enabled PCA process and the current data volume and CPU usage.
  2. Peers section indicates the destinations to which the PCA is delivering hits.
  3. Current Per Second Stats section indicates the current processing load for individual processes in the PCA. The Reassd Out column indicates how much data is emerging from the PCA right now.
• Delivery Tab: This tab can be used to troubleshoot delivery issues to the target recipients.
  • Target recipients should include the pipeline on the server on which you have noticed limit or no hit processing.
  • You can use the Ping link to test the connection between the PCA and the target.
  • Verify that the setting in the Security column matches the expected delivery protocol for the pipeline in question.
  • For issues in slow processing, the Speed test can verify the transfer rate across the network between the PCA and the target.
• Interface Tab: Use this tab to verify all instances of the CX Passive Capture Application and to review the configurations for all network interface cards (NICs) that are listening to web traffic.

HBR

Through the Portal, you can review the current status of the HBR machine. Health-Based Routing enables load balancing between multiple Canisters in a Tealeaf environment.

1. In the Portal menu, navigate to System Status > Health Based Routing.
2. In the General section, review the Health message.

   If all Canisters are reporting good health, the message should say something like:

   
   4 out of 4 Canisters Healthy and Available

3. To identify if hits are being spooled, review the value for Current Spooled Hits.

   This value must be assessed based on the current and expected traffic volume. You should divide this value by the number of hits per second. This value can be retrieved from the Pipeline Status tab in TMS.

4. Below the General report are two graphs indicating the percentage of healthy Canisters out of the total available and the percentage of traffic that is being properly passed to a Canister for evaluation.
5. At the bottom of the report, you can review the status information for individual Canisters configured to receive hits from HBR.
   • For a health Canister, the Health State message should say Healthy.
   • Other status messages typically include a Reason, which may be explored through other System Status reports.
   • If a Canister is overburdened and unable to keep up, you should verify that the Routing value does not indicate that the Canister is receiving too high of a percentage of traffic from HBR.
6. To refresh the report, click Refresh in the left navigation panel.
   • If there is no data in the HBR report, the HBR machine may be down. In the Portal Management page, ping the machine hosting HBR.
   • If some Canisters are reporting that they are down or in an unhealthy state, investigate each one using the Canister status report.
   • If all Canisters are down, HBR is unable to communicate with them.
     • In the Portal Management page, you can verify the configuration and availability of each Processing Server.
     • The problem may be an error in how the Canister configurations for HBR.