Brocade Communications Systems ServerIron ADX 12.4.00 Service Manual download pdf (Page 63)

ServerIron ADX NAT64 Configuration Guide 51

53-1002444-02

NAT46 static mapping configuration

DRAFT: BROCADE CONFIDENTIAL

If you are running a ServerIron ADX build prior to 12.4.00, you must specify an interface and

port number.

ServerIron ADX(config)# nat64 ipv6-prefix 2001:db8:8000::0/96

inject-static-route stateless ve 7 stateless

5. An IPv4 address (100.1.1.100) within the subnet defined by the NAT46 IPv4 prefix is mapped

to the IPv6 address (2001:db8:8000::100) specified in Step 1.

ServerIron ADX(config)# nat64 map 100.1.1.100 2001:db8:8000::100

In a static NAT46 configuration such as this one, the only routes injected into the local routing table

are routes for IPv4 addresses that specifically are mapped to IPv6 addresses. In this example, only

the route to 100.1.1.100 will be distributed to the IPv4 network and not the route to the entire

subnet.

In dynamic NAT46 configurations, routes for all IPv4 addresses that are learned are distributed. For

more information, refer to “Stateless NAT46 dynamic mapping configuration” on page 52.

NOTE

While this example describes NAT46 route injection for the OSPF protocol, you can also use this

feature with BGP and IS-IS. Only the routing protocol configurations will differ.

Configuring NAT46 packet fragmentation

Packets from the IPv4 client to the IPv6 server can be too large and need to be split into two IPv6

packets. The following describes the criteria for judging that packets are too large:

• Regular packets: IP packet total length greater than 1480 bytes

• Fragmented packets: IP packet total length greater than 1480 + 8 bytes

If the packets exceed these limitations, one of the following actions will be taken.

• If the ipv6 frag-full-4to6 command is configured, the packet will be split and no further actions

will be performed.

• If the condition in step 1 is not met, and the DF bit is set at the server, the “fragmentation

needed” ICMP error message will be sent.

• If the conditions in steps 1 and 2 are not met, the packet will be split.

The ipv6 frag-full-4to6 command is configured as shown in the following example.

ServerIronADX(config)# ipv6 frag-full-4to6

Syntax: [no] ipv6 frag-full-4to6

For more information about fragmentation support, refer to “NAT64 fragmentation support” on

page 5.

NOTE

The ipv6-frag-full-4to6 command was introduced in ServerIron ADX release 12.4.00 and it replaces

the frag-664-reverse-full-sized-pkt command from earlier releases.

1 2 ... 58 59 60 61 62 63 64 65 66 67 68 ... 148 149

No comments

Brocade Communications Systems ServerIron ADX 12.4.00 Service Manual Page 63