An ASA can only have one default route. Also it does not do policy-based routing. For that reason we can very seldom connect a given ASA to two routers and have it dynamically steer some flows to one and others to another. When we have a second ISP (and no router we control upstream), we typically use an ip sla operation with a route that tracks the success of that operation to decide if/when to flip all traffic to the second route.
How does your guest traffic know to take the comcast route outbound?
the comcast network is attached as a backup route in case verizon goes down. I'm doing sla tracking.
the comcast connection to the ASA is 18.104.22.168 on a /28 network (not the real address)
My guest network is a separate router attached to the same subnet as my comcast interface.
the guest router is attached to 22.214.171.124 (outside the ASA) and uses the default router of 126.96.36.199
the problem is, when users try to attach to OWA or CAS. using the named address to my ASA of 188.8.131.52, they route out through comcast's network, back into verizon's; but because they are presenting themselves as 184.108.40.206, the ASA sees that as a connected subnet and gives me a reverse verify path failure.
if I traceroute from 220.127.116.11 to 18.104.22.168, it's following the proper routes. it goes all the way out comcast's network to the backbone of verizon, then back in.
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...