Brocade Communications Systems ServerIron ADX 12.4.00 Service Manual Page 27

  • Download
  • Add to my manuals
  • Print
  • Page
    / 149
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 26
ServerIron ADX NAT64 Configuration Guide 15
53-1002444-02
Advanced stateful NAT64 configuration
2
DRAFT: BROCADE CONFIDENTIAL
ServerIron ADX(config)# router ospf
ServerIron ADX(config-ospf-router)# redistribution static
ServerIron ADX(config-ospf-router)# area 0
ServerIron ADX(config-ospf-router)# exit
ServerIron ADX(config)# ipv6 router ospf
ServerIron ADX(config-ospf6-router)# redistribute static
ServerIron ADX(config-ospf6-router)# area 1
ServerIron ADX(config-ospf6-router)# exit
4. Assign the VE interfaces to OSPF or OSPFv6 areas defined previously.
ServerIron ADX(config)# interface ve 10
ServerIron ADX(config-vif-10)# ipv6 ospf area 1
ServerIron ADX(config-vif-10)# exit
ServerIron ADX(config)# interface ve 20
ServerIron ADX(config-vif-20)# ip ospf area 0
ServerIron ADX(config-vif-20)# exit
5. An IPv4 NAT address pool is configured with static route injection.
ServerIron ADX(config)# nat64 pool nat64-zone1 192.0.2.1 192.0.2.10
prefix-length 24 port-pool-range 1 inject-static-route
6. An IPv6 prefix is configured with static route injection.
ServerIron ADX(config)# nat64 ipv6-prefix 2001:db8:8000::0/96
inject-static-route
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 ve 10
NOTE
While this example describes NAT64 route injection for the OSPF protocol, you can also use this
feature with BGP and IS-IS. Only the routing protocol configurations will differ.
NAT64 sticky session configuration
This section describes steps required to configure NAT64 sticky sessions.
Enabling ServerIron ADX to delete sticky sessions
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.
The same NAT64 pool IP address is selected for all subsequent flows from the client for as long as
this sticky session exists, 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.
To override this behavior, configure the nat64 nat-sticky-delete command to enable the NAT64
gateway to delete an existing sticky session that has run out of available ports and select a
different NAT64 pool IP address for the same client.
ServerIron ADX(config)# nat64 nat-sticky-delete
Syntax: [no] nat64 nat-sticky-delete
Page view 26
1 2 ... 22 23 24 25 26 27 28 29 30 31 32 ... 148 149

Comments to this Manuals

No comments