Recently viewed tickets

Log out

SiteManager GUI - GateManager & Agents

The basic GateManager functionality enables monitoring and control of this SiteManager. Using additional GateManager Agents in this SiteManager, the GateManager's monitoring and control capabilities can be extended to the devices attached to this SiteManager.

The SiteManager can support several types of Agents, and new Agent types can be installed (as a firmware plugin) at any time.

See Appendix F: Agent Type-Specific Parameters for a detailed description of all supported agents.

Note: In order to make use of an Agent, after you create it here, you may need to create an appropriate Alert Rule in the GateManager and then attach the Alert Rule to the Agent. Consult the GateManager Reference Manual for more information.

The Status column shows the status for each of the configured Agents. The following status codes may occur:

  • IDLE, UP:nn - the device is operational and ready to relay traffic.
    The UP:nn status indicates that there are nn active connections.
  • DOWN - the device is down.
  • STARTING - the Agent is trying to determine the device state.
  • WAIT - the device is up, but the Agent has not yet been acknowledged by the GateManager.
  • N/C - the device is up, but this LogTunnel Client is Not Connected to a LogTunnel Master.
    This indicates that either the Client is not yet linked to a LogTunnel Master in GateManager - or that the linked Master is offline.
  • ERROR - local configuration error; see the System Log for details.

To create and start an Agent to monitor an attached device, click on the New button, and fill in the new Agent settings:

  • Disable
    You can disable an Agent if you want to temporarily stop the GateManager's monitoring and control of the attached device.

  • S/N (Serial Number)
    Here you must enter a unique identification for the attached device. This is the identity that the GateManager uses internally to distinguish this specific Agent from any of the other Agents known by the same GateManager. If more than one Agent has the same Agent Serial Number, only one of them will be visible in the GateManager.

    When you create a new Agent, a Serial Number is automatically generated for the Agent based on the serial number of this SiteManager followed by # and a sequence number. For example, if the SiteManager's own serial number is 00:00:24:12:34:56, an automatically proposed Agent Serial Number might be 000024123456#03 (the digits before the # character is automatically hidden to reduce clutter on the screen).

    You may use the proposed serial number or overwrite it. If you overwrite it, be sure to use a string that you know will uniquely identify the Agent, e.g. the Ethernet MAC address of a network-attached device. If what you enter starts with #, the string will be used together with this SiteManager's serial number. For example, if you enter #wiggly, and SiteManager's own serial number is 00:00:24:12:34:56, the Agent Serial Number will be 000024123456#wiggly.

  • Device Name
    Enter the name or other ID (maximum 47 characters) used by the LinkManager operator and GateManager Administrator to identify this particular Device Agent, corresponding to the %n field code in the Agent Name Format . This field must not be left blank.
    With the default Agent Name Format, %n (%M) , the GM Appliance Name for this SiteManager is automatically appended to the specified Agent Name to create a GateManager Appliance Name for the Agent. This makes it easy for the GateManager Administrator to identify the SiteManager that hosts this Agent. For example, if this SiteManager's GM Appliance Name is test94 and you enter device-17 as the Agent Name on this page, the GateManager Appliance Name for the agent will show up as device-17 (test94).

  • Device Group
    Often a group of devices are logically related, meaning that a LinkManager user should get access to all the devices in the group at the same time, but not to any of the other devices attached to the same SiteManager.

    To group devices together, prefix the Group Name to the Device Name using the following syntax:
    $ group name : device name
    That is: a dollar sign , followed by the group name , a colon , some optional whitespace , and finally the device name .

    Group names can be freely chosen as long as the total length of the Device Name field does not exceed 47 characters, for example: "$group1: device1", "$group1: device2", "$group2: device1", and "$group2: device2".
    Note: The exact same characters must be used to identify a group; for example, "line1" and "line 1" identifies two different groups.

  • Device Type
    Here you select the proper Agent type corresponding to the type of the attached device. Agent types may be either a Custom Agent like the Ping Agent which can check for the presence of any kind of network-attached device, or a product specific Device Agent which provides automatic configuration of the necessary relay services for remote monitoring and control from a LinkManager.

  • Device IP & Parameters
    You can enter the specific parameters for this Agent in this field. The actual format of this field depends on the type of Agent.

    It is highly recommended that you use the icon to enter and edit the agent parameters.

  • Tunnel
    When a checkbox is present here, you can enable LogTunnel access to this device (the agent becomes a LogTunnel Client in GateManager).

  • [Properties icon]
    Press this icon to open the detailed parameter entry page for this particular Agent (see Appendix F: Agent Type-Specific Parameters ).

  • [Wastebin icon]
    Press this icon to delete this Agent entry.

  • Comment
    You can enter a comment further identifying this Agent or the attached device.
Creation date: 11/12/2019 13:23 (skr@secomea.com)      Updated: 16/01/2020 10:37 (skr@secomea.com)