Brocade Network OS Administrator’s Guide v4.1.1 - Manual (Page 390)

from the flood membership of the VLAN. For tagged BPDUs (as in PVST), a BPDU is tunneled on its
own service-VF flood domain.
PVLANs with service VFs
Private VLAN (PVLAN) configurations apply to service VFs. A service VF can be a primary or a
secondary VLAN. However, before an association between the primary and secondary VLAN can be
made at the trunk port, the classification of a PVLAN that is a service VF must have been configured.
Based on the PVLAN type, the classification is done at the respective promiscuous or host port. That
is, the classification of a primary VLAN is done at a promiscuous port, that of a community VLAN at a
community port, and that of an isolated VLAN at an isolated port.
The service VF classification is required only if a port operates in trunk mode. An access port does not
require classification rules. The validation that is done for the service VF corresponds to the port type.
IP over service VFs
Layer 3 configurations are applicable to service VFs as well. The interface ve command for virtual
Ethernet (VE) interfaces also applies to service VFs, and all commands under the interface ve
submode are supported.
Each VE interface is mapped to a service VF, and all such interfaces share the router’s MAC address.
A VE interface can be assigned to a VRF instance. Layer 3 runs per-VRF OSPF instances to
exchange routes between RBridges in a given VRF instance.
Transport VFs
Transport service enables a cloud provider to offer service applicability on a VLAN group level, rather
than at a per-individual tenant VLAN level.
The cloud-based service provider needs to provide different service-level agreements (SLAs) to
support tenant needs and changes. Transport VFs enable the provider to offer services applicability on
a VLAN group level, rather than at a per-individual tenant VLAN level, where the VLAN group
represents a specific tenant application. Accordingly, the service offered can be associated only with a
single transparent VLAN that collectively represents all the VLANs in the group that participate in
supporting a given application. With transport VFs, all VLANs that support the application share the
same Layer 2 forwarding domain (individual VLAN isolation is not maintained), and all end stations
that participate in a given application or transport VF instance must use unique MAC addresses.
Transport VF topology
The following figure shows four transport VF instances on the respective transparent VLANs (TVLANs)
5000, 6000, 7000 and 8000. Each transport VF carries 101 VLANs in that application. Across the
transport VFs, overlapping service VFs among tenants can be supported. The transport VFs can also
be extended to another VCS Fabric over a VPLS network.
PVLANs with service VFs
390 Network OS Administrator’s Guide
53-1003225-04