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

16 ServerIron ADX NAT64 Configuration Guide

53-1002444-02

Advanced stateful NAT64 configuration

DRAFT: BROCADE CONFIDENTIAL

Once this command is configured, the NAT64 gateway will automatically delete an existing sticky

session for a NAT64 pool if a connection request arrives from the same IPv6 client and the NAT64

pool IP address in the associated sticky session has run out of available source ports. The NAT64

gateway then selects a new IPv4 address from the configured NAT64 pool address range and

creates a new sticky session for the IPv6 client to NAT64 pool address.

Although existing sessions from the IPv6 client continue, all new connections will use the newly

created sticky session.

Disabling sticky behavior

By default, the stateful NAT64 gateway selects the same NAT64 pool IP address for a given IPv6

client and maintains this IPv6 client-to-NAT64 address mapping by means of a sticky session.

For as long as this sticky session exists, the same NAT64 pool IP address is selected for all

subsequent flows from the client. However, under certain heavy traffic conditions, the NAT64 pool

might run out of ports. In such an event, new connections from the same client are dropped by the

NAT64 gateway.

Use the nat64 disable-sticky command to disable sticky session behavior on the NAT64 gateway

and to ensure that a new IPv4 address is selected from the IPv4 NAT address pool whenever a

request comes from an IPv6 client.

ServerIron ADX(config)# nat64 disable-sticky

Syntax: [no] nat64 disable-sticky

Enabling connection logging

To enable connection logging for NAT64 traffic processed by the NAT64 gateway, enter the nat64

connection-log command.

ServerIron ADX(config)# nat64 connection-log

Syntax: [no] nat64 connection-log

Configuring HTTP client IP address insertion

When an IPv6 address is translated, the internal resource cannot see the client's original IPv6

address. In situations where an HTTP client's identity has to be maintained, the NAT64 gateway can

be configured to insert the client IP address as an HTTP header. The header will be inserted as the

last header in the HTTP request.

For example, to enable client IP insertion for HTTP traffic arriving on port 80, configure the nat64

http-client-ip-insertion port command as in the following example:

ServerIron ADX(config)# nat64 http-client-ip-insertion port 80

For example, where the original HTTP request is:

GET /abc/index.html HTTP 1/0\r\n

Host: foo.com\r\n

…

Connection: Keep-Alive\r\n

\r\n

After insertion, the HTTP request will be:

GET /abc/index.html HTTP 1/0\r\n

1 2 ... 23 24 25 26 27 28 29 30 31 32 33 ... 148 149

Comments to this Manuals

No comments

Brocade Communications Systems ServerIron ADX 12.4.00 Service Manual Page 28

Comments to this Manuals

Related products and manuals for Network switches Brocade Communications Systems ServerIron ADX 12.4.00