Upon taking the config from a VPN 515E with 6.3(5) to an ASA 5510 with 7.2(3), I am presented with a very perplexing problem. I have 18 peers tied to the same crypto map for redundancy. On the Pix, it isn't a problem; however on the ASA upon loading the 11 peer, I receive an error stating that 10 is the max number of peers that I can have tied to a crypto map. Just to clarify, I have issues typing:
crypto map mymap 200 set peer 18.104.22.168
more than 10 times. I don't have any problems with peers 1-10, just any peer after the 10th. Am I doing something incorrect? Is there a work around? I have looked through A LOT of Cisco documentation both on and off the web, and have not come up with anything remotely regarding this limitation.
What kinda work around do you think that I can come up with? We need the ASA because of the hub-spoke that we are trying to implement for our clinet.
I thought about using the same crypto with a different seq number, and changing the ACL#. However, the problem that I think I would have is if I use the same information in each ACL for example:
access-list 101 permit ip 192.168.100.0/24 192.168.200.0/24
access-list 102 permit ip 192.168.100.0/24 192.168.200.0/24
and split the peers between the two maps, won't the ASA get confused? There has to be some type of work around for this.
Any help would be SERIOUSLY appreciated. The client that I have to implement this for is getting pretty irriated, and I'm almost at my wits end! I don't have that much hair left, can you make sure I don't pull it all out! :)
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...