Licensing Requirements and Limitations for Microsegmentation
Involved Network Elements
You can configure microsegmentation on the Agile Controller-DCN or in single-node mode. Different network elements (NEs) are required for the two configuration modes. During the configuration, select a proper controller version.
Configuration Mode |
Product |
Description |
---|---|---|
Agile Controller-DCN mode |
Agile Controller-DCN |
The controller configures EPGs and GBPs and delivers the configurations to the forwarder through the NETCONF interface. |
Single-node mode |
Other network elements are not required. |
Licensing Requirements
Microsegmentation is a basic function of the switch, and as such is controlled by the license for basic software functions. The license for basic software functions has been loaded and activated before delivery. You do not need to manually activate it.
Version Requirements
Product |
Minimum Version Required |
---|---|
CE12800E (equipped with ED-E, EG-E, or EGA-E series cards) |
V200R005C10 |
For details about the mapping between software versions and switch models, see the Hardware Query Tool.
Software version evolution: V100R001C00 -> V100R002C00 -> V100R003C00 -> V100R003C10 -> V100R005C00 -> V100R005C10 -> V100R006C00 -> V200R001C00 -> V200R002C50 -> V200R003C00 -> V200R005C00 -> V200R005C10 -> V200R019C00 -> V200R019C10
Feature Limitations
- Microsegmentation is available only on the distributed Layer 3 VXLAN gateway networking.
- In versions earlier than V200R019C10, microsegmentation is valid only for Layer 3 known IPv4 unicast traffic on a VXLAN overlay network.
- Microsegmentation does not support EPG 0, which is invalid.
- One member can join only one EPG.
- When GBPs between EPGs define the Layer 4 port number, the default action for non-first fragments of TCP or UDP packets is permit. You need to adjust the MTU of each server and the forwarder to prevent packet fragmentation.
- Microsegmentation cannot be configured with the MQC-based traffic policy that defines VXLAN reserved field re-marking.
Limitations on configuring GBPs
- GBPs include permit and traffic statistics collection, and can be only applied to the system in the inbound direction.
- When you modify a segment policy or the segment classifier and segment behavior bound to a segment policy, the device traverses rules in sequence, delivers a new segment policy, and deletes the segment policy that needs to be modified. To prevent rule modification failures, ensure that the number of remaining ACL resources is greater than the highest one among the numbers of chip resources occupied by each rule in the segment policy.
- If you enable the traffic statistics collection function for a segment behavior bound to a segment policy, the function takes effect after a slight delay following the configuration. The delay is proportional to the number of rules in the segment classifier corresponding to the segment behavior. In extreme conditions, the delay may reach minutes. You need to enable traffic statistics collection for a segment behavior before binding the segment classifier and segment behavior to a segment policy.