Modernizing IBM SEA to handle Cisco micro-segmentation policy

CISCO ACI in conjunctions with VMWARE have developed the ability to apply multiple Private VLAN configurations (micro-segmentation) onto a single switchport.

Normal Private VLAN implementations require the creation of the Primary VLAN (200) which is promiscuous and designed to carry the traffic for its subdomain vlans categorized as Isolated (201) and Community (202). VLAN 201 and 202 communicate through the promiscuous port which forwards the traffic through the network. The current implementation of SEAs requires dedicated switchport configuration to handle the translation from the primary VLAN (200) to its subdomain vlans (201 and 202).

It is requested that IBM implement the ability for Trunking VEA's or the SEA, be configurable to partake of this implementation to remain compatible. We require the ability to capture dedicated Private VLAN communications over a specified Promiscuous VLAN for specific Sub VLANS for this implementation to work. I.E., we need to be able to specify in the Trunking VEA that a Specific VLAN is the promiscuous VLAN, and all control traffic should be translated over to its client VLAN. Additionally, we should be able to flag this client VLAN as Isolated (should only speak to the gateway and not others in its subnet) or Community (normal VLAN communications allowed within the subnet).