Question & Answer
Question
What are some of the common causes of interruption of traffic to Tealeaf servers?
Answer
Contents
Question
What are some of the common causes of interruption of traffic to Tealeaf servers?
Answer
Question
What are some of the common causes of interruption of traffic to Tealeaf servers?
Answer
Some causes of interruption of traffic to Tealeaf servers are:
- Keys are changed by the web administrator or they expire and the Tealeaf administrators are not notified.? This is a common problem.
- A network device upstream from Tealeaf is reconfigured and as a result the spanned traffic to Tealeaf is interrupted.? The result is that no sessions are processed.? If you encounter a situation in which Tealeaf is receiving no traffic check the Pipeline status in TMS to see if the Tealeaf Pipeline is receiving any traffic.? If not check the Capture Web Interface.? If you are not seeing any traffic being recieved OR if the traffic is 100% unidirectional then there is a problem with the router span port.
- Web Traffic increases after Tealeaf is implemented to the point where the original hardware used for Tealeaf is no longer adequate. When this happens you see increased instances of spooling and active sessions are running behind the current time.? Stopgap configuration changes can be made to minimize these problems but eventually you need to upgrade your hardware to meet the current requirements.
Article Reference
00001391
Applies to version(s): 7.x;8.x
"
[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSERNK","label":"Tealeaf Customer Experience"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}}]
Was this topic helpful?
Document Information
Modified date:
08 December 2018
UID
ibm10778241