Segmentation is the process of dividing the network into logical sub-networks called Segments by using isolation techniques on a forwarding device such as a switch, router, or firewall. Network segmentation is important when traffic from different organizations and/or data types must be isolated.
In the segment-aware topology, different Virtual Private Network (VPN) profiles can be activated for each segment. For example, Guest traffic can be backhauled to remote data center firewall services, Voice media can flow direct from Branch-to-Branch based on dynamic tunnels, and the PCI segment can backhaul traffic to the data center to exit out of the PCI network.
To activate the segmentation capability for an Enterprise, in the Operator portal, navigate to System Properties, and then set the value of the system property, enterprise.capability.enableSegmentation as True. For more information about how to configure system properties, refer to the "System Properties" section in the VMware SD-WAN Orchestrator Deployment and Monitoring Guide.
By default, you can configure a maximum of 16 segments per Enterprise. However, you can choose to increase this default value to a maximum of 128 segments per Enterprise. Ensure that you define the maximum number of allowed segments in the enterprise.segments.system.maximum system property. For more information about the various system properties that you must set up for the segmentation capability, refer to the "Segmentation" table in the "List of System Properties" section in the VMware SD-WAN Orchestrator Deployment and Monitoring Guide.
Limitations
- It is mandatory that you upgrade your SD-WAN Orchestrator and your Edges to version 4.3 or above.
- After you have configured 128 segments for an Enterprise, you cannot downgrade your Edges to a version lower than 4.3. If you need to downgrade your Edges, ensure that you have only 16 segments, which is the default value for any Enterprise and delete the remaining segments before you downgrade the Edges.
Configure a New Segment for an Enterprise
- From the SD-WAN Orchestrator navigation panel, go to Configure > Segments. The Segments page for the selected enterprise appears.
- Click the + button and enter the following details to configure a new segment.
Field Description Segment Name The name of the segment (up to 256 characters). Description The description of the segment (up to 256 characters). Type The segment type can be one of the following: - Regular - The standard segment type.
- Private - Used for traffic flows that require limited visibility in order to address end user privacy requirements.
- CDE - VMware provides PCI certified SD-WAN service. The Cardholder Data Environment (CDE) type is used for traffic flows that require PCI and want to leverage the VMware PCI certification.
Note: For Global Segment, you can set the type either to Regular or Private. For non-global segments, the type can be Regular, CDE, or Private.Service VLAN The service VLAN identifier. For information, see Define Mapping between Segments and Service VLANs (Optional) section in Security VNFs. Delegate To Partner By default, this checkbox is selected. If you unselect it, the Partner cannot change configs within the segment, including the interface assignment. Delegate To Customer By default, this checkbox is selected. If you unselect it, the Customer cannot change configs within the segment, including the interface assignment. - Click Save Changes.
- Does not upload user flow stats to Orchestrator except for VMware Control, VMware Management, and a single IP flow that counts all transmitted and received packets and bytes sent on the segment. For example, Customer flow stats like Source IP, Destination IP and so on, are not shown in the Monitor tab for the flows related to Private segment.
- Does not allow users to view flows in Remote Diagnostics.
- Does not allow traffic to be sent as Internet Multipath as all business policies that are set to Internet Multipath are automatically overridden to Direct by the Edge.
If the segment is configured as CDE, then the VMware hosted Orchestrator and Controller will be aware of the PCI segment and will be in the PCI scope. Gateways (marked as non-CDE Gateways) will not be aware or transmit PCI traffic and will be out of PCI scope.