PIX / ASA 7.0

Similar Questions

• User of the restrictions-pix/asa

  PIX / asa, I created the user with the privilege level, how I can restrcit the depending on the level of privilege.

  privilege level example 10 they can't enter config mode.

  advise the pl

  Thank you

  Knockaert

  Hello

  You must enable local command authorization to do so. See this link to enable local and configuration authorization steps.

  http://www.Cisco.com/en/us/docs/security/ASA/asa72/configuration/guide/mgaccess.html#wp1042039

• SSH PIX / ASA

  Hi guys,.

  How do enable you ssh on pix and asa. I enter the following command, but it did not work. Someone told me before that you have to couple of order entry to activate ssh. Could someone help me please.

  SSH 10.150.X.X 255.255.255.255 inside

  TKS

  Hello Kuldeep,

  First of all, of all the needs of the ASA/PIX to have a domain already defined:

  Something like:

  domain name "yourdomain.com".

  You need to file for SSH RSA keys to work:

  the encryption key generate rsa keys general module 1024

  (The bit length could be 512, 768,1024 or 2 048)

  The ASA said that there is already an existing key so if you want to remove it... say Yes.

  Then do a wr mem and try to SSH to the device.

  Of course, the commands you have entered first are needed after that too.

  It could be that useful...

  DL.

• PIX - ASA, allow RA VPN clients to access servers at remote sites

  I got L2L tunnels set up for a couple of remote sites (PIX) for several months now. We have a VPN concentrator, which will go EOL soon, so I'm working on moving our existing customers of RA our ASA. I have a problem, allowing RA clients access to a server to one of our remote sites. PIX and ASA (main site) relevant config is shown below. The error I get on the remote PIX when you try a ping on the VPN client is:

  Group = 204.14. *. *, IP = 204.14. *. * cheque card static Crypto Card = outside_map, seq = 40, ACL does not proxy IDs src:172.16.200.0 dst: 172.16.26.0

  The config:

  Hand ASA config

  access extensive list ip 172.16.0.0 inside_nat0_outbound allow 255.255.255.0 172.16.26.0 255.255.255.0

  access extensive list ip 172.16.1.0 inside_nat0_outbound allow 255.255.255.0 172.16.26.0 255.255.255.0

  access extensive list ip 172.16.22.0 inside_nat0_outbound allow 255.255.255.0 172.16.26.0 255.255.255.0

  access extensive list ip 172.16.200.0 inside_nat0_outbound allow 255.255.255.0 172.16.26.0 255.255.255.0

  access extensive list ip 172.16.0.0 inside_nat0_outbound allow 255.255.255.0 172.16.200.0 255.255.255.0

  access extensive list ip 172.16.0.0 outside_cryptomap_60 allow 255.255.255.0 172.16.26.0 255.255.255.0

  access extensive list ip 172.16.1.0 outside_cryptomap_60 allow 255.255.255.0 172.16.26.0 255.255.255.0

  access extensive list ip 172.16.22.0 outside_cryptomap_60 allow 255.255.255.0 172.16.26.0 255.255.255.0

  access extensive list ip 172.16.200.0 outside_cryptomap_60 allow 255.255.255.0 172.16.26.0 255.255.255.0

  card crypto outside_map 60 match address outside_cryptomap_60

  outside_map 60 set crypto map peer 24.97. *. *

  card crypto outside_map 60 the transform-set ESP-3DES-MD5 value

  map outside_map 65535-isakmp ipsec crypto dynamic outside_dyn_map

  outside_map interface card crypto outside

  =========================================

  Remote config PIX

  access extensive list ip 172.16.26.0 inside_nat0_outbound allow 255.255.255.0 172.16.0.0 255.255.255.0

  access extensive list ip 172.16.26.0 inside_nat0_outbound allow 255.255.255.0 172.16.1.0 255.255.255.0

  access extensive list ip 172.16.26.0 inside_nat0_outbound allow 255.255.255.0 172.16.22.0 255.255.255.0

  access extensive list ip 172.16.26.0 inside_nat0_outbound allow 255.255.255.0 172.16.200.0 255.255.255.0

  access extensive list ip 172.16.26.0 outside_cryptomap_60 allow 255.255.255.0 172.16.0.0 255.255.255.0

  access extensive list ip 172.16.26.0 outside_cryptomap_60 allow 255.255.255.0 172.16.1.0 255.255.255.0

  access extensive list ip 172.16.26.0 outside_cryptomap_60 allow 255.255.255.0 172.16.22.0 255.255.255.0

  access extensive list ip 172.16.26.0 outside_cryptomap_60 allow 255.255.255.0 172.16.200.0 255.255.255.0

  card crypto outside_map 60 match address outside_cryptomap_60

  peer set card crypto outside_map 60 204.14. *. *

  card crypto outside_map 60 the transform-set ESP-3DES-MD5 value

  outside_map interface card crypto outside

  EDIT: Guess, I might add, remote site is 172.16.26.0/24 VLAN VPN is 172.16.200.0/24...

  What you want to do is 'tunnelall', which is not split tunneling. This will still allow customers to join the main and remote site, but not allow them to access internet... unless you have expressly authorized to make a 'nat (outside)"or something. Your journey on the client will be, Secured route 0.0.0.0 0.0.0.0

  attributes of group policy

  Split-tunnel-policy tunnelall

  Who is your current config, I don't see where the acl of walton is attributed to what to split tunnel?

• PIX, ASA, and RSA SecureID

  Hi all

  I replaced our old Pix 515 for a new ASA 5520.

  On the Pix (running ios 6.x) we have configured the pix to use an RSA SecurID appliance AAA server to authenticate remote VPN clients. To do this, we set up a group AAA using the radius Protocol. Now, for the SAA, I found documentation indicating that I need to create a group AAA that uses the SDI Protocol.

  Now my questions are

  (1) can I still use the RADIUS Protocol on the SAA is to authenticate with RSA SecureID, or what I have to use SDI?

  (2) if I have to use SDI does mean I also have to change the configuration on my RSA I used to authenticate users of the PIX?

  Kind regards

  Screech

  Hi little Duke

  (1) you can still use the RADIUS.

  (2) Yes, you would need to allow auth requests come from ASA

  Roman

• PIX / ASA, including the DNS name of the ACLS

  Hello

  PIX or ASA supported DNS names in ACL or only IPs? Everyone heard talk of plans to support?

  As far as I know (D) DNS is only supported for VPN connections by saving the IPs of the box interface.

  Best regards

  Roberto

  only ip addresses.

• allowing permission aaa on pix / asa

  I managed to get authentication on easy enough but now finds it difficult to get permission to work properly. I auth/author enabled for my IOS stuff so any connected Tech will have rights based on what I give them about secure ACS. However, I can't the same thing to work on the code of PIX. I can connect fine with sign aa, but still, he invites me to the enable password. End result is that I want to be able to connect only once (and active). The white papers that can tell me the right way?

  Hello

  What you want to do, it is possible, try following the instructions in the attached PDF file.

  And you want to give access ASDM, then make sure that you leave Assistance user privilege to execute all display orders, i.e. show-(check) permit unmatched arguments.

  Let me know.

  Kind regards

  Prem

• PIX / ASA - OSPF load balancing

  Hello

  I read the balance a route via OSPF equal cost load the PIX. It will send packages via per package, or is there another method for distibuting the traffic to the break following equal cost?

  Thank you!!

  Lee

  Hello Lawrence,.

  PIX 6.3 now supports the NLB using OSPF only (up to 3 default routes)

  The PIX can receive up to 3 doors by default (all the same metric) 3 different routes of entry, and

  balance the load on a per destination basis. Currently, there is no way the PIX to

  determine which carries a package will be sent to. You cannot currently use static routes

  for load balancing.

  The used hash algorithm is not simple, it is very difficult to determine which

  Route (next hop) a package will be given an IP Source and Destination pair. Basically,.

  the PIX takes the source and destination IPs (two 32-bit numbers) and axe in one

  16-bit unique number. Then the number of 16-bit (0x0000 - 0xFFFF) is divided into thirds.

  The first 1/3 goes to the door of entry 1, the next 1/3 goes to the door of entry 2, and the last 1/3 goes to

  Gateway 3.

  I hope this helps! If Yes, please rate.

  Thank you

• Active/active failover configuration LAN-based PIX / ASA

  Hi all

  I would like to ask, if there is a restriction of length between the two ASA5510 in a LAN failover? Should not be, or I'm wrong?

  Thank you

  Norbert

  Hello

  normal duration of 100 m Ethernet. Or you can use the switches between them. I do not have a direct link.

  Best regards, Celio

• Source of interesting VPN traffic to PIX / ASA

  Is it possible the CLI to interesting to implement traffic source or otherwise test a VPN strategy?

  As far as I KNOW - this is not possible, because you cannot create a tcp/udp/icmp from a source interface in the device.

• Form of CONF. IPSec PIX to ASA

  Hi.I have a small question. I have a PIX configured with Ipsec configuration, but we have now upgraded to an ASA.

  I can just copy paste the configuration of PIX, ASA (all crypto and isakmp orders) or what I have to change some commands to make it work?

  ASA uses the same addresses that PIX used in its configuration.

  ""isakmp key"" command is replaced by the tunnel-group.

  use: -.

  tunnel-group xx.xx.xx.xx type ipsec-l2l

  tunnel-group ipsec-attributes xx.xx.xx.xx

  pre-shared key "isakmp key."

  where xx.xx.xx.xx is the address of the peer.

  Political ISAKMP are replced with

  ISAKMP crypto policy 'number

  authentication

  encryption

  hash

  Group

  life

  I hope this helps.

• The import of the PIX 501 config to ASA 5505

  Is there something special that must occur to import a PIX 501 (IOS Version 6.3) config to an ASA 5505 appliance or is it as simple as download the config?

  Greg

  No, this isn't unfortunately because your pix is running 6.4 and the ASA 5505 will run a minimum of code 7.x and there were quite a few changes. Note that many existing commands would work, but some will not. Attached is a link to a doc for improving pix ASA who speaks both a manual method and an assisted version of tool -.

  http://www.Cisco.com/en/us/docs/security/ASA/migration/guide/pix2asa.html

  Jon

• Version 7.0 of the PIX and ASA 5500

  Hi all

  Is ASA 5500 series identical a PIX 515 or 525 or 535 with version 7.0... I still see some areas where it confused between version 7.0 of the PIX and ASA 5500 series... If not, what are the benefits of ASA 5500 on the PIX 7.0?

  ASA is not the same as PIX, ASA is different hardware architecture. Although both can run the same code. One of the benefits of the SAA is that you can have an IPS module in it to make the prevention of intrusions.

  Search for comprarison on CCO.

• ASA ACL split Tunnel

  Cisco ASA.

  For example, I have the subnet in the tunnel of splitting ACL 192.168.0.0/16. I need made an exception to remove 192.168.89.0/24 in the ACL CE-tunnel - what is the best way to do it?

  Hi rioneljeudy ,

  You can restrict the subnets in the ACL used for the tunnel of split for example change the 16 something more specific or apply a filter, VPN policy. See an example on the following link:

  http://www.Cisco.com/c/en/us/support/docs/security/PIX-500-series-security-appliances/99103-PIX-ASA-VPN-filter.html

  It may be useful

  -Randy-

• Site to Site between ASA VPN connection and router 2800

  I'm trying to get a L2L VPN working between a ASA code 8.4 and a 2800 on 12.4.

  I first saw the following errors in the debug logs on the side of the ASA:

  Error message % PIX | ASA-6-713219: KEY-GAIN message queues to deal with when
  ITS P1 is complete.

  I see the following on the end of 2800:

  ISAKMP: (0): treatment charge useful vendor id
  ISAKMP: (0): provider ID seems the unit/DPD but major incompatibility of 157
  ISAKMP: (0): provider ID is NAT - T v3
  ISAKMP: (0): treatment charge useful vendor id
  ISAKMP: (0): provider ID seems the unit/DPD but major incompatibility of 69
  ISAKMP (0): provider ID is NAT - T RFC 3947
  ISAKMP: (0): treatment charge useful vendor id
  ISAKMP: (0): treatment of frag vendor id IKE payload
  ISAKMP: (0): IKE Fragmentation support not enabled
  ISAKMP: (0): entry = IKE_MESG_INTERNAL, IKE_PROCESS_MAIN_MODE
  ISAKMP: (0): former State = new State IKE_R_MM1 = IKE_R_MM1

  ISAKMP: (0): built NAT - T of the seller-rfc3947 ID
  ISAKMP: (0): send package to x.x.x.x my_port 500 peer_po0 (R) MM_SA_SETUP
  ISAKMP: (0): sending a packet IPv4 IKE.
  ISAKMP: (0): entry = IKE_MESG_INTERNAL, IKE_PROCESS_COMPLETE
  ISAKMP: (0): former State = new State IKE_R_MM1 = IKE_R_MM2

  ISAKMP (0): packet received from x.x.x.x dport 500 sports global (R)

  MM_SA_SETUP
  ISAKMP: (0): entry = IKE_MESG_FROM_PEER, IKE_MM_EXCH
  ISAKMP: (0): former State = new State IKE_R_MM2 = IKE_R_MM3

  ISAKMP: (0): processing KE payload. Message ID = 0
  ISAKMP: (0): processing NONCE payload. Message ID = 0
  ISAKMP: (0): found peer pre-shared key x.x.x.x corresponding
  ISAKMP: (2345): treatment charge useful vendor id
  ISAKMP: (2345): provider ID is the unit
  ISAKMP: (2345): treatment charge useful vendor id
  ISAKMP: (2345): provider ID seems the unit/DPD but major incompatibility of 54
  ISAKMP: (2345): provider ID is XAUTH
  ISAKMP: (2345): treatment charge useful vendor id
  ISAKMP: (2345): addressing another box of IOS!
  ISAKMP: (2345): treatment charge useful vendor id
  ISAKMP: (2345): vendor ID seems the unit/DPD but hash mismatch
  ISAKMP: receives the payload type 20
  ISAKMP (2345): sound not hash no match - this node outside NAT
  ISAKMP: receives the payload type 20
  ISAKMP (2345): no NAT found for oneself or peer
  ISAKMP: (2345): entry = IKE_MESG_INTERNAL, IKE_PROCESS_MAIN_MODE
  ISAKMP: (2345): former State = new State IKE_R_MM3 = IKE_R_MM3

  ISAKMP: (2345): sending package x.x.x.x my_port Exchange 500 500 (R)

  MM_KEY_EXCH

  ----------

  This is part of the configuration of the ASA:

  network of the ABCD object
  10.20.30.0 subnet 255.255.255.0
   
  network of the ABCD-Net object
  172.16.10.0 subnet 255.255.255.0
   
  cry-map-77-ip object-group XXXX object abc-site_Network allowed extended access list
   
  access list abc-site extended permitted ip object-group XXXX object abc-site_Network
   
  ip access list of abc-site allowed extended object abc-site_Network object-group XXXX-60
   
  NAT (any, any) static source 20 XXXX XXXX-20 destination static abc-site_Network abc-site_Network
   
  NAT (any, any) static source 20 XXXX XXXX-20 destination static abc-site_Network abc-site_Network
   
  XXXX-20
   
  object-group network XXXX-20
  ABCD-Net network object
  object-abcd-Int-Net Group
   
  XXXX_127
   
  object-group network XXXX-20
  ABCD-Net network object
  object-abcd-Int-Net Group
   
  ip access list of abc-site allowed extended object abc-site_Network object-group XXXX-60
   
   
  Crypto card off-map-44 11 match address cry-map-77
  card crypto out-map-44 11 counterpart set 62.73.52.xxx
  card crypto out-map-44 11 set ikev1 transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA MD5-ESP-3DES ESP-DES-SHA ESP-DES-MD5

  cry-map-77-ip object-group XXXX object abc-site_Network allowed extended access list

  Crypto card off-map-44 11 match address cry-map-77
  card crypto out-map-44 11 counterpart set 62.73.52.xxx
  card crypto out-map-44 11 set ikev1 transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA MD5-ESP-3DES ESP-DES-SHA ESP-DES-MD5

  card crypto out-map-44 11 set transform-set ESP-3DES-SHA ikev1

  object-group network XXXX
  ABCD-Net network object
  object-abcd-Int-Net Group

  ------------------------

  Here is a part of the 2800:

  !
  crypto ISAKMP policy 1
  BA 3des
  preshared authentication
  Group 2
  ISAKMP crypto key r2374923 address 72.15.21.xxx
  !
  !
  Crypto ipsec transform-set esp-SHA-ESP-3DES-3des esp-sha-hmac
  !
  card crypto cry-map-1 1 ipsec-isakmp
  the value of 72.15.21.xxx peer
  game of transformation-ESP-3DES-SHA
  match address VPN
  !
  type of class-card inspect match class-map-vpn
  game group-access 100
  type of class-card inspect cm-inspect-1 correspondence
  group-access name inside-out game
  type of class-card inspect correspondence cm-inspect-2
  match the name of group-access outside
  !
  !
  type of policy-card inspect policy-map-inspect
  class type inspect cm-inspect-1
  inspect
  class class by default
  drop
   
  type of policy-card inspect policy-map-inspect-2
  class type inspect class-map-vpn
  inspect
  class type inspect cm-inspect-2
  class class by default
  drop
  !

  !
  interface FastEthernet0
  IP address 74.25.89.xxx 255.255.255.252
  NAT outside IP
  IP virtual-reassembly
  security of the outside Member area
  automatic duplex
  automatic speed
  crypto cry-card-1 card
  !
  interface FastEthernet1
  no ip address
  Shutdown
  automatic duplex
  automatic speed
  !
  IP nat inside source overload map route route-map-1 interface FastEthernet0
  !
  IP access-list extended inside-out
  IP 172.16.10.0 allow 0.0.0.255 any
  IP nat - acl extended access list
  deny ip 192.168.0.0 0.0.255.255 172.16.10.0 0.0.0.255
  deny ip 10.200.0.0 0.0.255.255 172.16.10.0 0.0.0.255
  deny ip 192.168.0.0 0.0.255.255 172.16.10.0 0.0.0.255
  deny ip 0.0.255.255 28.20.14.xxx.0.0 172.16.10.0 0.0.0.255
  refuse the 10.10.10.0 ip 0.0.0.255 172.16.10.0 0.0.0.255
  refuse the 172.16.10.0 ip 0.0.0.255 192.168.0.0 0.0.255.255
  refuse the 172.16.10.0 ip 0.0.0.255 10.200.0.0 0.0.255.255
  refuse the 172.16.10.0 ip 0.0.0.255 192.168.0.0 0.0.255.255
  refuse the 172.16.10.0 ip 0.0.0.255 28.20.14.xxx.0.0 0.0.255.255
  refuse the 172.16.10.0 ip 0.0.0.255 10.10.10.0 0.0.0.255
  allow an ip
  outside extended IP access list
  allow an ip
  list of IP - VPN access scope
  IP 172.16.10.0 allow 0.0.0.255 192.168.0.0 0.0.255.255
  IP 172.16.10.0 allow 0.0.0.255 10.200.0.0 0.0.255.255
  IP 172.16.10.0 allow 0.0.0.255 192.168.0.0 0.0.255.255
  IP 172.16.10.0 allow 0.0.0.255 28.20.14.xxx.0.0 0.0.255.255
  IP 172.16.10.0 allow 0.0.0.255 10.10.10.0 0.0.0.255
  IP 192.168.0.0 allow 0.0.255.255 172.16.10.0 0.0.0.255
  IP 10.200.0.0 allow 0.0.255.255 172.16.10.0 0.0.0.255
  IP 192.168.0.0 allow 0.0.255.255 172.16.10.0 0.0.0.255
  28.20.14.xxx.0.0 0.0.255.255 ip permit 172.16.10.0 0.0.0.255
  ip licensing 10.10.10.0 0.0.0.255 172.16.10.0 0.0.0.255

  access-list 23 allow 192.168.0.0 0.0.255.255
  access-list 23 allow 10.200.0.0 0.0.255.255
  access-list 23 allow 172.16.10.0 0.0.0.255
  access-list 123 note category class-map-LCA-4 = 0
  access-list 123 allow ip 192.168.0.0 0.0.255.255 172.16.10.0 0.0.0.255
  access-list 123 allow ip 10.200.0.0 0.0.255.255 172.16.10.0 0.0.0.255
  access-list 123 allow ip 192.168.0.0 0.0.255.255 172.16.10.0 0.0.0.255
  access-list 123 allow ip 0.0.255.255 28.20.14.xxx.0.0 172.16.10.0 0.0.0.255
  access-list 123 allow ip 10.10.10.0 0.0.0.255 172.16.10.0 0.0.0.255
  access-list 123 allow ip 172.16.10.0 0.0.0.255 192.168.0.0 0.0.255.255
  access-list 123 allow ip 172.16.10.0 0.0.0.255 10.200.0.0 0.0.255.255
  access-list 123 allow ip 172.16.10.0 0.0.0.255 192.168.0.0 0.0.255.255
  access-list 123 allow ip 172.16.10.0 0.0.0.255 28.20.14.xxx.0.0 0.0.255.255
  access-list 123 allow ip 172.16.10.0 0.0.0.255 10.10.10.0 0.0.0.255
  !
  !
  !

  !
  route-map-1 allowed route map 1
  match the IP nat - acl
  !

  Hello

  I quickly browsed your config and I could notice is

  your game of transformation (iskamp) on SAA and router are not the same, try to configure the same on both sides.

  in the statement of the ASA NAT you gave (any, any) try to give the name of the interface instead of a whole.