Configuring Virtual Networks > Implementing Virtual Networks
Was this helpful?
Implementing Virtual Networks
Netvisor ONE uses Virtual Networks (vNETs), an abstract network resource realized across a fabric of Pluribus Networks switches. Using vNETs, you can segregate a physical fabric into many logical networks, each with separate resources, network services, and Quality of Service (QoS) guarantees. A vNET allows you to completely separate all traffic in one vNET from the traffic of other vNETs.
Figure 1:Using vNETs with Netvisor ONE
 
Each vNET has a single point of management. As the fabric administrator, you can create vNETs and assign ownership of each vNET to individuals with responsibility for managing those resources. You can create separate user names and passwords for each vNET manager. Using the separate vNET administration credentials, the vNET admin can use Secure Shell (SSH) to connect to the vNET manager and access a subset of the Netvisor ONE CLI commands to manage that vNET. This way, multiple tenants can share a fabric with each managing a vNET with security, traffic, and resource protection from other vNETs.
vNETs can create very flexible and complex network architectures. For example, a Pluribus Networks switch, or a fabric of switches, can be used to create multiple tenant environments in an OpenStack deployment. In Figure 1 Using vNETs with Netvisor ONE, the diagram displays three vNETs, each with a management interface and a data interface.Netvisor ONE assigns each vNET an IP address pool used for DHCP assignment of IP addresses to each node, server, or OS component.
Underlying each vNET lies the vNET manager. Each vNET manager runs in a zone. When you create services for a vNET, the services occupy the same zone on a switch. Netvisor ONE designates a shared service and created by default when creating services. However, each zone can only support a single instance of a service. If you need a second service instance for a vNET, then it needs to occupy a separate zone. Netvisor ONE designates the zone as a dedicated service. In most cases, you can create services as shared unless you specifically want to create a dedicated service.
When you create a fabric, Netvisor ONE automatically creates a vNET with the name fabric-name-global. This vNET owns all resources within the fabric, and as you create new vNETs, resources move from the default vNET to the new vNETs. Global services remain in the default vNET unless assigned specifically to a vNET.