Service interfaces and UNIs

April 9, 2024

ID 256481

Service interfaces and UNIs are interfaces for connecting devices to transport and network services. These interfaces can be created on top of any OpenFlow interfaces except those corresponding to the WAN interfaces of the SD-WAN.

In turn, on top of service interfaces, you can create ACL interfaces that filter traffic between transport services based on specified constraints.

You can create all necessary UNIs in one UNI template, and then apply it to a CPE device when creating and registering that device. In this case, all UNIs from the template are automatically created on the CPE device.

The difference between UNI (user network interfaces) and service interfaces is that UNIs are used when creating network services, and service interfaces are used when creating transport services. In addition, service interfaces cannot be added to the graphical designer tool that is used to build the network service topology, or assigned to tenants.

Note that when you create a UNI, a corresponding service interface is automatically created for it, but for service interfaces, UNIs are not created.

In this section

Creating a service interface

Creating an ACL interface

Viewing the usage of a service interface and an ACL interface

Deleting a service interface and an ACL interface

Creating a UNI template

Creating a UNI in a template

Editing a UNI in a template

Deleting a UNI in a template

Deleting a UNI template

Creating a UNI

Editing a UNI

Deleting a UNI

Did you find this article helpful?
What can we do better?
Thank you for your feedback! You're helping us improve.
Thank you for your feedback! You're helping us improve.