Silent Brick System
Breadcrumbs

Establish remote connections

Create remote connection

  • ➤ Open the user interface of the target system.

  • ➤ Navigate to 'Settings' -> 'Connections'.

  • ➤ Click on 'Create Endpoint'.

StJcHW2DsUYHpJuA.full
  • ➤ Assign a name under 'Endpoint Name'.

  • ➤ Provide a description.

  • ➤ Click on 'Create'.

mkqq2WduIbWo2VAp.full
  • ➤ Select the endpoint.

  • ➤ Download the endpoint from the target system.

cAwwvK4XbnMLJUMW.full
  • ➤ Open the user interface of the source system.

  • ➤ Navigate to 'Settings' -> 'Connections'.

  • ➤ Import the endpoint configuration.

4wBYhG11e13kyxmG.full
  • ➤ The connection is established when...

    • ➤ ...the status shows 'Established'.

    • ➤ ...a current value is displayed under 'Last Seen'.

  • ➤ If the connection is not established, check the following...

    • ➤ ...a connection from source to destination IP is possible

    • ➤ ...ping from source to destination is permitted

    • ➤ ... TCP port 22 from source to destination is permitted

Configure NAT

In some cases, the target system may not be directly reachable via its native IP address, but only accessible through forwarding behind a firewall or router. Thus, the target system externally has a different IP address than the one actually assigned internally by the device. This is referred to as Network Address Translation, or NAT.

If such a situation exists, the NAT setting can be enabled and configured after importing the endpoint configuration. Proceed as follows:

  • ➤ Open the web interface of the source system

  • ➤ Navigate to "Connections"

  • ➤ Open the context menu of the affected connection via right-click.

  • ➤ Select "Use NAT Address."

3q1MVoKFK6HU4tvy.full
  • ➤ The NAT settings dialog will open.

G2kGc1XkJ53jnIJx.full
  • ➤ Enter the external IP address of the target system under IP Address of NAT/Firewall.

    • ➤ Specify the port assigned externally for forwarding to the internal port 22 (default: 22).

  • ➤ Save the settings.

Configure Floating IP

The use of Floating IP addresses requires static IP addresses. When using the Floating IP, all archives must be taken offline before any network changes. A change to the data network IP address requires reconfiguration of the Floating IP.

For replication of Compliant WORM archives, a Floating IP can be configured on the host connection.

The Floating IP is a third IP address that automatically switches to the Replica in the event of a failure of the source system. Thus, the system remains continuously available under the Floating IP address.

Configuring the Floating IP requires an existing remote connection with static IP addresses.

  • ➤ Switch to the source system of the replication.

  • ➤ Select the corresponding remote connection.

  • ➤ Open the context menu by right-clicking.

mMxngREmERrrngx4.large
  • ➤ In the submenu “Floating IP,” select the “Setup” option.

4ynuFCHWsMhBFADl.large
  • ➤ Define the desired Floating IP address.

6qPtRHcLCjBF5fwE.full
  • ➤ Select a switching mode.

    • ➤ “If One Compliant Archive is Unavailable”: Switching occurs as soon as a single Compliant archive becomes unavailable.

    • ➤ "If Network Resources Fail": The switch is triggered when the network connection fails.