Network interfaces
Each CID has a Corporate network interface and an Instrument network interface. Their separate roles keep instrument traffic isolated while allowing the CID to reach CID Hub, OpenLab services, and CDS clients. Both interfaces support automatic addressing through Dynamic Host Configuration Protocol (DHCP) or a static configuration.
Interface roles
The two interfaces serve different networks and must not share a default route.
| Interface | Role | Typical configuration |
|---|---|---|
| Corporate NIC | Connects the CID to the corporate network, CID Hub, the OpenLab Server, and CDS clients. | DHCP is required for initial activation. Automatic configuration is recommended; static configuration is available after activation. |
| Instrument NIC | Connects the Windows VM to an isolated instrument network. | Static address in the instrument subnet; no default gateway and normally no DNS server. |
warning
Leave Gateway Address (Not Recommended) blank on the Instrument NIC. A gateway can create a competing default route or allow instrument traffic to cross network boundaries.
Configuration fields
CID Hub displays these values for each interface.
| Field | Meaning |
|---|---|
| Configuration method | Automatic addressing or manually supplied values. |
| Connection state | Whether the operating system reports the interface as connected. |
| IP Address | The IPv4 address assigned to the interface. |
| Subnet Mask | The IPv4 subnet mask. |
| MAC Address | The physical interface address. |
| Gateway Address | The route used to reach networks outside the local subnet. Use this only on the Corporate NIC. |
| DNS Address | One or more DNS resolvers. These are normally required only on the Corporate NIC. |
| Domain Name | The DNS search domain reported by the interface. |
For requirements, see System requirements. For configuration instructions, see Configure network cards.
Last updated: