01-09-2003 04:52 AM
Hi,
We are experincing problems with the Cache engines, they have been operational for around a year with good savings, and are currently running on ver 4.2.3. The problems started occuring after implementing QoS on the core links. While running Qos it works fine for around a day with no slow response issues, after which it slows down to around a minute to load a browser page (Intranet based site). Are there any know problems with deploying QoS with the CE's, I have a zero drop bit rate on the policy to which the CE traffic is being allocated and has got a high preference and 50% bandwidth percentage.
Attached is a copy of the config of the CE:
dns-cache size 4096
!
http authentication header 407
http append x-forwarded-for-header
http authenticate-strip-ntlm
http cache-cookies
http client-no-cache-request revalidate
http proxy incoming 8080
http proxy outgoing origin-server
http max-ttl days text 3 binary 10
!
ftp proxy incoming 8080
!
clock timezone Africa/Johannesburg 0 0
!
!
!
ip domain-name alexanderforbes.net
!
!
!
https proxy incoming 443
!
interface FastEthernet 0/0
ip address x.x.x.x 255.255.255.0
no autosense
bandwidth 100
full-duplex
exit
interface FastEthernet 0/1
no autosense
bandwidth 100
full-duplex
shutdown
exit
!
!
ip default-gateway x.x.x.x
!
primary-interface FastEthernet 0/0
!
!
ip name-server a.b.c.d
!
!
logging console enable
logging console priority debug
!
!
bypass auth-traffic enable
!
pre-load enable
pre-load depth-level-default 10
pre-load concurrent-requests 5
pre-load traverse-other-domains
pre-load url-list-file /local1/afurl.txt
pre-load fetch domain news24.co.za cnn.com alexanderforbes.co.za alexanderforbes.com bday.co.za zafinance.co.za msn.co.za google.com
!
!
!
!
!
!
rule enable
rule block url-regex .*\cmd.exe
rule block url-regex .*/root.exe
rule block url-regex .*/default\.ida
rule block url-regex ^http://.*/default\.ida$
rule block url-regex ^http://.*www\.worm\.com/default\.ida$
rule no-cache url-regex .*aw-cgi.*
rule no-cache url-regex .*cgi-bin.*
!
!
transaction-logs enable
transaction-logs archive interval every-hour every 15
transaction-logs sanitize
transaction-logs export enable
transaction-logs export compress
transaction-logs export interval 15
transaction-logs export ftp-server 172.17.20.105 cisco **** /
transaction-logs export ftp-server 172.17.20.106 cisco **** /AFJHB1CE507
!
!
username admin password 1 O4AnUJw9jCklE
username admin privilege 15
!
snmp-server enable traps content-engine disk-read
snmp-server enable traps content-engine disk-write
snmp-server enable traps content-engine transaction-log
snmp-server enable traps entity
snmp-server enable traps snmp authentication
snmp-server enable traps snmp cold-start
snmp-server host 172.25.254.3 public
snmp-server community public
snmp-server notify inform
!
!
!
ntlm server domain aforbes
authentication login local enable primary
authentication configuration local enable primary
!
!
!
!
!
Any assistance will be appreciated.
Thanks
01-15-2003 05:54 AM
There is nothing I'm aware of.
It would be interesting to capture a sniffer trace in front of the CE to see what's going on when everything is ok and everything is slow.
Do you set the precedence correctly for traffic originated by the CE ?
If you put low priority, this could be the reason of the delay.
Regards,
Gilles.
01-17-2003 08:34 AM
One possibility is that you have a DNS issue from the CE so that the lookups are timing out.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide