From: Robert Watson (watson.robert@gmail.com)
Date: Fri Sep 08 2006 - 16:49:25 ART
Autoaliasing of Pool Address
Many customers want to configure Cisco IOS NAT to translate their local
addresses to global addresses allocated from unused addresses from an
attached subnet. This requires that the router answer ARP requests for those
addresses so that packets destined for the global addresses are accepted by
the router and translated. (Routing takes care of this packet delivery when
the global addresses are allocated from a virtual network which isn't
connected to anything.)
When a NAT pool used as an inside global or outside local, then the pool
consists of addresses on an attached subnet, and the software will generate
an alias for that address so that the router will answer ARPs for those
addresses.
This automatic aliasing also occurs for inside global or outside local
addresses in static entries. It can be disabled for static entries with the
"no-alias" keyword:
ip nat inside source static <local-ip-address> <global-ip-address> no-alias
Extendable
allows translations from a single inside IP to multiple outside addresses
you add the extendable key to your 1 to 1 static translations
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Kal
Han
Sent: Wednesday, September 06, 2006 9:53 PM
To: Cisco certification; ccielab@groupstudy.com
Subject: nat - extendable, no-alias and redundancy
Hi
Can some one let me know where exactly these keywords can be used with nat.
nat... extendable, no-alias and redundancy.
I tried to look at cisco documentation. But its very unclear.
*extendable*
(Optional) Extends the translation.
*no-alias*
(Optional) Prohibits an alias from being created for the global address.
*redundancy *group-name
(Optional) Establishes NAT redundancy.
They just wrote the same thing in the description.
Thanks
Kal
This archive was generated by hypermail 2.1.4 : Sun Oct 01 2006 - 16:55:40 ART