...
-When using NAT with the "extendable" and "redundancy" arguments, the command must be entered with "redundancy" being entered before "extendable": C8K-0(config)#ip nat outside source static 123.123.123.123 10.1.1.123 vrf 10 ? add-route Add a static route for outside local address extendable Extend this translation when used match-in-vrf Match incoming vrf no-alias Do not create an alias for the local address no-payload No translation of embedded address/port in the payload pool Name pool of local addresses redundancy NAT redundancy operation stateless No flow entries(session) for mapping C8K-0(config)#ip nat outside source static 123.123.123.123 10.1.1.123 vrf 10 extendable ? add-route Add a static route for outside local address match-in-vrf Match incoming vrf no-alias Do not create an alias for the local address no-payload No translation of embedded address/port in the payload pool Name pool of local addresses stateless No flow entries(session) for mapping -However, when the command is entered, the running-config shows the command with "extended" before "redundancy": C8K-0(config)#ip nat outside source static 123.123.123.123 10.1.1.123 vrf 10 redundancy HSRP10 extendable C8K-0(config)#do sh run | inc ip nat outside source ip nat outside source static 123.123.123.123 10.1.1.123 vrf 10 extendable redundancy HSRP10 C8K-0(config)# -If it is necessary to remove this NAT rule, it cannot be copied and pasted from the running-config and must be entered as it originally was configured: C8K-0(config)#no ip nat outside source static 123.123.123.123 10.1.1.123 vrf 10 extendable redundancy HSRP10 ^ % Invalid input detected at '^' marker. C8K-0(config)#no ip nat outside source static 123.123.123.123 10.1.1.123 vrf 10 redundancy HSRP10 extendable C8K-0(config)# -This is an issue with the config parser which can cause confusion during configuration, but does not have any functional impact
-Attempt to configure NAT with "redundancy" and "extendable" CLI arguments
-Configure NAT rule with "redundancy" before "extendable"
-This is an issue with the config parser which can cause confusion during configuration, but does not have any functional impact -Nat Config with redundancy and extendable keyord is lost post reload.