1
Download Brocade Communications Systems ServerIron ADX 12.4.00 Technical data
Transcript
DRAFT: BROCADE CONFIDENTIAL Stateless NAT64 static mapping configuration ServerIron ServerIron ServerIron ServerIron ServerIron 3 ADX(config-vlan-1)# interface ve 7 ADX(config-vlan-1)# exit ADX(config)# interface ve 7 ADX(config-vif-7)# ipv6 address 2001:db8:80::80 ADX(config-vif-7)# exit 2. OSPF and OSPFv6 are configured for static route redistribution. The IPv6 side is configured as OSPF Area 0 and the IPv4 side is configured as OSPF Area 1. ServerIron ServerIron ServerIron ServerIron ServerIron ServerIron ServerIron ADX(config)# ipv6 router ospf ADX(config-ospf6-router)# redistribute static ADX(config-ospf6-router)# area 0 ADX(config-ospf6-router)# exit ADX(config)# router ospf ADX(config-ospf-router)# redistribute static ADX(config-ospf-router)# area 1 3. The NAT64 IPv4 prefix is configured with static route injection. ServerIron ADX(config)# nat64 ipv4-prefix 200.1.1.0/24 inject-static-route 4. The NAT64 IPv6 prefix is configured with static route injection. ServerIron ADX(config)# nat64 ipv6-prefix 2001:db8:64::0/96 inject-static-route stateless 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 (200.1.1.100) within the subnet defined by the NAT64 IPv4 prefix is mapped to the IPv6 address (2001:db8:80::80) specified in step 1. ServerIron ADX(config)# nat64 map 200.1.1.100 2001:db8:80::80 In a static NAT64 configuration such as this one, the only routes injected into the local routing table are routes for IPv4 addresses that are mapped specifically to IPv6 addresses. In this example, only the route to 200.1.1.1 will be distributed to the IPv4 network and not the route to the entire subnet. In dynamic NAT64 configurations, routes for all IPv4 addresses that are learned are distributed. For more information, refer to “Stateless NAT64 dynamic mapping configuration” on page 36. 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. Stateless NAT64 packet fragmentation configuration Packets from the IPv6 client to the IPv4 server can be too large and need to be split into two IPv4 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: ServerIron ADX NAT64 Configuration Guide 53-1002444-02 35
