Feature Requirements |
Series |
Models |
|---|---|---|
A traffic policy applied to a VSI instance does not support policy-based routing actions. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
MF classification in VXLAN mode does not support policy-based routing actions. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The discard PBR policy supports only direct routes. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The interface specified as the outbound interface of a discard PBR policy is mutually exclusive with the Layer 2 interface configuration. An interface cannot be configured as a Layer 2 interface after being specified as the outbound interface of a discard PBR policy. An interface cannot be specified as the outbound interface of a discard PBR policy after being specified as a Layer 2 interface. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Only a VLAN-type Layer 3 sub-interface can be specified as the outbound interface of a discard PBR policy. After a VLAN-type Layer 3 sub-interface is bound to redirection, the VLAN-type configuration cannot be deleted. A sub-interface can be specified as the outbound interface of a discard PBR policy only when it is configured as a Layer 3 sub-interface. After a Layer 3 sub-interface is specified as the outbound interface of a discard PBR policy, the VLAN-type configuration of the sub-interface cannot be deleted. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
A redirection action (except for IPv4 single-next hop and IPv4 multi-next hop) is configured in a traffic behavior. If the behavior is not bound to a traffic policy or it is bound to a traffic policy but the policy is not applied, after the redirection configuration in the behavior is deleted, the applied RE, NST, NHP, and VPN-Group resources are not released. After data smoothing or verification is performed, residual resources are released. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |