PDM doesn't support multiple uses of a given control access list

[nleslie56]

I'm configuring a pix to connect to a concentrator 3000. Everything is fine so far and all the commands have been accepted in the CLI. However, i get this error message when i close out of the command line. "PDM doesn't support multiple uses of a given control access list."

I've culled over the config and everything looks fine. This is my first pix and i'm trying to follow as text book as possible. The config is below. I hate to just paste the whole thing in there but i'm not sure which part is giving me the error. Any ideas from anyone would be appreciated.


PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password RH4nGhXickfRrqVW encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname pix
domain-name pix
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list 110 permit ip 10.182.7.0 255.255.255.0 192.168.1.0 255.255.255.0
access-list 120 permit icmp any any
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 216.36.123.230 255.255.255.252
ip address inside 10.182.7.50 255.255.255.224
ip audit info action alarm
ip audit attack action alarm
pdm location 10.182.7.0 255.255.255.0 inside
pdm location 192.168.1.0 255.255.255.0 outside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list 110
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 216.36.123.229 1
route outside 192.168.1.0 255.255.255.0 192.168.1.10 1
timeout xlate 0:05:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
http server enable
http 10.182.7.32 255.255.255.224 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set aptset esp-3des esp-md5-hmac
crypto map aptmap 10 ipsec-isakmp
crypto map aptmap 10 match address 110
crypto map aptmap 10 set peer 63.170.20.175
crypto map aptmap 10 set transform-set aptset
crypto map aptmap interface outside
isakmp enable outside
isakmp key ******** address 63.170.20.175 netmask 255.255.255.255
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption 3des
isakmp policy 10 hash md5
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
telnet timeout 5
ssh 0.0.0.0 0.0.0.0 outside
ssh timeout 5
console timeout 0
dhcpd address 10.182.7.51-10.182.7.62 inside
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
dhcpd enable inside
terminal width 80

 

[moraga695]

Hello,

I don't know if this is an official fix for your situation, but it worked for me.

The problem is that your line "access-list 110 permit ip 10.182.7.0 . . . " is referenced in the line "nat (inside) 0 access-list 110" and again in the line "crypto map aptmap match address 110". The PDM doesn't like this.

My fix would be to create a duplicate of the "access-list 110 permit ip . . ." line but call it access-list 111. Then change the crypto map line to read "crypto map aptmap match address 111".

I believe this will solve the PDM issue. Others may have a more "refined" fix but I belive this will work for you.

Steve W.

 

[nleslie56]

Thank you so much. That did the trick. The thing i'm a little confused about is the pix example i printed from the cisco website uses an access-list in 3 different places, one instance to specify the ip traffic, the other to specifiy no nat on the traffic and the same access list in the crypto.....i'm wondering if my example is outdated or the firmware on my pix is different than the example. I did notice the example is pix 6.3 (1) and my pix is 6.3 (4).

In any case, thanks once again for your help...i had reconfigured the pix so many times yesterday my eyes were about to bulge out of my head.

 

[moraga695]

You are right, Cisco examples show access-lists being referred to multiple times and that is perfectly ok - but not if you are using the PDM for configuration. I don't think that version of the PIX OS makes a difference if using the PDM. It's still an issue with 6.3(5), the current version and the version of the PDM that goes with it.

 

[dopehead]

This way of doing it is only usable for one vpn tunnel, if you were to have more than one tunnel you would have to create a second acl for that tunnel, and also change the nat 0 acl to another acl that contains both tunnels traffic, and then a third acl for the new tunnel.

This is why i always start off with two acls, makes it much easier to add tunnels later.

Network Systems Engineer
CCNA/CQS/CCSP/Infosec
Check the danish Cisco CSA Forum here :

http://www.csaforum.dk