Feature Requirements |
Series |
Models |
|---|---|---|
MAP-T or MAP-E does not support the reassembly of IPv6 fragments sent by the CPE. After receiving IPv6 fragments from the CPE, the device fails to forward the packets in the MAP-E scenario. In the MAP-T scenario, the packets are not reassembled, converted into IPv4 fragments, and then forwarded. You are advised to properly plan the network MTU values to prevent IPv6 packet fragmentation. |
NetEngine 8000 F |
NetEngine 8000 F1A |
MAP-T or MAP-E does not support the reassembly of more than two IPv4 fragments sent by the network side. More than two fragments of an IPv4 packets fail to be forwarded on the network side. You are advised to properly plan the network MTU values to prevent IPv4 packet fragmentation. |
NetEngine 8000 F |
NetEngine 8000 F1A |
The MAP function does not apply to user-side VPN instances. The VPN configuration in the prefix pool and the map-rule command in the prefix pool are mutually exclusive. If an AAA server authorizes a VPN instance, users access the VPN instance as common users, without the MAP function used. Do not deploy user-side VPN instances if the MAP function is used. If the IPv4 stack of a terminal to which a MAP user is attached needs to access an IPv4 VPN network, specify a VPN instance when configuring an IPv4-prefix in a MAP rule. The IPv6 stack of a terminal to which a MAP user is attached cannot access an IPv6 VPN network. Therefore, do not deploy the MAP function in this situation. |
NetEngine 8000 F |
NetEngine 8000 F1A |
When an EDSG is configured for traffic from the network side to the user side in a MAP-E or MAP-T scenario, the rate limit is performed on IPv6 packets after IPv4 translation is performed. You are advised to configure the precision compensation function. In a MAP-T scenario, the difference between the IPv6 and IPv4 header lengths is used for compensation. In a MAP-E scenario, the IPv6 header length is used for compensation. |
NetEngine 8000 F |
NetEngine 8000 F1A |