This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies. For details on cookie usage on our site, read our Privacy Policy
At peak hours we have about 300-400 syslog messages/second. If there are no limits at all, then i guess using the built-in would be able to put the management plane to 100% usage if a loop occurs. And that would be a bad thing 🙂
... View more
The suggested solution almost solved the problem. The users still - but rarely - see the timeout issue. The solution changed the problem from being unacceptable and annoying, to an acceptable occurence.
... View more
We use the Syslog integration in the PAN Agents to forward User/IP-mappings from our wireless controllers to PA 5020 firewalls. We are considering to move the Syslog integration to connect directly with the PA5020 instead of the PAN Agents. But i remember having read something about limitations on the built-in Syslog reciever. That we should still use the PA Agents for "large scale use". I have now searched for hours for a document describing how many mappings (or other nubmers/limits) the built-in Syslog kan handle. But with no luck. Can anyone help with information about what can be expected by the built-in Syslog listener? Our setup is: 30 PA agents in different Active Directory domains forwarding userinformation. 30 Wireless controllers forwarding userinformation to the seperate PA agents. In total there's about 50.000 IP mappings where about 35.000 comes from Syslog.
... View more
Thanks Karthik - I will try it and get back if it worked. I will try changing the timeout settings first - and if i doesn't work, then the application override method.
... View more
Description We are experiencing a timeout problem when using outlook/exchange across the PA firewall. When the RPC connection between Outlook and Exchange is idle, the PA apparently terminates the connection. This causes the Outlook client to hang/stall until restarted - and thereby establishing a new RPC connection. When the timeout occours, a Baloon-message appears from the taskbar telling that Outlook is trying to fetch data from the Exchange-server running the CAS role. Problem exist on various combinations of client and server We have seen this with Outlook 2007/2010 and 2013, and Exchange 2007 and 2010. Current workaround Using Exchange cached mode in the Outlook client causes the client to communicate with Exchange in another way. The timeout error does not appear in this configuration. What have we already tried? We have read that Exchange sents a keep-alive beacon every 2 hour through the RPC connection. We have tried adjusting this to a lower value - without succes. So instead we tried raising the Session Timeout for TCP to 7200 seconds. But this didn't help either. It worked before changing to PA We didn't experience this problem earlier when using the Microsoft TMG "firewall". But i guess they detected the trafic and didn't let it timeout. My question is - Is any one else experiencing the same problem? If yes - have you found a solution? I guess it is a general problem when using RPC through the PA.
... View more