To achieve this, the ASA Outside (e0) interface need to be connected to a switch with dot1Q encap.
Create 2 sub-interfaces (need IPs from each T1's ISP) under Outside interface to host connection from 2 different links.
Next, you need a switch (put before ASA) to host 2 VLANs that will be used to connect those T1 links. Example - Vlan 10 & Vlan 20. Set the switchport connected to ASA Outside interface as trunk with dot1Q encap, and allow those 2 vlans to pass through.
For the existing T1, connect the RJ45 to the switch, and make sure the switch port belongs to one of those VLANs, example VLAN10.
For your new T1 link, connect the RJ45 to the switchport belongs to VLAN20.
Is there really a need to create sub-interfaces on the ASA? How about connecting the ASA to a L3 switch as the next hop and to let the switch take care of routing the traffic according to a configured policy-based routing?
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...