diff --git a/dhcp-and-dhcp-relay.rst b/dhcp-and-dhcp-relay.rst index ce9f4b0e..fa638f04 100644 --- a/dhcp-and-dhcp-relay.rst +++ b/dhcp-and-dhcp-relay.rst @@ -42,6 +42,37 @@ Netris also enables you to define Custom DHCP Options.
+Netris DHCP +=========== + +To enable Netris' built-in DHCP service on an L2VPN V-Net: + + - Add a gateway to the V-Net — native DHCP requires a gateway. + - Check the DHCP checkbox next to the gateway IP address. + - Provide a starting and ending IP address for the DHCP scope. + - Select a DHCP Options Set. + +.. note:: + A DHCP Options Set is required to enable Netris DHCP — Netris does not currently ship a default option set, so one must be created (see DHCP Option Sets above) before DHCP can be enabled on a V-Net. + +.. image:: images/dhcp-builtin.png + :alt: Netris DHCP configuration in V-Net settings + :align: center + :class: with-shadow + +.. raw:: html + +

Figure: Netris DHCP configuration in V-Net settings

+ +SoftGate–Controller dependency for Netris DHCP +----------------------------------------------- + +Netris DHCP has no hard dependency on the Controller for day-to-day service. The active SoftGate's local DHCP server hands out leases from its own local leases file, independent of Controller reachability — if the Controller is unreachable, the SoftGate keeps issuing dynamic leases on its own, from its last Controller-synced configuration, which the Netris agent caches locally. + +The Controller's role is keeping IP assignments stable across a SoftGate failover: the Netris agent on the active SoftGate pushes each new lease up to the Controller, which converts it into a static IP–MAC reservation and syncs it back down to every SoftGate as a static binding. That round trip isn't instantaneous — if the SoftGate serving DHCP for a V-Net fails over before a given client's lease has completed the round trip and been written into every SoftGate's static bindings, the newly active SoftGate has no record of that client yet and may hand it a different dynamic IP. + +The Controller's reservation set persists independently of most V-Net edits: setting a V-Net to inactive preserves it, so DHCP can't hand a previously leased IP to a different endpoint and create a conflict once the V-Net is reactivated, and changing the lease range doesn't clear it either. Unchecking DHCP, or removing the V-Net's IP subnet and saving, resets it; deleting the V-Net cleans it up entirely. + DHCP Relay ========== Netris supports using an external DHCP server by enabling the DHCP Relay function. This allows DHCP clients inside a V-Net to obtain addresses from a non-Netris-managed DHCP server running in the same or another VPC. Both DHCPv4 and DHCPv6 are supported. @@ -73,6 +104,13 @@ To configure DHCP Relay in a V-Net:
+DHCPv6 Relay: Switch Loopback IPv6 Address +------------------------------------------- + +When DHCPv6 Relay to a third-party server is configured (Address Family set to IPv4/IPv6 Dual-Stack or IPv6-Only), Netris derives an IPv6 loopback address for the switch and assigns it, as a /128, to the loopback interface in the relevant VRF(s). This address is used as the source address of relayed DHCPv6 traffic, the same role the switch's existing IPv4 loopback plays for DHCPv4 relay. + +The address is not randomly generated — it's deterministically derived from the switch's existing main IPv4 loopback address: Netris takes the IPv4 loopback address, converts it to hex, and uses that as the lower 32 bits of an address in the ``fd00::/8`` unique local address range. For example, an IPv4 loopback of ``10.2.3.4`` produces the IPv6 loopback ``fd00::0a02:0304/128``. + Example: """""""" diff --git a/images/dhcp-builtin.png b/images/dhcp-builtin.png new file mode 100644 index 00000000..576108ef Binary files /dev/null and b/images/dhcp-builtin.png differ diff --git a/introduction.rst b/introduction.rst index a00a4ee2..cb05efaa 100644 --- a/introduction.rst +++ b/introduction.rst @@ -35,7 +35,7 @@ A traditional enterprise or cloud data center is typically built around a single * **East-West (backend, scale-out) fabric.** A dedicated, high-bandwidth, lossless network that connects GPU servers directly to each other for collective communications — the all-reduce, all-gather, and all-to-all traffic patterns generated by distributed training and large-model inference. The backend fabric carries no client traffic and is sized very differently from the frontend. It can be implemented over Ethernet (e.g., NVIDIA Spectrum-X), or over InfiniBand using NVIDIA Quantum. Netris manages both. Some teams call this the *backend network* or *scale-out network*. -* **NVL72 (rack-scale) fabric.** An NVLink-based, in-rack fabric that connects up to 72 GPUs in a single liquid-cooled rack into one NVLink domain, so the rack behaves as a single logical accelerator. NVL72 ships with NVIDIA GB200 NVL72 and GB300 NVL72 rack-scale systems. NVLink switching inside the rack is managed by NVIDIA NMX (NVLink Management Software). +* **NVL72 (rack-scale, scale-up) fabric.** An NVLink-based, in-rack fabric that connects up to 72 GPUs in a single liquid-cooled rack into one NVLink domain, so the rack behaves as a single logical accelerator. NVL72 ships with NVIDIA GB200 NVL72 and GB300 NVL72 rack-scale systems. NVLink switching inside the rack is managed by NVIDIA NMX (NVLink Management Software). * **Out-of-band (OOB) management fabric.** A separate management network used to reach the management interfaces of every device in the deployment — Ethernet switches, InfiniBand switches, NVLink switches, DPUs, server BMC/IPMI, PDUs, environmental controllers, and orchestration platforms. The OOB fabric carries no tenant traffic. It can be deployed as part of the North-South fabric or as a standalone fabric, depending on the operator's availability objectives. diff --git a/netris-architecture.rst b/netris-architecture.rst index 650697ca..df5d9635 100644 --- a/netris-architecture.rst +++ b/netris-architecture.rst @@ -18,7 +18,7 @@ Every Netris deployment — whether you are running a traditional Ethernet data * **Netris Switch Agent** — software running on every Netris-managed switch. Translates controller intent into vendor-specific switch configuration and reports telemetry back to the controller over an outbound, encrypted gRPC channel. -* **Netris SoftGate** (VPC Gateway) — optional but adopted by 95% of Netris customers. A multi-tenant, horizontally scalable, XDP accelerated software edge that provides ingress and egress services for VPCs — elastic IPs, NAT, tenant-specific connectivity, and L4 load balancing — and runs on operator-provided bare-metal x86 servers at the edge of the North-South fabric. +* **Netris SoftGate** (VPC Gateway) — optional but adopted by 95% of Netris customers. A multi-tenant, horizontally scalable, XDP-accelerated software edge that provides ingress and egress services for VPCs — NAT (SNAT and DNAT), tenant-specific connectivity, and L4 load balancing — and runs on operator-provided bare-metal x86 servers at the edge of the North-South fabric. These three components are present in every Netris deployment. If you are running a traditional data center without a GPU cluster, this is the whole picture. @@ -75,7 +75,7 @@ Infrastructure devices managed by Netris establish **outbound** connections to t Netris SoftGate =============== -Netris SoftGate (also known as VPC Gateway) is a multi-tenant, horizontally scalable edge gateway for cloud providers. SoftGate provides elastic IPs, NAT, tenant-specific connectivity, and L4 load balancing — complementing physical network multi-tenancy with cloud networking functionality that switches alone cannot provide. The SoftGate software runs on a dedicated set of operator-provided bare-metal x86 servers at the edge of the Netris-managed North-South fabric. 95% of Netris customers have opted to add SoftGate to their Netris-managed switch fabrics. +Netris SoftGate (also known as VPC Gateway) is a multi-tenant, horizontally scalable edge gateway for cloud providers. SoftGate provides NAT (SNAT and DNAT), tenant-specific connectivity, and L4 load balancing — complementing physical network multi-tenancy with cloud networking functionality that switches alone cannot provide. The SoftGate software runs on a dedicated set of operator-provided bare-metal x86 servers at the edge of the Netris-managed North-South fabric. 95% of Netris customers have opted to add SoftGate to their Netris-managed switch fabrics. You can learn more about SoftGate architecture and deployment scenarios in the :doc:`Netris SoftGate HS ` document. diff --git a/network-policies.rst b/network-policies.rst index 466a00ce..881c833b 100644 --- a/network-policies.rst +++ b/network-policies.rst @@ -9,7 +9,7 @@ Netris VPC The Netris VPC offers you the ability to operate your resources within a logically segregated virtual network. You can create, edit, and remove VPCs as needed. The VPC acts as a VRF in traditional networking, providing the flexibility to employ overlapping IP ranges across various VPCs while maintaining secure management and operation of resources. -Netris Controller ships with one VPC (VPC-1) pre-provisioned; it cannot be deleted. VPC-1 carries two distinct roles at once — it is both the **System VPC** (the trust boundary and anchor for infrastructure objects such as switch loopbacks and SoftGate-terminated BGP/NAT/load-balancer traffic) and the **Default VPC** (the VPC the Controller substitutes for the required VPC field when a value isn't explicitly given, and the one pre-populated in "Add new" dialogs in the web UI). These are different concepts that happen to be the same VPC by default. See the Netris VPC page for the full explanation and for the list of objects that belong to a VPC, before creating additional VPCs. +Netris Controller ships with one VPC (VPC-1) pre-provisioned; it cannot be deleted. VPC-1 carries two distinct roles at once — it is both the **System VPC** (the trust boundary and anchor for infrastructure objects such as switch loopbacks and SoftGate-terminated BGP/NAT/load-balancer traffic) and the **Default VPC** (the VPC the Controller substitutes for the required VPC field when a value isn't explicitly given, and the one pre-populated in "Add new" dialogs in the web UI). These are different concepts that happen to be the same VPC by default. See :doc:`vpc` for the full explanation and for the list of objects that belong to a VPC, before creating additional VPCs. The following diagram shows a VPC concept in the Netris Controller. diff --git a/supported-switch-hardware.rst b/supported-switch-hardware.rst index df4c89df..7dd6167b 100644 --- a/supported-switch-hardware.rst +++ b/supported-switch-hardware.rst @@ -370,9 +370,16 @@ Arista - - ✔ * - Arista - - 7280R3A - - Jericho2 - - 144 x 100G or 36 x 400G + - 7060X6-32PE + - Tomahawk 5 + - 32 x 800G OSFP + - EOS + - + - ✔ + * - Arista + - 7060X6-64PE + - Tomahawk 5 + - 64 x 800G OSFP + 2 x SFP+ - EOS - - ✔ @@ -384,16 +391,16 @@ Arista - - ✔ * - Arista - - 7358X4 - - Trident-4 - - 128 x QSFP or 32 x OSFP / QSFP-DD + - 7280R3A + - Jericho2 + - 144 x 100G or 36 x 400G - EOS - - ✔ * - Arista - - 7368X4 - - Tomahawk 3 - - 128 x 100G or 32 x 400G + - 7280R4 + - Jericho3+ + - Up to 32 x 800G - EOS - - ✔ @@ -404,6 +411,20 @@ Arista - EOS - - ✔ + * - Arista + - 7358X4 + - Trident-4 + - 128 x QSFP or 32 x OSFP / QSFP-DD + - EOS + - + - ✔ + * - Arista + - 7368X4 + - Tomahawk 3 + - 128 x 100G or 32 x 400G + - EOS + - + - ✔ * - Arista - 7500R3 - Jericho, Jericho2 @@ -411,3 +432,10 @@ Arista - EOS - - ✔ + * - Arista + - 7700R4 + - Jericho3-AI + - Per leaf: 18 x 800G host + 20 x 800G fabric (AI distributed Etherlink fabric, not a general leaf/spine switch) + - EOS + - + - ✔