AMETHYST: Remote Monitoring and Maintenance

All documents from the original Software Support Library (SSL)

Moderators: Leon van Heerden, Luanda_Junzi, Belinda Frick, Lee Hendricks

AMETHYST: Remote Monitoring and Maintenance

Postby Odette Danster » Thu Nov 25, 2010 4:58 pm

Please note that this post has been replaced with this post: AMETHYST: Remote monitoring and Maintenance

AMETHYST Remote Maintenance and Monitoring requires the following configuration at the client:

  • The Datatex monitoring software will connect from IP 129.232.154.30 to the client's Internet addressable IP on the ports below. The Firewall must then forward the traffic to the Amethyst server.
  • For security purposes the traffic should be restricted to our static IP address(129.232.154.30) to ensure no one else can connect to this facility.

129.232.154.30 [TCP RANDOM PORT] -> CLIENT-IP [TCP port 10022]
129.232.154.30 [TCP RANDOM PORT] -> CLIENT-IP [TCP port 27007]

CLIENT-IP [ TCP RANDOM PORT ] -> notifications.datatex.co.za (129.232.154.30) [ TCP port 443 ]

License access
CLIENT-IP [ TCP RANDOM PORT ] -> license.datatex.co.za(129.232.154.30) [ TCP port 443 ]
See example below
Cap.JPG


Requirements

  1. Remote Monitoring Requirements

      A TCP Connection from Datatex (IP 129.232.154.30) to the Client's Firewall on port 27007 must be forwarded to the internal IP address of the Amethyst Server on TCP port 27007.
    Note:
    1. The remote monitoring will not be used with VPN access.
    2. The Monitor port is a proprietary protocol and doesn't allow remote access to the server.
    3. If this port is not correctly configured, the remote monitoring will not work.
    Please supply Datatex with public IP to enable remote monitoring for your site.

  2. Remote Maintenance Requirements:

    1. The Client's Firewall needs to forward the TCP port 10022 to the Amethyst server's IP on TCP port 22. The traffic must be restricted to the external Datatex IP 129.232.154.30. (If port 10022 can not be redirected, please use TCP port 22 and forward it to the Amethyst's IP on TCP port 22).
    2. If the installation is a virtual machine a additional port will be required:
      TCP port 443 to license.datatex.co.za
    Please supply Datatex with the public IP and port (22 or 10022) to connect to via SSH when remote maintenance is required.
What Datatex cannot do with Remote Monitoring/Maintenance access?
  • Physically checking cables/krone blocks and lights on the cards.
  • Check or install Client software like the USBClient or AMTClient
  • Anything physically on the agent PC's like the USBTap.
  • If you are unable to playback recordings on the AMETHYST Supervisor, we also need to be onsite to check the problem since it is a PC specified issue.
What Datatex can do with Remote Monitoring/Maintenance access?
  • Datatex can access the Amethyst Server. We have access to the web interfaces. This means we can check settings, licenses, Supervisor access, etc.
  • We can check call data, recordings or other information received on the Amethyst Server.
  • We can see events for recorded devices on the Cardserver.
You do not have the required permissions to view the files attached to this post.
Odette Danster
 
Posts: 126
Joined: Thu Nov 18, 2010 12:01 pm

Re: AMETHYST: Remote Monitoring and Maintenance

Postby Belinda Frick » Fri Apr 13, 2018 8:47 am

The IP of 196.211.90.134 has been replace with 129.232.154.30.

Allow access for monitoring / maintenance from 129.232.154.30.
Belinda Frick
 
Posts: 3808
Joined: Fri Nov 12, 2010 4:25 pm


Return to Support Archive's (Amethyst)

Who is online

Users browsing this forum: Google [Bot] and 1 guest

cron