The IPCOM VX series provides the functions to deploy and manage multiple virtual network devices (IPCOM VA).
Resource Orchestrator can link each IPCOM VA with tenants in coordination with virtual fabrics using Ethernet fabric.
Figure J.2 Linking IPCOM VA and Virtual Fabrics with Tenants
When using virtual fabrics, a VFAB VLAN ID (S-TAG ID) for the fabric ID of each virtual fabric is configured independently. In order to enable communication between IPCOM VA and virtual fabrics, the S-TAG IDs of both the IPCOM VA and the virtual fabric must be the same.
There are following two patterns for matching the S-TAG IDs of IPCOM VA and virtual fabrics:
Configuration matching S-TAG IDs between IPCOM VA and virtual fabric
For details on configuration, refer to "Figure J.3 Relationship of S-TAG IDs of IPCOM VA and Virtual Fabrics".
Configuration matching S-TAG IDs between each interface of IPCOM VA and virtual fabrics
For details on configuration, refer to "Figure J.4 Relationship of S-TAG IDs of IPCOM VA and Multiple Virtual Fabrics".
Figure J.3 Relationship of S-TAG IDs of IPCOM VA and Virtual Fabrics
Figure J.4 Relationship of S-TAG IDs of IPCOM VA and Multiple Virtual Fabrics
Relationship between IPCOM VA in Pools and Virtual Fabrics
Network devices (IPCOM VA) belonging to the global pool can be shared with multiple tenants, and they are not dedicated to any specific tenants. Therefore, the network devices (IPCOM VA) belonging to the global pool can be linked with the default VFAB.
The network devices (IPCOM VA) in the global pool cannot be used for tenants corresponding to a VFAB other than the default VFAB.
The network devices (IPCOM VA) that can be linked with a VFAB other than the default VFAB are the ones that belong to the local pool of the tenant corresponding to that VFAB.
Pool | Fabric | Coordination of IPCOM VA Belonging to a Pool and VFAB | Sharing of IPCOM VA Between Multiple Tenants |
|---|---|---|---|
Global pool | Default VFAB | Possible | Possible |
VFAB | - | - | |
Local pool | Default VFAB | Possible (*) | Not possible |
VFAB | Possible | Not possible |
- Not applicable (Global pools can only be coordinated with the default VFAB)
* Note: Tenants in the local pool need to be specified as the tenants that use the default VFAB in advance.
Figure J.5 Relationship between IPCOM VA in Pools and Virtual Fabrics
Configuration Examples of IPCOM VA and Virtual Fabrics
There are the following two patterns of configuration of IPCOM VA and virtual fabrics:
Link IPCOM VA and virtual fabrics on a one-to-one basis without separating virtual fabrics into external and internal networks
For the configuration example, refer to "Figure J.6 Example of Configuration for Virtual Fabrics Not Separated into External and Internal Networks".
Link IPCOM VA and virtual fabrics on a one-to-n basis separating virtual fabrics into external and internal networks
Use this pattern of configuration when separating external network communication from internal network communication.
For the configuration example, refer to "Figure J.7 Example of Configuration for Virtual Fabrics Separated into External and Internal Networks".
Link IPCOM VA and virtual fabrics on a one-to-n basis using virtual fabrics only on an internal network
Use this pattern of configuration when performing external network communication with an IPCOM VA directly, not through virtual fabrics.
In order to perform external network communication with an IPCOM VA directly, it is necessary to configure "MAC Address Distribution Mode" for the external network connection port on an IPCOM VX.
For the configuration example, refer to "Figure J.8 Example of Configuration for Virtual Fabrics Used only on an Internal Network".
Figure J.6 Example of Configuration for Virtual Fabrics Not Separated into External and Internal Networks
Figure J.7 Example of Configuration for Virtual Fabrics Separated into External and Internal Networks
Figure J.8 Example of Configuration for Virtual Fabrics Used only on an Internal Network
