Can't find what you need?

• Ask the Community
• Create a Case
Reset Search



What is the difference between Virtual Fabric service and transport services?

« Go Back


TitleWhat is the difference between Virtual Fabric service and transport services?
Virtual Fabric purpose:

Virtual Fabrics has been introduced in order to create the ability for Data Center Switches to re-utilize the standard range of 802.1Q VLAN ID's.

The Virtual Fabric implementation extends the usable VLAN assignment through a VCS fabric by utilizing the TRILL Fine Grain Label field along with port based configuration that classifies each ingress packet in order to build the TRILL FGL field. Virtual Fabrics use this method to provide support for overlapping VLAN within a VCS fabric.

The implementation offers two provisioning services. The two provisioning services models are Service and Transport. This FAQ will attempt to familiarize the reader with a comparison of the two service modes to provide an understanding of the use, configuration and packet header interpretation.
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

Service Attributes

  • 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

Service Attributes

  • 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.
Additional notes



Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255