As you ruled out BGP, you can use two static default routes (equal admin distance). This will load balance by default on a per-destination basis. If you want you can change it to per packet but that increases load on the CPU.
1. Static will only balance outbound traffic, not inbound. Even if you went with BGP you couldn't be guaranteed to load balance inbound, you can only increase your chances with playing with attributes like AS path. But the final decision is up to your providers on how traffic will enter your site (ie despite your as-path prepend they can force traffic one way or the other).
2. Depends. Generally, per destination is the way to go but if all your traffic goes to one site, it doesn't help. It's good if you have different sites that you go to. Per packet increases the load on CPU but has higher load balancing percentages.
To load balance out you can use static routes, to load balance in you can get a product that deals with DNS load balancing.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...