Symantec Access Management

  • 1.  Effect of clustering and sockets per port

    Posted Feb 21, 2018 11:17 AM

    In our prod environment, we have 12 policy servers split evenly between 2 data centers.  In the past we always defined all 12 policy servers in the HCO for our customers.  Recently we have explored using clustering in the HCO by defining 2 HCO's; the first with one datacenter as primary and the other as the fallover and the reverse for the other HCO.  We then have our customers split up which HCO they use so that the app is split evenly over the datacenters.

     

    When we tested this out, we had one of our customers reporting that they were getting random 500 errors in their app.  Wondering if it would make sense that we would need to increase the max sockets per port since now we are actively using 6 policy servers instead of 12.

     

    We will test this theory out but looking for some input as to if our hypothesis sounds logical.

     

    Thanks



  • 2.  Re: Effect of clustering and sockets per port
    Best Answer

    Broadcom Employee
    Posted Mar 05, 2018 11:31 AM

    It is possible that the HCO changes have resulted in more connections from web agents to some of the policy servers.  The smps.log can be examined to see if any of the policy servers have been running out of connections.  The 500 errors the users are seeing should be tracked on the web agent to see if they were caused by the agent unable to connect to the policy server or a problem not related to policy server connections.