As one function of Converged Fabrics, there is a function to divide a single Ethernet Fabric into multiple virtual Ethernet Fabrics for management purposes. Divided virtual Ethernet Fabrics are referred to virtual fabrics (VFAB).
In Resource Orchestrator, virtual fabrics can be linked with tenants.
Figure H.2 Linking Virtual Fabrics with Tenants
When using virtual fabrics, VLAN IDs are managed independently for each virtual fabric. This means that the same VLAN IDs can be used for different virtual fabrics. Moreover, the same VLAN IDs can be used for tenants linked with different virtual fabrics.
Figure H.3 Relations between Virtual Fabrics and VLAN IDs
*: VLAN ID guarantees uniqueness within a VFAB.
Relations between Tenants and Virtual Fabrics
The following two patterns are supported for the relations between tenants and virtual fabrics.
Multiple tenants correspond to a single virtual fabric
A single tenant corresponds to a single virtual fabric
For either pattern, it is necessary to specify which virtual fabric corresponds to which tenant. When using a tenant for which a corresponding virtual fabric has not been specified, it is considered that the default VFAB is specified. The default VFAB is regarded as pattern a. above.
For details on relationships between tenants and virtual fabrics, specify the network configuration information (XML definition) when registering network devices.
For details on the specification method, refer to "15.6.1 Creation" in the "Reference Guide (Command/XML) CE".
Figure H.4 Relations between Tenants and Virtual Fabrics
Relations between Pools and Virtual Fabrics
Network resources belonging to the global pool can be shared with multiple tenants, and they are not dedicated to any specific tenants. Therefore, the network resources belonging to the global pool are regarded as corresponding to the default VFAB.
The following indicates that the network resources corresponding to the default VFAB.
Network resources belonging to the network pool of the global pool
Network resources belonging to the network pool under a tenant for which linkage with VFAB is not configured.
Network resources in the global pool can be shared with multiple tenants corresponding to the default VFAB. The network resources in the global pool cannot be used for tenants corresponding to a VFAB other than the default VFAB.
Figure H.5 Relations between Pools and Virtual Fabrics
*: VLAN ID guarantees uniqueness within a VFAB.
Virtual Fabric Auto-configuration
In Resource Orchestrator, virtual fabrics can be automatically configured for Converged Fabric.
Virtual fabric auto-configuration can be performed for virtual fabrics which satisfy the following conditions:
The following two settings are configured in the network configuration information (XML definition) for Converged Fabric.
The AutoConfiguration element is omitted.
Otherwise, "true" is configured for the AutoConfiguration element.
"true" is configured for the vfabauto attribute of the Vfab element.
For the following cases, the modification operation can be automatically configured in Resource Orchestrator, but settings must be modified in the Converged Fabric.
When migrating tenants among virtual fabrics while performing virtual fabric auto-configuration
When migrating resources among virtual fabrics, by network resource or network pool operations
When the following conditions are satisfied, auto-configuration of this modification operation is performed:
For the destination virtual fabric, the following two settings are configured in the network configuration information (XML definition) for Converged Fabric.
The AutoConfiguration element is omitted.
Otherwise, "true" is configured for the AutoConfiguration element.
"true" is configured for the vfabauto attribute of the Vfab element.
Moreover, in addition to the conditions above, when the following conditions are satisfied, the configuration of the virtual fabric information related to the port profile configured in Resource Orchestrator is modified automatically.
The Netdevice element in the portprofile attribute has been omitted in the network configuration information (XML definition).
Otherwise, "enable" is configured in the portprofile attribute.
The default VFAB is not the target of auto-configuration, as it is the virtual fabric which was configured in the device when installing Converged Fabric. Therefore, the values specified in the vfabauto attribute in the Vfab element in the network configuration information (XML definition) have no meaning. They are treated as if "false" is specified.
At the timing of the first auto-configuration, auto-configuration of virtual fabrics is performed on the condition that "pre-configuration involving the target virtual fabric in the target virtual Converged Fabric has not been performed". This condition defines the status that the following has been satisfied:
The vfab use command has not been executed for the relevant virtual fabric, and
The vfab mode command has not been executed for the relevant virtual fabric, and
The vfab cir-ports command has not been executed for the relevant virtual fabric, and
The ports in dot1ad mode that use the relevant virtual fabric are in either one of the following statuses:
Do not belong to the interface group for Converged Fabric.
Belong to only the Converged Fabric interface group which is composed of the ports in dot1ad mode. Moreover, VLAN is not configured for the interface group.
When auto-configuration cannot be performed, as the conditions above are not satisfied, operation is as below.
When registering or modifying the network devices for Converged Fabric
When even a single auto-configuration among virtual fabrics of the auto-configuration targets to be registered or modified cannot be performed, registration or modification of Converged Fabric network devices fails.
When registration or modification fail, after performing either of the following corrective actions, perform registration or modification of network devices for Converged Fabric again.
Delete the virtual fabric for which auto-configuration could not be performed from the network configuration information (XML definition).
Modify the hardware settings for Converged Fabric to satisfy the conditions above.
When performing batch registration or modification of network devices for Converged Fabric
When registration or modification of multiple Converged Fabrics is performed, if there is even one Converged Fabric which cannot be automatically configured, registration or modification will fail. Other Converged Fabrics are processed as below.
Registration or modification of Converged Fabrics which were defined before the failure are performed correctly.
Converged Fabrics which were defined after the failure are not registered or modified.
When registration or modification fail, perform either of the following corrective actions, and then perform batch registration or modification of network devices for Converged Fabrics which have been defined after the failure again.
Delete the virtual fabric for which auto-configuration could not be performed from the network configuration information (XML definition).
Modify the hardware settings for Converged Fabric to satisfy the conditions above.
