Brocade Communications Systems ServerIron ADX 12.4.00 Service Manual Page 59

  • Download
  • Add to my manuals
  • Print
  • Page
    / 149
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 58
ServerIron ADX NAT64 Configuration Guide 47
53-1002444-02
NAT46 static mapping configuration
4
DRAFT: BROCADE CONFIDENTIAL
NOTE
A maximum of 1024 entries is supported in the mapping table. Entries can be defined manually
using the nat64 map command or dynamically using real-time or prefetched dynamic mappings. For
more information, refer to “Populating the NAT46 mapping table” on page 45.
Stateless NAT46 static mapping with route injection
In NAT46 configurations using static mapping of IPv4 and IPv6 addresses, an IPv4 prefix is defined
for an IPv4 subnet of mapped IPv4 addresses and an IPv6 prefix for an IPv6 subnet is used to
represent the IPv4 clients to the IPv6 resources.
Route injection can be used to make the addresses assigned to these translations available as
destinations in the routing tables of the respective IPv6 and IPv4 networks. Once these routes are
injected into the respective routing tables, route distribution is then performed using any one of the
routing protocols supported by ServerIron ADX: OSPF, IS-IS, and BGP (IPv4 to IPv6).
NAT46 route injection requires that the ServerIron ADX have a routing adjacency relationship with a
router for the protocols for which you want route distribution.
IPv4 route injection: For resources that are mapped to an IPv4 address, the IPv4 subnet is
defined by the IPv4 prefix specified with the nat64 ipv4-prefix command. This command has
the inject-static-route option which directs the ServerIron ADX to inject a static route to each of
the IPv4 addresses within the defined IPv4 subnet that have an IPv6 address mapped to them.
This mapping can be either performed using DNS dynamic mapping or though creation of a
static entry using the nat64 map command. This destination is advertised to the adjacent
neighbor and made available in routing tables of the IPv4 network.
Starting with ServerIron ADX release 12.4.00, configuring the inject-static-route option with the
nat64 ipv6-prefix command allows the configured IPv6 routing protocol to advertise the subnet
defined by the IPv6 prefix to the adjacent IPv6 neighbor and thereby make it available in the
routing tables of the IPv6 network, The next hop to the subnet is advertised to the IPv6 network
as the adjacent router. In all prior releases of the ServerIron ADX, you are required specify an
IPv6 interface on the ServerIron ADX (Ethernet or VE) that is directly connected to the adjacent
router.
Figure 15 shows a typical IPv4-only client to IPv6 resource topology configured with router
adjacency relationships on both the IPv4 and IPv6 sides of the ServerIron ADX. In this
configuration, routes defined by the IPv4 prefix and IPv6 prefix are advertised to the adjacent
routers and distributed to the respective networks using the routing protocol configured.
FIGURE 15 NAT46 route injection
.
To accomplish this redistribution, you must configure the routing protocol on your ServerIron ADX
with the redistribute static command.
ServerIron ADX
with NAT46
Router
IPv4-only Client
IPv4
NAT64 IPv6 Prefix: 2001:db8::
NAT64 IPv4 Prefix: 100.1.1.0/24
IPv6 address:
2001:11::
IPv6-only Server
IPv4 address:
192.0.2.1
Router
Page view 58
1 2 ... 54 55 56 57 58 59 60 61 62 63 64 ... 148 149

Comments to this Manuals

No comments