Services🔗
Services are Layer-2 broadcast domains (VLANs) that are optionally routed through the Layer-3 fabric as VXLAN frames. Services enable devices connected to different parts of the network to appear to be in the same local segment. Layer-3 addressing and routing can be optionally enabled for each service to support IP packet forwarding as well as DHCP relay services. A service is linked to a tenant for further isolation of network reachability.
Creating a Service🔗
- From within the Services window (Tenancy -> Services) select the Tenant to assign the Service to.

- Click the Add a new Service button. Type a name in the field that appears and click Create Service

- The Service Enable switch defaults to off. The Tenant field shows which tenant the Service is assigned to

| Setting | Value | Description |
|---|---|---|
| Layer-2 VLAN | Required | The 802.1q VLAN tag to be used on the provisioned switch ports. |
| Layer-2 VNI | (Autoassigned) | Specifies the VXLAN VNID number if the user wishes to override the automatic assignment. |
| Anycast Address | Optional | Comma-separated lists of anycast gateway addresses for IPv4 and IPv6 subnets. Each anycast address serves as the default gateway for a different subnet within the same VLAN, enabling Layer-3 routing and reachability across multiple subnets. |
| DHCP Relay | Optional | Enables DHCP packet forwarding to a central DHCP server(s) for address requests. |
| MTU | Optional | Maximum Transmission Unit for the Layer-2 segment. This is either automatically generated or not required. |
Note
You must set the DHCP source address range in the Tenant Layer 3 section described below in order to support DHCP Relay. The DHCP Source address range is used by Verity to create loopback addresses within each Leaf switch to serve as the source address for the DHCP requests for the tenant when it is configured on the switch)
- Click the Enable checkbox to enable the Service. This will place the Service into Edit Mode.
- Fill out any required fields.
- Click Save.
Enable Layer-3 Anycast IP/Mask on a Service🔗
Note
Prior to enabling Tenant-to-Tenant routing your chosen Tenant must have a Service with a Layer-3 Anycast IP/Mask field set.
