RE: NAT and "extendable" keywor

Syed,

> -----Original Message-----
> Sent: Wednesday, April 21, 2010 9:26 AM
> To: ccielab_at_groupstudy.com
> Subject: OT: NAT and "extendable" keywor
>
> Group:
> I did look at the command reference but could not exactly locate the
> "extendable keyword" purpose.
>
> regards,Khalid
>

I'm sure there are better explanations for this, but it's used when there are multiple source and destination mappings using the same source. i.e. if you had two exit points out of your network and wanted to use the same source. I don't think this is a requirement with route-map based NAT though.

Have a look here at route-map based NAT:

 https://supportforums.cisco.com/docs/DOC-5061

Rack1R1(config)#ip nat inside source static 150.1.1.1 155.1.146.3
Rack1R1(config)#ip nat inside source static 150.1.1.1 155.1.13.1
% 150.1.1.1 already mapped (150.1.1.1 -> 155.1.146.3)
Rack1R1(config)#no ip nat inside source static 150.1.1.1 155.1.146.3
Rack1R1(config)#ip nat inside source static 150.1.1.1 155.1.146.3 extendable
Rack1R1(config)#ip nat inside source static 150.1.1.1 155.1.13.1 extendable
Rack1R1(config)#do show ip nat trans ver
Pro Inside global Inside local Outside local Outside global
--- 155.1.146.3 150.1.1.1 --- ---
    create 00:06:18, use 00:06:13 timeout:0,
    flags:
static, extendable, use_count: 0, entry-id: 3, lc_entries: 0
--- 155.1.13.1 150.1.1.1 --- ---
    create 00:06:13, use 00:06:13 timeout:0,
    flags:
static, extendable, global-only-entry, use_count: 0, entry-id: 4, lc_entries: 0

-ryan

Blogs and organic groups at http://www.ccie.net
Received on Wed Apr 21 2010 - 13:48:47 ART