Describes a switching option that forwards all traffic to an external switch for policy application and processing.
Reflective relay is a switching option that
-
forwards all traffic to an external switch, which then applies policy and sends the traffic back to the destination or target VM on the server as needed
-
provides packet replication to each VM locally on the server for broadcast or multicast traffic, and
-
uses the tagless approach of IEEE standard 802.1Qbg with no local switching.
Reflective relay is available beginning with Cisco APIC Release 2.3(1). One benefit of reflective relay is that it leverages the external switch for switching features and management capabilities, freeing server resources to support the VMs. Reflective relay also allows policies that you configure on the Cisco APIC to apply to traffic between the VMs on the same server.
In the Cisco ACI, you can enable reflective relay, which allows traffic to turn back out of the same port it came in on. You can enable reflective relay on individual ports, port channels, or virtual port channels as a Layer 2 interface policy using the APIC GUI, NX-OS CLI, or REST API. It is disabled by default.
The term Virtual Ethernet Port Aggregator (VEPA) is also used to describe 802.1Qbg functionality.
Reflective relay support
Reflective relay supports the following:
-
IEEE standard 802.1Qbg tagless approach, known as reflective relay.
Cisco APIC Release 2.3(1) release does not support the IEE standard 802.1Qbg S-tagged approach with multichannel technology.
-
Physical domains.
Virtual domains are not supported.
-
Physical ports, port channels (PCs), and virtual port channels (vPCs).
Cisco Fabric Extender (FEX) and blade servers are not supported. If reflective relay is enabled on an unsupported interface, a fault is raised, and the last valid configuration is retained. Disabling reflective relay on the port clears the fault.
-
Cisco Nexus 9000 series switches with EX or FX at the end of their model name.