RE: The ip nat optional extendable

From: laidlaw@consecro.com
Date: Mon Sep 10 2007 - 18:10:54 ART


From this page:

http://www.cisco.com/en/US/tech/tk648/tk361/technologies_white_paper09186a0080091cb9.shtml

b" "Extendable" static translations:

The extendable keyword allows the user to configure several ambiguous
static translations, where an ambiguous translations are translations
with the same local or global address.ip nat inside source static
<localaddr> <globaladdr> extendableSome customers want to use more than
one service provider and translate into each provider's address space.
You can use route-maps to base the selection of global address pool on
output interface as well as an access-list match. Following is an
example:ip nat pool provider1-space ...ip nat pool provider2-space ...ip
nat inside source route-map provider1-map pool provider1-spaceip nat
inside source route-map provider2-map pool provider2-space!route-map
provider1-map permit 10 match ip address 1 match interface Serial0/0!route-map
provider2-map permit 10 match ip address 1 match interface Serial0/1Once
that is working, they might also want to define static mappings for a
particular host using each provider's address space. The software does
not allow two static translations with the same local address, though,
because it is ambiguous from the inside. The router will accept these
static translations and resolve the ambiguity by creating full
translations (all addresses and ports) if the static translations are
marked as "extendable". For a new outside-to-inside flow, the appropriate
static entry will act as a template for a full translation. For a new
inside-to-outside flow, the dynamic route-map rules will be used to
create a full translation.

  -------- Original Message --------
  Subject: The ip nat optional extendable
  From: "Laidlaw, Patrick A." <Patrick.Laidlaw@wwt.com>
  Date: Mon, September 10, 2007 3:34 pm
  To: <ccielab@groupstudy.com>

  So for all you smart guys out there I've got a question for you.

  The optional command "extendable" has a definition on Cisco's website
  extendable
  (Optional) Extends the transmission. So what in the world does that
  mean? What does this optional command actually do for nat.

  I've been looking and don't really see anything explaining how it
  helps
  out NAT or what kind of situation you would or would not use it in. I
  know I've seen lots of examples with it in them and that it's needed
  in
  many of them but why is it needed.

  Patrick Laidlaw
  E: patrick.laidlaw@wwt.com
  w: www.wwt.com

  _______________________________________________________________________
  Subscription information may be found at:
  http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Sat Oct 06 2007 - 12:01:10 ART