Skip to main content
Migration Notice
We're migrating documentation from the old portal into this one. Some things may look a little different or out of place in the meantime — we know, and we're working to get it right. If something's unclear or doesn't look right, let us know.
Version: 4.4.0

Configuring Eyeglass with Dual NIC Environments

Introduction

Some environments don't allow a single VM to reach both the source and target clusters over one network interface, due to security or network design requirements. This guide covers configuring Eyeglass with a second NIC and static routes so it can reach clusters on separate networks.

Prerequisites

  1. SSH to Eyeglass as admin, then sudo -s.
  2. Shut down the appliance:
    shutdown
  3. In vCenter/vSphere, add a second NIC to the Eyeglass VM (use the e1000 NIC type).
  4. Attach the new NIC to the second virtual switch.
  5. Power the VM back on.
note

Eyeglass must be able to reach each cluster's platform API and SSH over the corresponding IP network.

Adding a Static Route

Assume a single Eyeglass appliance with two NICs — one configured at 10.105.16.100, the other at 10.105.17.101. To add a route so the second NIC can reach its cluster:

  1. SSH to the Eyeglass appliance, log in as admin, then sudo -s to become root.
  2. Run:
    yast2
  3. Tab to Network Settings, then tab to Routing.
  4. Tab to the Add button and press Enter.
  5. Enter the destination IP and subnet mask.
    note

    Use CIDR notation (e.g. /24) rather than 255.255.255.0 — using the dotted-decimal form here will cause an error.

  6. Tab to OK and press Enter. The new route now appears in the routing table (these routes are persistent across reboots).
  7. Adjust each cluster's network configuration as needed for your environment.
note

In a simple network where the cluster is on the same subnet as one of the Eyeglass NICs, a router is typically the next-hop address in the static route for one cluster, while the default route (0.0.0.0) is used to reach the other cluster.