Contents

MAP-E commands· 1

display map instance· 1

display nat map interface tunnel 5

map-e instance· 6

map-e instance dynamic· 7

map-e spoofing-enable· 8

mode· 9

nat map enable· 10

source interface· 14

 

MAP-E commands

display map instance

Use display map instance to display MAP instance information.

Syntax

display map instance [ name instance-name ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

name instance-name: Specifies a MAP-E instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays information about all MAP-E instances.

verbose: Displays detailed information about MAP-E instances. If you do not specify this keyword, the command displays brief information about MAP-E instances.

Usage guidelines

If no argument or keyword is specified for this command, the command displays brief information about all MAP instances.

Execute this command to view the MAP-E instance configuration and MAP-E rule information obtained from the DHCPv6 server.

Examples

# Display brief information about MAP-E instance a.

<Sysname> display map instance name a

Type: MAP-E

Instance-name: a

Mode: PD

Interface-name: Ten-GigabitEthernet0/0/6

Tunnel-name: N/A

Prefix: ::/0

MAP status: Invalid

# Display brief information about all MAP-E instances.

<Sysname> display map instance

Type: MAP-E

Instance-name: a

Mode: PD

Interface-name: Ten-GigabitEthernet0/0/6

Tunnel-name: N/A

Prefix: ::/0

MAP status: Invalid

 

Type: MAP-E

Instance-name: b

Mode: PD

Interface-name: Ten-GigabitEthernet0/0/6

Tunnel-name: N/A

Prefix: 2001:DB8:1:64BE:103::/80

MAP status: Valid

# Display detailed information about MAP-E instance a.

<Sysname> display map instance name a verbose

Type: MAP-E

Instance-name: a

Mode: PD

Interface-name: N/A

Tunnel-name: N/A

Prefix: ::/0

MAP status: Invalid

MAP Rule Info:

  BR Address: ::

  Rule IPv4 Address: 0.0.0.0/0

  Rule IPv6 Prefix Address: ::/0

  EA-Bits Length: 0

  flags: 0

Calculated Info:

  IPv4 Start Address: 0.0.0.0

  IPv4 End Address: 0.0.0.0

  PSID: N/A

  MAP IPv6 Address: ::

Other Info:

  NAT last notified: N/A

  Tunnel last notified: N/A

# Display detailed information about all MAP-E instances.

<Sysname> display map instance verbose

Type: MAP-E

Instance-name: a

Mode: PD

Interface-name: N/A

Tunnel-name: N/A

Prefix: ::/0

MAP status: Invalid

MAP Rule Info:

  BR Address: ::

  Rule IPv4 Address: 0.0.0.0/0

  Rule IPv6 Prefix Address: ::/0

  EA-Bits Length: 0

  flags: 0

Calculated Info:

  IPv4 Start Address: 0.0.0.0

  IPv4 End Address: 0.0.0.0

  PSID: N/A

  MAP IPv6 Address: ::

Other Info:

  NAT last notified: N/A

  Tunnel last notified: N/A

 

Type: MAP-E

Instance-name: b

Mode: PD

Interface-name: Ten-GigabitEthernet0/0/6

Tunnel-name: N/A

Prefix: 2001:DB8:1:64BE:103::/80

MAP status: Valid

MAP Rule Info:

  BR Address: 2001:DB8:CAFE::1

  Rule IPv4 Address: 192.0.0.0/24

  Rule IPv6 Prefix Address: 2001:DB8:1:64BE::/64

  EA-Bits Length: 16

  flags: 128

Calculated Info:

  IPv4 Start Address: 192.0.0.1

  IPv4 End Address: 192.0.0.1

  PSID:

    PSID Offset: 2

    PSID Len: 4

    PSID: 3

  MAP IPv6 Address: 2001:DB8:1:64BE:130:C000:1:3

Other Info:

  Expired Time: Jan 10 07:45:14 2023

  NAT last notified: N/A

  Tunnel last notified: N/A

 

Type: MAP-E

Instance-name: c

Mode: PD

Interface-name: Ten-GigabitEthernet0/0/6

Tunnel-name: N/A

Prefix: ::/0

MAP status: Invalid

MAP Rule Info:

  BR Address: ::

  Rule IPv4 Address: 0.0.0.0/0

  Rule IPv6 Prefix Address: ::/0

  EA-Bits Length: 0

  flags: 0

Calculated Info:

  IPv4 Start Address: 0.0.0.0

  IPv4 End Address: 0.0.0.0

  PSID: N/A

  MAP IPv6 Address: ::

Other Info:

  NAT last notified: N/A

  Tunnel last notified: N/A

  ERROR_INFO: PD prefix has been released.

Table 1 Command output

Field	Description
Type	MAP instance type. ·     MAP-E. ·     MAP-T (not supported in the current software version).
Instance-name	MAP instance name.
Mode	Method in which the MAP-E instance obtains MAP-E information. ·     NDRA—NDRA method. ·     PD—DHCPv6 method.
Interface-name	Name of the physical interface to which the MAP-E instance is bound.
Tunnel-name	Name of the tunnel interface to which the MAP-E instance is bound.
Prefix	Obtained IPv6 prefix. This field displays ::/0 if no IPv6 prefix is obtained.
MAP status	State of the MAP instance. ·     Invalid—The MAP instance is unavailable because no MAP information is applied or the MAP instance resolution fails. ·     Valid—The MAP instance is available.
MAP Rule Info	MAP rule information: ·     BR Address—IPv6 address of the BR. The value for this field is :: when the MAP instance is in Invalid state. ·     Rule IPv4 Address—IPv4 address specified by the MAP rule. The value for this field is 0.0.0.0/0 when the MAP instance is in Invalid state. ·     Rule IPv6 Prefix Address—IPv6 prefix specified by the MAP rule. The value for this field is ::/0 when the MAP instance is in Invalid state. ·     EA-Bits Length—Number of embedded address (EA) bits. The value for this field is 0 when the MAP instance is in Invalid state. ·     flags—Decimal format rule identifier. When the binary format is used, the last bit value determines the MAP rule type. The value for this field is 0 when the MAP instance is in Invalid state. ¡     1—Basic mapping rule (BMR). ¡     0—Forwarding mapping rule (FMR).
Calculated Info	MAP-E information calculated by the MAP rule. ·     IPv4 Start Address—Start IPv4 address. The value for this field is 0.0.0.0 when the MAP instance is in Invalid state. ·     IPv4 End Address—End IPv4 address. The value for this field is 0.0.0.0 when the MAP instance is in Invalid state. ·     PSID—Port set ID. The value for this field is N/A when the MAP instance is in Invalid state. ¡     PSID Offset—Number of offset bits of the PSID. ¡     PSID Len—Length of the PSID. ¡     PSID—PSID value. ·     MAP IPv6 Address—IPv6 address of an interface on a MAP-enabled CE. The value for this field is :: when the MAP instance is in Invalid state.
Other Info	Other MAP-E information. ·     Expired Time—Time when the prefix expired. ·     NAT last notified—Most recent time when the NAT module was notified about the public IPv4 address and port number of the CE. ·     Tunnel last notified—Most recent time when MAP information was pushed to the tunnel module. ·     ERROR_INFO—Reason why the MAP-E instance is faulty. (For example, the MAP-E instance is faulty because the prefix is unavailable or the prefix has been released.) This field is not displayed when no MAP-E information is applied or the MAP-E instance is correctly resolved.

 

display nat map interface tunnel

Use display nat map interface tunnel to display public resources obtained in MAP-E information on MAP-E tunnel interfaces. The MAP-E information is notified by the MAP CE to the NAT module through the DHCPv6 server.

Syntax

display nat map interface tunnel [ number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

number: Specifies a tunnel interface number. The specified tunnel interface number must already exist. If you do not specify this argument, the command displays public resources obtained in MAP-E information on all created MAP-E tunnel interfaces.

Usage guidelines

Upon receiving the MAP-E information notified by the DHCPv6 server, the NAT module of the MAP CE automatically generates address groups named in the MAP-E_tunnel_xx format. Such address groups are called MAP address groups. The NAT module manages public resources through MAP address groups.

A MAP address group contains public IPv4 addresses and port sets. The public IPv4 addresses are directly obtained from MAP-E information by the MAP CE. Port sets are calculated by the MAP CE based on the value, length, and offset bits of the PSIDs in the MAP-E information. You can use this command to view the mappings between public IPv4 addresses and port sets.

Examples

# Display public resources obtained in MAP-E information on the specified MAP-E tunnel interface.

<Sysname> display nat map interface tunnel 10

  Address group name/ID: MAP-E_tunnel_10/80001

    Resource information:

      Start address        End address        Start port    End port

      1.1.1.1              1.1.1.1            2100          2200

                                              2400          2500

      2.1.1.0              2.1.1.255          1024          65535

      3.1.1.1              3.1.1.1            1024          65535

# Display public resources obtained in MAP-E information on all created MAP-E tunnel interfaces.

<Sysname> display nat map interface tunnel

NAT MAP address group information:

  Totally 2 NAT MAP address groups.

  Address group name/ID: MAP-E_tunnel_1/80002

    Resource information:

      Start address        End address        Start port    End port

      1.1.1.1              1.1.1.1            2100          2200

                                             2400          2500

      2.1.1.0              2.1.1.255          1024          65535

      3.1.1.1              3.1.1.1            1024          65535

 

  Address group name/ID: MAP-E_tunnel_2/2002

    Resource information:

      Start address        End address        Start port    End port

      10.1.1.1             10.1.1.1           2100          2200

                                              2400          2500

      20.1.1.0             20.1.1.255         1024          65535

      30.1.1.1             30.1.1.1           1024          65535

Table 2 Command output

Field	Description
NAT MAP address group information	Information about the MAP address groups.
Totally n NAT MAP address groups	Number of MAP address groups.
Address group name/ID	Name/ID of the MAP address group.
Resource information	Resource information about the MAP address group.
Start address	Start IPv4 address.
End address	End IPv4 address.
Start port	Start port number in the port set.
End port	End port number in the port set.

 

map-e instance

Use map-e instance to bind a MAP-E instance to a MAP-E tunnel interface.

Use undo map-e instance to restore the default.

Syntax

map-e instance instance-name

undo map-e instance

Default

No MAP-E instance is bound to a MAP-E tunnel interface.

Views

MAP-E tunnel interface view

Predefined user roles

network-admin

Parameters

Instance-name: Specifies a MAP-E instance name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

Operating mechanism

After you bind a MAP-E instance to a MAP-E tunnel interface, the DHCPv6 module pushes the MAP-E rule information of the MAP-E instance to the tunnel and NAT modules.

For the sent IPv4 packets, the tunnel module performs the following tasks:

1.     Uses the MAP-E rule to calculate the source IPv6 address.

2.     Uses the calculated IPv6 address and IPv6 address of the BR as the source IPv6 address and destination IPv6 address, respectively.

3.     Encapsulates the IPv4 packets with an IPv6 packet header.

For the received IPv6 packets, the tunnel module uses the MAP-E information to identify whether the source and destination IPv6 addresses are valid and decapsulates the IPv6 packet header.

The NAT module uses the MAP-E information to translate the private IPv4 address and port number to a public IPv4 address and port number.

Restrictions and guidelines

You can bind only created MAP-E instances to MAP-E tunnel interfaces. You cannot delete MAP-E instances that are bound to MAP-E tunnel interfaces. To delete such MAP-E instances, first delete the MAP-E tunnel interfaces to which the MAP-E instances are bound.

You can bind a MAP-E instance to only one tunnel interface and bind only one MAP instance to the same tunnel interface.

Examples

# Bind MAP-E instance a to MAP-E tunnel interface Tunnel 1.

<Sysname> system-view

[Sysname] interface tunnel 1 mode map-e

[Sysname-Tunnel1] map-e instance a

Related commands

display map instance

map-e instance dynamic

Use map-e instance dynamic to create a MAP-E instance that dynamically obtains MAP-E information from the DHCPv6 server and enter its view.

Use undo map-e instance to delete MAP-E instances.

Syntax

map-e instance instance-name dynamic

undo map-e instance instance-name

Default

No MAP-E instance exists.

Views

System view

Predefined user roles

network-admin

Parameters

instance-name: Specifies a MAP-E instance name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

After the DHCPv6 module obtains MAP-E information, it pushes the MAP-E information to the NAT and tunnel modules through a MAP-E instance. The NAT and tunnel modules use the MAP-E rule to perform address translation and packet encapsulation.

The MAP-E instance is bound to the physical interface that receives DHCPv6 replies so that it carries the MAP-E information in the DHCPv6 replies.

The MAP-E instance is bound to a MAP-E tunnel interface and pushes the MAP-E information to the NAT and tunnel modules through the MAP-E tunnel interface.

Examples

# Create MAP-E instance ist1 and enter its view.

<Sysname> system-view

[Sysname] map-e instance ist1 dynamic

[Sysname-mape-ist1]

Related commands

map-e instance

source interface

map-e spoofing-enable

Use map-e spoofing-enable to enable anti-spoofing for MAP-E tunnel packets.

Use undo map-e spoofing-enable to disable anti-spoofing for MAP-E tunnel packets.

Syntax

map-e spoofing-enable

undo map-e spoofing-enable

Default

Anti-spoofing is enabled for MAP-E tunnel packets.

Views

MAP-E tunnel interface view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

After receiving an IPv6 packet from the peer end, the MAP-E tunnel interface enabled with this feature on the CE first checks packet validity, and then decapsulates the packet if it passes the check.

Operating mechanism

The packet check rule is as follows:

·     If the outer source IPv6 address is the IPv6 address of the MAP BR, the packet passes the check.

·     If the outer source IPv6 address is not the IPv6 address of the MAP BR, the MAP-E module calculates an IPv6 address by using the BMR rule based on the inner source IPv4 address of the packet. Then, it matches the calculated IPv6 address against the outer source IPv6 address of the packet. If the calculated IPv6 address does not match the outer source IPv6 address, the MAP-E module drops the packet to avoid spoofing attacks.

Recommended configuration

Disable this feature on the local MAP-E tunnel interface when the peer end is a third-party device that does not support this feature.

Examples

# On MAP-E tunnel interface Tunnel 0, disable anti-spoofing for MAP-E tunnel packets.

<Sysname> system-view

[Sysname] interface tunnel 0 mode map-e

[Sysname-Tunnel0] undo map-e spoofing-enable

mode

Use mode to specify a method for MAP instances to obtain MAP-E information.

Use undo mode to restore the default.

Syntax

mode { ndra | pd }

undo mode

Default

MAP-E instances obtain MAP-E information through DHCPv6.

Views

MAP-E instance view

Predefined user roles

network-admin

Parameters

ndra: Specifies the NDRA method.

pd: Specifies the DHCPv6 method.

Usage guidelines

After you specify a method for a MAP instance to obtain MAP-E information, the physical interface to which the MAP-E instance is bound uses the specified method to obtain MAP-E information.

The CE, working as a DHCPv6 client, can use one of the following methods to obtain MAP-E information:

·     DHCPv6—Stateful. The DHCPv6 client sends a DHCPv6 request to the DHCPv6 server for prefix and MAP-E information.

·     NDRA—Stateless. The DHCPv6 client automatically obtains a prefix from a ND RA message based on the neighbor discovery protocol, and then sends an Information-request packet to the DHCPv6 server for MAP-E information.

Examples

# Specify the NDRA method for MAP-E instance ist1 to obtain MAP-E information.

<Sysname> system-view

[Sysname] map-e instance ist1 dynamic

[Sysname-mape-ist1] mode ndra

Related commands

display map instance

map-e instance dynamic

nat map enable

Use nat map enable to enable Mapping of Address and Port (MAP) for NAT.

Use undo nat map enable to disable NAT MAP.

Syntax

nat map enable

undo nat map enable

Default

NAT MAP is disabled.

Views

MAP-E tunnel interface view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

MAP is an IPv4-to-IPv6 transition technique, which allows carriers to carry IPv4 services in a pure IPv6 network. Integrating with stateless and dual translation and encapsulation techniques, MAP can map IPv4 packets to IPv6 packets statelessly. The MAP technique contains the following types based on the IPv4 packet encapsulation method: Mapping of Address and Port with Encapsulation (MAP-E) and Mapping of Address and Port using Translation (MAP-T). Both MAP-E and MAP-T are IPv4-over-IPv6 IPv6 transition techniques.

Only MAP-E is supported in the current software version.

Basic concepts

The following describes basic concepts for MAP-E:

·     MAP-E—A stateless transition technique that encapsulates IPv4 packets with an IPv6 packet header.

·     MAP Customer Edge (CE)—A device located between the IPv4 network and the IPv6 network.

·     MAP Border Relay (BR)—A device located at the border of the IPv6 network and the IPv4 network.

·     MAP rule—Describes the mapping between an IPv4 prefix (network number of an IPv4 address), dedicated IPv4 address, or shared IPv4 address and an IPv6 prefix or address. MAP rules include BMRs and FMRs.

¡     BMR—Describes the mapping between an IPv6 address and an IPv4 address+port. A MAP CE uses a BMR to perform NAT44 on IPv4 packets and encapsulates the translated IPv4 packets with an IPv6 packet header. A MAP BR uses a BMR to decapsulate IPv6 packets and encapsulate the returned packets with an IPv6 packet header, and then forwards the packets to MAP CEs based on an IPv6 route in the MAP domain.

¡     FMR—Used to implement direct communication between MAP CEs in a MAP domain without MAP BRs. In a MAP domain, when a MAP CE accesses another MAP CE, the source IPv6 address is the IPv6 address calculated by the MAP CE through BMR, and the destination IPv6 address is the address of the peer MAP CE. An FMR is used by the MAP CE to calculate the IPv6 address of the peer MAP CE, which is used as the destination IPv6 address. A BMR can also serve as an FMR.

·     MAP domain—Consists of CEs and BRs that use the same MAP rule.

·     Port set—A port group which has a range of consecutive port numbers. Numbers of ports in different port groups are independent of each other. Different MAP CEs have different port groups.

·     Port Set ID (PSID)—The length (k) of a PSID determines the sharing ratio (R), which equals to 2k. Transport layer ports are divided into 2k sets and each set contains a group of consecutive port numbers. Each set is used by a MAP CE.

·     Shared IPv4 address—An IPv4 address shared among multiple CEs. A CE can use only ports in a port set to communicate with other devices. Shared IPv4 addresses are also known as port-restricted IPv4 addresses.

·     End-user IPv6 prefix—IPv6 prefix assigned to the MAP CE through DHCPv6. The End-user IPv6 prefix of a MAP CE is unique.

·     MAP IPv6 address—IPv6 address of a CE enabled with MAP, which is used to reach the CE from the BR or other CEs.

·     Rule IPv6 prefix—IPv6 prefix and length specified by the MAP rule.

·     Rule IPv4 prefix—IPv4 prefix and length specified by the MAP rule. The IPv4 prefix and length represent the network number and mask length of an IPv4 address, respectively.

·     Embedded Address bits (EA-bits)—Indicates the total length of the IPv4 suffix and the PSID in the IPv6 prefix assigned to a CE.

Operating mechanism

The following describes the operating mechanism of MAP-E. The NAT MAP feature is used to implement step 2. After you enable this feature on a MAP CE, the MAP CE uses the public resources obtained from the MAP-E information to perform IPv4 address+port translation.

1.     The MAP CE, acting as a DHCPv6 client, sends a DHCPv6 request to the DHCPv6 server for the End-user IPv6 prefix and MAP-E information. The request contains Option Request Option (Option 6), which is used to request from the DHCPv6 server for Option 94 that contains MAP-E information.

Option 94 in the response sent by the DHCPv6 server issues MAP-E information through the following sub-options. Option 89 and Option 93 make up a BMR.

¡     Option 89 contains the EA-bits, IPv4 prefix, IPv4 prefix length, IPv6 prefix, and IPv6 prefix length.

¡     Option 93 contains the value, length, and offset bits of a PSID.

¡     Option 90 contains the IPv6 address of the MAP BR.

2.     The NAT module of the MAP CE uses the public resources obtained from the MAP-E information to translate the source IPv4 address and source port in a private IPv4 packet.

Public resources include public IPv4 address and port information. The MAP CE can directly obtain the public IPv4 address information from the MAP-E information. At the same time, the MAP CE calculates the post sets based on the value, length, and offset bits of the PSID.

3.     The MAP CE calculates the IPv6 address corresponding to the public IPv4 address and port number based on the BMR.

4.     The tunnel module of the MAP CE encapsulates the original IPv4 packet with an IPv6 packet header, in which the source IPv6 address is obtained in step 3, and the destination IPv6 address is the IPv6 address of the BR. Then, the MAP CE sends the encapsulated packet to the MAP BR through the IPv6 network.

5.     Upon receiving the packet, the MAP BR checks the source IPv6 address and source port. If the IPv6 packet passes the check, the MAP BR removes the IPv6 packet header to obtain the original IPv4 packet, and then forwards the IPv4 packet based on the route.

If the IPv6 packet fails the check, the MAP BR discards the IPv6 packet.

Port number mapping mechanism

Upon receiving a private IPv4 packet, the MAP CE translates the source IPv4 address and source port of the packet. Then, the tunnel module of the MAP CE encapsulates the translated IPv4 packet with an IPv6 header. To improve public IPv4 address usage, MAP uses transport layer ports to extend IPv4 addresses. As a result, a public IPv4 address on the MAP CE can be used by multiple private users.

MAP divides a 16-bit transport layer port number into the following parts:

·     A—PSID offset, which is the number of PSID offset bits. The default value is 6. The PSID offset avoids conflicts with well-known port numbers in the range of 0 to 1023.

·     PSID—The length (k) of a PSID determines the sharing ratio (R), which equals to 2k. Transport layer ports are divided into 2k sets and each set contains a group of consecutive port numbers. Each MAP CE has a unique port set.

·     M—The length (m) of this field determines the number of consecutive ports in the port set, which is 2m.

Consequently, a total of 2k port sets are obtained. A PSID uniquely identifies a port set. Each port set contains a number of ((2A)-1)×(2m) ports.

Figure 1 Transport layer port structure for MAP

 

For example, the PSID offset is 4, the PSID length is 10, and the length of the M field is 2. The transport layer ports are divided into 210=1024 port sets. Each port set contains ((24)-1)*(22)=60 port numbers. Table 3 shows the mappings between PSID values and port sets. The port sets in the table are segmented because the port numbers in the port sets are not consecutive.

Table 3 Mappings between PSID values and port sets

PSID value	First range of consecutive port numbers in the port set (A=0001)	Second range of consecutive port numbers in the port set (A=0010)	…	Fifteenth range of consecutive port numbers in the port set (A=1111)
0	4096, 4097, 4098, 4099	8192, 8193, 8194, 8195	…	61440, 61441, 61442, 61443
1	4100, 4101, 4102, 4103	8196, 8197, 8198, 8199	…	61444, 61445, 61446, 61447
2	4104, 4105, 4106, 4107	8200, 8201, 8202, 8203	…	61448, 61449, 61450, 61451
3	4108, 4109, 4110, 4111	8204, 8205, 8206, 8207	…	61452, 61453, 61454, 61455
…	…	…	…	…
1023	8188,8189,8190,8191	12284,12285,12286,12287	…	65532, 65533, 65534, 65535

 

Address mapping mechanism

The MAP CE maps the translated IPv4 address and port number of the original IPv4 packet to an IPv6 address based on the mapping rule, as shown in Figure 2. The IPv6 address contains the Rule IPv6 prefix, EA, Subnet ID, and Interface ID fields. The mapping rule establishes a strong connection between the IPv4 address and port information and the IPv6 address to perform a stateless mapping. This protects the MAP BR from maintaining the mapping between the IPv6 and IPv4 addresses.

·     Rule IPv6 prefix—IPv6 prefix assigned to the MAP CE by the DHCPv6 server.

·     Subnet ID—ID of the first subnet. The value for s is 0.

·     EA—A combination of the IPv4 suffix and the value of the transport layer port's PSID.

·     Interface ID—A combination of an IPv4 address and PSID value.

¡     IPv4 address—If the DHCPv6 server assigns a shared IPv4 address or a dedicated IPv4 address to the MAP CE, the value is the assigned 32-bit IPv4 address. If the DHCPv6 server assigns a Rule IPv4 prefix to the MAP CE, the value for this field is right-padded with 0s to create a 32-bit field. For example, if the Rule IPv4 prefix is 2.1.1.0/29, the value for this field is 0x02010100 (hexadecimal).

¡     PSID—If the PSID value extracted from the EA-bits is less than 16 bits, it is left-padded with 0s to create a 16-bit field. For example, if the PSID value extracted from the EA-bits is 0xAC, the value for this field is 0x00AC. If the DHCPv6 server assigns a Rule IPv4 prefix or a dedicated IPv4 address, no PSID value can be extracted. The value for this field is 0x0000.

Figure 2 Mapping between an IPv4 address and an IPv6 address

 

Examples

# Create MAP-E tunnel interface Tunnel 1 and enable NAT MAP on the interface.

<Sysname> system-view

[Sysname] interface tunnel 1 mode map-e

[Sysname-Tunnel1] nat map enable

source interface

Use source interface to bind a MAP-E instance to a physical interface.

Use undo source interface to restore the default.

Syntax

source interface interface-type interface-number

undo source interface

Default

A MAP-E instance is not bound to any physical interface.

Views

MAP-E instance view

Predefined user roles

network-admin

Parameters

interface-type interface-number: Specifies an interface type and interface number.

Usage guidelines

After the physical interface to which a MAP-E instance is bound receives a response from the DHCPv6 server, the device associates the MAP-E rule information in the response with the MAP-E instance.

You can bind a MAP-E instance to only one physical interface and bind only one MAP instance to the same physical interface.

Examples

# Bind MAP-E instance ist1 to physical interface GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] map-e instance ist1 dynamic

[Sysname-mape-ist1] source interface gigabitethernet 1/0/1

Related commands

display map instance

map-e instance dynamic