Kings, The add-route option is specific to NAT pool, not the type of NAT implementation. So wherever you have a restriction in a task like perhaps you are prohibited from adding a static route locally, you can use this add-route keyword to insert a static route into the routing table, based on the pool range and netmask. Very similar to RRI in VPN.
A nice little addition to NAT i thought :-) Stu On Mon, Apr 19, 2010 at 10:08 AM, Kingsley Charles < [email protected]> wrote: > Hi all > > It seems, the "add-route" option where a static route for the NAT pool is > added in the routing table is applicable only for NVI NAT i.e., when using > "ip nat enable". > > *ip nat pool *name start-ip end-ip netmask netmask add-route > > Please let me know, if have seen it working for domain based NAT i.e., when > using "ip nat inside/outisde" > > > With regads > Kings > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > -- Regards, Stuart Hare CCIE #25616 (Security), CCSP, Microsoft MCP Sr. Support Engineer – IPexpert, Inc. URL: http://www.IPexpert.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
