- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2011 01:03 PM
Global load information:
Step Size:Dynamic Configured:10 Actual:10
Teardown-timer: Configured:20 Actual:2
Average Average Peak Average
Service Name Load Number ResponseTime Response Time
-----------------------------------------------------------------------
RRMH004 2 0 2110405
RRMH005 2 619427 1893706
Global load information:
Step Size:Dynamic Configured:10 Actual:10
Teardown-timer: Configured:20 Actual:20
Average Average Peak Average
Service Name Load Number ResponseTime Response Time
-----------------------------------------------------------------------
RRMH004 2 0 0
RRMH005 2 0 0
Solved! Go to Solution.
- Labels:
-
Application Networking
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2011 06:25 PM
Hi Alberto
I checked your configuration and looked fine.
So, if your problem is related to the high value of reponse time,
it maybe a server issue.
Regarding low performance issue of CSS, it may be related to
the flow idle timeout value. I've handled perfomance issue as
TAC SR and some of them were related to the idle timeout.
Since idle timeout of tcp is 16 seconds by default, flow will be
deleted from active flow list (show flows) if flow is idle more than
16 seconds.
If you want to change this idle timer, please configure as below.
CSS11503-A(config-owner-content[test-test])# flow-timeout-multiplier 100
BTW, your CSSes run about 800 days. I suggest you upgrade WebNS
or reboot CSSes since there are some bugs regarding 828 days issue
as follows:
CSCek37489 : CSS: Backup CSS sends invalid VRRP packets after long running
CSCsy38035 : CSS: After long run, Master of CSS detect Dup vrrp packet
Regards,
Yuji
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2011 07:17 PM
In general, high value of response time occurs due to slowness of server response.
So, I suggest you check the load of server application.
In the meantime, I'll check CSS.
What kind of probe do you configure on RRMH005?
Please let me know your keepalive configuration?
And also please get the following log?
CSS11503# llama
CSS11503(debug)# flow statistics
CSS11503(debug)# show system-resources
CSS11503(debug)# icp probe service RRMH005 [url by quoted text]
Regards,
Yuji
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2011 11:55 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2011 06:25 PM
Hi Alberto
I checked your configuration and looked fine.
So, if your problem is related to the high value of reponse time,
it maybe a server issue.
Regarding low performance issue of CSS, it may be related to
the flow idle timeout value. I've handled perfomance issue as
TAC SR and some of them were related to the idle timeout.
Since idle timeout of tcp is 16 seconds by default, flow will be
deleted from active flow list (show flows) if flow is idle more than
16 seconds.
If you want to change this idle timer, please configure as below.
CSS11503-A(config-owner-content[test-test])# flow-timeout-multiplier 100
BTW, your CSSes run about 800 days. I suggest you upgrade WebNS
or reboot CSSes since there are some bugs regarding 828 days issue
as follows:
CSCek37489 : CSS: Backup CSS sends invalid VRRP packets after long running
CSCsy38035 : CSS: After long run, Master of CSS detect Dup vrrp packet
Regards,
Yuji
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2011 10:16 AM
