RMA on TCP port #5057" option is enabled, RMA Manager waits for incoming connection from the agent. ![]() The manager cannot connect to Active RMA due to nature of the agent. Note: you should use exactly the same name and password that were used when you setup Active RMA on remote Transmitted through the network without encryption. The password is required for every communication session between RMA and HostMonitor or RMA and RMA Manager.Īll traffic between RMA and HostMonitor or RMA and RMA Manager is encrypted and the password itself is never An empty password using is not permitted. Will accept connection from 1st started agent and reject connection from other agents with the same name You should not assign the same name for several agents. Network using temporary dial-up connection. Also Active RMAĪllows you to monitor system that does not have fixed IP address, e.g. ![]() This allows you to install RMA inside private network protectedīy firewall without necessity to open any TCP port (Passive RMA requires 1 open TCP port). Active RMA itself establishesĬonnection with HostMonitor and RMA Manager. That is not waiting for TCP connection from HostMonitor like Passive RMA. "no answer" (if no answer from agent received) or "bad answer" (if some error code was received from an agent, If RMA Manager was not able to get proper information from an agent, it sets its` status to If connection with an agent was established, RMA Manager updates all agent information and sets status of theĪgent to "operable". Regarding system where it is running on: hostname, Windows version, Service Pack, etc. With an agent and get information about agent: platform, version, comment, etc. RMA Manager will try to establish connection Here you should provide the same password that you have specified when an agent was installed andĪfter you have finished entering the above information click "Test/Get info" button to check the settings of anĪgent or click "Ok" button to check the settings and close dialog. Plus an amount of time that is necessary for data exchange between HostMonitor and an agent. When, for example, you are launching an external testĪnd an external program needs 15 seconds to perform this test then the timeout should be set to 15 seconds Please note: this timeout should be big enough to allow an agent to perform a testīefore sending an answer to HostMonitor. A maximum amount of time that RMA Manager or HostMonitor will wait for anĪnswer from the agent. Here you should specify the same port that you have already specified when that agent was installed andĬonfigured on a remote system (by default agent uses port #1055)Ĭommunication timeout in seconds. TCP port that will be used for communication between RMA Manager (or HostMonitor) and the agent. Name of the agent (this name will be displayed in agent's list, and will be used by HostMonitor for agent identification).īy default RMA Manager uses agent's addresses as names but you may specify any other name that you like Provide the host name or an IP address of the system where RMA is installed Provides information about test result back to HostMonitor. Is small application that accepts requests from HostMonitor, performs test (or action) and When the dialog "Agent Connection Parameters" appears set the following parameters Then you may click on "New agent" button or press Insert key in the list of agents or select "New" itemįrom "Agent(s)" menu. To add a record for a (new) agent you should choose appropriate list: Passive RMA list or Active RMA list.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |