Remedy - Server - What is the Maximum recommended Latency Time between the Clients & Servers for problem-free Remedy.  Do we have any guidelines or requirements for network performance?

Version 2
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Remedy AR System Server


    APPLIES TO:

    BMC Remedy AR System Server



    QUESTION:

    Is it possible to determine what the minimum or average ping times necessary to allow the User tool to successfully login? What about other calls to send and receive data? This is what the customer is describing:

    We're having problems with people logging into our server from other locations in the US. Especially if our company Intranet is busy.

    The router/firewall people have traced the login requests from various client PCs and they feel that they see:

    1) Client sends login request to server.
    2) Server responds.
    3) Client sends another login request before it receives original response.
    4) Server responds again.
    5) Client sends another login request before it sees next server response.
    6) This apparently continues until the client errors out.

    This occurs only when the network is very busy, and the network folks feel that the Client isn't waiting long enough for its response.

    Question: What is the Maximum recommended Latency Time between the Clients & Servers for problem-free Remedy.

    They say, for example, "4-Hops", well, 4-hops on Gigabit and 4-hops on 10Mb are different. So, what's the 'average' Ping times that Remedy would like to see for this 4-hop 'general rule'.


    Do we have any guidelines or requirements for network performance?


    ANSWER:

     

    Legacy ID:KA332069

    There is no magic number. In fact, we don't resend anything under our control. We either get a response or we don't. The actual retry logic and timeout settings for retry are at the TCP level and we don't do any configuration or option setting at that level. The only time we will resent in this scenario is because we have made contact and are the wrong protocol so we need to try an older one 
    or if the user presses the login button again (after a timeout that is in the range of 1 minute). 

      

     


    Article Number:

    000019014


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles