VS Fundamentals
Concepts
Admin-VS and common VS
A virtual system (VS) is classified as an Admin-VS or a common VS.
Common VS (VSn): The network administrator uses hardware-level and software-level emulation to partition a physical system (PS) into VSs. Each interface works only for one VS, and each VS runs individual routing tasks. VSs share software and hardware resources, including IPU.
Admin-VS: Each PS has a default VS named Admin-VS. All unallocated interfaces belong to this VS. The Admin-VS can process services in the same way as a common VS. In addition, the PS administrator can use the Admin-VS to manage VSs.
VS working modes
VSs work in independent management mode.
Flexible resource management: Resources are allocated using a resource template. The resource template can be modified dynamically to allocate resource. This mode improves VS resource management flexibility.
File-directory isolation: Each VS has its own file directory. A PS administrator can check all VS file directories, such as configuration files and log files, and access their contents. A VS administrator can only check and access its contents. This results in improved security.
Separate alarm reports: A VS reports its own alarms to the network administrator. Faults are located quickly, and VS security is guaranteed.
Independent starts and stops: A PS administrator starts, stops, or resets a VS without affecting other VSs.
VS-switches: When configuring or operating VSs, a PS administrator can switch between VSs.
After you create a VS, allocate logical and hardware resources to the VS.
Logical resources include u4route, m4route, u6route, m6route, vpn-instance.
Before you configure VSs, specify a port mode for the VSs.
A port mode determines the scope of resources allocated to a VS. Currently, only PORT mode is supported. In port mode, VSs share service resources that a PS provides, and some features can only be enabled on a single VS.
Resource template: By using a resource template, multiple logical resource items can be allocated to a VS at a time, which saves time of the user. After a resource template is modified, it must be loaded to the corresponding VS for the change to take effect.
In Figure 2-1, a PS is partitioned into VSs, VS1 carries voice services, VS2 carries data services, and VS3 carries video services. Each type of service is transmitted through a separate VS, and these services are isolated from one other. VSs share all resources except interfaces. Each VS functions as an individual router to process services.
VSs can be configured on both physical or logical interfaces, and an interface can only be assigned to a single VS. Logical interface configured on a physical interface work for the same VS in the PS to which the LC belongs.
VS partitioning does not require a PS, and a PS must have sufficient interfaces on which VSs can be configured.
VS Authority Management
Table 2-1 shows VS authority management.
Role |
Creating a VS |
Allocating Resources to a VS |
|---|---|---|
PS administrator |
√ |
√ |
VS administrator |
- |
- |
√: indicates that the function is supported.
-: indicates that the function is not supported.
A VS administrator can perform operations only on the managed VS, including starting and stopping the allocated services, configuring routes, forwarding service data, and maintaining and managing the VS.
On the NE20E, physical interfaces can be directly connected so that different VSs on the same Physical System (PS) can communicate.
