nat64 bind instance

Function

The nat64 bind instance command binds a traffic behavior to a NAT64 instance.

The undo nat64 bind instance command deletes the binding between a traffic behavior and a NAT64 instance.

By default, no traffic behavior is bound to a NAT64 instance.

This command is supported only on the NetEngine 8000 F1A.

Format

nat64 bind instance instance-name

undo nat64 [ bind instance [ instance-name ] ]

Parameters

Parameter	Description	Value
instance-name	Specifies the name of a NAT64 instance.	The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.

Parameter

Description

Value

instance-name

Specifies the name of a NAT64 instance.

The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.

Views

Traffic behavior view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
nat	write

Usage Guidelines

Usage Scenario

To bind a traffic behavior to a NAT instance, run the nat64 bind instance command. On a carrier network, NAT64 must be performed for all user traffic. To meet this requirement, configure a traffic profile and apply it to an inbound interface. Traffic distribution policies must be defined to direct traffic to a service board for NAT64 processing. The configuration involves defining ACL rules, traffic classifiers, traffic behaviors, and traffic distribution policies and applying the traffic distribution policies.

Prerequisites

An ACL, an ACL rule, and a traffic classifier have been configured.
A NAT64 instance has been configured.

Follow-up Procedure

Configure a traffic distribution policy, bind the traffic classifier to the traffic behavior, and apply the policy in the interface or system view.

Precautions

NAT64 does not support dynamic load balancing or a global address pool.

In the traffic behavior view, the NAT64 redirection is mutually exclusive with redirection actions (including the deny action, NAT44 traffic distribution, DNS redirection action, HTTP redirection action, and redirect action, and redirect-CPU action).

If the destination address of a packet matches both an ACL rule and a FIB entry, the ACL rule takes precedence over the FIB entry for traffic diversion. For example, a NAT64 IPv6 prefix 2001:db8::1/96 is defined for NAT64 instance A, and the prefix matches ACL1 which is bound to NAT64 instance B. Packets destined for 2001:db8::1/96 are preferentially matched against ACL1 and assigned to NAT64 instance B instead of NAT64 instance A. As a result, NAT64 processing fails to be performed for the packets.

Example

# Bind a traffic behavior named b1 to a NAT64 instance named nat1.

<HUAWEI> system-view
[~HUAWEI] nat64 instance nat1 id 1
[*HUAWEI-nat64-instance-nat1] commit
[~HUAWEI-nat64-instance-nat1] quit
[~HUAWEI] traffic behavior b1
[*HUAWEI-behavior-b1] nat64 bind instance nat1