Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi CommunityI'm facing a problem here together with writing files to a CIFS share.Reading warmed data from the same CIFS share is perfect and fast. For a 4.5MB Worddoc we do have like 0.5 seconds to download that from the share. If I upload the sa...
Having a ACE-Deployed for loadbalancing web-requests which are coming from a reverse-proxy. The session persistency is based on the x-forwarded-for HTTP-header entry. The situation works fine but in certain situations it looks like the ACE (172.16.3....
Hi allI'm currently troubleshooting a situation where the default-route (0.0.0.0) is disappearing.We have actually about 1500 OSPF Routes on a CSS 11506 which is also injecting the default-route for OSPF into the AREA 0 (there is only area 0).No, don...
I'm running in a problem where auto-discovery is failing. We have remote-offices with one router and one wae in inline deployment, so far so good, this works perfect.On the Main-Office we have two routers for redundancy, on the lan site we use hsrp.C...
Hi PeterWe've been able to track down that a software upgrade on the NetApp was the source of the problem.Initially the custemer used NetApp Ontap 7.3.2 which did work fine. After the upgrade to 7.3.5p1 and 7.3.5.1 we started seeing the slow CIFS pe...
Dear AshfaqI agree to your post. In normal conditions, my write is 4x slower then the reads, but this is not 28x slower what I expect here.Let me give you some more information:It takes about 1min to download a 100MB file from a CIFS share. This resu...
HiSo here some more information.We are running WAAS version 4.2.3b. The lines are various bandwidth from 2Mb/s up to 100Mb/s. Latency is 8-10ms.The thing I don't really understand is the big difference between read and write operation.Kind Regards-Lu...
I just verified "show stats http" and there is a zero (0) for max parslen errors and static parse errros, so we should be fine on the length and on the value we're expecting. Here the relevant snippets from the configuration. ! sticky http-header X...
