It will route between them, but you'll also need to add the approrpaite local/remote networks into the individual L2L tunnel configuration section for each tunnel. Without this the concentrator won't know that you want traffic destined for these subnets to go over the specific L2L tunnel.
For example, let's say the network behind the VPN concentrator is 184.108.40.206, the network behind the PIX is 220.127.116.11 and the network behind the CP is 18.104.22.168.
In the L2L config section on the concentrator for the PIX tunnel you would have defined a Local NW of 22.214.171.124 and a Remote NW of 126.96.36.199. You need to add another Local NW in here of 188.8.131.52 so that traffic source from 184.108.40.206 (behind the CP) will be routed over to the PIX.
Similarly in the L2L config section on the concentrator for the CP tunnel you would have defined a Local NW of 220.127.116.11 and a Remote NW of 18.104.22.168. You need to add another Local NW in here of 22.214.171.124.
To add more than one NW you need to create a Network List under Config - Policy Mgmt - Traffic Mgmt - NW List, then use those lists in the specific L2L config section for each tunnel.
You also need to modify the access-list on the PIX to include traffic FROM 126.96.36.199 TO 188.8.131.52 as IPsec traffic, and do a similar thing on the CP.
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...