Configuration and Scalability Limits
-
Ensure that ServiceInfra is configured before other steps are executed to configure MAP-T for exception handling. The service infrastructure is used for the management plane.
-
Configuring map-t-cisco instances :
-
Only a single external domain can be configured for each map-t-cisco instance.
-
The maximum number of CPE domains that can be configured for MAP-T exception handling is 1024.
-
The number of map-t-cisco instances supported for exception handling is 32 and the maximum number of CPE domain parameters that can be used in a single map-t-cisco instance is 256.
-
A map-t-cisco instance can be configured only with a default VRF.
-
-
To ensure IPv4/IPv6 translation is successfully performed, set the path MTU of the tunnel for both IPv4 and IPv6 traffic to 1500 bytes.
-
The IOS XR software does not support IPv6 fragmentation.
-
If an IPv4 packet that does not have a DF bit set is translated to an IPv6 packet that exceeds the configured MTU, the packet is translated by VSM and forwarded.
Note
-
If the Path-MTU value is not configured, the default value is assumed to be 1280 bytes.
-
Configure the MTU on physical VSM interfaces to 1518 bytes.
-
-
If an IPv6 packet that does not have a fragment header set is translated to an IPv4 packet that exceeds the minimum MTU, the packet is dropped and an ICMP error message is sent.
-
-
Modification of path-mtu value is not recommended. If you modify the path-mtu setting, delete the service-inline interface and configure it again for the path-mtu changes to take effect.
-
Deletion of ServiceApp configuration from a MAP-T domain is not permitted.