Cisco ASA - need to allow Ping and Traceroute

Similar Questions

• NX - OS enable ping and traceroute

  Hi all!

  At my new job, I have a cisco nexus switch 5548 and I never worked with her before.

  Can someone explain to me how to activate the command 'ping' or 'traceroute' on this subject?

  P.S I hear it can be activated with the command "function (config) #"... Is it true?

  THX in advice

  Hello

  You must enable any feature to use ping and traceroute commands.

  Here's the documentation on this subject:

  Ping:

  http://www.Cisco.com/c/en/us/TD/docs/switches/Datacenter/nexus5000/SW/co...

  Traceroute:

  http://www.Cisco.com/c/en/us/TD/docs/switches/Datacenter/nexus5000/SW/co...

• EzVPN between Cisco ASA 5505 (with NEM mode) and Ciscoo 881 Roure

  Hi friends,

  I configured the Cisco ASA 5505 and Cisco router with DMVPN 881. 3 offices works very well but one office remains failure. I did the same configuration for all facilities but this router does not work. Any ideas?

  Please find below the exit of 881 router Cisco:

  YF2_Tbilisi_router #.
  * 4 August 09:31:26.793: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH...
  * 09:31:26.793 4 August: ISAKMP (0): increment the count of errors on his, try 4 out 5: retransmit the phase 1
  * 4 August 09:31:26.793: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH
  * 4 August 09:31:26.793: ISAKMP: (0): 1.1.1.1 package sending 500 peer_port 500 (I) my_port AG_INIT_EXCH
  * 09:31:26.793 4 August: ISAKMP: (0): sending a packet IPv4 IKE.
  * 4 August 09:31:36.793: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH...
  * 09:31:36.793 4 August: ISAKMP (0): increment the count of errors on his, try 5 of 5: retransmit the phase 1
  * 4 August 09:31:36.793: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH
  * 4 August 09:31:36.793: ISAKMP: (0): 1.1.1.1 package sending 500 peer_port 500 (I) my_port AG_INIT_EXCH
  * 09:31:36.793 4 August: ISAKMP: (0): sending a packet IPv4 IKE.
  * 09:31:44.929 4 August: ISAKMP: (0): serving SA., its is 88961 B 34, delme is 88961 B 34
  * 4 August 09:31:46.793: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH...
  * 09:31:46.793 4 August: ISAKMP: (0): the peer is not paranoid KeepAlive.

  * 09:31:46.793 4 August: ISAKMP: (0): removal of reason ITS status of 'Death by retransmission P1' (I) AG_INIT_EXCH (peer 1.1.1.1)
  * 09:31:46.793 4 August: % CRYPTO-6-EZVPN_CONNECTION_DOWN: user (customer) = group = Youth_Facility_2 Server_public_addr = 1.1.1.1
  * 4 August 09:31:46.793: ISAKMP:isadb_key_addr_delete: no key for address 1.1.1.1 (root NULL)
  * 09:31:46.793 4 August: ISAKMP: (0): removal of reason ITS status of 'Death by retransmission P1' (I) AG_INIT_EXCH (peer 1.1.1.1)
  * 09:31:46.793 4 August: ISAKMP: Unlocking counterpart struct 0x8AA90C50 for isadb_mark_sa_deleted(), count 0
  * 09:31:46.793 4 August: ISAKMP: delete peer node by peer_reap for 1.1.1.1: 8AA90C50
  * 09:31:46.793 4 August: ISAKMP: (0): entry = IKE_MESG_INTERNAL, IKE_PHASE1_DEL
  * 09:31:46.793 4 August: ISAKMP: (0): former State = new State IKE_I_AM1 = IKE_DEST_SA

  * 4 August 09:31:47.805: del_node 2.2.2.2 src dst 1.1.1.1:500 fvrf 0 x 0, ivrf 0 x 0
  * 09:31:47.805 4 August: ISAKMP: (0): the peer is not paranoid KeepAlive.

  * 4 August 09:31:47.805: ISAKMP: (0): profile of THE request is (NULL)
  * 09:31:47.805 4 August: ISAKMP: created a struct peer 1.1.1.1, peer port 500
  * 09:31:47.805 4 August: ISAKMP: new created position = 0x8AA90C50 peer_handle = 0 x 80004819
  * 09:31:47.805 4 August: ISAKMP: lock struct 0x8AA90C50, refcount 1 to peer isakmp_initiator
  * 09:31:47.805 4 August: ISAKMP: (0): client configuration parameters 87531228 adjustment
  * 09:31:47.805 4 August: ISAKMP: 500 local port, remote port 500
  * 09:31:47.805 4 August: ISAKMP: find a dup her to the tree during his B 88961, 34 = isadb_insert call BVA
  * 4 August 09:31:47.805: ISAKMP: (0): set up client mode.
  * 4 August 09:31:47.805: ISAKMP: (0): built of NAT - T of the seller-rfc3947 ID
  * 4 August 09:31:47.805: ISAKMP: (0): built the seller-07 ID NAT - t
  * 4 August 09:31:47.805: ISAKMP: (0): built of NAT - T of the seller-03 ID
  * 4 August 09:31:47.805: ISAKMP: (0): built the seller-02 ID NAT - t
  * 4 August 09:31:47.805: ISKAMP: more send buffer from 1024 to 3072
  * 09:31:47.805 4 August: ISAKMP: (0): ITS been pre-shared key and XAUTH authentication using id ID_KEY_ID type
  * 09:31:47.805 4 August: ISAKMP (0): payload ID
  next payload: 13
  type: 11
  Group ID: Youth_Facility_2
  Protocol: 17
  Port: 0
  Length: 24
  * 09:31:47.805 4 August: ISAKMP: (0): the total payload length: 24
  * 09:31:47.809 4 August: ISAKMP: (0): entry = IKE_MESG_FROM_IPSEC, IKE_SA_REQ_AM
  * 09:31:47.809 4 August: ISAKMP: (0): former State = new State IKE_READY = IKE_I_AM1

  * 4 August 09:31:47.809: ISAKMP: (0): Beginner aggressive Mode Exchange
  * 4 August 09:31:47.809: ISAKMP: (0): 1.1.1.1 package sending 500 peer_port 500 (I) my_port AG_INIT_EXCH
  * 09:31:47.809 4 August: ISAKMP: (0): sending a packet IPv4 IKE.
  * 4 August 09:31:57.809: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH...
  * 09:31:57.809 4 August: ISAKMP (0): increment the count of errors on his, try 1 5: retransmit the phase 1
  * 4 August 09:31:57.809: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH
  * 4 August 09:31:57.809: ISAKMP: (0): 1.1.1.1 package sending 500 peer_port 500 (I) my_port AG_INIT_EXCH
  * 09:31:57.809 4 August: ISAKMP: (0): sending a packet IPv4 IKE.
  * 4 August 09:32:07.809: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH...
  * 09:32:07.809 4 August: ISAKMP (0): increment the count of errors on his, try 2 of 5: retransmit the phase 1
  * 4 August 09:32:07.809: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH
  * 4 August 09:32:07.809: ISAKMP: (0): 1.1.1.1 package sending 500 peer_port 500 (I) my_port AG_INIT_EXCH
  * 09:32:07.809 4 August: ISAKMP: (0): sending a packet IPv4 IKE.
  * 4 August 09:32:17.809: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH...
  * 09:32:17.809 4 August: ISAKMP (0): increment the count of errors on his, try 3 of 5: retransmit the phase 1
  * 4 August 09:32:17.809: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH
  * 4 August 09:32:17.809: ISAKMP: (0): 1.1.1.1 package sending 500 peer_port 500 (I) my_port AG_INIT_EXCH
  * 09:32:17.809 4 August: ISAKMP: (0): sending a packet IPv4 IKE.
  * 4 August 09:32:27.809: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH...
  * 09:32:27.809 4 August: ISAKMP (0): increment the count of errors on his, try 4 out 5: retransmit the phase 1
  * 4 August 09:32:27.809: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH
  * 4 August 09:32:27.809: ISAKMP: (0): 1.1.1.1 package sending 500 peer_port 500 (I) my_port AG_INIT_EXCH
  * 09:32:27.809 4 August: ISAKMP: (0): sending a packet IPv4 IKE.
  * 4 August 09:32:37.809: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH...
  * 09:32:37.809 4 August: ISAKMP (0): increment the count of errors on his, try 5 of 5: retransmit the phase 1
  * 4 August 09:32:37.809: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH
  * 4 August 09:32:37.809: ISAKMP: (0): 1.1.1.1 package sending 500 peer_port 500 (I) my_port AG_INIT_EXCH
  * 09:32:37.809 4 August: ISAKMP: (0): sending a packet IPv4 IKE.
  * 09:32:46.793 4 August: ISAKMP: (0): serving SA., his is 872E1504, delme is 872E1504
  * 4 August 09:32:47.809: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH...
  * 09:32:47.809 4 August: ISAKMP: (0): the peer is not paranoid KeepAlive.

  * 09:32:47.809 4 August: ISAKMP: (0): removal of reason ITS status of 'Death by retransmission P1' (I) AG_INIT_EXCH (peer 1.1.1.1)
  * 09:32:47.809 4 August: % CRYPTO-6-EZVPN_CONNECTION_DOWN: user (customer) = group = Youth_Facility_2 Server_public_addr = 1.1.1.1
  * 4 August 09:32:47.809: ISAKMP:isadb_key_addr_delete: no key for address 1.1.1.1 (root NULL)
  * 09:32:47.809 4 August: ISAKMP: (0): removal of reason ITS status of 'Death by retransmission P1' (I) AG_INIT_EXCH (peer 1.1.1.1)
  * 09:32:47.809 4 August: ISAKMP: Unlocking counterpart struct 0x8AA90C50 for isadb_mark_sa_deleted(), count 0
  * 09:32:47.809 4 August: ISAKMP: delete peer node by peer_reap for 1.1.1.1: 8AA90C50
  * 09:32:47.809 4 August: ISAKMP: (0): entry = IKE_MESG_INTERNAL, IKE_PHASE1_DEL
  * 09:32:47.809 4 August: ISAKMP: (0): former State = new State IKE_I_AM1 = IKE_DEST_SA

  * 4 August 09:32:48.909: del_node src 2.2.2.2:500 dst 1.1.1.1:500 fvrf 0 x 0, ivrf 0 x 0
  * 09:32:48.909 4 August: ISAKMP: (0): the peer is not paranoid KeepAlive.

  * 4 August 09:32:48.909: ISAKMP: (0): profile of THE request is (NULL)
  * 09:32:48.909 4 August: ISAKMP: created a struct peer 1.1.1.1, peer port 500
  * 09:32:48.909 4 August: ISAKMP: new created position = 0x8AA90C50 peer_handle = 0 x 80004818
  * 09:32:48.909 4 August: ISAKMP: lock struct 0x8AA90C50, refcount 1 to peer isakmp_initiator
  * 09:32:48.909 4 August: ISAKMP: (0): client setting Configuration parameters 88C05A48
  * 09:32:48.909 4 August: ISAKMP: 500 local port, remote port 500
  * 09:32:48.909 4 August: ISAKMP: find a dup her to the tree during the isadb_insert his 87B57D38 = call BVA
  * 4 August 09:32:48.909: ISAKMP: (0): set up client mode.
  * 4 August 09:32:48.909: ISAKMP: (0): built of NAT - T of the seller-rfc3947 ID
  * 4 August 09:32:48.909: ISAKMP: (0): built the seller-07 ID NAT - t
  * 4 August 09:32:48.909: ISAKMP: (0): built of NAT - T of the seller-03 ID
  * 4 August 09:32:48.909: ISAKMP: (0): built the seller-02 ID NAT - t
  * 4 August 09:32:48.909: ISKAMP: more send buffer from 1024 to 3072
  * 09:32:48.913 4 August: ISAKMP: (0): ITS been pre-shared key and XAUTH authentication using id ID_KEY_ID type
  * 09:32:48.913 4 August: ISAKMP (0): payload ID
  next payload: 13
  type: 11
  Group ID: Youth_Facility_2
  Protocol: 17
  Port: 0
  Length: 24
  * 09:32:48.913 4 August: ISAKMP: (0): the total payload length: 24
  * 09:32:48.913 4 August: ISAKMP: (0): entry = IKE_MESG_FROM_IPSEC, IKE_SA_REQ_AM
  * 09:32:48.913 4 August: ISAKMP: (0): former State = new State IKE_READY = IKE_I_AM1

  * 4 August 09:32:48.913: ISAKMP: (0): Beginner aggressive Mode Exchange
  * 4 August 09:32:48.913: ISAKMP: (0): 1.1.1.1 package sending 500 peer_port 500 (I) my_port AG_INIT_EXCH
  * 09:32:48.913 4 August: ISAKMP: (0): sending a packet IPv4 IKE.
  * 4 August 09:32:58.913: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH...
  * 09:32:58.913 4 August: ISAKMP (0): increment the count of errors on his, try 1 5: retransmit the phase 1
  * 4 August 09:32:58.913: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH
  * 4 August 09:32:58.913: ISAKMP: (0): 1.1.1.1 package sending 500 peer_port 500 (I) my_port AG_INIT_EXCH
  * 09:32:58.913 4 August: ISAKMP: (0): sending a packet IPv4 IKE.
  * 4 August 09:33:08.913: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH...
  * 09:33:08.913 4 August: ISAKMP (0): increment the count of errors on his, try 2 of 5: retransmit the phase 1
  * 4 August 09:33:08.913: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH
  * 4 August 09:33:08.913: ISAKMP: (0): 1.1.1.1 package sending 500 peer_port 500 (I) my_port AG_INIT_EXCH
  * 09:33:08.913 4 August: ISAKMP: (0): sending a packet IPv4 IKE.
  * 4 August 09:33:18.913: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH...
  * 09:33:18.913 4 August: ISAKMP (0): increment the count of errors on his, try 3 of 5: retransmit the phase 1
  * 4 August 09:33:18.913: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH
  * 4 August 09:33:18.913: ISAKMP: (0): 1.1.1.1 package sending 500 peer_port 500 (I) my_port AG_INIT_EXCH
  * 09:33:18.913 4 August: ISAKMP: (0): sending a packet IPv4 IKE.
  * 4 August 09:33:28.913: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH...
  * 09:33:28.913 4 August: ISAKMP (0): increment the count of errors on his, try 4 out 5: retransmit the phase 1
  * 4 August 09:33:28.913: ISAKMP: (0): transmit phase 1 AG_INIT_EXCH
  * 4 August 09:33:28.913: ISAKMP: (0): 1.1.1.1 package sending 500 peer_port 500 (I) my_port AG_INIT_EXCH
  * 09:33:28.913 4 August: ISAKMP: (0): sending a packet IPv4 IKE.

  There is no DMVPN on the SAA. All that you have configured, is not compatible with the ASA or something another DMVPN then. At least debugging shows that there are some EzVPN involved.

  The debug version, it seems that there is no communication on UDP/500 possible between devices. Maybe something is blocking who?

• Cisco VPN client 3.5.1 and Cisco ASA 5.2 (2)

  Hello

  I have a strange problem about Cisco VPN client (IPSec) with Cisco ASA. The Cisco ASA runs software version 5.2 (2). The Cisco VPN client version is 3.5.1.

  The problem is the customer able Cisco VPN to authenticate successfully with Cisco ASA, but could not PING to any LAN behind the Cisco ASA. In any case, the problem disappeared when we used the Cisco VPN version 4.6 or 4.8 of the customer. All parameters are exactly the same. What has happened? What is the cause of this problem? How can I solve this problem?

  Please advice.

  Thank you

  Nitass

  I understand your problem, I never used 3.5.1 so I thought that maybe nat - t is not enabled by default as 4.x.

• % 7-ASA-710005: request TCP thrown error in the Client VPN Site to CISCO ASA 5510

  Hi friends,

  I am trying to built customer to site VPN CISCO ASA 5510 8.4 (4) and get error below when connecting to a cisco VPN client software. Also, I'm below ASA, log. Please help me to reslove.

  Error in CISCO VPN Client software:

  Secure VPN connection terminated locally by the client.

  Reason: 414: unable to establish a TCP connection.

  Error in CISCO ASA 5510

  7-ASA-710005%: TCP request and eliminated from 49276 outward: 10000

  The ASA configuration:

  XYZ # sh run
  : Saved
  :
  ASA Version 8.4 (4)
  !
  hostname XYZ
  domain XYZ
  activate the password encrypted 3uLkVc9JwRA1/OXb N3
  activate the encrypted password of R/x90UjisGVJVlh2
  2KFQnbNIdI.2KYOU encrypted passwd
  names of
  !
  interface Ethernet0/0
  nameif outside_rim
  security-level 0
  IP 1.1.1.1 255.255.255.252
  !
  interface Ethernet0/1
  full duplex
  nameif XYZ_DMZ
  security-level 50
  IP 172.1.1.1 255.255.255.248
  !
  interface Ethernet0/2
  Speed 100
  full duplex
  nameif outside
  security-level 0
  IP address 2.2.2.2 255.255.255.252
  !
  interface Ethernet0/3
  Speed 100
  full duplex
  nameif inside
  security-level 100
  IP 3.3.3.3 255.255.255.224
  !
  interface Management0/0
  Shutdown
  No nameif
  no level of security
  no ip address
  !
  boot system Disk0: / asa844 - k8.bin
  passive FTP mode
  DNS domain-lookup outside
  DNS server-group DefaultDNS
  Server name xx.xx.xx.xx
  Server name xx.xx.xx.xx
  Server name xx.xx.xx.xx
  Server name xx.xx.xx.xx
  domain XYZ
  network object obj - 172.17.10.3
  Home 172.17.10.3
  network object obj - 10.1.134.0
  10.1.134.0 subnet 255.255.255.0
  network object obj - 208.75.237.0
  208.75.237.0 subnet 255.255.255.0
  network object obj - 10.7.0.0
  10.7.0.0 subnet 255.255.0.0
  network object obj - 172.17.2.0
  172.17.2.0 subnet 255.255.255.0
  network object obj - 172.17.3.0
  172.17.3.0 subnet 255.255.255.0
  network object obj - 172.19.2.0
  172.19.2.0 subnet 255.255.255.0
  network object obj - 172.19.3.0
  172.19.3.0 subnet 255.255.255.0
  network object obj - 172.19.7.0
  172.19.7.0 subnet 255.255.255.0
  network object obj - 10.1.0.0
  10.1.0.0 subnet 255.255.0.0
  network object obj - 10.2.0.0
  10.2.0.0 subnet 255.255.0.0
  network object obj - 10.3.0.0
  10.3.0.0 subnet 255.255.0.0
  network object obj - 10.4.0.0
  10.4.0.0 subnet 255.255.0.0
  network object obj - 10.6.0.0
  10.6.0.0 subnet 255.255.0.0
  network object obj - 10.9.0.0
  10.9.0.0 subnet 255.255.0.0
  network object obj - 10.11.0.0
  10.11.0.0 subnet 255.255.0.0
  network object obj - 10.12.0.0
  10.12.0.0 subnet 255.255.0.0
  network object obj - 172.19.1.0
  172.19.1.0 subnet 255.255.255.0
  network object obj - 172.21.2.0
  172.21.2.0 subnet 255.255.255.0
  network object obj - 172.16.2.0
  172.16.2.0 subnet 255.255.255.0
  network object obj - 10.19.130.201
  Home 10.19.130.201
  network object obj - 172.30.2.0
  172.30.2.0 subnet 255.255.255.0
  network object obj - 172.30.3.0
  172.30.3.0 subnet 255.255.255.0
  network object obj - 172.30.7.0
  172.30.7.0 subnet 255.255.255.0
  network object obj - 10.10.1.0
  10.10.1.0 subnet 255.255.255.0
  network object obj - 10.19.130.0
  10.19.130.0 subnet 255.255.255.0
  network of object obj-XXXXXXXX
  host XXXXXXXX
  network object obj - 145.248.194.0
  145.248.194.0 subnet 255.255.255.0
  network object obj - 10.1.134.100
  Home 10.1.134.100
  network object obj - 10.9.124.100
  Home 10.9.124.100
  network object obj - 10.1.134.101
  Home 10.1.134.101
  network object obj - 10.9.124.101
  Home 10.9.124.101
  network object obj - 10.1.134.102
  Home 10.1.134.102
  network object obj - 10.9.124.102
  Home 10.9.124.102
  network object obj - 115.111.99.133
  Home 115.111.99.133
  network object obj - 10.8.108.0
  10.8.108.0 subnet 255.255.255.0
  network object obj - 115.111.99.129
  Home 115.111.99.129
  network object obj - 195.254.159.133
  Home 195.254.159.133
  network object obj - 195.254.158.136
  Home 195.254.158.136
  network object obj - 209.164.192.0
  subnet 209.164.192.0 255.255.224.0
  network object obj - 209.164.208.19
  Home 209.164.208.19
  network object obj - 209.164.192.126
  Home 209.164.192.126
  network object obj - 10.8.100.128
  subnet 10.8.100.128 255.255.255.128
  network object obj - 115.111.99.130
  Home 115.111.99.130
  network object obj - 10.10.0.0
  subnet 10.10.0.0 255.255.0.0
  network object obj - 115.111.99.132
  Home 115.111.99.132
  network object obj - 10.10.1.45
  Home 10.10.1.45
  network object obj - 10.99.132.0
  10.99.132.0 subnet 255.255.255.0
  the Serversubnet object-group network
  object-network 10.10.1.0 255.255.255.0
  network-object 10.10.5.0 255.255.255.192
  the XYZ_destinations object-group network
  object-network 10.1.0.0 255.255.0.0
  object-network 10.2.0.0 255.255.0.0
  network-object 10.3.0.0 255.255.0.0
  network-object 10.4.0.0 255.255.0.0
  network-object 10.6.0.0 255.255.0.0
  network-object 10.7.0.0 255.255.0.0
  network-object 10.11.0.0 255.255.0.0
  object-network 10.12.0.0 255.255.0.0
  object-network 172.19.1.0 255.255.255.0
  object-network 172.19.2.0 255.255.255.0
  object-network 172.19.3.0 255.255.255.0
  object-network 172.19.7.0 255.255.255.0
  object-network 172.17.2.0 255.255.255.0
  object-network 172.17.3.0 255.255.255.0
  object-network 172.16.2.0 255.255.255.0
  object-network 172.16.3.0 255.255.255.0
  host of the object-Network 10.50.2.206
  the XYZ_us_admin object-group network
  network-object 10.3.1.245 255.255.255.255
  network-object 10.5.33.7 255.255.255.255
  network-object 10.211.5.7 255.255.255.255
  network-object 10.3.33.7 255.255.255.255
  network-object 10.211.3.7 255.255.255.255
  the XYZ_blr_networkdevices object-group network
  object-network 10.200.10.0 255.255.255.0
  access list XYZ extended ip 10.19.130.0 allow 255.255.255.0 145.248.194.0 255.255.255.0
  access list XYZ extended ip 10.19.130.0 allow 255.255.255.0 host 172.16.2.21
  access list XYZ extended ip 10.19.130.0 allow 255.255.255.0 host 172.16.2.22
  access list XYZ extended ip 10.19.130.0 allow 255.255.255.0 host XXXXXXXX
  Access extensive list ip 10.19.130.0 XYZ_PAT allow 255.255.255.0 any
  Access extensive list ip 10.1.134.0 XYZ_PAT allow 255.255.255.0 host 195.254.159.133
  Access extensive list ip 10.1.134.0 XYZ_PAT allow 255.255.255.0 host 195.254.158.136
  Access extensive list ip 10.1.134.0 XYZ_PAT allow 255.255.255.0 any
  Access extensive list ip 10.1.134.0 XYZ_PAT allow 255.255.255.0 209.164.192.0 255.255.224.0
  Access extensive list ip 10.1.134.0 XYZ_PAT allow 255.255.255.0 host 209.164.208.19
  Access extensive list ip 10.1.134.0 XYZ_PAT allow 255.255.255.0 host 209.164.192.126
  IP 10.1.134.0 allow Access-list extended sheep 255.255.255.0 208.75.237.0 255.255.255.0
  Allow Access-list extended sheep 255.255.255.0 10.1.134.0 IP 10.7.0.0 255.255.0.0
  IP 10.1.134.0 allow Access-list extended sheep 255.255.255.0 172.17.2.0 255.255.255.0
  IP 10.1.134.0 allow Access-list extended sheep 255.255.255.0 172.17.3.0 255.255.255.0
  IP 10.1.134.0 allow Access-list extended sheep 255.255.255.0 172.19.2.0 255.255.255.0
  IP 10.1.134.0 allow Access-list extended sheep 255.255.255.0 172.19.3.0 255.255.255.0
  IP 10.1.134.0 allow Access-list extended sheep 255.255.255.0 172.19.7.0 255.255.255.0
  10.1.134.0 IP Access-list extended sheep 255.255.255.0 allow 10.1.0.0 255.255.0.0
  10.1.134.0 IP Access-list extended sheep 255.255.255.0 allow 10.2.0.0 255.255.0.0
  Allow Access-list extended sheep 255.255.255.0 10.1.134.0 IP 10.3.0.0 255.255.0.0
  10.1.134.0 IP Access-list extended sheep 255.255.255.0 allow 10.4.0.0 255.255.0.0
  10.1.134.0 IP Access-list extended sheep 255.255.255.0 allow 10.6.0.0 255.255.0.0
  Allow Access-list extended sheep 255.255.255.0 10.1.134.0 IP 10.9.0.0 255.255.0.0
  Allow Access-list extended sheep 255.255.255.0 10.1.134.0 IP 10.11.0.0 255.255.0.0
  10.1.134.0 IP Access-list extended sheep 255.255.255.0 allow 10.12.0.0 255.255.0.0
  IP 10.1.134.0 allow Access-list extended sheep 255.255.255.0 172.19.1.0 255.255.255.0
  IP 10.1.134.0 allow Access-list extended sheep 255.255.255.0 172.21.2.0 255.255.255.0
  10.1.134.0 IP Access-list extended sheep 255.255.255.0 allow 172.16.2.0 255.255.255.0
  access-list extended sheep allowed host ip 10.19.130.201 172.30.2.0 255.255.255.0
  access-list extended sheep allowed host ip 10.19.130.201 172.30.3.0 255.255.255.0
  access-list extended sheep allowed host ip 10.19.130.201 172.30.7.0 255.255.255.0
  access-list extended sheep allowed ip object-group Serversubnet-group of objects XYZ_destinations
  10.10.1.0 IP Access-list extended sheep 255.255.255.0 allow 10.2.0.0 255.255.0.0
  10.19.130.0 IP Access-list extended sheep 255.255.255.0 allow host XXXXXXXX
  IP 10.19.130.0 allow Access-list extended sheep 255.255.255.0 145.248.194.0 255.255.255.0
  Access extensive list ip 10.8.108.0 Guest_PAT allow 255.255.255.0 any
  CACIB list extended access permitted ip 10.8.100.128 255.255.255.128 145.248.194.0 255.255.255.0
  Access extensive list ip 10.8.100.128 Cacib_PAT allow 255.255.255.128 all
  Access extensive list ip 10.1.134.0 New_Edge allow 255.255.255.0 208.75.237.0 255.255.255.0
  Allow XYZ_global to access extended list ip 10.7.0.0 255.255.0.0 10.1.134.0 255.255.255.0
  Access extensive list ip 10.1.134.0 XYZ_global allow 255.255.255.0 10.7.0.0 255.255.0.0
  Access extensive list ip 172.17.2.0 XYZ_global allow 255.255.255.0 10.1.134.0 255.255.255.0
  Access extensive list ip 172.17.3.0 XYZ_global allow 255.255.255.0 10.1.134.0 255.255.255.0
  Access extensive list ip 172.19.2.0 XYZ_global allow 255.255.255.0 10.1.134.0 255.255.255.0
  Access extensive list ip 172.19.3.0 XYZ_global allow 255.255.255.0 10.1.134.0 255.255.255.0
  Access extensive list ip 172.19.7.0 XYZ_global allow 255.255.255.0 10.1.134.0 255.255.255.0
  Access extensive list ip 10.1.0.0 XYZ_global allow 255.255.0.0 10.1.134.0 255.255.255.0
  Access extensive list 10.2.0.0 ip XYZ_global 255.255.0.0 allow 10.1.134.0 255.255.255.0
  Allow XYZ_global to access extended list ip 10.3.0.0 255.255.0.0 10.1.134.0 255.255.255.0
  Access extensive list 10.4.0.0 ip XYZ_global 255.255.0.0 allow 10.1.134.0 255.255.255.0
  Access extensive list 10.6.0.0 ip XYZ_global 255.255.0.0 allow 10.1.134.0 255.255.255.0
  Access extensive list ip 10.9.0.0 XYZ_global allow 255.255.0.0 10.1.134.0 255.255.255.0
  Allow XYZ_global to access extended list ip 10.11.0.0 255.255.0.0 10.1.134.0 255.255.255.0
  Access extensive list 10.12.0.0 ip XYZ_global 255.255.0.0 allow 10.1.134.0 255.255.255.0
  Access extensive list ip 172.19.1.0 XYZ_global allow 255.255.255.0 10.1.134.0 255.255.255.0
  Access extensive list ip 172.21.2.0 XYZ_global allow 255.255.255.0 10.1.134.0 255.255.255.0
  Access extensive list ip 10.1.134.0 XYZ_global allow 255.255.255.0 172.17.2.0 255.255.255.0
  Access extensive list ip 10.1.134.0 XYZ_global allow 255.255.255.0 172.17.3.0 255.255.255.0
  Access extensive list ip 10.1.134.0 XYZ_global allow 255.255.255.0 172.19.2.0 255.255.255.0
  Access extensive list ip 10.1.134.0 XYZ_global allow 255.255.255.0 172.19.3.0 255.255.255.0
  Access extensive list ip 10.1.134.0 XYZ_global allow 255.255.255.0 172.19.7.0 255.255.255.0
  Access extensive list ip 10.1.134.0 XYZ_global allow 255.255.255.0 10.1.0.0 255.255.0.0
  Access extensive list ip 10.1.134.0 XYZ_global allow 255.255.255.0 10.2.0.0 255.255.0.0
  Access extensive list ip 10.1.134.0 XYZ_global allow 255.255.255.0 10.3.0.0 255.255.0.0
  Access extensive list ip 10.1.134.0 XYZ_global allow 255.255.255.0 10.4.0.0 255.255.0.0
  Access extensive list ip 10.1.134.0 XYZ_global allow 255.255.255.0 10.6.0.0 255.255.0.0
  Access extensive list ip 10.1.134.0 XYZ_global allow 255.255.255.0 10.9.0.0 255.255.0.0
  Access extensive list ip 10.1.134.0 XYZ_global allow 255.255.255.0 10.11.0.0 255.255.0.0
  Access extensive list ip 10.1.134.0 XYZ_global allow 255.255.255.0 10.12.0.0 255.255.0.0
  Access extensive list ip 10.1.134.0 XYZ_global allow 255.255.255.0 172.19.1.0 255.255.255.0
  Access extensive list ip 10.1.134.0 XYZ_global allow 255.255.255.0 172.21.2.0 255.255.255.0
  XYZ_global to access extended list ip 172.16.2.0 allow 255.255.255.0 10.1.134.0 255.255.255.0
  Access extensive list ip 10.1.134.0 XYZ_global allow 255.255.255.0 172.16.2.0 255.255.255.0
  Access extensive list ip 172.30.2.0 XYZ_global allow 255.255.255.0 host 10.19.130.201
  XYZ_global list extended access allowed host ip 10.19.130.201 172.30.2.0 255.255.255.0
  Access extensive list ip 172.30.3.0 XYZ_global allow 255.255.255.0 host 10.19.130.201
  XYZ_global list extended access allowed host ip 10.19.130.201 172.30.3.0 255.255.255.0
  Access extensive list ip 172.30.7.0 XYZ_global allow 255.255.255.0 host 10.19.130.201
  XYZ_global list extended access allowed host ip 10.19.130.201 172.30.7.0 255.255.255.0
  XYZ_global list extended access permitted ip object-group Serversubnet-group of objects XYZ_destinations
  XYZ_global list extended access permitted ip object-group XYZ_destinations-group of objects Serversubnet
  ML_VPN list extended access allowed host ip 115.111.99.129 209.164.192.0 255.255.224.0
  permit access list extended ip host 115.111.99.129 ML_VPN 209.164.208.19
  permit access list extended ip host 115.111.99.129 ML_VPN 209.164.192.126
  permit access list extended ip host 10.9.124.100 Da_VPN 10.125.81.88
  permit access list extended ip host 10.9.124.101 Da_VPN 10.125.81.88
  permit access list extended ip host 10.9.124.102 Da_VPN 10.125.81.88
  Da_VPN list extended access allowed host ip 10.9.124.100 10.125.81.0 255.255.255.0
  Da_VPN list extended access allowed host ip 10.9.124.101 10.125.81.0 255.255.255.0
  Da_VPN list extended access allowed host ip 10.9.124.102 10.125.81.0 255.255.255.0
  Sr_PAT to access extended list ip 10.10.0.0 allow 255.255.0.0 any
  Da_Pd_VPN list extended access allowed host ip 10.9.124.100 10.125.80.64 255.255.255.192
  Da_Pd_VPN list extended access allowed host ip 10.9.124.100 10.125.64.0 255.255.240.0
  permit access list extended ip host 10.9.124.100 Da_Pd_VPN 10.125.85.46
  permit access list extended ip host 10.9.124.100 Da_Pd_VPN 10.125.86.46
  Da_Pd_VPN list extended access allowed host ip 10.9.124.101 10.125.80.64 255.255.255.192
  Da_Pd_VPN list extended access allowed host ip 10.9.124.101 10.125.64.0 255.255.240.0
  permit access list extended ip host 10.9.124.101 Da_Pd_VPN 10.125.85.46
  permit access list extended ip host 10.9.124.101 Da_Pd_VPN 10.125.86.46
  Da_Pd_VPN list extended access allowed host ip 10.9.124.102 10.125.80.64 255.255.255.192
  Da_Pd_VPN list extended access allowed host ip 10.9.124.102 10.125.64.0 255.255.240.0
  permit access list extended ip host 10.9.124.102 Da_Pd_VPN 10.125.85.46
  permit access list extended ip host 10.9.124.102 Da_Pd_VPN 10.125.86.46
  Access extensive list ip 10.19.130.0 XYZ_reliance allow 255.255.255.0 145.248.194.0 255.255.255.0
  access-list coextended permit ip host 2.2.2.2 XXXXXXXX
  access-list coextended allow the host ip XXXXXXXXhost 2.2.2.2
  permitted this access list extended ip 10.1.134.0 255.255.255.0 208.75.237.0 255.255.255.0
  permitted this access list extended ip 208.75.237.0 255.255.255.0 10.1.134.0 255.255.255.0
  access list acl-outside extended permit ip host 57.66.81.159 172.17.10.3
  access list acl-outside extended permit ip host 80.169.223.179 172.17.10.3
  access list acl-outside scope permit ip any host 172.17.10.3
  access list acl-outside extended permitted tcp any host 10.10.1.45 eq https
  access list acl-outside extended permit tcp any any eq 10000
  access list acl-outside extended deny ip any any newspaper
  pager lines 10
  Enable logging
  debug logging in buffered memory
  outside_rim MTU 1500
  MTU 1500 XYZ_DMZ
  Outside 1500 MTU
  Within 1500 MTU
  IP pool local XYZ_c2s_vpn_pool 172.30.10.51 - 172.30.10.254
  ICMP unreachable rate-limit 1 burst-size 1
  ICMP allow all outside
  ICMP allow any inside
  don't allow no asdm history
  ARP timeout 14400
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 208.75.237.0 obj - 208.75.237.0 no-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 10.7.0.0 obj - 10.7.0.0 no-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 172.17.2.0 obj - 172.17.2.0 no-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 172.17.3.0 obj - 172.17.3.0 no-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 172.19.2.0 obj - 172.19.2.0 no-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 172.19.3.0 obj - 172.19.3.0 no-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 172.19.7.0 obj - 172.19.7.0 no-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 10.1.0.0 obj - 10.1.0.0 non-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 10.2.0.0 obj - 10.2.0.0 non-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 10.3.0.0 obj - 10.3.0.0 no-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 10.4.0.0 obj - 10.4.0.0 non-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 10.6.0.0 obj - 10.6.0.0 non-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 10.9.0.0 obj - 10.9.0.0 no-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 10.11.0.0 obj - 10.11.0.0 no-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 10.12.0.0 obj - 10.12.0.0 non-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 172.19.1.0 obj - 172.19.1.0 no-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 172.21.2.0 obj - 172.21.2.0 no-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.1.134.0 obj - 10.1.134.0 destination static obj - 172.16.2.0 obj - 172.16.2.0 non-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.19.130.201 obj - 10.19.130.201 destination static obj - 172.30.2.0 obj - 172.30.2.0 no-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.19.130.201 obj - 10.19.130.201 destination static obj - 172.30.3.0 obj - 172.30.3.0 no-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.19.130.201 obj - 10.19.130.201 destination static obj - 172.30.7.0 obj - 172.30.7.0 no-proxy-arp-search to itinerary
  NAT (inside, all) static source Serversubnet Serversubnet XYZ_destinations XYZ_destinations non-proxy-arp-search of route static destination
  NAT (inside, all) source static obj - 10.10.1.0 obj - 10.10.1.0 destination static obj - 10.2.0.0 obj - 10.2.0.0 non-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.19.130.0 obj - 10.19.130.0 destination static obj-XXXXXXXX XXXXXXXX - obj non-proxy-arp-search to itinerary
  NAT (inside, all) source static obj - 10.19.130.0 obj - 10.19.130.0 destination static obj - 145.248.194.0 obj - 145.248.194.0 no-proxy-arp-search to itinerary
  NAT source (indoor, outdoor), obj static obj - 10.1.134.100 - 10.9.124.100
  NAT source (indoor, outdoor), obj static obj - 10.1.134.101 - 10.9.124.101
  NAT source (indoor, outdoor), obj static obj - 10.1.134.102 - 10.9.124.102
  NAT interface dynamic obj - 10.8.108.0 source (indoor, outdoor)
  NAT (inside, outside) source dynamic obj - 10.19.130.0 obj - 115.111.99.129
  NAT (inside, outside) source dynamic obj - 10.1.134.0 obj - 115.111.99.129 destination static obj - 195.254.159.133 obj - 195.254.159.133
  NAT (inside, outside) source dynamic obj - 10.1.134.0 obj - 115.111.99.129 destination static obj - 195.254.158.136 obj - 195.254.158.136
  NAT (inside, outside) source dynamic obj - 10.1.134.0 obj - 115.111.99.129
  NAT (inside, outside) source dynamic obj - 10.1.134.0 obj - 115.111.99.129 destination static obj - 209.164.192.0 obj - 209.164.192.0
  NAT (inside, outside) source dynamic obj - 10.1.134.0 obj - 115.111.99.129 destination static obj - 209.164.208.19 obj - 209.164.208.19
  NAT (inside, outside) source dynamic obj - 10.1.134.0 obj - 115.111.99.129 destination static obj - 209.164.192.126 obj - 209.164.192.126
  NAT (inside, outside) source dynamic obj - 10.8.100.128 obj - 115.111.99.130
  NAT (inside, outside) source dynamic obj - 10.10.0.0 obj - 115.111.99.132
  NAT source (indoor, outdoor), obj static obj - 10.10.1.45 - 115.111.99.133
  NAT (inside, outside) source dynamic obj - 10.99.132.0 obj - 115.111.99.129
  !
  network object obj - 172.17.10.3
  NAT (XYZ_DMZ, outside) static 115.111.99.134
  Access-group acl-outside in external interface
  Route outside 0.0.0.0 0.0.0.0 115.111.23.129 1
  Route outside 0.0.0.0 0.0.0.0 115.254.127.130 10
  Route inside 10.10.0.0 255.255.0.0 10.8.100.1 1
  Route inside 10.10.1.0 255.255.255.0 10.8.100.1 1
  Route inside 10.10.5.0 255.255.255.192 10.8.100.1 1
  Route inside 10.8.100.128 255.255.255.128 10.8.100.1 1
  Route inside 10.8.108.0 255.255.255.0 10.8.100.1 1
  Route inside 10.19.130.0 255.255.255.0 10.8.100.1 1
  Route inside 10.99.4.0 255.255.255.0 10.99.130.254 1
  Route inside 10.99.132.0 255.255.255.0 10.8.100.1 1
  Route inside 10.1.134.0 255.255.255.0 10.8.100.1 1
  Route outside 208.75.237.0 255.255.255.0 115.111.23.129 1
  Timeout xlate 03:00
  Pat-xlate timeout 0:00:30
  Timeout conn 01:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
  Sunrpc timeout 0:10:00 h323 0:05:00 h225 mgcp from 01:00 0:05:00 mgcp-pat 0:05:00
  Sip timeout 0:30:00 sip_media 0:02:00 prompt Protocol sip-0: 03:00 sip - disconnect 0:02:00
  Timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
  timeout tcp-proxy-reassembly 0:01:00
  Floating conn timeout 0:00:00
  dynamic-access-policy-registration DfltAccessPolicy
  identity of the user by default-domain LOCAL
  AAA authentication LOCAL telnet console
  LOCAL AAA authorization command
  No snmp server location
  No snmp Server contact
  Server enable SNMP traps snmp authentication linkup, linkdown cold start
  Crypto ipsec transform-set esp-aes-256 ikev1, esp-sha-hmac vpn2
  Crypto ipsec transform-set esp-aes-256 ikev1, esp-md5-hmac vpn6
  Crypto ipsec transform-set esp-aes-256 ikev1, esp-sha-hmac vpn5
  Crypto ipsec transform-set esp-aes-256 ikev1, esp-md5-hmac vpn7
  Crypto ipsec transform-set esp-aes-256 ikev1, esp-sha-hmac vpn4
  Crypto ipsec transform-set esp-aes-256 ikev1, esp-sha-hmac vpn1
  Crypto ipsec transform-set esp-aes-256 ikev1, esp-sha-hmac vpn_reliance
  Crypto ipsec transform-set esp-3des esp-md5-hmac ikev1 c2s_vpn
  86400 seconds, duration of life crypto ipsec security association
  Crypto-map dynamic dyn1 ikev1 transform-set c2s_vpn 1 set
  Crypto-map dynamic dyn1 1jeu reverse-road
  card crypto vpn 1 corresponds to the address XYZ
  card 1 set of peer XYZ Peer IP vpn crypto
  1 set transform-set vpn1 ikev1 vpn crypto card
  card crypto vpn 1 lifetime of security set association, 3600 seconds
  card crypto vpn 1 set security-association life kilobytes 4608000
  correspondence vpn crypto card address 2 DON'T
  2 peer NE_Peer IP vpn crypto card game
  2 set transform-set vpn2 ikev1 vpn crypto card
  3600 seconds, duration of life card crypto vpn 2 set security-association
  card crypto vpn 2 set security-association life kilobytes 4608000
  card crypto vpn 4 corresponds to the address ML_VPN
  card crypto vpn 4 set pfs
  vpn crypto card game 4 peers ML_Peer IP
  4 set transform-set vpn4 ikev1 vpn crypto card
  3600 seconds, duration of life card crypto vpn 4 set - the security association
  card crypto vpn 4 set security-association life kilobytes 4608000
  vpn crypto card 5 corresponds to the address XYZ_global
  vpn crypto card game 5 peers XYZ_globa_Peer IP
  5 set transform-set vpn5 ikev1 vpn crypto card
  3600 seconds, duration of life card crypto vpn 5 set - the security association
  card 5 security-association life set vpn crypto kilobytes 4608000
  vpn crypto card 6 corresponds to the address Da_VPN
  vpn crypto card game 6 peers Da_VPN_Peer IP
  6 set transform-set vpn6 ikev1 vpn crypto card
  3600 seconds, duration of life card crypto vpn 6 set - the security association
  card crypto vpn 6 set security-association life kilobytes 4608000
  vpn crypto card 7 corresponds to the address Da_Pd_VPN
  7 peer Da_Pd_VPN_Peer IP vpn crypto card game
  7 set transform-set vpn6 ikev1 vpn crypto card
  3600 seconds, duration of life card crypto vpn 7 set - the security association
  card crypto vpn 7 set security-association life kilobytes 4608000
  vpn outside crypto map interface
  crypto map vpn_reliance 1 corresponds to the address XYZ_rim
  card crypto vpn_reliance 1 set of peer XYZ_rim_Peer IP
  card crypto 1 ikev1 transform-set vpn_reliance set vpn_reliance
  vpn_reliance card crypto 1 lifetime of security set association, 3600 seconds
  card crypto vpn_reliance 1 set security-association life kilobytes 4608000
  card crypto vpn_reliance interface outside_rim
  dynamic mymap 1 dyn1 ipsec-isakmp crypto map
  crypto isakmp identity address
  No encryption isakmp nat-traversal
  Crypto ikev1 enable outside_rim
  Crypto ikev1 allow outside
  IKEv1 crypto policy 1
  preshared authentication
  aes-256 encryption
  sha hash
  Group 5
  lifetime 28800
  IKEv1 crypto policy 2
  preshared authentication
  aes-256 encryption
  sha hash
  Group 5
  life 86400
  IKEv1 crypto policy 4
  preshared authentication
  aes-256 encryption
  sha hash
  Group 5
  life 28000
  IKEv1 crypto policy 5
  preshared authentication
  aes-256 encryption
  sha hash
  Group 2
  life 86400
  IKEv1 crypto policy 100
  preshared authentication
  3des encryption
  sha hash
  Group 2
  life 43200
  IKEv1 crypto policy 65535
  preshared authentication
  3des encryption
  sha hash
  Group 2
  life 86400
  Telnet 10.8.100.0 255.255.255.224 inside
  Telnet timeout 5
  SSH timeout 5
  SSH group dh-Group1-sha1 key exchange
  Console timeout 0
  no basic threat threat detection
  no statistical access list - a threat detection
  no statistical threat detection tcp-interception
  internal XYZ_c2s_vpn group strategy
  username testadmin encrypted password oFJjANE3QKoA206w
  tunnel-group XXXXXXXX type ipsec-l2l
  tunnel-group ipsec-attributes XXXXXXXX
  IKEv1 pre-shared-key *.
  tunnel-group XXXXXXXXtype ipsec-l2l
  tunnel-group XXXXXXXXipsec-attributes
  IKEv1 pre-shared-key *.
  tunnel-group XXXXXXXX type ipsec-l2l
  tunnel-group ipsec-attributes XXXXXXXX
  IKEv1 pre-shared-key *.
  tunnel-group XXXXXXXX type ipsec-l2l
  tunnel-group ipsec-attributes XXXXXXXX
  IKEv1 pre-shared-key *.
  tunnel-group XXXXXXXX type ipsec-l2l
  tunnel-group ipsec-attributes XXXXXXXX
  IKEv1 pre-shared-key *.
  tunnel-group XXXXXXXX type ipsec-l2l
  tunnel-group ipsec-attributes XXXXXXXX
  IKEv1 pre-shared-key *.
  tunnel-group XXXXXXXX type ipsec-l2l
  tunnel-group ipsec-attributes XXXXXXXX
  IKEv1 pre-shared-key *.
  type tunnel-group XYZ_c2s_vpn remote access
  attributes global-tunnel-group XYZ_c2s_vpn
  address pool XYZ_c2s_vpn_pool
  IPSec-attributes tunnel-group XYZ_c2s_vpn
  IKEv1 pre-shared-key *.
  !
  class-map inspection_default
  match default-inspection-traffic
  !
  !
  type of policy-card inspect dns preset_dns_map
  parameters
  message-length maximum 512
  Policy-map global_policy
  class inspection_default
  inspect the preset_dns_map dns
  inspect the ftp
  inspect h323 h225
  inspect the h323 ras
  inspect the netbios
  inspect the rsh
  inspect the rtsp
  inspect the skinny
  inspect esmtp
  inspect sqlnet
  inspect sunrpc
  inspect the tftp
  inspect the sip
  inspect xdmcp
  inspect the icmp
  Review the ip options
  !
  global service-policy global_policy
  level 3 privilege see the running-config command exec mode
  logging of orders privilege see the level 3 exec mode
  privilege see the level 3 exec mode command crypto
  context of prompt hostname
  no remote anonymous reporting call
  call-home
  Profile of CiscoTAC-1
  no active account
  http https://tools.cisco.com/its/service/oddce/services/DDCEService destination address
  email address of destination [email protected] / * /
  destination-mode http transport
  Subscribe to alert-group diagnosis
  Subscribe to alert-group environment
  Subscribe to alert-group monthly periodic inventory
  monthly periodicals to subscribe to alert-group configuration
  daily periodic subscribe to alert-group telemetry
  Cryptochecksum:caa7476cd348ed89b95d37d4e3c9e1d8
  : end

  XYZ #.

  Good news

  Follow these steps:

  network object obj - 172.30.10.0_24

  172.30.10.0 subnet 255.255.255.0

  !

  the LOCAL_NETWORKS_VPN object-group network

  object-network 1.1.1.0 255.255.255.0

  !

  NAT (inside, outside) 1 static source LOCAL_NETWORKS_VPN destination LOCAL_NETWORKS_VPN static obj - 172.30.10.0_24 obj - 172.30.10.0_24 - route search

  * Where 1.1.1.0/24 is the internal network that you want to reach through the tunnel.

  Keep me posted.

  Thank you.

  Please note all messages that will be useful.

• ASA CA LOCAL SERVER backup and restore

  Hello

  I would like to Setup cisco asa for a CA server and provide the authentiaction of the user about digital certificates.

  I was wondering is it possible to make a complete backup and restore configuration including ca local server (root certificate) certificates user and cross to another ASA firewall if location hw?

  x 10

  Please see the backup attached and restore the procedure via CLI...

• VLANS with Cisco ASA 5505 and non-Cisco switch

  I have an ASA5505 and a switch Netgear GSM7224 L2 that I try to use together.  I can't grasp how VLANs (or at least how they should be put in place).  When configuring my VLAN on the ASA5505 it seems simple enough, but then on my switch, I thought I'd create just the same VLAN numbers that I used on the SAA and then add the ports that I wanted to use for each VLAN.

  Currently on my ASA, I have the following VLAN configured...

  outside - vlan11 - Port 0/0

  inside - vlan1 - Port 0/1

  dmz_ftp - vlan21 - Port 0/2

  Port of Corp - vlan31 - 0/3

  I need to do the same thing on my switch as well...  On my way, I'm a little confused as to how I need to configure the VLAN.  Below is the screenshot of web GUI...

  

  Note: Normally you can now change the VLAN ID (red), but in this case the default vlan (vlan id 1) may not be changed or deleted, you can does not change its settings.

  Tagged (green), Untagged (purple) and Autodetect (yellow) you must select at least 1.  I'm not sure how to in one place to tell my inner vlan (vlan1).

  I want VLAN1 ports 1-8 on my Netgear switch used alone to talk to interface/0/1 on the ASA5505 port.  I don't want to NOT port 9-24 able to talk to ports 1-8 on the Netgear switch ports OR 0/0, 0/2 - 0 / 7 on the Cisco ASA 5505.

  So, how can I configure my inner Vlan1 on ports 1-8 on the switch?  Do mark, UNTAG, autodetect them?  What about tours?  I've been a bit the impression that I would set up my VLAN on both devices, then trunk port 1 and dedicate this port on both devices to nothing other than the sheath and the security of vlan would then take the packages where they need to go.  Is this the wrong logic?

  Hi Arvo,

  If the port of the ASA is just part of a single VLAN (i.e. e0/0 single door 11 VLAN), this is called an access port. If the port of the ASA had to carry several VLANs, it would constitute a Trunk port.

  To access ports (VLAN unique), you must set the switch corresponding to be unidentified for port this VLAN individual. If you decide to configure a trunk port, then the port of the switch must be set for labelling for each of VLAN who win the trunk.

  For example, ASA I have:

  interface Ethernet0/1
  switchport access vlan 20
  !
  interface Vlan20
  nameif inside
  security-level 100
  ip address 192.168.100.254 255.255.255.0
  

  With the above configuration, the configuration of the switch would look like this (assuming the e0/1 port of the SAA is connected to 0/1 on the switch):

  VLAN 20 - 0/1 = untagged

  If instead you use a trunk port, the config would look like this:

  interface Ethernet0/0
  switchport trunk allowed vlan 10,20
  switchport mode trunk
  !
  interface Vlan10
  nameif outside
  security-level 0
  ip address dhcp setroute
  !
  interface Vlan20
  nameif inside
  security-level 100
  ip address 192.168.100.254 255.255.255.0
  

  Assuming that the ASA e0/0 port is connected to 0/1 on the switch):

  VLAN 10 - 0/1 = tagged
  VLAN 20 - 0/1 = tagged
  

  Hope that helps.

  -Mike

• Site to Site VPN between Cisco ASA 5505 and Sonicwall TZ170

  I'm trying to implement a VPN site-to site between our data center and office.  The data center has a Cisco ASA 5505 and the Office has a Sonicwall TZ170.  I managed to configure the two so that the vpn connects.  Each of the firewall I ping the IP Address of the internet firewall on the other side and a desktop computer I can ping the IP Address of the firewall internal datacenter but I can't carry traffic between private subnets datacenter and desktop.  Can anyone help?

  The config below has had IPs/passwords has changed.

  External Datacenter: 1.1.1.4

  External office: 1.1.1.1

  Internal data center: 10.5.0.1/24

  Internal office: 10.10.0.1/24

  : Saved
  :
  ASA Version 8.2 (1)
  !
  hostname datacenterfirewall
  mydomain.tld domain name
  activate the password encrypted
  passwd encrypted
  names of
  name 10.10.0.0 OfficeNetwork
  10.5.0.0 DatacenterNetwork name
  !
  interface Vlan1
  nameif inside
  security-level 100
  10.5.0.1 IP address 255.255.255.0
  !
  interface Vlan2
  nameif outside
  security-level 0
  1.1.1.4 IP address 255.255.255.0
  !
  interface Ethernet0/0
  switchport access vlan 2
  !
  interface Ethernet0/1
  !
  interface Ethernet0/2
  !
  interface Ethernet0/3
  !
  interface Ethernet0/4
  !
  interface Ethernet0/5
  !
  interface Ethernet0/6
  !
  interface Ethernet0/7
  !
  passive FTP mode
  clock timezone IS - 5
  clock to summer time EDT recurring
  DNS server-group DefaultDNS
  buydomains.com domain name
  permit same-security-traffic inter-interface
  permit same-security-traffic intra-interface
  inside_access_in list extended access permit icmp any one
  inside_access_in list extended access permitted tcp a whole
  inside_access_in list extended access udp allowed a whole
  inside_access_in of access allowed any ip an extended list
  outside_access_in list extended access permit icmp any one
  outside_access_in list extended access udp allowed any any eq isakmp
  IP DatacenterNetwork 255.255.255.0 OfficeNetwork 255.255.255.0 allow Access-list extended pixtosw
  pixtosw list extended access allow icmp DatacenterNetwork 255.255.255.0 OfficeNetwork 255.255.255.0
  IP OfficeNetwork 255.255.255.0 DatacenterNetwork 255.255.255.0 allow Access-list extended pixtosw
  pixtosw list extended access allow icmp OfficeNetwork 255.255.255.0 DatacenterNetwork 255.255.255.0
  outside_cryptomap_66.1 list of allowed ip extended access all OfficeNetwork 255.255.255.0
  outside_cryptomap_66.1 ip OfficeNetwork 255.255.255.0 allowed extended access list all
  outside_cryptomap_66.1 list extended access permit icmp any OfficeNetwork 255.255.255.0
  outside_cryptomap_66.1 list extended access allowed icmp OfficeNetwork 255.255.255.0 everything
  pager lines 24
  Enable logging
  asdm of logging of information
  Within 1500 MTU
  Outside 1500 MTU
  IP verify reverse path to the outside interface
  ICMP unreachable rate-limit 1 burst-size 1
  ASDM image disk0: / asdm - 623.bin
  don't allow no asdm history
  ARP timeout 14400
  NAT-control
  Global 1 interface (outside)
  NAT (inside) 1 0.0.0.0 0.0.0.0
  inside_access_in access to the interface inside group
  Access-group outside_access_in in interface outside
  Route inside 0.0.0.0 0.0.0.0 1.1.1.1 1
  Route OfficeNetwork 255.255.255.0 outside 1.1.1.1 1
  Timeout xlate 03:00
  Timeout conn 01:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
  Sunrpc timeout 0:10:00 h323 0:05:00 h225 mgcp from 01:00 0:05:00 mgcp-pat 0:05:00
  Sip timeout 0:30:00 sip_media 0:02:00 prompt Protocol sip-0: 03:00 sip - disconnect 0:02:00
  Timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
  timeout tcp-proxy-reassembly 0:01:00
  dynamic-access-policy-registration DfltAccessPolicy
  Enable http server
  http 10.5.0.0 255.255.255.0 inside
  No snmp server location
  No snmp Server contact
  Server enable SNMP traps snmp authentication linkup, linkdown cold start
  Crypto ipsec transform-set esp-SHA-ESP-3DES-3des esp-sha-hmac
  Crypto ipsec transform-set ESP-AES-256-SHA 256 - aes - esp esp-sha-hmac
  Crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac
  Crypto ipsec transform-set ESP-DES-SHA esp - esp-sha-hmac
  Crypto ipsec transform-set ESP-DES-MD5 esp - esp-md5-hmac
  Crypto ipsec transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac
  Crypto ipsec transform-set ESP-3DES-MD5-esp-3des esp-md5-hmac
  Crypto ipsec transform-set ESP-AES-128-SHA aes - esp esp-sha-hmac
  Crypto ipsec transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac
  Crypto ipsec transform-set ESP-AES-128-MD5-esp - aes esp-md5-hmac
  Crypto ipsec transform-set esp-aes-256 walthamoffice, esp-sha-hmac
  life crypto ipsec security association seconds 28800
  Crypto ipsec kilobytes of life - safety 4608000 association
  Crypto dynamic-map ciscopix 1 corresponds to the address outside_cryptomap_66.1
  Crypto dynamic-map ciscopix 1 transform-set walthamoffice
  Crypto dynamic-map ciscopix 1 the value reverse-road
  map dynmaptosw 66-isakmp ipsec crypto dynamic ciscopix
  dynmaptosw interface card crypto outside
  crypto isakmp identity address
  crypto ISAKMP allow outside
  crypto ISAKMP policy 10
  preshared authentication
  3des encryption
  sha hash
  Group 2
  life 86400
  crypto ISAKMP policy 13
  preshared authentication
  aes-256 encryption
  sha hash
  Group 2
  lifetime 28800
  crypto ISAKMP policy 30
  preshared authentication
  aes-256 encryption
  sha hash
  Group 2
  life 86400
  No encryption isakmp nat-traversal
  Telnet 10.5.0.0 255.255.255.0 inside
  Telnet timeout 5
  SSH 10.5.0.0 255.255.255.0 inside
  SSH timeout 5
  Console timeout 0
  management-access inside
  dhcpd address 10.5.0.2 - 10.5.0.254 inside
  dhcpd allow inside
  !

  a basic threat threat detection
  Statistics-list of access threat detection
  no statistical threat detection tcp-interception
  NTP server 66.250.45.2 source outdoors
  NTP server 72.18.205.157 source outdoors
  NTP server 208.53.158.34 source outdoors
  WebVPN
  attributes of Group Policy DfltGrpPolicy
  VPN-idle-timeout no
  username admin password encrypted
  tunnel-group 1.1.1.1 type ipsec-l2l
  tunnel-group 1.1.1.1 ipsec-attributes
  pre-shared-key *.
  !
  !
  !
  type of policy-card inspect dns preset_dns_map
  parameters
  message-length maximum 512
  !
  context of prompt hostname
  Cryptochecksum:7f319172e5de9c0e550804a263f8e49e
  : end

  Mattew, obvious lack of education is the rule exempt from nat for your tunnel, your access list pixtosw is similar on this example, I assume that you have gone through this link, if it does not see the configs on both sides.

  Add the statement of rule sheep in asa and try again.

  NAT (inside) 0-list of access pixtosw

  http://www.Cisco.com/en/us/products/HW/vpndevc/ps2030/products_configuration_example09186a008052c9d4.shtml

  Concerning

• Configuration of the Cisco ACS 5.3 AnyConnect VPN and management of a Cisco ASA 5500.

  We have configured a Cisco ASA 5505 as a VPN endpoint for one of our user groups.  It works, but it works too well.

  We have a group called XXX we need to have access to the Cisco AnyConnect Client.  We have selected this group of our Active Directory and added to our ACS configuration.  We've also added a group called YYY that will manage the ASA. However, this group has no need to access the VPN.

  We added XXX movies for the elements of the policy of access to the network-> authorization profiles.  We also have a profile of YYY.

  She continues to knock on our default Service rule that says allow all.

  We have also created a default network access rule. for this.

  I am at a loss.  I'm sure I missed a checkbox or something.

  Any help would be really appreciated.

  Dwane

  We use Protocol Management GANYMEDE ASA and Ray for VPN access?

  For administration, you must change the device by default admin access strategy and create a permission policy. Even by the way, you can change the network access by default for vpn access and create a respective policy for that too.

  On the SAA, you must configure Ganymede and Ray both as a server group.

  For the administration, you can set Ganymede as an external authentication under orders aaa Server

  AAA-server protocol Ganymede GANYMEDE +.

  Console HTTP authentication AAA GANYMEDE

  Console Telnet AAA authentication RADIUS LOCAL

  authentication AAA ssh console LOCAL GANYMEDE

  Console to enable AAA authentication RADIUS LOCAL

  For VPN, you must set the authentication radius under the tunnel-group.

  I hope this helps.

  Kind regards

  Jousset

  The rate of useful messages-

• IKE Dead Peer Detection between Cisco ASA and Cisco PIX

  I have a network environment in Star with about 30 offices of satellite remote using VPN Site to Site connectivity.  The majority of remote satellite offices have the features of Cisco PIX 501 running PIX Version 6.3.  The hub office runs a version 8.2 (1) Cisco ASA.

  I configured Dead Peer Detection on the Cisco ASA device at the office hub with the default settings of the following-

  Confidence interval - 10 seconds

  Retry interval - 2 seconds

  I think I'm right assuming that raises are limited to 3 before the tunnel is completely demolished.  Basically, the problem that I am facing is with several remote satellite offices.  What seems to be the case, the tunnel between the remote offices and the hub is demolished (probably because of the length of IKE, always 86400 seconds) and the tunnel then fails to renegotiate unless traffic is physically forced from the hub office.  The tunnel NOT to renegotiate after satellite office, ONLY the end of the hub; so that means sending traffic to the satellite when the VPN tunnel is out of service, not to renegotiate the tunnel.  The Hub office is a colo and therefore traffic rarely comes to that end, the tunnel remains so down until manual intervention occurs and the ICMP traffic is forced into the tunnel.

  Should the KeepAlive and retry interval settings corresponds to both ends, for example if the two devices be configured for DPD?

  What are the potential pitfalls to the extension of the life of IKE, and this will help or even hinder the problem?

  Thank you in advance for helping out with this.

  Hi Nicolas,.

  I think that the two DPD settings must match on both ends, if these do not match then problems like yours might arise which seems to happen here, is that one end shows a tunnel down, but the other end may not detect it down, we could have to watch debugs, or record two ends to see if this is the case , setting in the meantime ike DPD for same timers could hetlp on.

  In regard to the increase in the life expectancy of IKE, well you just need to be aware that this could allow keys to be discovered since these are not renegotiated unless the tunnel is down on the level of IKE. Other than that I don't see why this would affect you.

• Exempt NAT and in cisco ASA intervlan routing scenario

  Hi, I'm new to Cisco ASA. I did some study on Cisco ASA recently and you try to understand how it works.

  The chart above illustrates the architecture of network in my company (attachment). The two FW (5520, version 8.0) are configured with nat control and same-security-traffic permit inter-interface. I have a ping of device A to unit B (10.10.105.244 > 10.10.70.70/24).

  At FW 02, I added an inbound ACL (10.10.105.0/24 > 10.10.70.0/24) because of the difference in level of security between the input and output interface (SL 50 < sl="" 100).="" for="" the="" return="" traffic="" (10.10.70.0/24=""> 10.10.105.0/24), I only need to add a device nat exempted from the rules as I have it configured with permit same-security-traffic inter-interface. My understanding is correct?

  FW 01, I need to add an entry ACL (10.10.70.0/24 > 10.10.105.244). Without the rule, my ping will be unsuccessful. Can I know why I need to add this rule to incoming traffic, because same-security-traffic permits inter-interface is set to FW 01? Can I know why I have no need to nat exempt traffic (10.10.105.0/24 > 10.10.70.0/24)?

  Sorry for the long explanation. I hope to get clarification and to ensure that my interpretation is correct.

  Thanks for all the comments. Have a nice day :)

  Hello

  For your first question: ""I know why I need to add this rule to incoming traffic, because the same-security-traffic inter-interface permit is set to FW 01?".

  It probably has to do with the ICMP inspection. By default, ICMP traffic is not inspected by the ASA for the return of the device traffic B to the device will be dropped on FW 01. You must activate the ICMP inspection by adding it to the MPF on the SAA default configuration.

  For your second question: "I know why I don't not need to nat exempt traffic (10.10.105.0/24 > 10.10.70.0/24)"?".

  NAT-control does not affect the same security interfaces, i.e. the same security interfaces can communicate without NAT even if NAT-control is turned on (with some exceptions). See this link for more information.

• CSCux29978 - Cisco ASA IKEv1 and IKEv2 buffer overrun vulnerability - 1

  Hello

  im confused. In the Advisory secruity on this bug https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/ci...

  He said not "affected" in the line of the main version of ASA 9.1. 9.1 is so affected by this bug and we need to upgrade to 9.1. (7) or not?

  regarding

  Christian

  Hi Christian,

  According to the chart, the only version not affected is code 8.5 9.1 code, you must update to 9.1.7 to be safe from this vulnerability.

  Cisco ASA Major Release	First version fixed
  7.21	Affected; migrate to 9.1 (7) or later version
  8.21	Affected; migrate to 9.1 (7) or later version
  8.31	Affected; migrate to 9.1 (7) or later version
  8.4	8.4 (7.30)
  8.51	Not affected
  8.61	Affected; migrate to 9.1 (7) or later version
  8.7	8.7 (1.18)
  9.0	9.0 (4.38)
  9.1	9.1 (7)
  9.2	9.2 (4.5)
  9.3	9.3 (3.7)
  9.4	9.4 (2.4)
  9.5	9.5 (2.2)

  It may be useful

  -Randy-

• Need help - Cisco ASA with the power of fire

  Hello

  Currently, we use asa 5510 without function of firepower. Our goal is to publish web servers and microsoft lync with reverse proxy method. control internet traffic, apply extensions individual file not to download, management of bandwidth etc.

  Is it possible if we add firepower on asa 5510... Please guide me... Thank you

  Power of fire must be installed on the new series X of the SAA.  5512 x, x 5515, 5525 x, etc.

  If you have a 5510, you probably want a 5512 x with an SSD.  Cisco has beams of firepower include the ASAx with SSD and the license of firepower.

  Adds that you must also Firesight management software, and there is a license bundle of 2 camera for under $ 500 that you can install on VMWare.

  Firepower is not reverse proxy, it's transparent online packages, analysis and filtering by URL / Application / and threat mitigation.

  If you want a reverse proxy, you should look into Microsoft ISA server or a Proxy Server reverse dedicated Web.  Cisco gave its product Web Director, who has done this function.

  You can host Web sites behind a firewall of ASA without proxy reverse.  And the ASA has an inspection of the request for HTTP traffic, responsible for watching HTTP requests.  The firepower to the ASA system also has specific signatures that monitor traffic to the web servers and prevent specific vulnerabilities that are known on those servers, so if that is what you want the Reverse Proxy for, then the power of fire module would probably cover your needs.

  Don't forget that until the next quarter firepower system has no decryption on the box, and you might want to wait that the feature is released and put in place, so that you know what size firewall you need protect your network with the SSL decryption.  I believe that the ASA5512x is testing at 75 Mbps stream decrypted via the fire power module, which is about half of what was before CX, then you could use the sizing numbers CX and extrapolate until Cisco releases official decryption numbers.

• Configure to integrate Cisco ASA and JOINT

  Hello

  We have Cisco ASA and JOINT, need assistance on the integration of the same thing; Please email me so that I'll share the details of the architecture.

  Thank you best regards &,.

  REDA

  Hi reda,.

  If I correctly your diagram, you do not want to send any traffic from the external switch to the JOINT with a SPAN port and all traffic from your DMZ interfaces with another.

  Is this correct?

  If so, can you tell me why you want to inspect the traffic before it goes through the firewall? As I said in my original answer, we generally advise putting IP addresses after the firewall.

  Not to mention that in your case, I guess that some traffic will be inspected twice so you will need to assign a different virtual sensors to each JOINT internal interfaces to ensure that the same instance does not see the traffic of several times.

  Kind regards

  Nicolas

• "" Cisco ASA multiple defects remote control let users deny Service and bypass the security controls ".

  Recently we have heard people talk of "Cisco ASA several flaws let users deny remote Service and bypass the security controls" under the securitytracker. However, as everyone knew, ASA 8.3 need a lot more resources on ASA HW to run. I checked that the bugs associated to above problem "CSCtg69742, CSCth36592, CSCtg61810, CSCte53635, CSCte46460, CSCte20030, CSCtf29867, CSCte14901, CSCsz80777, CSCsz36816" in the Cisco Bug Toolkit. None of them show any information if there is a fix for ASA 8.2 (x).

  This means that Cisco starts to stop supporting 8.2 (x) and to push customers to their "so-called" best image 8.3 version (x) as a strategy of "marketing?

  Cisco is best to find a solution for this problem on 8.2 (x) rather than push customers to something Cisco "love." It may not be the best interest of the customers AT ALL. Instead of pushing customers to ASA 8.3 (x), Cisco likely to push customers to its big competitor Juniper:)

  Sean,

  I did a quick search on the Bug Toolkit for CSCtg69742 and found the following result.

  Fixed in
  8.2 (3)
  8.3 (1.5)
  8.3 (2)
  8.2 (2.15)
  8.2 (2.107)
  100,7 (0.17) M
  100.5 (5.16) M
  8.3 (1,100)
  100.7 (6.1) M
  8.4 (0.99)

  This was posted in the column on the left side of the search results page.

  I recommend you research each ID of Bug Bug Toolkit (http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs) for the version name (number) that contains the fix for this bug.

  HTH

  Amol