Brocade Communications Systems ServerIron ADX 12.4.00 Service Manual Page 129

  • Download
  • Add to my manuals
  • Print
  • Page
    / 149
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 128
ServerIron ADX NAT64 Configuration Guide 117
53-1002444-02
Forwarding packets without NAT translation
7
DRAFT: BROCADE CONFIDENTIAL
ServerIronADX(config)# interface ethernet 1/1
ServerIronADX(config-if-e1000-1/1) ip address 30.30.0.1 255.255.0.0
ServerIronADX(config-if-e1000-1/1) ip address 15.15.15.100 255.255.0.0
ServerIronADX(config-if-e1000-1/1) ip nat outside
Forwarding packets without NAT translation
By default, if the ServerIron ADX receives a non-SYN packet for a TCP flow from an internal NAT
client and no existing NAT session is found, the ServerIron ADX will drop that packet.
You can optionally configure the ServerIron ADX to forward such packets without NAT translation by
entering the following command.
ServerIronADX(config)# nat-forward-no-session
Syntax: [no] nat-forward-no-session
The nat-forward-no-session command is required in some special cases (such as when dynamic
NAT is used with VIP overlap) when the ServerIron ADX would drop packets because it cannot locate
the corresponding NAT sessions. This occurs in cases where the remote client open connections to
a real server directly and the ServerIron ADX routes the initial SYN packet to the real server. When
the SYN-ACK packet subsequently arrives from the real server, the ServerIron ADX checks the
session table to locate the corresponding session. However, because the SYN-ACK packet does not
belong to the an session from the real server itself, there will be no corresponding session.
Therefore, the ServerIron ADX will not find the session table entry and would drop it. If the
nat-forward-no-session command is configured, the SYN-ACK packet is not dropped and is
forwarded to remote client.
IP NAT with VIP overlap
The ServerIron ADX can be configured to use an IP address assigned to a virtual server as a
dynamic NAT pool IP.
In this configuration, the connections initiated from inside going out will be translated and will take
the source IP of the virtual server. The return traffic to these already established connections will
be routed back to the host that initiated this connection. At the same time, a connection initiated by
an outside host coming in to the virtual server, will be load balanced and sent to a real server.
The access list (ACL) defining the traffic for this scenario can contain both real servers already
bound to the virtual server, as well as any other hosts on the same subnet. Brocade recommends
that for this scenario, the dynamic NAT pool should only contain a single IP address, that is, the
virtual server IP address.
Figure 21 illustrates an example where IP NAT is configured with VIP overlap.
Page view 128
1 2 ... 124 125 126 127 128 129 130 131 132 133 134 ... 148 149

Comments to this Manuals

No comments