Virtual Fabric is a part of the Brocade Multi-tenancy framework and is built to support both a one to one and a one to many port to VLAN mapping. Both services can co-exist on the same switch and ports providing flexibility in deployment.
Service Virtual Fabric provides the following.
port-based frame classification
- support ctag virtualization
- support ctag translation
- support source MAC address classification
- A fabric wide L2 flooding domain with support for optimized L2-ECMP forwarding for unicast and multicast traffic
- Distribute MAC learning per VF
- Ability to police, SPAN, sFlow specific flows or all traffic in the Service VF
- Ability to plumb a L3 subnet over a service VF
- Ability to support Private VLANS within a Service VF
Transport Virtual Fabric provides the following.
Port-based Frame Classificans
- support CTAG range class
- support defualt class
- Transport tunnel all aggregated customer vlans..
- Shared VLAN model
- L2 or L3 services NOT supported
Use Cases for each
TheTransport mode is meant to support Managed hosting, Colocation, Managed Private Cloud, wholesale and White Label cloud providers and enterprises that provide leased servers markets.
The Service mode is meant to support Public Cloud LaaS and enterprise Private Cloud markets.
FGL field translation differences
The transport mode VF uses the FGL outer label is derived from the Transport VF Service ID and the inner label holds the c-tag provisioned on the interface.
The Service mode VF uses the FGL outer label for the upper 12 bits of the VF VLAN ID and the inner label for the lower 12 bits of the VF VLAN ID.
Configuration differences between the two services.
The knob that controls which type of service is being deployed exist on the global VLAN configuration. The existence of command "transport-service <service_id>"
configures for VF for Transport services.